 |
what I would like to see in a next version of NetBeans
Posted by vbrabant on June 14, 2006 at 11:15 AM | Comments (19)
Somes little enhancements I would like to see in next release of NetBeans are the following:
1. today, NetBeans editor permits to use Camel Notation. So, if I type NPE and press Ctrl-Space, I obtain NullPointerException.
I would like that NetBeans editor goes further and accept also Camel notation for methods. So, when I type Integer.tHS and press Ctrl-Space, it should become Integer.toHexString(|);
2. Please, add context when I want to add/modify code concerning the elements of the Visual Editor. Would facilitate our work.
3. Isolate a Visual Element. You know. You start by doing a simple Swing GUI that become more and more complex. Should be easy, to select from the properties windows a GUI element (like a sub JPanel, containing a lot of buttons, labels, ...) and then ask to NetBeans to isolate that Visual Element. Result is a new Class and his associated xml file. And should be added in the Local Palette (that contains all Beans of your current and associated projects).
The third feature would be a really nice one.
Hope to see that in NetBeans 6.x
Bookmark blog post:  del.icio.us  Digg  DZone  Furl  Reddit
Comments
Comments are listed in date ascending order (oldest first) | Post Comment
-
I'd like to see
a way of seeing the details of the code error under the cursor without having to mouse over it.
custom run configurations (different properties/env vars etc), instead of just one per project
in-place editing of javadocs - the javadoc editor is all very well, but idea/eclipse style in place editing is much nicer, including type sensitivity for {@link} tags, etc
remote development - use the collboration system to do the project intelligence/source parsing/building etc on a big headless box somewhere (eg my dual g5), but do the typing/visuals on a lower powered smaller machine (eg my 12" ibook).
Posted by: goron on June 14, 2006 at 12:56 PM
-
A more professional and more consistent look and feel for the user interface. The first user experience with Netbeans is much less pleasant than with Intellij or Eclipse and might therefore hamper Netbean's acceptance. As a technically brilliant product Netbeans may be less successful than deserved due to an ameteurish user interface.
Posted by: phaener on June 14, 2006 at 01:56 PM
-
phaener, I would like to know more about whaty ou think is amateurish about the user experience. Seems very simple and straightforward to me. I have been using JDeveloper and Netbeans 5.5 daily builds and though JDeveloper comes across to me as a very powerful and feature rich IDE put together, Netbeans comes across as the same to me as well (with the enterprise pack and profiler installed of course). I just am curious that is all.
As for the feature that I would like most comes from Eclipse unfortunately. I really liked the auto compile and report all the problems whenever you save the project. That was quite handy and so were the quick fixes that the IDE automatically did for you. Other than that, there was nothing in Eclipse that appealed to me....well there were a lot more refactorings so that would be appreciated as well.
Posted by: suryad on June 14, 2006 at 02:34 PM
-
For me, it looks unprofessional because of things that I find hard to explain - the spacing in the titlebar - the text in the Projects titlebar is too close to the edges of the titlebar, for example.
I think it is spacing and layout for the most part. It looks like something *I* would do, and I don't know much about HCI. I look at stuff others do and say, boy - I wish I could do that. And netbeans just doesn't look that good.
The spacing between the icons in the navigator panel and the edge is too small. It's too tight. I know you have to display a LOT of info in netbeans or people will complain, but it just doesn't look right.
I compare the look and layout of netbeans to any of my KDE applications and it just doesn't begin to compare. And I can't really explain it.
Posted by: trcorbin on June 14, 2006 at 03:39 PM
-
Suryad, I agree with you that Netbeans it is very poweful and feature rich. The technical merits are however just one of the aspects deciding over success or failure of a product. The visual appearance may be equally important, and here there is some potential for Netbeans to improve: getting slicker and more pleasant to use. A good user interface should not get in the way with the coder, and I feel that IntelliJ does a much better job being "invisible" and not interfering. The first visual impression with Netbeans is similar as with many other open source projects: the interface and icons look like created by a software engineer and not by a graphical artist.
Posted by: phaener on June 14, 2006 at 03:55 PM
-
I think Netbeans has a lot going for it but its look could indeed be improved. One thing I always do when installing a new netbeans is add some command-line magic in /etc/netbeans.conf: "-J-Dswing.aatext=true --fontsize 16". The font of the GUI itself is usually too small for me and in general I do not like the font. It misses "body". It should be more massive. The font from eclipse or vim for that matter is much more pleasant. I haven't found a way to easily change that though.
Posted by: mchristi on June 15, 2006 at 06:52 AM
-
I would like to see a better Maven integration - netbeans freeform and mevenide are kind of nice but this is more a loose link than an integration
Posted by: schiewe on June 15, 2006 at 09:15 AM
-
I would like to see a better integration of inherited visual classes and reused components. A more easy way to create events for components using keyboard and the more important, import sizes and position from feel design to null layout.
Posted by: flikxxi on June 15, 2006 at 11:30 AM
-
You know honestly I do agree with all your points about the Netbeans gui. I dont like the fonts. It is too anorexic in my opinion. And also thanks for that tip about editing the conf file and getting the fonts to appear a bit bigger.
Posted by: suryad on June 15, 2006 at 12:22 PM
-
XSD support would be nice considering frameworks like Spring are moving towards using it over DTD and IDEs such as Eclipse & IntelliJ have such good support for it. Also its been on the feature request list since before v3.4 :)
Posted by: andrewyatz on June 15, 2006 at 03:16 PM
-
Netbeans looks beautiful.
Whoa! what bull..
There is a REAL problem with this group think at Sun and its hurting.
Yeah we know looks don't matter, so netbeans doesn't matter too.
Posted by: f1chowdary on June 15, 2006 at 04:06 PM
-
Please fix all those bugs. I often get errors using Matisse when positioning components.
The other thing is netbeans does not always compile .java files, especially the JFrame and JPanel (Matisse controlled) source files. It usually only recognizes a change when I modify them through Matisse. Directly editing the listeners etc, does not always flag the files as modified and the IDE simply skips the compilation stage. This is annoying.
Also, can the netbeans debugger monitor multiple threads? If so, how do I do this. I must say the netbeans interface is not as intuitive as Eclipse.
Such minor modifications and fixes would be most appreciated.
Posted by: rizzix on June 15, 2006 at 04:43 PM
-
The best thing to add to netbeans would be the ability to see all compile errors instantly, as in eclipse. If I change class B and class A uses class B, eclipse will tell me right away that there's no a problem. With netbeans I have to remove all the class files and recompile everything, way slow. With eclipse it's instantaneous.
Posted by: trcorbin on June 15, 2006 at 06:40 PM
-
i would love to have option to lauch matisee only from netbeans.i don't want and can't afford all enterprice things.please give me my single gui builder like JFormDesigner :).
Posted by: hithacker on June 17, 2006 at 07:43 AM
-
My list is all about the Java code editor:
More refactorings, specially "Extract local variable", "Extract constant", and Extract field". Only the lack of these refactorings prevents me from using NetBeans now
IntelliJ IDEA's style context-aware code completion. It speeds up the coding process a lot, as only what can be correct in some place is shown as an option.
Case insensitivecode completion.
Everything posted by other people, specially the "needed mouse over the error to see it's description" issue.
Posted by: thiagohp on June 19, 2006 at 10:02 AM
-
My list is all about the Java code editor:
More refactorings, specially "Extract local variable", "Extract constant", and Extract field". Only the lack of these refactorings prevents me from using NetBeans now
IntelliJ IDEA's style context-aware code completion. It speeds up the coding process a lot, as only what can be correct in some place is shown as an option.
Case insensitivecode completion.
Everything posted by other people, specially the "needed mouse over the error to see it's description" issue.
Posted by: thiagohp on June 19, 2006 at 10:02 AM
-
My list is all about the Java code editor:
More refactorings, specially "Extract local variable", "Extract constant", and Extract field". Only the lack of these refactorings prevents me from using NetBeans now
IntelliJ IDEA's style context-aware code completion. It speeds up the coding process a lot, as only what can be correct in some place is shown as an option.
Case insensitivecode completion.
Everything posted by other people, specially the "needed mouse over the error to see it's description" issue.
Posted by: thiagohp on June 19, 2006 at 10:09 AM
-
I'm very sorry for the triple post. There is no posting confirmation message and there is a delay between the comment posting and it appearing, so I thought my post was not posted. :(
Posted by: thiagohp on June 19, 2006 at 10:11 AM
-
I just want to post for the 4th time what is listed in the triple post.
Plus this:
. Version control plugins that work the same way as the new CVS one: Perforce, Clearcase, Subversion.....
Posted by: wqtjavanet on August 18, 2006 at 10:28 PM
|
java.net RSS Feeds
