🚀 go-pugleaf

Ryan,

jbinit() is just an internal method created by the JBuilder code
generator.  There's nothing non-standard about having your own methods. 
If you create an applet with JBuilder, there will be an init() method
created.  An applet wouldn't work without one.  

Guy

Ryan Pedersen wrote:
> 
> What about all the crap that JBuilder puts in the code.  I am new to
> Java but the classes that I have taken all have me building public
> void init() methods for an Applet and JBuilder does a method called
> jbinit().  Is that a none Java compliant item or is that just the way
> the code is built?  I too would like any advice for good visual
> editors.
> 
> Ryan Pedersen
> ryanp@accessone.com
> rpedersen@nextlink.net
> 
> On Fri, 03 Jul 1998 15:18:47 +0200, Michael Hermann
> <hermann@kirk.fmi.uni-passau.de> wrote:
> 
> >dbalok@my-dejanews.com wrote:
> >>
> >> I am looking for some advice.  Which is better, Micro$oft's Visual J++ or
> >> Borland's JBuilder?  and what makes it more better?
> >
> >JBuilder 2.0 without the slightest doubt.
> >
> >For one thing it has a far better IDE and visual modeler, for
> >another it supports both JDK 1.1 and the 1.2 beta (while J++ 1.1
> >does not even truly support 1.1).
> >
> >But most of all because JBuilder generates Java code whereas J++
> >(any version) tries to lock you into MSes non-compatible version
> >of Java.
> >
> >If you want to generate Java code, J++ is not the right tool, it's
> >a non-Java compatible Java IDE !
> >
> > -Mike

-- 
Guy Scharf
Software Architects, Inc.
Mountain View, CA
Developing software for ISVs