A (175)

244 CHAPTER 7: Making Apps Interactive: Intents, Event Handling, and Menus

You can add this either before or after the MainActivity definition, as you can see in
Figure 7-28. Notice that we are using the MenuItem label to label the top of this Activity
subclass screen, so that users will know that it is the “Edit Galaxy Info” screen. If you want the
application name (brand) on the top of the screen, you would simply leave the app_name
constant reference; that is entirely your call.

You could also use the short-form tag style, since there are no child tags inside of the
parent tag, such as an child tag, and thus, you could write this tag using the
following XML markup:

<activity android:name="absolute.beginners.hellouniverse.EditGalaxy"
android:label="@string/edit_galaxy" />

Now let’s get back to adding the bottom half of our EditGalaxy UI design, which is not going to go
quite as smoothly as you think that it might, and so we will have an opportunity to learn even more
RelativeLayout alignment parameters which can be utilized to make your UI design absolutely perfect!

Finishing Up the RelativeLayout UI Design

Create your third set of and UI elements by copying and pasting your second
set of and UI elements and change edit_pop to edit_fleet for the UI
widget and submit_pop to submit_fleet for the UI widget, as shown in Figure 7-29. Leave
your android:text reference for the set to ok_button and the android:layout_alignLeft
reference for the set to @+id/edit_colony, so that all of the EditText UI widgets will align
with the first EditText UI widget.

Figure 7-28. Adding the child tag for the EditGalaxy class, and an Edit Galaxy Info reference