On Jul 6, 8:21 pm, "Muthu Ramadoss" <[EMAIL PROTECTED]> wrote: > So if a GWT + Gears web application can > magically target many different clients (WebBrowser + MobileBrowser) etc., > then that would be the killer framework in my opinion. A few quick thoughts as they come to mind... The bottom line to GWT is that it is just generating JavaScrip code. It has no particular advantage in mobile that I can see. Having said that, it really is overlooked by the industry picks as a veritable tool. I've developed a GWT-based product last year for a pretty serious client. As advertised, GWT provides leverage over blank metal JavaScript implementation, and with Eclipse integration it is an awesome tool overall. I couldn't do with JavaScript what I can in the way I can with GWT and wouldn't even bother to try. You still have to be able to go down to the blank metal occasionally, but that's at the fringes of ActiveX control integration (VLC comes to mind), if that's a scenario for mobile to begin with. If your browser executes JavaScript and you can do without ActiveX, flash and other complications, you're (almost) good to go. The down side is you still have to get your JavaScript code over the air. If you can keep things slim and keep it nicely cached once loaded, it's not a bad approach, assuming you're careful with your airtime at runtime, where JSON (over RPC) should be a very efficient way to connect to the back end over the air. When building the UI, you still have to consider small screen (mobile) vs. desktop. Also there is no thread model in JavaScript so you have to make do with timers. The biggest issue which I don't know how to cover is multi-touch. A dedicated client (like an Android app could). can cover this prominent use case, assuming the Android SDK has been extended... over which Google has full control... as opposed to JavaScript.
>From what I've superficially seen, Gears has an achilles heel in the Data Switch. This concept will IMHO not work for non-trivial apps, or, over the problem space of any given app, it basically means Data Switch has to be able to solve NP-complete problems syncing data stores of complexity when connected, without interfering with other apps in such a way that the user experience suffers, to allow deterministic execution of your app. (on second thought, let me rephrase, to arrive at a valid solution to your problem). I am generalizing but the playing field looks pretty ugly. We will see if I'm proven wrong, maybe the laws of computability have changed or I'm getting senile. Whatever that case, I won't be in line to try to build a web app using Data Switch. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" 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-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
