I'm looking forward to declaring UI elements in Python because Python is much more flexible and concise  than XML. For instance, if you look at the detail view's parcel.xml today, you see a lot of the same structures (like "an area containing a label and an attribute editor") and constants (like the borders around various blocks).

The thing I hate most about parcel.xml is that there's no way for me to represent or encapsulate this repetiton; the new proposal suffers from the same problem. Declaring things in Python will let me parameterize generation of these elements. (Getting names of blocks right is trivial, but getting things to align consistently, given native-control weirdness across platforms, has consumed inordinately-huge amounts of my time.)

...Bryan

Alec Flett wrote:
I feel like folks are leaning towards pje's python .update mechanism as the GUT of item declaration.. and I think that's a mistake and I think its because people feel burned by parcel.xml. Its the underlying API sure, but if we never HAD parcel.xml, I can guarantee you that I wouldn't be the first one to say ".update() is really tedious for the UI - lets find a simpler way to declare this stuff.. what about xml?"


_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev

Reply via email to