The desktop application works offline (do all the job locally without ever connecting to a server). And the business code can work with or without a database. So AIR may not be the choice as I'm not so confident to compile the business code into Javascript (AIR).
>>You could write your backend in java exposing services through requestfactory and consume them from the gwt and swing frontend Does your suggestion still applies? The desktop application should be easy to install and do not need to configure any servers locally. I'm relative now to Java, so I'd be really grateful if you could elaborate. >>Anyway, can't the desktop users simply use the gwt app? What limitations do it have? -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/oZYXcdzTkAAJ. 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.
