App Template for iOS 7
Posted: Mon Dec 09, 2013 12:42 am
Dear LiveCoders,
I wanted to share an app template
which is made by me -and colleagues- to mimic some iOS 7 behaviors
but it doesn't rely upon strict api's
so it should work on iOS 6 or Android, even on desktop.
Main features:
* The bottom navBar is now at the right-hand side of the screen, user have to slide from right to left to reveal it.
It's a useful approach to overcome the limitations of a handheld device's restricted screen-estate.
You have more field for the main screen and you have more field -even more by scrolling- for the menu.
* The user can go back to previous pages by sliding from left to right.
During the transition, the header bar or topBar changes with changing-transparency effects.
To accomplish this, we had to use a "One Card - Several Groups for Pages" approach.
Because LiveCode can't show different cards or substacks at the same time on mobile.
You should put your content into the relevant group.
* It has a simple scaling algorithm to support different screen sizes.
It's tested on all i-Devices but not on Android.
It doesn't use the resolutionIndependence of 6.5, btw.
Please check the stack script for the scaling code.
* App can keep history of previous pages between multiple run-times.
When you close the app, it records the active page and the previous pages then at the next run it remembers them.
* It shows also a simple approach for installing and content-updating issues.
For this and more, don't forget to check the library stack.
Known Issues:
* The stack's poorly commented, sorry for that.
But thanks to the LiveCode's english-like scripting style, you wouldn't have much problem for understanding the code.
Feel free to ask anything related to it.
* To test it on a physical device, you have to update the provisioning profiles.
* Back button doesn't work and pages change without any transition effects;
I didn't implement these to keep the code as simple as possible.
Since, this is just a template.
* On physical devices, screen transitions have a noticeable lag around 200 ~ 300 milliseconds.
We couldn't come up with an acceptable solution for that, unfortunately.
Hope it helps to some of you, at least to some degree.
Best,
~ Ender Nafi
I wanted to share an app template
which is made by me -and colleagues- to mimic some iOS 7 behaviors
but it doesn't rely upon strict api's
so it should work on iOS 6 or Android, even on desktop.
Main features:
* The bottom navBar is now at the right-hand side of the screen, user have to slide from right to left to reveal it.
It's a useful approach to overcome the limitations of a handheld device's restricted screen-estate.
You have more field for the main screen and you have more field -even more by scrolling- for the menu.
* The user can go back to previous pages by sliding from left to right.
During the transition, the header bar or topBar changes with changing-transparency effects.
To accomplish this, we had to use a "One Card - Several Groups for Pages" approach.
Because LiveCode can't show different cards or substacks at the same time on mobile.
You should put your content into the relevant group.
* It has a simple scaling algorithm to support different screen sizes.
It's tested on all i-Devices but not on Android.
It doesn't use the resolutionIndependence of 6.5, btw.
Please check the stack script for the scaling code.
* App can keep history of previous pages between multiple run-times.
When you close the app, it records the active page and the previous pages then at the next run it remembers them.
* It shows also a simple approach for installing and content-updating issues.
For this and more, don't forget to check the library stack.
Known Issues:
* The stack's poorly commented, sorry for that.
But thanks to the LiveCode's english-like scripting style, you wouldn't have much problem for understanding the code.
Feel free to ask anything related to it.
* To test it on a physical device, you have to update the provisioning profiles.
* Back button doesn't work and pages change without any transition effects;
I didn't implement these to keep the code as simple as possible.
Since, this is just a template.
* On physical devices, screen transitions have a noticeable lag around 200 ~ 300 milliseconds.
We couldn't come up with an acceptable solution for that, unfortunately.
Hope it helps to some of you, at least to some degree.
Best,
~ Ender Nafi