Re: [Ldsoss] Non-Web Application Frameworks

2006-11-02 Thread Jay Askren
There are still many advantages to client apps. Even though the internet has boomed, not everyone has access to the internet every minute of the day and if I have my laptop with me, I would like to be able to use some applications even though I might not have access to the internet. Sure, I could

Re: [Ldsoss] Non-Web Application Frameworks

2006-11-02 Thread Paul Penrod
I'd like to take your premise one step further. For years in the Unix, IBM, DEC and many other frame environments, network connections and the subsequent protocol and remote applications (such as Web, Gopher, FTP, etc.) were treated as resources and not requirements in many instances. I

RE: [Ldsoss] Non-Web Application Frameworks

2006-11-02 Thread Steven H. McCown
Has anyone ever noticed that this list tends to concentrate on hashing and re-hashing which OSS tools are best? Then, the discussion moves to whether client-server, webapps, or standalone apps are best. Next, we always jump on to (my favorite) legal issues. Goto line 1 and repeat... I'd like

Re: [Ldsoss] Non-Web Application Frameworks

2006-11-02 Thread Jay Askren
Paul, I agree with you 100%. That's exactly the model I'm using on my application and that's really what I was trying to say. I don't know that I would call it a limux model since lots of applications use it. I should also say to that I'm not arguing against web application, for Mitch's

Re: [Ldsoss] Non-Web Application Frameworks

2006-11-01 Thread Tom Welch
I've used Swing and SWT. I've found that Swing is much easier to work with .. especially if you are going to move from one platform to another. The learning curve is a little steep if you want to do a lot of customizing of the UI but it does give you a lot of control over what you want to

Re: [Ldsoss] Non-Web Application Frameworks

2006-11-01 Thread m h
I should've mentioned in my post, I've also used swing and swt (jface too) (as well as vb, qt and some pygtk). If you are wed to java, use either of swing or swt. There are pluses and minuses to each, which others have mentioned. I would still recommend wx. -matt ps - The main dev of

Re: [Ldsoss] Non-Web Application Frameworks

2006-11-01 Thread Mary Shaw
Have you fully considered the advisability of writing the application as a client app as opposed to a web-based app? I've taken a few such full-blown applications and turned them into web-based apps. As time goes on, I (and my bosses)find more more reasons to develop new applications as web-based

Re: [Ldsoss] Non-Web Application Frameworks

2006-11-01 Thread Jesse Stay
I completely agree on this. With the advent of AJAX and javascript libraries and frameworks, it has become very easy, and perhaps more powerful to create client apps on the web (I now consider the web just a method to deploy interactive client applications). Jesse On Nov 1, 2006, at 2:37

Re: [Ldsoss] Non-Web Application Frameworks

2006-10-31 Thread Jay Askren
At work, I'm using the Eclipse RCP, and unfortunately, not only is it a huge learning curve, but good up to date documentation is somewhat scarce. For a small app, it's much easier to just write it in Swing. In addition to the ones you mentioned, I believe Netbeans also has an RCP framework,

Re: [Ldsoss] Non-Web Application Frameworks

2006-10-31 Thread John Harrison
Swing has its faults but it is very well documented. The java docs are about as good as you can find, and there are lots of tutorials. If you really hate Swing you might want to look at SWT. On 10/31/06, Jay Askren [EMAIL PROTECTED] wrote: At work, I'm using the Eclipse RCP, and