StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POHelp required with layout - not sure which is the best to use
primarykey
Id
5181779
data
AcceptedAnswerId
5185632
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-03-03T14:08:35.313
FavoriteCount
0
LastActivityDate
2011-03-03T19:40:17.567
LastEditDate
LastEditorUserId
0
OwnerUserId
643105
ParentId
0
PostTypeId
1
Score
0
ViewCount
22
LastEditorDisplayName
text
Body
I am new to Android development and having gone through the tutorial resources at developer.android.com, I'm still not clear which layouts are most useful in different circumstances. To give a specific example, I would like to be able to replicate the UI from the Ebay application i.e a menu bar at the top and bottom of the screen and a panel in the middle. The bottom toolbar has buttons of equal size even when the length of the text differs. I thought about implementing using a TableLayout with three rows, the top and bottom row containing the toolbars. Then for the bottom row I added a Linear Layout and added Buttons. However my buttons are not of equal size and I'm also not sure that this is the best way to layout this UI configuration. Can somebody provide the XML to achive this. Thanks
Tags
<xml><eclipse><android-layout>
Title
Help required with layout - not sure which is the best to use
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USfujih
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.