On Tue, Mar 8, 2011 at 1:08 PM, Casper Bang <[email protected]> wrote:
> > - Trying to pinpoint Java elements. For example, any occurrence of a > > method, class, or package name in an XML file is a bad sign. You > should be > > using annotations for that. > > Interestingly, you make no mentioning of XML as a layout mechanism. > Having worked on Android with Romain Guy (a stark defender of XML > layout) can I infer you are of the same opinion? Indeed I am. > I am kind of torn > personally, given that I love type-safety and the fact that I can > explore an API, and get full type-safety, with any IDE (rather than > trying to guess magic string content like vertical, wrap_content, > fill_parent etc). I hear you. I have waffled for quite a bit myself about these issues, and I'm not saying I won't change my mind again, but at the moment, I stand more on the side of the fence that says that having some support for declarative layouts is a net benefit. In particular, I am feeling the pain of not having this in my Eclipse plug-in (SWT) development. Java code is just not very well suited to represent nesting of containers (interestingly, Eclipse 4 will offer declarative SWT layouts). > It doesn't really seem like it has benefited > tooling, the WYSIWYG editor is still quite useless (and now seems to > be completely replaced by App Inventor). > I'm not sure that App Inventor is supposed to replace the Eclipse layout editor, these two tools seem to be aimed at different audiences. The good news about that is that it's really a matter of tool maturity. Nothing technically prevents the layout editor from becoming a very solid tool with all the validations that you currently wish it had. -- Cédric -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
