Hi, OK, it's one thing to tell me that _any_ GWT app could run as a desktop app. I can accept that that might very well be possible.
In the same way, you can turn any pencil into a pendant by hanging it round your neck on a piece of string. What I was hoping for was some indication and/or example of why it would be desirable. I write web sites when I want people to be able to use my app casually or when the data needs to be held remotely (size, ever-changing data etc) I write desktop apps when I have to because I need to use the local file system plus or minus the web, or when I need to eliminate the lag of the net or I need my users to be able to work in a lead-lined box or on the train in tunnels that haven't yet been fitted with an internet link (in the UK, we are starting to see train tunnels with internet links now). So why would would I need both? Ian http://examples.roughian.com 2008/10/28 lkcl <[EMAIL PROTECTED]> > > > > On Oct 27, 2:51 am, "Ian Bambury" <[EMAIL PROTECTED]> wrote: > > If you gave a practical example it might help people understand the > benefits > > ian, hi, i do know what you mean. > > however, it is quite hard to give a practical example when what > you're talking about is that the entire GWT application - unmodified > - /unmodified/ - could run as a desktop app, if a GWT-Desktop library > existed. > > :) > > so - it actually doesn't matter what example you pick. the principle > is: _any_ GWT application would also run under GWT-Desktop. just as > java, not javascript. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
