On Oct 28, 6:17 am, GWBasic <[EMAIL PROTECTED]> wrote:
> The browser and desktop are fundamentally different environments,
pyjamas-desktop shows that that's no longer really the case; it shows
that there are sufficient concepts in the DOM model to map one-for-one
into desktop widget set frameworks; it shows that, certainly when
compared to Qt4 and GTK2, a DOM-model-based widget set is actually
superior, offering better functionality, more functionality, and a
simpler API!
> really deliver is write once, test everywhere. If you want to have
> some way of turning a GWT application into a desktop application; it
> will probably exist at some point.
yes. called GWT-Desktop :)
> (Cough AIR Cough)
that's a javascript-based route. and, ironically, AIR is based on
webkit (just as pyjamas-desktop is based on webkit)
> You will,
> however, need to test your application on every operating system that
> you plan on supporting; and potentially write special cases for
> specific differences in each operating system that you support.
why?
why would that need to be the case?
as Adobe AIR, google chrome, safari, iphone-safari and android shows,
webkit is supported on _tons_ of platforms.
by _staying away_ from desktop-specific APIs (and using
XMLHTTPRequest to do communication, even on loopback 127.0.0.1) your
entire app is OS-independent; the webkit-based runtime is OS-
independent.
as the GWT apps themselves show, it's not in the slightest bit
necessary for the app to be OS-dependent, even when running in
multiple different web browsers.
l.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
