🚀 go-pugleaf

Ernie:

Okay, you can replace swingall.jar as I mentioned earlier (but that
may have an effect on JBuilder) or...

Stick 1.02 somewhere else and use the new library mechanism in JB 2.0,
create a library for Swing 1.02.  Make sure that library is at the top
of the list for the project (you can make it a default that way) and
you'll use those classes first when you compile without running the
risk of funky behaviour in JBuilder.

-Rich

Ernie Rael wrote:
> 
> The original post had two questions. Blakes response kind
> of answers one, it says you can keep up with changes.
> A more complete response like:
>   . Just replace the swingall.jar.
> or
>   . Swing is just a component of a release, so the
>     procedure is diferent......
> I don't want two separate palettes, one with swing01
> and the other with swing02. If jb2 doesn't include
> swing02,the best way to update is definitely material
> for the FAQ.
> 
> The first question, "which swing, 1.0.1 vs 1.0.2,is used",
> remains unanswered.
> 
> -ernie
> 
> On Wed, 06 May 1998 23:44:44 -0400, "Michael J. Rozlog"
> <rozm@email.msn.com> wrote:
> 
> >check out Blake Stone's response in the borland.public.jbuilder.ide
> >group with the tread of "Swing and JB2".
> >
> >Mike
> >
> >Matt Tucker wrote:
> >>
> >> Does anyone know what version of Swing JBuilder 2 is based on? Swing
> >> 1.02 was recently released with a lot of fixes... how will Inprise keep
> >> with the changes?
> >>
> >> Thanks!
> >> -Matt Tucker

-- 

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rich Wilkman
Senior Quality Assurance Engineer
Borland JBuilder Team

If you see something that looks like an opinion up there,
it's mine and mine alone.

Mail sent to me from the newsgroups won't bounce but will
be ignored.  If I have time, I'll respond, but you  have
a better chance if you confine your posts to the newsgroups
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=