Results from NetCAT 6.0 Community Acceptance survey
Suggested Features
"Native" support for Groovy
1. Class indexing/searching interface 2. Performance (good, but a never ending process) 3. Conditional Breakpoints
Fix spurious "invalid breakpoint" messages in debugger (115033). Better support for Ajax/JSF integration _outside of_ VWP, possibly through a Dynamic Faces plugin of some kind? I can't think of a third one because 6.0 is the best yet.
1. More speed improvements to bring NB into line with IntelliJ. 2. Support for Apache Geronimo. 3. The ability to move libraries between different versions of the IDE without having to move them manually.
-code generation (jsp from database, or the old form from a class)(the crud database application wizard not only working with one table) for example -performance, for example opening a jsp page its so slow -the visual jsf samples doesnt work , for example the travelcenter brokes in designer view.
Anything related to doing web application development. All of the nifty things you do already that I didn't know I needed! Honestly since I use no other IDE, I don't have much expectation, but Netbeans is great for me.
project level libraries some performance improvements ability to open maven projects
IMPROVE PERFORMANCE. See defects #120222 and #119415 for example. MUST HAVE CLEARCASE SUPPORT Need to clean up editor with respect to copy/paste. Pasting copied text never seems to be spaced correctly related to the text above/below it. I know you can use a combination of key strokes to sort of do this, but our competitors do it automatically...we should too.
1) Plugin Portal that ONLY shows plugins that can be used by the particular version of NB. 2) A proper SVG-tiny editor incorporated in the IDE to be used in mobile projects, that is WYSIWYG. E.g. Inkscape in the NB, that generates SVG tiny files. 3) Auto follow of a source file in the navigator window. So show the file in the navigator that has currently the focus in the editor without having to hit CTRL-SHIFT-1.
-Performance Improvement -Better support for page design and templates, support and improvement for this plug-in is a good option: http://blogs.sun.com/winston/entry/template_creation -Again Performance Improvement is crucial
1. Performance improvement on "often-occurring IDE activities" such as run-single-main, run-single-test. 2. Smart detection of a Test case class and a Main() class based on the class, not its location: Currently all classes in "test" folder are treated as "test", and you can not run a Main() on it, which is ridiculous. 3. More refactor and editor smart completion improvement in the direction of IntelliJ's features.
1. support for google android 2. improvements in the visual designer (uml): ejb3 support, entity-relationships, database creation, ... 3. first class maven2 support
1.) Some JavaME Custom Canvas Builder GUI (for CustomItem) or something like Matisse for CLDC with easy layout 2.) More Templates/Designs To CRUD database application 3.) Out-Of-The-box support for php instead of a plugin
Code formatting (styleguides) and template configuration per project Faster code completion (still very slow occasionally) Better Javadoc support (code completion, "ctrl-click" to jump to a "linked" class)
1) Better Websphere support. 2) Profiler support for other JVM's (IBM) 3) Faster startup if possible.
1- html and java editor speed improvements 2- tapestry 5 support 3- less memory usage
1. VWP Design Time Performance 2. VWP (Woodstock) Run Time Performance 3. Memory usage improvements with large VWP apps
Support for Android Full support of Woodstock components in VW apps Deployment to Glassfish on remote server
1. Speed in file loading and load/deploy equivalent to Eclipse. Having used Eclipse now, I really notice the difference. 2. Enhancements in modeling and interacting with databases, especially a graphical tool for use as a front-end rapid prototyping tool similar to Microsoft's Visio tool. 3. Better documentation of the authentication tools offered through Access Manager (to be renamed FAM).
SVG editor CSS Edition preview Possibility to build project analysis/conception doc within editor and link them to project
1. Table/Column name completion in SQL editor. 2. Visual DB Schema designer. 3. Visual Reports designer in mold of JasperReports.
support for SEAM and facelets.
1.Performance should improve 2.Debugger improvements like in place object inspector 3.More Platform development support (improve apisupport project)
More optimal memory requirements, because it's eating my computer resources. Improvement in creation code from design model. Compatibility with asteroid, because of making apps for new gPhones.
1. Better Library Management in C++ and java 2. Task and project Management system
1. Better Maven integration! 2. Faster Glassfish deployment and startup. This is crucial for large web applications. MyEclipse exploded archive deployment is a good example.
#74474 Prepopulation of Library Manager from system JARs #117098 No user notification that file is opening in editor #97192 In "Attach debugger" dialog make "Port" field remember previous entries
1: Issue #94193 (bean property editing) 2: Some degree of JCA tooling support 3: Issue #95022 (VWP component resizing)
1. A dedicated method/GUI to set up project dependencies, especially for freeform projects. 2. Be able to add one source directory to multiple projects. 3. To be able to handle all virtual hosts in Services/Servers/Tomcat. (currently only localhost is available)
1. More powerful and easily configured free-form web project support. Possibly include importing from MyEclipse projects? 2. Groovy 3. Import/export options with interoperability with other IDEs (makes other IDE users more likely to try NB and feel at home)
1) javadoc and comments completion (all features as in eclipse) 2) new way to manage libraries (libs from project, libs from folder...) current way really sux 3) autobuild (very useful for web projects)
1.) Project-based libraries so that the project would be self-contained resulting in easier sharing of projects and nightly builds based on the NetBeans-generated Ant files could be done without the user-based global libraries defined (with all the benefits of libraries in the IDE) 2.) Return the Java-Beans/BeanInfo support 3.) User-based formatting preferences applied during code checkout/checkin bug #118377
1. OSGi bundles development support 2. Android integration à-la Eclipse 3. Optimizations, as it sometimes the editor lags too much
- performance of code completion, background compilation and opening of subdirs - gui for testing of web services - compile on save
1. Integrate visual JSF development with Maven projects. 2. Improve CVS/Subversion integration (remove the requirement to download an svn client, have something similar to the Eclipse "Repository Exploring" perspective) 3. Improve Eclipse keyboard bindings to ease transition from Eclipse converts. Currently, ctrl+F (which provides the same function in both NB and Eclipse) does not work when using the Eclipse key bindings, neither does Ctrl+O, which I recently learned the equivalent for it is ctrl+f12 in netbeans).
1-Open source frameworks support for spring, hibernate...etc. 2-Improving the quality. 3-Fast code completion and rich editor like eclipse editor.
1. Better Refactoring for Ruby and C++ 2. Better Code Completion for Ruby.
Subversion support Maven support JBoss integrated
1. Better support for sharing projects between members in a team; Libraries, other team-related tasks
Responsiveness More intelligent -Xmx detection Better Collab support for project sharing
Better performance; Better Java development toolkit, such as code completion, quick fix, refactor, shortkey bindings, etc Better UML support.
Surround with try-catch on selection right click as in 5.5. Being able to specify source level for each individual Java source file in a free-form project, if different from the project's default source level. Get rid of freezes, excessive memory usage and slow reaction times. For example, now (6.0 RC1, jdk1.6.0_03) my IDE GUI freezes every few minutes, but I can wake it up using some Attach API tool such as jinfo, jstack or similar against the NetBeans JVM (could be a JVM bug, though). Extra: Auto-comment tool.
Smarter parameter matching. Faster startup.
proper Hibernate/Spring support proper facelets support (+visual) improved database explorer (edit feature, ) equal maven integration as ant integration (eg. have frameworks,...)
Break build scripts dependency on NetBeans (+ relative paths) Improved Library Manager (exports, imports, etc.) Includes & Excludes in projects with existing sources
javaEE maven support automatic code cleanup on save (imports, ...) Source/Doc jar support without using libraries android support
more automatic databinding with swing components and databases.
GWT integration, existing module needs lots of work. Great to see netbeans work properly with IcedTea (OpenJDK), currently lots of things do not work properly.
Library Management Improvement (Easier to share libraries) The be able to build a RCP application on NetBeans platform. Issue/Artifact tracking integration support
1. Mobility Pack on Mac
1. Speed. There is a noticeable difference between 6.0 and 5.5.1 in this area. 6.0 is slower on nearly all operations. 2. Memory Footprint. 6.0 is between 50-80% larger memory footprint, for just doing basic SE work (i.e. no visual web, no J2EE). I am under OSX, latest Tiger/5.0
Add back the JavaDoc AutoComment tool
- Load/Save of SQL code snippets to named files - faster code completion / content assist (Eclipse still does better here) - Python and Groovy support on par with (J)Ruby
auto-generation of javadoc comments for project integrate obfuscator with Java SE better docs for visual API
- Visual Web - Netbeans freezes when a component is added to the designer (in RC1). - Documentation of (new) features, like beans binding, is not detailed enough. JDeveloper or Visual Studio tutorials could serve as a reference. - Property change events for entities can not be generated from a regular (non-database) Java project, nor can template for entity generation be edited. Overall, binding related features should be better documented and easier to use in regular projects. - Binding in generated database project does not always work as expected. For example, 'change as you type' works for some columns, and for some it doesn't. - When generating entities, IDE hangs and stops code generation if a table and a view have the same structure (t_customer and v_Customer, where v_customer only does 'select * from t_customer') - Startup times could be improved by not opening the main project when IDE starts, but only opening the IDE. It's just a matter of user experience... - Netbeans platform... well, like most other things, it lacks proper documentation (books, tutorials...) I love Netbeans, and chose it over JDeveloper and other IDEs for a serious project. I just named things that I think need improvement. Keep up the good work, and good luck.
1) Maven integration is the best vs. others. However, it 'd be great if they worked identically to netbeans created projects. 2) Phenomenally awesome to have first rate GWT integration. Even better -- Matisse + GWT. 3) Continue innovating on the RCP.
1. project-based libraries to support team development 2. much faster build - eg our project at work does a no-op build (ie already built) in almost zero time with intellij idea, but netbeans takes 2 mins to go through all the 6 projects. annoying when all you want to do us run. 3. dtrace support on OS X
activity on the nbfacelets project on java.net some form of beaninfo editor better xml editor support
-Better jsf support i.e. visual editing for all the possible tags of the faces-config.xml file. -Uml must be compatible with XMI. Is it already in NB? -Spring support
JSF Designer SPEED! 3rd party JSF-component support synchronized views and code completion for JSP/JSF
- Geronimo application server - Hibernate (as a separate plugin and facilities) - Spring and Jboss Seam and GWET
more refactorings code analisys (sqe integration?) better code formatter
- better Java Editor; I am still an Eclipse user and the Eclipse Editor is more intelligent. For example the insertion of the symbol ;. Eclipse handles this very well. Also the formation of the code in Netbeans is not so good. - Although the new look of Netbeans is much better, it still has the 90's area look (except the splash screen and the welcome page, but the icons are not really good) - For me the most important feature is performance. Eclipse still feels faster than Netbeans. I think here is much room for better performance and less memory use.
- profiling memory as well as cpu at the same time - better/smoother integration of xml with java (e.g. an xml-file (maybe the ant-file) has a java class referenced inside and the java-file is renamed, but currently the reference inside xml isn't) - better performance for the UML-module (still too slow, still to much memory usage)
Subversion support to work better. EJB generation to generate better EJB code code folds in JSP better parsing of JSP/JSF. there is information overload, perhaps configurable options on what you want to see in the margin, error stripe etc.
1. JGoodies Forms support in the GUI editor 2. Support for non-Java web (HTML/CSS/AJAX) projects with upload (FTP maybe)/test server tie-ins 3. Work with Nimbus look and feel
Overall Netbeans Performance, especially on large files with lots of changes Show "todos" in the stripe on the right side of the editor
The ability to import UML models from rational rose (*.mdl files), better performance, and more solid JSP editing support.
Faster, faster and faster.
Support GUI beans that do their own padding, see issue #69823. Can't use free design without it. Convert JBuilder forms to NetBeans. Handle line renumbering when doing a debug/fix. Not sure if this is a JRE thing or if NetBeans can do it on its own.
1.Broader support for various version control systems. 2.Expanding "Project Properties" dialog to include more options that currently need to be done via manual editing of nbproject/project.properties (i.e. test-sys-prop.propsfile option)
1. Netbeans is a great environment and is coming on in leaps and bounds. But there is one area where the whole is let down by a part. The WSDL Editor leaves a LOT to be desired when compared with the eclipse WSDL editor. The design as such is ok, but adding new operations is a real pain and REALLY slows down development. We install both environments on all of our devloper machines for this one reason alone. The new WSDL wizard could do with a rethink as well. You can contact me for details if you want. 2. There is a cool new XSLT editor available but it is well hidden in the XSLT Service Engine Project. This could be easily extended for use for all XSLT files. Altova MapForce works exactly like this.
For RCP I would like to see better META-INF.services integration. Currently I have to manually add a file with the name of the service my module is implementing, such as org.myorg.mynodeeditorapi.IMyNodeEditor in the META-INF.services folder under the source folder to be able to use the right click enable editor in META-INF services node under the Important Files node. I should be able to right click and be presented with a context menu with an Add option. Maybe next release?
- Faster (all features and aspects) - More configurability...like eclipse - Wicket UI support - Visual Editing for *all* html-based files!
Speed improvement
1. Improved glassfish edit/deploy/test cycle. 2. Groovy editor support. 3. Import statements following with copy|cut/paste from another file.
1- GTK+ matisse for C/C++ projects. 2- Support for Android projects, also with matisse. 3- PHP projects.
1. Better documentation for RCP development, API cleanup, better javadocs, avoiding calling deprecated methods in netbeans code, ... 2. Oracle db and app server support
Better JSF support: 1. Add additional jsf tag libraries so they appear in the right-hand side panel 2. Visual jsf editor Identation in java editor could be improved too
Better code formatting options. JSP debugging.
- Bundled Hibernate! - Graphical overview on subversion branches/tags/version history.
- to have the undocked windows displayed in "undecorated Frames" (without additional window framing) would look much cooler. - i am missing a visual hint on where a marked
Background compilation. More (easy) ways to integrate non-Tomcat web containers (Jetty, generic JSR45 compatible, etc).
- better performance editor (even if NB is faster/lighter now) - better editor code completion (see #89281) - better editor refactoring process (see #121733)
1. Provide a framework for Enterprise Application development like it's done for Swing Applications. Just choose popular Java EE patterns and combine them in a usable project type. Project that will handle security (login page, jaas, single sign on), modularity, transactions, logging, database, etc., All the things that are needed to create a simple but complete Enterprise application. 2. Superior Subversion support. 3. More editor improvements, more hints, more refactorings
Speed, Speed, Speed
1.) Link with editor (synching between project view and currently opened file in the editor). There was an extension I had for 5.5.1 (by Ramon Ramos) and I was surprised that this is still no standard feature for NB 6. 2.) Fold everything in the project window. Fold all within node in the project window. 3.) Nicer JUnit view. And more flexible. GUI, text only or tightly integrated (current view with some add-ons).
(1) easier management of shortcuts, especially consistent naming and the ability to export from release to release
- JavaScript Editor support could be like Aptana, with frameworks integration
Improve performance of the edit-compile-debug cycle. It is still painfully slow (relative to competing IDEs) to test minor changes.
1 General performance improvement 2 A better debug "Variables" integration with the editor (like in MS Visual Studio 2005, just moving the pointer over of the source it lets you navigate throw its hierarchy) 3 A better JUnit 4 GUI
1) UML code generation needs to be knowledgeable of Java annotations. 2) Greatly improve performance when working with UML diagrams. 3) Ability to produce UML documentation with JavaDoc features (e.g. html tags, , @{link}, etc.)
I can't think of much that is missing. An error highlighter in the C++ editor like the one in the Java editor would be nice. I'm somewhat interested in learning D, not really sure. One of my biggest issues with D is that it lacks an IDE. If the demand is there I might like that.
1. Speed (CC, navigator, switching between source files, javadocs, etc.). Background compilation/compile-on-save. Fully support slicing a single source tree into distinct, possibly interdependent, projects (through excludes/includes), including GUI. 2. Current Plugin Manager RFEs, esp. make it non-modal and provide explicit and unambiguous information, install and configuration options for global vs user-dir modules. E.g. how do you replace a globally-installed module with a new version, installing it into user dir without turning off or uninstalling all the modules that depend on it? I'd like this scenario to work seamlessly in the next version (and I want to be sure it's going to do exactly this and not something else). 3. Functional programming support - projects, editor, code completion, integration with compiler, running target application from the IDE, integration with the command-line environments. OCaml, Haskell, SML.
Better support for javadoc comments.
cross scheme query design in the query builder.
Attach source code to jar file directly. Pure java svn client support.
- 6.0 RC1/2 are sometimes using 100% cpu. I think it is compiling but it doesn't show what its doing (in lower right side). This is so bad that I cannot live with it. - faster CTRL-SHIFT-O (Open file). - Debugging a file now doesn't do a 'build' before starting. It does something different but that task sometimes forgets to compile files. (I use an editor outside netbeans). If I press 'build' before debug all is fine.
Easier configuration for using SCM tools like Perforce. I use netbeans at home and work unfortunately at work we have to use Perforce so far I haven't figured out how to integrate it into netbeans.
Application framework skeleton support, for instance, a better way to lay out the architecture. More rendering option for JSF, try to support others like facelets. Functionality to customize templates such as the Entity from database wizard.
Enhance debugger's view on byte[] variables #113892 Improve code folds #40104#47638 "Collapse Operations" in UML-Diagram #79814
Groovy&Grails Support, it would be great if Java SE Pack could come with all JavaFX stuff by default, NetBeansSuiteInstallerBuilder.
1. UML projects that are version-control friendly 2. Shareable code conventions/formatting (Import/Export) 3. Shareable templates (Import/Export)
The new dialog for desktop database applications is a great starting point. I would love to see that get more attention for some future release. There are some obvious next steps to make the end result more user-friendly: - An "Are you sure?" dialog if you click on Refresh instead of Save with unsaved changes (same for Exit) - Giving focus to the first field in a new row. - Creating a login screen. The About screen is great, but I've needed more login screens than about screens. (Although now I'll have to use the about screen since I get one free) I could go on, but the point is this: you've created something really useful. Expect that there could be a demand for it. The second improvement would be something to do with startup time. I've accepted the fact that NetBeans takes a while to start. It depends on the machine. It depends on other things. Lots of programs take a while to get going. But my boss tried NetBeans and he had one comment. "It takes a long time to start." And he's right. It's that first impression. I know it's not slow once it starts. I know that it takes a bit to get going for good reasons. But whether it's actually making it faster, or making the startup *seem* faster or friendlier, I think it would help if it could be improved. Third, and least, I'd like to see something in the Help menu that explains the little icons and badges. A reference. A cheat sheet. Call it what you want. One place I can access directly from the Help menu that shows the picture, tells me what the picture is supposed to be (you mean that's not an inverted wishbone, it's part of a wrench?) and what it denotes. It's like the earlier discussion of whether the "ant" looked like an ant, a spider, or some other sort of bug. Why is the xml file represented by a pecan leaning behind a barrel? What do three billiard balls have to do with a .java file? I'm kidding about the xml file, or course. It's a coffee bean leaning behind a barrel. ;) I have no idea what most of them are. They're just abstract shapes. (I've learned what the forms are but that took a while and it's one of the most obvious ones. Okay, I'm not saying I'm not partly to blame.) I'm sure they all make sense. I'm equally sure they aren't obvious to everyone. So a nice visual legend on demand that people can find easily might be a help.
Better freeform projects!! I and other people have already submitted RFEs relating to freeform projects. It would be nice if the NetBeans Platform could be made to start faster.
1) The suggestions outlined in this blog entry to make Visual Web more usable: http://www.ryandelaplante.com/rdelaplante/entry/my_netbeans_visual_web_pack 2) Excellent support for JSF 2.0 and Java EE6 (including huge performance improvements in Visual Web, it is almost unusable the way it is when closing and opening pages) 3) Strong focus on SQE plugins -- maybe even integrate it into base IDE : code metrics, test coverage, possible bugs, style etc. 4) Top notch out of the box support for features that a large amount of developers use like Spring, Hibernate, and TestNG even if Sun is pushing different technologies. This will make more developers consider trying NetBeans.
1. Integrate Maven support, e.g. via mevenide 2. Per project settings, e.g. for palette, hints settings, code formatting and templates 3. Easier way to integrate C/C++ projects into java projects when using JNI/JNA
complete support of CSS , even for IE specific features customizable palette freemarker editor
1. Fully integrated testing tools (JUnit, Code Coverage (Coberatura, Emma), Static Analysis (Checkstyle, FindBugs, PMD)) 2. Fully integrated Maven support 3. more Java FX Script
JUNIT's classic GUI in running tests JAVADOC tool (as in NB 5.5) JSF Managed Beans improvement
IDE Stability, performance and feature consolidation.
- plugin for Android (the new Google's platform for cellphones). - Matisse for edit Android user interfaces. - Support for PHP language, and frameworks.
