Ultimately, you'll want as much of everything as possible resolved at compile-time, which means that even if you were using CSS it'd most probably be resolved at build time into a static structure (like the current XML files)... which means that what you want can be achieved today without changing Android itself or even the development tools: just create a tool that can generate Android layouts from whatever format you like.
In addition, CSS is typically designed to be applied to something, so you wouldn't have CSS in addition to XML, you'd have it on top of XML. Finally, CSS (even without the HTML-specific parts, and even without dynamic stylesheet) is a complex beast. To make things worse, many of the implementations out there have all the HTML-specific behaviors baked in, and typically have real-world legacy browser compatibility added on top of that. That means that adding proper CSS support in official tools is potentially a large and costly task, that shouldn't be considered lightly. JBQ On Fri, Jan 23, 2009 at 10:59 PM, Raja Nagendra Kumar <[email protected]> wrote: > > For Style and Theams defination, CSS is considered to be a better > standard...(as it has seen many revisions and widely used already in > the web areas).. Any reason, why Android using XML approach as opposed > to CSS.. Are there any plans of support of CSS too in future.. > > Regards, > Raja Nagendra Kumar, > C.T.O > www.tejasoft.com > > > -- Jean-Baptiste M. "JBQ" Queru Android Engineer, Google. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" 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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
