On Wed, Aug 8, 2012 at 12:02 PM, Guntupalli Karunakar <karuna...@indlinux.org> wrote:
> Mobile OS or mobile interfaces, which I guess includes Android, > Nokia, Samsung etc interfaces. > Probably better to list the mobile models from which the entries are > taken from. The initial FUEL effort was based on the Linux operating system and the applications therein. A primary advantage that the effort implicitly had was the availability of the source code (including translatable entities) should one was required to revisit and understand the context of the standardization. The specific reason I am eager to understand the extension of the FUEL process/method to the mobile workspace is that I see the target base platform being "closed". For example, Android ICS may have the source code available, but not the translatable entities. In addition to that, the current form of the mobile platform has taken a radical shift forward from "menu driven" (which was the staple of Nokia and Palm) to "activity driven" (via applications). The application developers use the SDK provided by the platform (Android, Bada and iOS) to ensure that the UI/UX remains consistent. -- sankarshan mukhopadhyay <https://twitter.com/#!/sankarshan> ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ IndLinux-group mailing list IndLinux-group@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/indlinux-group
