The OpenTools architecture of JBuilder is designed to make extending
your Java development environment extremely easy. There's extensive
documentation on the available API, and plugging your changes
into JBuilder is as easy as dropping a JAR in JBuilder's lib/ext
directory. That's all well and good, until something goes wrong
and you need to debug a problem with your OpenTool.
Luckily, JBuilder's debugger is well suited to
this task if you know how to configure your environment.
For users of our JBuilder 3 / 3.01 for Windows product line
this release is a major upgrade well worth checking out.
Users of our JBuilder 3 -- Solaris and Foundation editions will
find a few welcome updates to functionality they've already become
accustomed to.
Did you know that JBuilder has a command-line interface? With
the Professional and Enterprise editions you will be able to compile
whole JBuilder projects from scripts or makefiles without ever
displaying the IDE. All JBuilder editions, including Foundation,
have a lot of potential for taking advantage of the command line
for a wide variety of purposes.
What goes on when you push the make button on JBuilder's toolbar?
There are a lot of sophisticated features that many JBuilder users
are familiar with. Let us take you on a tour of the hidden benefits
have you may been ignoring in JBuilder's Java compiler.
How was JBuilder designed? Why is the Foundation Edition
free? What is the OpenTools API? These questions and
more are explored in the first of a series of articles that delves
into the depths of the JBuilder experience
|
