🚀 go-pugleaf

that's the problem with any environment you decide on, and JBuilder is more
open in it than most (it at least gives the option to NOT use the Borland
APIs).
As long as you're not standardising on a set of APIs you're bound to the
smallest common denominator which means the core JDK plus whatever you write
yourselves.
Best make a decision on a common IDE and API set and stick to that and/or
make all those APIs used by individuals available from a central location
(this means among other things the redistributables of JBuilder).

Marco Azevedo <azevedomt@bol.com.br> schreef in berichtnieuws
3edd0c98$1@newsgroups.borland.com...
>
>
> It's just it. thanks !
> I has tested JBuilder8 personal and it is very very good. It brings
productivity to Java developement. But I need to have a portable source.
Cause anothers programmers can want to use other IDE, maybe.
>
> Thanks again
>
> Marco
>
>
>
> Rich Wilkman <richw@formlessvoid.com> wrote:
> >Marco:
> >
> >Plenty of them -- they live in the com.borland packages.  Also delivered
> >with JBuilder are 3rd party libraries in their own, non-Sun packages.
> > The JDK is just the starting point for doing Java work.  Is this really
> >your question or are you trying to get to something else?
> >
> >-Rich
> >
> >Marco Azevedo wrote:
> >
> >>Is there any Class in JBuilder that does not exist in SUN JDK?
> >>
> >>
> >>
> >
>
>