> I known nothing aboutpyjamas, but I'm intrigued about what lkcl has > been discussing. What he has done (and is suggesting could be done with > GWT) is to have a browser-based application (via a Java->Javascript > translater like GWT) and a desktop application (via a direct Java > runtime) derived from the *same* codebase.
yep. > Why bother, you ask? * webkit is big, but so are full web browsers. despite being big, webkit is _still_ ported to ARM embedded platforms - and used on Android for example. * webkit is _fast_. * you've cut out the javascript (not entirely) from the equation, thus simplified the development process and speeded up execution. > For your mobile or infrequent users, perhaps a > browser-based solution is preferable. At the same time, people who sit > in front of a stationary desktop system may prefer the look and feel of > a desktop application. With thepyjamasapproach, you can satisfy both > constituents with a single set of code. yep :) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
