NetBeans IDE has been known in recent years as "the only IDE you'll ever need" because of its out-of-the-box support for a rich set of technologies (Java SE, ME, and EE). This remains true, and now it has gotten better! NetBeans IDE 6.7 M2 is the first official NetBeans IDE distribution that is "ergonomic" to user needs by only loading functionality on demand. That is, the IDE does not load all its technologies as soon as it starts. Instead it lets users express their preferences, and then adjusts itself to best suit their needs.
Now the NetBeans IDE goes even further to deliver on its promise of being "the only IDE you'll ever need". It can continue to expand its functionality while reacting to the needs of its individual users. The running IDE process enables only the required functionality, eliminates bugs and inefficiencies from those parts that are unused, without being deactivated by the user. We are proud to be able to optimize these processes to deliver the first and only "ergonomic" IDE that fits itself to its user's needs forever.
Screen shot:
The NetBeans IDE aims to accommodate its users. However, we want more than synergy between the IDE and its users, we want synergy between the NetBeans team and users/partners/developers using the IDE. The NetBeans community is a great community, one of the best communities of any open source product in the world. The community is known for the valuable feedback it provides. During the NetBeans 6.5 release we realized that we wanted to improve the way we received feedback, to make reporting more frequent and more detailed.
We are proud to announce that the NetBeans IDE 6.7 has been enhanced with excellent self diagnostic tool to help with "in field" identification of errors and to simplify the reporting process. The Profile Me Now! feature is here to help us achieve better performance and have less bugs, in short, to help make greater software! This task continues to be made possible by synergy between our users, partners and developers and the NetBeans team. (Thank you all for your help!) And now, Profile Me Now will make that synergy stronger.
Here's how it works: Make sure the Memory toolbar is displayed (step 0). Then click on the button to let the system start to capture thread dumps from the running IDE (step 1). Then work in the IDE, emulate an action which seems to be slow. Press the button again to turn the self profiling off (step 2). The system then generates a standard NetBeans Profiler snapshot and shows it. Now you analyze the dump or attach it to Issuezilla's bug report.
For Java sources generated by various tools, like JAXB, JAX-WS, or JAX-RPC, the generated source roots are now displayed in grey in the Projects tab. These sources are generated by tools and not expected to be edited by users.
The behavior of these generated sources is as follows:
Java SE, Web, EJB, and EE App Client projects handle generated sources.
You can also use this feature for your own custom build steps: override the -pre-compile target in your build.xml and generate classes to a direct subdirectory of ${build.generated.sources.dir}. The IDE should automatically detect and display them, and include them along with real sources when compiling your project.
This feature allows tracking and editing of several SVG Rich Component parameters using the: Properties Window, Inspector and Flow Designer in the Visual Mobile Designer.
This feature allows users to rotate an SVG image by 90/180/270 degrees. It helps developers to design SVG mobile applications in landscape mode:
90 degrees
This feature allows users to switch between registered SVG Snippets. There are two default snippets registered, "Classic" and "Gradient". This API also allows users to plug in new sets of Snippets.
Panel to switch registered SVG Snippets.
All the features are described in more detail on netbeans php blog. Here is a list of Milestone2 features:
Now it is possible to create Qt applications and libraries without complex project configuration and hand-editing of Makefiles.
Typical Qt files, such as forms, resources, and translations, can be easily created from inside the IDE using standard Qt editing tools: Qt Designer for form files and Qt Linguist for translations.
Code Assistance will be configured automatically for you, if NetBeans can find a Qt installation on your computer.
New Qt-specific project properties cover typical configuration needs, at the same time allowing experts to fine-tune the generated qmake project file.
The Macro Expansion view allows you to view code with expanded macros.
To enable the Macro Expansion view, choose Window->Other->Macro Expansion from the main menu. To expand a certain piece of code, select Navigate->View Macro Expansion from the pop-up menu.
Macro expansions are located inside guarded blocks.
Semantic highlighting is provided for expanded code. It is also possible to use hyperlinks.
New hyperlink operation is available Alt+Ctrl+Click to open Macro View. If hold Alt+Ctrl and hover block with macro expansion then tooltip is shown and no need to open macro view until more details are needed.
There are some improvements in code assistance for C/C++ projects.
You can now disable browser opening on run.
And you can configure the JDK to use with Grails project.
The code completion can handle method reference and safe dereference operators. For Grails domain and controller classes it provides names of dynamic methods.
Now there is a support to invoke any Grails command (or custom script) on your project. You can invoke it from context menu item "Run Grails Command...".
In displayed dialog you can easily filter out commands and run selected.
The Ruby Platform node now contains child nodes for the gems that are installed for that platform.
There is a new visual diff viewer for displaying assert_equals failures.
In addition run focused test is now supported for Shoulda tests.
The Rake Runner dialog now maintains a list of the previously entered parameters and automatically populates the list of parameters for migrate and fixtures tasks.
It is now possible to specify the initial URL that should be displayed when running a Rails application.
| gems-node.png | ![]() |
9975 bytes |
| rake-runner-migrate.png | ![]() |
9005 bytes |
| test-diff.png | ![]() |
18329 bytes |