>> far easier than web dev > > Nope. It is easier, because you just need to code and are absolutely free in refactoring. No need to mess with XML or HTML files, too. No need to use reflection. BTW, Wicket is the only web-application framework, I've found which feels quite similar easily. Others are a nightmare - just like Eclipse RCP is.
> I can spot a Swing UI a mile away. Usually ugly, and doesn't mesh > correctly with established GUI standards on platforms. Maybe you can spot a *bad* Swing UI a mile away. Please take a look at JFormDesigner, JGoodies tools or even - shame on me - our SmartSVN. >> runs much faster than a webapp (but everybody knows than >> > desktop are faster than networks), etc... > > But first you have to locally install the application, ensure you have > a compatible JRE, fix your classpath if you have multiple JRE's > installed. On Windows, a good Java application comes (at least optionally) with its own JRE, on Mac it is already installed - even on decent Linux versions it is installed. If someone is changing its systemwide classpath, (s)he deserves any problems. One major advantage of Java applications is, that you usually can move it around (from one location to another at the same machine, or even on a different machine), you don't need to *install* it. > Next you often don't have working copy/paste between > native applications and swing apps, Copy/pasting text is supported since ages. Copy/pasting non-text requires coding like in native applications, too. > are the swing apps slow 10 years ago you were right. > don't > support drag'n drop between the OS and the swing application, etc. Depends on the application. Of course, it needs extra coding, just like for native applications, too. > I tend to like native apps much better than Java apps. For me it is the opposite, because I often have to work with multiple operating systems and there are only very few native applications on different operating systems. > And in several > cases, I like web apps even more than respective native GUI apps > (gmail, bug trackers, viewvc, etc). This is right for applications which require no serious user or file system interaction or which inherently operate remotely - like those you've mentioned. For any other application (file manager, IDE, decent e-mail client, office-style application) *I* never would use a web-application judging by the ones I already saw or tried. But that's just *me* opinion. -- Best regards, Thomas Singer _____________ syntevo GmbH http://www.syntevo.com Martijn Dashorst wrote: > On Wed, Jan 28, 2009 at 2:39 PM, Piller Sébastien <[email protected]> wrote: >> far easier than web dev > > Nope. > >> almost no compatibility issue between jre versions > > With Wicket you don't even have any compatibility issues *AT ALL*. > >> looks pretty nice (builtin selectable "look and feel", etc.) > > I can spot a Swing UI a mile away. Usually ugly, and doesn't mesh > correctly with established GUI standards on platforms. > >> runs much faster than a webapp (but everybody knows than >> desktop are faster than networks), etc... > > But first you have to locally install the application, ensure you have > a compatible JRE, fix your classpath if you have multiple JRE's > installed. Next you often don't have working copy/paste between > native applications and swing apps, are the swing apps slow, don't > support drag'n drop between the OS and the swing application, etc. > > I tend to like native apps much better than Java apps. And in several > cases, I like web apps even more than respective native GUI apps > (gmail, bug trackers, viewvc, etc). > > Martijn > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
