Maybe I'll be stoned but... seen a lot of examples but seen none clarifying this:
Talking about the realtionship between classes and layouts... is any layout related with any class? one, more than one, is there no relation at all? layouts are just like "resources" used from the class you prefer or from many of them? layouts may be "embedded" into another layouts for making "complex" UIs? I think an example makes it easy. Let's see we are trying to make a simple application that manages a list of strings associating any string with a color. I'll have an "element" which will be an object containing one string and one color and then, I'll have a list containing elements. When making the UI, let's say you want to have a lists showing the elements and a text field with a button and a color picker (for adding a new element to the list). What's de idea on android? Having a layout for element (showing the color and the string as you want) and another layout for the list (I mean, a ListView containing the layout you generate for showing elements) is the best choice? will you a class for managing everything? or will you have different classes for controlling different layouts? Syrely it's a question no-to-be-here but I don't know where to ask about this. The examples I've found where too simple or too complicated (by now I hope :D). Thanks, Luis. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
