I'm partly humoured partly intrigued. How would this GWT have access to the File System and other such resources, since by definition javascript can't do any of that kind of thing. What if it wants to do other cool things on your system?
I've never been a fan of building bad desktop clients, which without wanting to start a flame war, J2SE is very good at. You get cross- platform but the worst of all worlds. I speak from experience, and perhaps ignorance as well, but I feel like doing a good desktop client really _requires_ you to use the technology on that platform that can take advantage of everything the OS has to offer. For Example Objective-C + Cocoa on OS X, .NET in windows, and whatever those crazy linux hippies build their UIs in these days (C++?) But maybe I'm just not enough of a visionary ;) On Oct 27, 7:35 pm, Thomas Broyer <[EMAIL PROTECTED]> wrote: > > 2008/10/27 Guy Rouillier <[EMAIL PROTECTED]> > > > > Ross, you are thinking too narrowly. Think of a single code base. When > > > it runs on the desktop, it has access to local file system and other OS > > > facilities. When it runs in a browser like GWT does today, it degrades > > > nicely and only loses minimal functionality. Write once, run anywhere. > > You can already do it at no cost (i.e. no need to rewrite GWT in pure > Java) with Adobe AIR or Mozilla Prism. > > On 27 oct, 03:51, "Ian Bambury" <[EMAIL PROTECTED]> wrote: > > > If you gave a practical example it might help people understand the benefits > > We're building an ECM client with GWT, and packaging it within Adobe > AIR gives us added features or enhanced user experience: > - drop a file from your desktop into the app to upload it to the > server (you'll have to wait for Yahoo! BrowserPlus to be unlocked if > you want to do it within the browser) > - click the "add document" link and, instead of the GWT DialogBox > containing a FileUpload that's used when running within a browser, the > app directly pops the file selection dialog, where you even can select > multiple files for upload in one go (yes, I know, this could be done > in any browser with a Flash object) > > For an application storing only personal data (i.e. nothing shared > with other users or coming from/sent to the network), you could make > it to run entirely client-side. This is already doable with Gears or a > recent Safari/WebKit, bringing your online application off line (see > Buxfer for instance), but only if you only need an SQL databse. With > file-system access, you could store data within files (XML, JSON, > "binary") and/or export your data into local files (images, PDFs, > etc.) without having to send them to the server that would echo them > for your browser to pop the download dialog box (this last part, again > could be done with some Flash in a browser I guess) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
