> But why reinvent the wheel in JSON when there is already an XML description?
To be honest I haven't dug into the Android XML definitions very much because it locks me into only Android and requires the slightly more verbose XML syntax. If I develop a custom JSON syntax that facilitates common UI widgets (button, textfield, dropdown, etc), then I just need to write the custom implementation per platform. This also allows me to insulate myself from the "I changed it for the sake of changing it" Google developers that don't always have their sights set on keeping things consistent for us "consumers" - though the same could happen with my API usage approach (i.e. the API parms could change just as much as the XML structure and subsequently require me to change my code just as much). I guess at the end of the day I am somewhat just testing the waters to see what I can create and then hopefully submit something back to the community to use. Aaron Bartell http://mowyourlawn.com http://mowyourlawn.com/blog/ On Mon, Oct 4, 2010 at 3:52 PM, Jeffrey Kesselman <[email protected]> wrote: > Not to my knwoledge... > > But why reinvent the wheel in JSON when there is already an XML description? > -- You received this message because you are subscribed to the Google Groups "Android Discuss" 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/android-discuss?hl=en.
