Note that there are some explanatory texts on larger screens.

plurals
  1. POWhat's the right choice? Create new Activities or just create a different Layout and replace the existing layout?
    primarykey
    data
    text
    <p>Since I am new to Android, I am now thinking on what is the correct way of doing things.</p> <p>As it stands, the application Im writing has 4 different screens:</p> <ul> <li>Screen 1 - list of nodes (main screen)</li> <li>Screen 2 - options menu, tableLayout with buttons</li> <li>Screen 3 - navigation</li> <li>Screen 4 - text details on version etc</li> </ul> <p>These screens can be navigated to/from using a "header" View that is placed on top. The header then has 4 different buttons:</p> <pre><code>+--------------------+ | menu with buttons | +--------------------+ | | | | | | | C O N T E N T | | | | | | | +--------------------+ </code></pre> <p><b>main.xml</b> is really just a LinearLayout that INCLUDES the header.xml and then the content, in that case the list of nodes in a ListView</p> <p><b>options.xml</b> is the same thing almost, it includes the headerxml and then a bunch of buttons...</p> <p>...and so on with the two other screens.</p> <p>So, when I press one of the buttons in the header/menu on top the content should be switched to that screen. <b>My question is:</b></p> <ul> <li><p>Should I create one Activity for each screen? I read on Google that:<br> <i>An activity presents a visual user interface for one focused endeavor the user can undertake.</i><br> So that can be interpretet that I shoukd use one Activity for each of these screens.</p></li> <li><p>Should I <b>not</b> create more Activities than the startup, and then just run the <i>setContentView(R.layout.whatever)</i> when I want to change the "content" above?</p></li> </ul> <p>Regards</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload