Re: Development Advice
Chuck Davis <cjgunzel <at> gmail.com>
2009-01-01 21:42:56 GMT
Hey Kevin:
First, yes by "container" I mean the JEE/servlet containers.
My migration from mid-range to pc platforms is a long story with which
I will not bore you at this time. Because of my background, however,
and what I wanted to accomplish with accounting software I was not
looking at something as crude as a browser so I didn't even think
about the "containers" until much later. I just heard Weblogic and
Websphere were expensive so I knew I could not use them -- never heard
about apache until I took up with Linux.
As for Eclipse, I tried to write some Swing classes and for every
JFrame I created it started a new instance of the JVM just to create
that one Component. So I quickly ran out of memory. Eclipse seems to
be developed on windows for windows and we Linux users are second
class citizens as far as I can tell. Perhaps the windows jvm works
differently and that is why Eclipse works better for you??? Just a
guess.
Now, to keep this Netbeans legal, Netbeans has a fabulous swing
applications development environment so I just stick my toe in the
Eclipse department occasionally. There, I got Netbeans in to keep
this legal! :)
Chuck
On Wed, Dec 31, 2008 at 3:05 PM, Kevin Duffey <andjarnic <at> yahoo.com> wrote:
> Hi Chuck,
>
> Good points.. I respect your position and understand why you are doing what
> you are doing. Makes sense. By container do you mean a J2EE container? A
> servlet container? Not quite sure what you mean by that because as long as I
> can remember, prior to J2EE 1.0 coming out there were free J2EE containers
> available, or at the very least servlet containers. I know Jetty and Tomcat
> have been around for as long as I can remember.
>
> I am honestly still confused about the issues with Swing and Eclipse. Are
> you trying to run the Swing application inside the same JVM as the Eclipse
> IDE itself? I've written several Swing apps with Eclipse.. startup times
> were seconds at most and used very little memory. This may be different for
> you if your application is quite large? I solved part of that by utilizing
> my own plugin engine framework that I and another had built a few years
> ago... right before Eclipse RCP was made available... it was a very similar
> design to the Eclipse plugin engine, using extension points, extensions,
> etc... which I think is a great design. The beauty was the initial delay was
> simply loading in the plugin.xml config files.. the rest didnt do anything
> until needed. So startup times with a good 20 or so plugins was still about
> 3 seconds or so, and only the first time.. we employed a bit of a cache
> system as well that checked for differences between plugins and only
> reloaded there config info if there was a difference. The plugin.xml
> extensions were used to build up the menu system, so the main UI that showed
> up was built with no code execution (other than the bit of code to handle
> the menu itself.. but all the menu items, handlers, etc were added via
> plugin.xml's from the various plugins).
>
> This was back in the JDK 1.3 days... with 1.6, it is much faster to start
> up, so I am curious what it is you mean by it being so slow? This is a
> netbeans forum... so perhaps shoot me an email directly, but I imagine this
> would apply to netbeans as well.
>