-
Welcome to B4X forum!
B4X is a set of simple and powerful cross platform RAD tools:
- B4A (free) - Android development
- B4J (free) - Desktop and Server development
- B4i - iOS development
- B4R (free) - Arduino, ESP8266 and ESP32 development
Best practice: Multiple Screens (not different layouts)
- Thread starter KMatle
- Start date
- Similar Threads Similar Threads
The 'standard' way Android is designed for is one screen equals one activity.
It's easier to work with several activities rather than with several panels.
If you chnage the rotation the OS displays the current activity, it's up to you manage which panel is the current one.
When I began with Android I worked like with Windows one screen one form or panel in Android then I switched to the Android 'standard' way.
Currently I'm developping an applcation which is intended, for the moment, for tablets only and here I change my mind and I work again with panels but half screen panels.
Best regards.
It's easier to work with several activities rather than with several panels.
If you chnage the rotation the OS displays the current activity, it's up to you manage which panel is the current one.
When I began with Android I worked like with Windows one screen one form or panel in Android then I switched to the Android 'standard' way.
Currently I'm developping an applcation which is intended, for the moment, for tablets only and here I change my mind and I work again with panels but half screen panels.
Best regards.
Upvote
0
This is a good question, i am currently creating an app for Navigation (ships).
The main activity layout with all the buttons and global information is loaded, and then depending on the type of information the operator wants to display i have different layouts loaded into a panel (that take up about 66% of the screen area).
This way the globall info is always there and the user selected items is displayed within the panel (these panels display, positional info, engine and shaf RPM, Thruster Info and also things like doors that are open or closed for safety).
I wasn't sure if this was best practice but it just seemed logical to me and works well.
Not sure i answered your question, i just think sometimes one way works better than another.
Regards
Stu
The main activity layout with all the buttons and global information is loaded, and then depending on the type of information the operator wants to display i have different layouts loaded into a panel (that take up about 66% of the screen area).
This way the globall info is always there and the user selected items is displayed within the panel (these panels display, positional info, engine and shaf RPM, Thruster Info and also things like doors that are open or closed for safety).
I wasn't sure if this was best practice but it just seemed logical to me and works well.
Not sure i answered your question, i just think sometimes one way works better than another.
Regards
Stu
Upvote
0
@Theera: Yep 
That was on my mind, too.
@Klaus: For my first steps it's easier to handle several layouts/panels because I only need "more space" for devices with small screens. I will try the "activity thing" a bit later. I do think this is good for more complex APP's.
By the way: I've published my first APP in Google Play :sign0060:
https://play.google.com/store/apps/details?id=de.matle.HypoR&hl=de
That was on my mind, too.@Klaus: For my first steps it's easier to handle several layouts/panels because I only need "more space" for devices with small screens. I will try the "activity thing" a bit later. I do think this is good for more complex APP's.
By the way: I've published my first APP in Google Play :sign0060:
https://play.google.com/store/apps/details?id=de.matle.HypoR&hl=de
Upvote
0