I was thinking about this. Making some sort of a web ui project that would read the ui stuff from the xml and build it for the browser. Something like 'AWTk'. It sounds like a lot of work ;) I mean, a huge, huge pile of work, on a moving target (as the platform is certain to evolve quite a bit).
I'll have to take a look and see what you have, though. What about style definitions for inputs? I wound up doing a much scaled down thing. Remote data calls to the server can 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 screens. On Fri, May 9, 2008 at 8:04 AM, Aleksandras G. <[EMAIL PROTECTED]> wrote: > > Hello all, > > my apologies for misplaced announcement, but i though it > would make sense - while waiting for real Android-phones to arrive: > > one can already start porting and distributing their > Android app as standalone Linux/Windows desktop app, > or even as web app (using standard Android APIs+xml, no code mods.) > > > http://code.google.com/p/drine/ > > I'm letting you know about Dr.i.n.e project - Drine Is Not An Emulator > > The above project page contains source code (Apache 2.0 license), > sample code and demos, some screenshots, design docs (incomplete) > > brief outline of Android features currently supported by Drine lib: > > * loading resources from Xml: > UI-layouts, drawables, NinePatchDrawbles, strings, raw > > * supported layouts: > linearlayout, table row, tablelayout > > > * Activity, Dialog, WebView, canvas, fonts, sqlite-db/cursors, view > hierarchy handling, events, focus, bitmaps, > input controls, etc etc (there's long list of what's already > supported, but the yet > much much longer is the "unsupported" list android of APIs. More > details in the docs) > > * UI-bridges: Drine-SWT for Windows/Linux (uses IBM's SWT), AWTk - for > the web (i nicked it "AWTk - Android Web Toolkit"), > features Android Activities servlet which executes activity in any > J2EE servlet-container, talks to ATWk's javascript > code on the browser which renders Android's UI and graphics in > DHMTL, dispatches UI/App-events back and forth via ajax > > * (A good way check if Drine is useful for you, is to try and compile > your own ADC entry app against Drine's classes, and see how far can > it go. > Complete list of supported classes you can find here: ) > > I was also quite frustrated with "19%... ADB hang-ups" in Eclipse > (happens in 1 out of 4-7runs), > it was bad enough for me (taking away way too much time from > developing > my own adc entry - R2GR), so I started this Android API emulation > project to > save time and frustration i was having. It turned out to be a big > undertaking, but it was fun and saved me tons of time as April 14th > was approaching… > (my app starts up in less then 1second via Drine libs, debugging is > painless > and fast, etc) > > May be some developers will find it useful, > particularly in the context of "What to do with my app after Android > Challenge I ?" > > The project is still in alpha, im hoping some of you will find > it useful, try it, and may be even contribute to it, e.g. i imagine > someone > could come and contribute a UI-bridge for Drine to use pure Android's > APIs on > some "other" phones, e.g. on Nokia tablet N810 > > > sorry for being not quite on topic, if you have questions, > please post them here, i'll try my best to answer > > Aleksandras > (let us hope there's still a lot of life and coding after > ADC... :) > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
