It
should be possible update modules from more than one
AU server at once. Now there can be more than one AU
server defined in the IDE (AutoUpdate types),
but only one is active. User should set more
active (enabled) AU servers to download modules
from.
Complete lists of new features: Core IDE, Autoupdate, Projects,
Current internal
compiler-parser based on javac 1.3 does not support
JDK 1.4 Java language extension ("assert"
keyword) and new classfile version.
Proposed solution for version 3.3 is to use javac
1.4 as a base. In longer term the
solution will be NetBeans' own parser combined
with more open javac implementation
providing API according JSR which should be invoked.
It should be possible to base the form on any class,
including non-visual. This requires
changing the form-type specification and extending
ways of form creation (e.g. also without
a template). Form type conversion could be
implemented too (makes sense for changes
like from JDialog to JPanel, etc).
The Component Palette will be moved out of the main
IDE window, should be floating and
dockable (by default in a window together with
individual forms grouped in a tabbed
pane). The GUI Editing workspace is then no
longer needed. Form Editor should support docking of
its parts into various windows,
according to user's wish. So the user could
e.g. dock everything (Component Palette,
Component Inspector, and forms) into one Form Editor
Window, or conversely let the components stand
separately. This arrangement would be
respected when opening new forms.
Component Palette needs to be redesigned. First --
it should not be in main window toolbar,
but in Form Editor's window (displayed only if
some form is opened). Second -- the
current JTabbedPane implementation cannot handle
more palette categories (tabs)
satisfactorily.
Object Browser
40%
New Object Browser
New
Object Browser
Complete lists of new features: Java support, Class support, Java Beans, Javadoc, Form Editor, Object Browser,
The current
version of NetBeans Debugger shows all static /
private / ... fields for variables in Watches &
Variables tabs. It is useful when you want to find
some details of implementation, but
it can be uncomfortable for many other purposes. For
example if I am inspecting an instance of
java.util.Vector, I probably want to see its
content not its serialVersionUID,
capacityIncrement etc. So we plan to add some
variable filtering capability to NetBeans Debugger.
It is a good
idea to logically organize breakpoints in the case
of large projects. Grouped in a
group, they can be enabled, disabled, or removed as
a single unit. A group can be
visually implemented by a node in the Debugger
Window, tab Breakpoints. Descendant
nodes should represent all breakpoints (eventually
sub-groups) belonging to the group.
Annotations is a
method to highlight a part of text of the document.
The text is highlighted either by special background
color or by putting an icon on the gutter or both.
