StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POScaling a simple UI with relative dimensions defined
primarykey
Id
9660530
data
AcceptedAnswerId
9832623
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-03-12T00:59:41.887
FavoriteCount
0
LastActivityDate
2012-05-19T08:25:20.207
LastEditDate
2012-03-12T01:06:28.077
LastEditorUserId
1248859
OwnerUserId
1248859
ParentId
0
PostTypeId
1
Score
2
ViewCount
1512
LastEditorDisplayName
text
Body
What I have is a drawing of a UI layout, that I want to be able to scale up and down to fill an android screen. I know this doesn't really fit with the android UI "way" I've been reading about, but this is a very simple app for connection to an appliance - it has a couple of basic setting buttons, and a couple of realtime information display views. In this case, the UI elements all need dimensions that are known relative to the total width and height. I've had a play with doing a layout using a combination of linear and relative layout tags in XML, and given a fixed emulator screen setting, I can make an arrangement of interface elements with explicitly set sizes that fill it up the way I want... Of course this doesn't work when I try it on different screen sizes. So my next step is going to be to add code to calculate the size of each element just before the activity is first created - then override the xml values I use to do the original layout. I don't mind doing this, but am a bit worried that it means the UI design will be defined in multiple places, and this isn't really ideal. As I'm trying this, I'd really love to hear from more experienced developers if there's going to be a problem i haven't considered, and I'd be better off stopping any attempt to work with standard UI system Views and layouts, and jump straight to the 2D graphics library, or if there is a "nicer" way of setting relative sizes for objects in an XML layout related to device screen size that I've missed, despite my searching? thanks!
Tags
<android><android-layout><user-interface>
Title
Scaling a simple UI with relative dimensions defined
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USJulian Higginson
UserOwnerUserId
1. USJulian Higginson
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
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POScaling a simple UI with relative dimensions defined
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.