🚀 go-pugleaf

Try new Swing1.1Beta3 and it will break.  New package names have been used in
the newest version of Swing1.1B3.
Let me know if somebody knows how to install Swing1.1B3 with JB2.

AJ






In article <360953F3.C644F39@ici.net>,
  "Eric J. Schwarzenbach" <ejs@ici.net> wrote:
> Eric J. Schwarzenbach wrote:
> > I just installed swing 1.1beta2 into Jbuilder 2--it compiles and runs
> > fine, but I get a big old error when I try to access the help system
> at
> > all...for example clicking on "Help topics". Does anyone know what the
> deal is
> > here or if there is a work around?
>
> > I installed swing 1.1Beta2 the same way that I installed swing1.0.3
> using tips
> > posted here and that has been working fine for weeks.
>
> Not only did the help system stop working, the component tree and object
> inpector panes in the visual designer came up blank (perhaps the main
> window too--I forget).
>
> But I've got it working now. I had to revert to the old swingall.jar
> (swing 1.0.3--I had already replaced the original 1.0.1 that shipped
> with Jbuilder 2), make my swing1.1 library point to the swingall.jar in
> my swing1.1Beta2 installation direcotry instead of the jbuilder\bin one,
> and create a "JBCL with swing 1.1" library that was the same as the old
> one except for path changes for swing 1.1.
>
> I believe with this method I can have projects using either swing 1.1 or
> swing 1.0.3, just by choosing different libraries, and go back and forth
> with no effort.
>
> This all seems to work fine--the app builds and runs (and I'm using a
> method that doesnt exist in 1.0.3 so I know its being used), help system
> works, the designer works. It wasn't all that hard to do, either--I
> didn't even need to edit any INI files.
>
> So now I'm wondering, what's the catch? The recipes for getting new
> versions of swing working that I've seen posted in these newsgroups seem
> to all involve replacing jbuilder's swingall.jar file. Am I losing
> something by not doing this? I assume that jbuilder itself, particularly
> the parsing used for the designer views and such, is still using the old
> swing, even though I can compile and run with the new one. So I loose
> the display of swing1.1 features in the designer? (not much of a loss
> considering the designer doesn't handle some swing components very well
> to start with...)
>
> If I'm missing something, someone please let me know.
>
> Eric
>
>


-----== Posted via Deja News, The Leader in Internet Discussion ==-----
http://www.dejanews.com/rg_mkgrp.xp   Create Your Own Free Member Forum