>>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. As a said before, I never done that before (using RF from non-gwt clients), but Thomas confirmed that it's possible. Your app will carry the requestfactory-client.jar, I don't think you need any server localy. You will need, of course, configure the app to tell it where the RF server is located >>Anyway, can't the desktop users simply use the gwt app? >What limitations does it have? Well, desktop apps are desktop apps. It's far easier to do things like access filesystem, external devices, etc. If you don't depend on such things, then I think your users will be ok with only the gwt frontend On Wed, Jul 13, 2011 at 5:28 AM, Alain Ekambi <[email protected]>wrote: > If you (or your customer) can afford writing 2 different client for the > same application, then a native desktop client(be it Java, C#, or C++) is > good choice. > As for having your businnes code on the client(desktop). No matter which > language you choose the businnes code will be on the client. So if someone > really really want to crack it he will. > If it s supposed to be the same application running on 2 different > platforms why not simply reuse code instaed of duplicating it ? > > > 2011/7/13 Warren Tang <[email protected]> > >> 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 does it have? >> >> >> On Wednesday, July 13, 2011 5:54:30 AM UTC+8, Magno Machado wrote: >> >>> I never used it before, but afaik requestfactory can be used from non gwt >>> clients >>> >>> You could write your backend in java exposing services through >>> requestfactory and consume them from the gwt and swing frontend >>> >>> Anyway, can't the desktop users simply use the gwt app? >>> >>> On Tue, Jul 12, 2011 at 6:15 PM, Alain Ekambi >>> <[email protected]>wrote: >>> >>>> If you want to turn you GWT applicattion into a desktop application >>>> Adobe AIR is a good option. >>>> Appcelerator Titanium is also a solid but i personally prefer AIR. >>>> >>>> >>>> 2011/7/12 Juan Pablo Gardella <[email protected]> >>>> >>>>> gwt4air perhaps help. >>>>> >>>>> >>>>> 2011/7/12 Warren Tang <[email protected]> >>>>> >>>>>> I need to build an application which has both a web font-end and a >>>>>> desktop front-end. There is a relational database. Lightweight frameworks >>>>>> are preferred. >>>>>> My previous project was done with SmartGWT + GWT + MyBatis. And it is >>>>>> the only java project I've done. >>>>>> Currently my thought is GWT + Spring + MyBatis. I also heard about >>>>>> SpringRoo. But the idea is quite vague for me. So could someone kindly >>>>>> make >>>>>> it clear for me? How can I use GWT + Swing/SwingRoo to support both the >>>>>> web >>>>>> and the desktop client, and reuse the business code? What else do I need? >>>>>> What's their roles? >>>>>> >>>>>> -- >>>>>> 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/-/**HF43CGyLvqQJ<https://groups.google.com/d/msg/google-web-toolkit/-/HF43CGyLvqQJ> >>>>>> . >>>>>> To post to this group, send email to [email protected]. >>>>>> To unsubscribe from this group, send email to google-web-tool...@** >>>>>> googlegroups.com. >>>>>> >>>>>> For more options, visit this group at http://groups.google.com/** >>>>>> group/google-web-toolkit?hl=en<http://groups.google.com/group/google-web-toolkit?hl=en> >>>>>> **. >>>>>> >>>>> >>>>> -- >>>>> 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 google-web-tool...@** >>>>> googlegroups.com. >>>>> >>>>> For more options, visit this group at http://groups.google.com/** >>>>> group/google-web-toolkit?hl=en<http://groups.google.com/group/google-web-toolkit?hl=en> >>>>> **. >>>>> >>>> >>>> >>>> >>>> -- >>>> >>>> GWT API for non Java based platforms >>>> http://code.google.com/p/**gwt4air/ <http://code.google.com/p/gwt4air/> >>>> http://www.gwt4air.appspot.**com/ <http://www.gwt4air.appspot.com/> >>>> >>>> >>>> -- >>>> 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 google-web-tool...@** >>>> googlegroups.com. >>>> >>>> For more options, visit this group at http://groups.google.com/** >>>> group/google-web-toolkit?hl=en<http://groups.google.com/group/google-web-toolkit?hl=en> >>>> **. >>>> >>> >>> >>> >>> -- >>> Magno Machado Paulo >>> http://blog.magnomachado.com.**br <http://blog.magnomachado.com.br> >>> http://code.google.com/p/**emballo/ <http://code.google.com/p/emballo/> >>> >> -- >> 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/-/aVyn-MDKq4IJ. >> >> 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. >> > > > > -- > > GWT API for non Java based platforms > http://code.google.com/p/gwt4air/ > http://www.gwt4air.appspot.com/ > > > -- > 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. > -- Magno Machado Paulo http://blog.magnomachado.com.br http://code.google.com/p/emballo/ -- 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.
