🚀 go-pugleaf

A couple of comments and questions below...

Timothy Stewart wrote:
[snip] 
> I have been able to use the Swing 1.0.1 included, 
> Swing 1.0.2, Swing 1.0.3, Swing 1.1 Beta 4 and switch between them.  I 
> also have noticed no problems switching between JDK versions.
> 
> I have my JDK versions located in c:\java\jdk1.1.6, 
> c:\java\jdk1.2beta.. etc.
> 
> My JBuilder is installed on d:\jbuilder.  I installed my swing into
> d:\jbuilder\lib\swing-1.0.3... d:\jbuilder\lib\swing-1.0.2.. etc.  I 
> don't know
> that this is necessary, that's just where I put them.
> 
> Then, I went into my project properties, Clicked on the 
> [ Libraries... ] button.. clicked on [ New... ], then typed in a 
> description (Swing 1.0.3), then  a classpath 
> (d:\jbuilder\lib\swing-1.0.3\swingall.jar), then okay.  JBuilder
> says, "Building dependency files" for a couple of seconds, then that's 
> it.
> 
> I can then remove the old Swing library from my project and add the 
> new one.
> 
> The JDK's work in a similar manner.

I would expect that with the setup you describe, the JBuilder IDE (i.e.
the GUI designer) will still be using Swing 1.0.1, because that's what's
on your IDEClassPath (check JBuilder.ini in the JBuilder\bin directory).
Can you confirm or deny this?

One way to check it is to put a JTable (or JdbTable) in a JScrollPane.
Swing 1.0.3 will automatically put the table's header in the
scrollpane's header area, but Swing 1.0.1 will not.

Does the behavior in the GUI designer depend on which JDK you've
selected? Does it depend on which Swing lib you've selected?

How did you solve the problem of the JBCL lib including a path to the
Swing 1.0.1 swingall.jar?
 
> I am very impressed with JBuilder 2, in comparison with JBuilder 1.  I 
> had used Symantec's offerings and Microsoft's.  JBuilder was just 
> easier to use, and had more of the features I wanted, although version 
> 1 did have some problems.  I have been running version 2 on a Pentium 
> 166, 128 Mb RAM running 95, a Pentium 233 Laptop with 64 Mb RAM 
> running 95 (my main one for the past few months), and a Pentium II 
> 400, 384 Mb RAM running NT (only for a week or so now).
> 
> All run well, although obviously, the 166 is a bit slower.  My only 
> problem with any bugs is that every couple weeks I get a nasty 
> JBuilder has accessed some memory location xxx or something like this.  
> I have to shutdown and restart. Sorry I can't remember the exact 
> wording of the dialog box.

I agree with the above. In fact, I don't think it's crashed on me so
far. I'm on a Dell Dimension XPS P200s (Pentium MMX 200 MHz) with 64
Mbyte RAM, running NT4 Server. My only problem is that JBuilder consumes
vast amounts of memory. The JBuilder process has reached above 85 Mbyte
virtual memory. Does anyone else have problems with this? Can it be
avoided? Currently, I restart JBuilder when it starts to grow too big.

Regards,
Kjell Rilbe