What a progress i see! The notorious JBuilder 1.0 used to crash at least
once per hour. Now it crashes only on bad weeks... Good for Inprise. But
i'd rather use good old Visual SlickEdit. No debugger or RAD, but really
covenient environment for any developer.

-=V=-

Olivier fillon wrote:
>
> >JBuilder v3's debugger uses the Sun JDK with the new debugger hooks, so
> >this is not a problem.  Seems to work great with Java3D.
> It does
> >
> >However, I have stopped using JBuilder because
> >there is minor bug in 3.0 that makes it unusable for me.  When an
> >application is run or debugged under JBuilder, the initial directory of
> >the process is random within the classpath (as opposed to always starting
> >at the location of the project file, as happened in JBuilder 2).  So if
> >you intend to read in configuration files relative to the local directory,
> >the system is useless.
>
> You can always set the bootclasspath as a VM argument can't you???
> Never had any such problem but I specify my environment in my VM args.Isn't
> it cleaner this way anyway?
>
> >But I have gotten the impression from
> >this limited usage, that JBuilder 3 is actually less stable than the
> >lastest release of JBuilder 2.
> I would go against this:
> This only time my JB3 crash is when I do a file search for text recursively
> on big amount of files
> JB2 used to crash 3 times a day, JB3 only on some bad weeks...
> Olivier
> Using JB3 everyday, and having no share in Imprise;-)
> In short, if you want to: you can use JBuilder for j3d apps.
>
> ===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
> of the message "signoff JAVA3D-INTEREST".  For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".

===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA3D-INTEREST".  For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".

Reply via email to