I'm not sure how you'd automate something like that. We did it the hard way -- define a generic API for manipulating windows and controls, write two backends for it (Swing and GWT) to target at runtime. Nothing automatic, though; just a lot of hard work.
On Feb 22, 6:53 am, Lothar Kimmeringer <[email protected]> wrote: > Hello Thomas, > > Am 22.02.2012 15:47, schrieb Thomas Broyer: > > > > > On Wednesday, February 22, 2012 3:44:42 PM UTC+1, Cerberus wrote: > > > Am 22.02.2012 14:35, schrieb Alain Ekambi: > > > Why do you need a swing app ? Any specific reason? > > > There are specific reasons namely OSI levels 8 and 9: politics and > > religion ;-) > > Seriously: I need to implement an application that should run as > > desktop appli- > > cation and as application in a browser (the desktop-application can't > > run as > > browser-application for some reason). So I need to implement twice or > > find a > > way to get one using the other. > > > This is partly why Adobe AIR and Titanium Desktop (among others) have been > > made. > > And it's the cheapest solution you could find. > > Without going into detail, I'm a bit stuck with the need to convert it > to Swing. The target framework is fixed here. > > Best regards, > > Lothar -- 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.
