hi again, thanks for the first review Kev. :) Kev Gman wrote: > What about style definitions for inputs?
that's the thing with Dr.i.n.e - for an app to be fully portable, one can use only Android APIs (EditText, ViewGroup, Drawable, etc). So no, no style definitions in XML/java directly, however AWTk application's skin is user-definable (./web_skin/ directory in the source tree). AWTk supports android.graphics.drawableNinePatchDrawable, with this thing one can do a lot of nice web-like stuff using Android APIs-only (you can lots of these NinePaches in screenshots of drine docs) > wound up doing a much scaled down thing. Remote data calls to the server > an be made by way of the same mechanism on browser/ajax and android, so I > would build simple mockups with web pages, then translate them to android with my own ADC entry, i was going similar "scaled-down" route initially, untill i've reallized i am ending up with waay too much code-branching/ duplication (to handle desktop/web ports along with native Android app). But when suddenly ADC-deadline was extended 1.5months... This Dr.in.e. idea accured to me, i had plenty of time so i went for it... yes it's a lot of work (795kb of java + 34kb javascript), and it'a "moving target", but after M5-rc15 - the Android's APIs become rather stable, so Drine has started to reap first benifits for me... but now I very much hope it does so for other developers out here... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Challenge" 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-challenge?hl=en -~----------~----~----~----~------~----~------~--~---
