I suppose that can answer the question : - AWT uses OS lib for drawing. Android is mostly Java. Of course there should be some C lib for drawing on the screen somewhere...
- AWT, Swing and other are for desktop. Mobile devices UI are a lot differents : one app at a time uses the full screen, no resizing - AWT is by default not nice. I support Google wanted a nice Look and Feel for all their devices. - Event management on a PC and a small mobile device is different : more interrupt (call, SMS, battery, no mouse...) - AWT is only used for drawing. Google needed to create a whole Desktop (menus, virtual screens). So they needed to write a lot of code anyway. But : I agree : it may be boring to rewrite the same app again and again (C, .NET, Java/Swing, iPhone, Andorid, Symbian, etc). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "android-framework" 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-framework?hl=en -~----------~----~----~----~------~----~------~--~---
