NetBeans6.5 M1 众多期待的特性一览表!

Netbeans 6.5 M1 已经发布,最新版本的NetBeans 增强了许多功能,同时也引入了许多值得期待的新特性.
其中我比较喜欢的是DataBase 的改进,Eclipse 项目导入变得比以前更方便了,可以正确的区分Web项目
和普通项目,还有Spring   Hibernate 增强. GUI 中新增了JDK1.6 u10 中的look&feel 只要你用的是 JDK1.6 u10
就可以使用这个外观预览.数据绑定功能也改进了!   全新的多线程Debug  功能支持!
 JavaScript  也加入的Debug功能,还加入了好几个Javascript 库,像JQuery ,Yahoo ui dojo 等等!
还新增了一个 "驼峰拼写" 代码补全功能. 很有意思.
JavaEE 的lib path 也变成了可变的了.此外还增加了快速搜索功能. 更方便搜索!   还有好多个特性呢!

还有PHP Groovy Ruby 等都有增强!
具体看下面的介绍! 英文太多了就不翻译了 大家自己看吧!

UNC paths on Windows

Now the NetBeans IDE supports UNC paths like ""computerName"sharedFolder" . It is possible to install the IDE to UNC like folder and also it is possible to create projects and other resources on UNC paths.

File Associations options panel and Open As... action

A new panel in options dialog which allows to say to NetBeans that files with certain extension should be treated as files with a certain MIME type (see #133773 ). You can add a new extension to the list of modify existing one. If you want to restore default setting for selected extension, you just click the Default button.

In connection with the above change there was also added a new Open As... action. It is enabled only for files which are not recognized by the IDE. User can choose one from supplied MIME types and from now on all files with this extension are treated as of choosen MIME type.

Running some IDE distributions on JRE

Certain IDE distributions (e.g. PHP IDE) don't require Java JDK to run on, JRE is enough.

Plugin Manager now checks OpenIDE-Module-Package-Dependencies of all modules which user selects to be installed. If the user's IDE is running on JRE and the unsatified package dependency might indicate that JDK is required, user is warned about it and the plugin installation is not allowed.

QuickSearch

Quickly search for action or type is now easy. Use Ctrl-I.

• wiki: http://wiki.netbeans.org/QuickSearch
• UI spec:http://ui.netbeans.org/docs/ui/quicksearch/index.html

Variable based paths in J2SE/J2EE projects

Since NetBeans 6.1 it is possible to control whether JAR/Folder added to project classpath is referenced via absolute or relative path. Now it is also possible to define a global IDE named variable pointing to a folder and use this variable as a base for referring to JARs/Folders.

This feature further simplifies project sharing between users. In scenario where a project depends on JARs for which:

• it is not desirable to store them in VCS; and which
• can be placed in different locations for different users

a named IDE variable can be used.

The variables are managed via Tools -> Variable menu item:

In above screenshot single variable is defined with these details:

When variable based JAR/Folder is added to project classpath you can see its path starting with variable name (and tooltip showing absolute path):

Variable based JAR/Fodler is added to classpath via standard means of "Add Jar/Folder" button in classpath customizer (or "Add JAR/Folder" action on project's Libraries node in project's view). Custom file chooser is shown with one new option "Use Variable Path":

Just browse for your JAR/Folder and if selected file is under a variable the option gets enabled. Alternatively press "..." button and setup a new variable.

If a user opens project with a variable based path and the variable is not defined in user's IDE then standard broken reference warning is shown to advice user to define variable:

Eclipse project import and synchronization

The Eclipse project import feature facilitates mixed IDE development teams. It allows you to select Eclipse projects from an Eclipse workspace and generate NetBeans projects for them. The generated NetBeans project keeps a link to the original Eclipse project and will update itself after any relevant change: for example, changing the classpath of the Eclipse project. The update is done automatically when the NetBeans project is opened, or can be explicitly requested via a context menu item "Synch with Eclipse" on the project.

This is early preview of the Eclipse import feature which will be fully implemented in Milestone 2. (It supersedes the limited Eclipse import feature available in former NetBeans releases on the update center.) We would appreciate feedback and real-life Eclipse projects for testing; best is to use Issuezilla. (component ide , subcomponent eclipse project import )

Enhanced Java Web Start support

Support for creating applets that can be deployed via Java Web Start was added to NetBeans IDE. Note: the functionality is available in JDK 1.6.0 update 10.

Each application or applet deployed via Java Web Start can specify external resources (usually other JNLP file in internet). Dialog is opened by clicking on 'External Resources' button.

Each applet can have number of properties defined in JNLP file, those properties can be defined in dialog that is opened by clicking 'Applet Parameters'. Also you can set applet dimensions in the dialog.

Platform

Sliding windows support original window sizes

Slided-in windows can keep their preferred size instead of being stretched to the whole height/width of the IDE window.

(see #135318 ).

Possibility to configure some Window System properties for applications based on Platform

Some window system features can be turned off by branding of core.windows module.

TreeTableView replacement introduced

OutlineView is a new replacement for buggy TreeTableView. It supports drag and drop, in-place editing of tree cells, enhanced sorting etc. The data model is fully compatible with TreeTableView.

(see #33281 ).

Opening Options dialog with preselected subcategories

API in options.api module has been changed to allow open Options dialog with preselected subcategory (see #109538 ). In your code you can call OptionsDisplayer.getDefault().open("CategoryID/SubcategoryID"); where CategoryID and SubcategoryID are registration names from layer. For selection a panel under Miscellaneous category use OptionsDisplayer.getDefault().open(OptionsDisplayer.ADVANCED+"/SubcategoryID"); .

Support allowing a user to drop a text into the palette

It is possible to drag and drop any text to the Palette window to create a new code snippet. It works for HTML editor palette only at the moment, more document types will follow soon.

PHP

Features first introduced in Early Access for PHP

The NetBeans IDE Early Access for PHP was released in April at the same time as NetBeans 6.1. Milestone 1 of NetBeans 6.5 now contains all features introduced in this release .

Next, in NB 6.5 M1, PHP features are a part of the "all-in-one" distribution of NetBeans, so they can be used together with all the other NetBeans features. Of course, there is still the slim PHP edition of NetBeans, targeted for PHP development specifically.

See below for more features added in NetBeans 6.5 Milestone 1, that were not present in Early Access. Also, to keep up with the new features added to NetBeans PHP support, make sure to check and bookmark the NetBeans PHP Team Blog .

Database-related code snippets

Generate code to connect to a MySQL database and to display the data in a database table. These snippets are available under the Generate Code action [Alt+Insert], just like in the Java editor.

Find Usages

Available also for PHP development. Right click the item and select "Find Usages" or hit Alt-F7.

Multiple project configurations

• running, debugging either as script or as web page in browser
• index file, arguments ...

Ajax

JavaScript Debugger

• Supported browsers
  • Firefox 2.0.0.X
  • Requires Firebug 1.1beta. An automatic installation is attempted when not found.
• Add & delete breakpoints in JavaScript code
  • Html Files
  • JavaScript Files
  • URL source resulting from server side technologies such as JSP
• Manage debugger session
• View & navigate source artifacts
  • Html Files
  • JavaScript files
  • URL source resulting from server side technologies such as JSP
• View window/frame structure
• View & navigate JavaScript Callstack
• View local variables
• Set & delete watches
• View (static) browser DOM in the IDE
• J2EE & Ruby Project integration
  • Debug Client Session: Run the project and launch a JavaScript debugging session in NetBeans, attached to the Firefox 2.0.0.X browser where the client-side application is running
  • Source Mapping: Correlate a client-side application (browser DOM) identified by a URI with the corresponding source file in the J2EE project (limited mapping in M1) Mapping for:
    • Html files
    • JavaScript files

User Guide

JavaScript Library Manager

• Utilizes NetBeans Library Manager to manage JavaScript libraries
• Wizard to add JS libraries to Java EE, Ruby, or PHP projects (Tools->Add JavaScript Libraries)

Bundled JavaScript Libraries

• Yahoo UI
• WoodStock
• jQuery
• dojo
• scriptaculous
• prototype

Java

Javadoc Analyzer

This plugin provides ability to check and fix Javadoc comments in your source code. Just select project/package/files and invoke "Source | Analyze Javadoc". Auto comment functionality is back.

Call Hierarchy

Show all callers/callees in the search scope of the selected member.

Formatting Settings per Project

You can specify formatting settings individually for each project

CamelCase code completion

Code completion improved. Just write first letters of each word in method to get smart code completion. For instance "iL" stands for invokeLater.

Improved Encapsulate Fields Refactoring

Encapsulate Fields Refactoring Improved. New options available.

Option to remove whitespace at end of line

Top voted enhancement finally implemented

Groovy

Editor

• placeholder

Java SE Project Integration

Database

Improved New Connection dialog

Now the dialog for creating a new database connection does not expect you to know the details of the JDBC URL to open a connection. If you want to modify the URL, however, you can do so, just click on the "Show JDBC URL" checkbox. Changes to the URL are reflected in the fields and vice versa.

SQL history dialog

SQL that has been executed is saved to a file in the userdir and available for viewing in a dialog and also SQL can be selected and reinserted in an existing SQL file.

Server Support

GlassFish V3 integration module.

Is now part of the Web & Java EE and Ruby bundles. No need to get the modules from the update center.

Web frameworks (Spring, Hibernate, JSF, JSF CRUD Generator, JPA)

Spring

• Improved Java class FQN completion

Code completion is now faster than the earlier version. For efficiency, Java class FQN completion is now a two step process. Most of the times, a user will need only classes defined locally in the project (source classpath). Hence the first CTRL+SPACE will list only the items in the source classpath, as shown below:

If the user wishes to add an item not in the source classpath, he can press CTRL+SPACE again. Also, if the typed prefix does not match any local item, the completion will automatically switch to show all items instead of just local items.

• Go to Spring Bean dialog

A Go to Spring Bean dialog is similar to the Go to Type dialog and will allow the user to quickly navigate to a given Spring Bean definition by it's name. The user selects the main menu item Navigate | Go to Spring Bean... or the keyboard short cut Alt + Shift + B to invoke the Go to Spring Bean dialog.

• Refactoring support for Java properties

When refactoring Java Bean property getters and setters, the corresponding usages in the Spring XML Configuration files are also modified.

Hibernate (Available via Development Update center for M1)

• Reverse Engineering support. With an existing configuration, POJOs and mapping files can be generated using this feature. See Reverse Engineering for more details

.

• HQL query execution support. Execute HQL queries right inside the IDE. Queries can include joins and clauses. See HQL Editor for more details

.

• Refactoring of hibernate mapping files is supported. See Refactoring for more details.

.

JSF, JSF CRUD Generator

The editor support for both JSF Configuration Files and JSF JSP Pages are both improved. The improved features include: Code Completion, Hyperlink, Refactoring, and Find Usage. More details can be found at Editor Support in JSF Configuration Files and JSP Files .

• Code Completion: On top of the generic JSP editing features, the JSP editor for the JSF page file provides additional code completion for Managed Beans and Resource Bundles.

Example	Code Completion UI
Managed Beans
Resource Bundles

• Hyperlink: By using the Hyperlink inside the JSF configuration files and JSF JSP Pages, developers can fast navigate from one source to another reference.

• Refactoring Support: The refactoring support processes all files in the list of JSF configuration files. Bean and Java class/method usages are found in bean and alias elements and their subelements, as well as elements in the util namespace.

Example	Refactoring UI
Managed Beans
Folder / Package

• Find usages: The JSF support will plug into the Java find usages to show JSF beans definitions which refer to Java elements (classes, methods, fields, properties). The Find Usages action will be available for bean definitions as well, to show beans used by other beans.

Example	Usages UI
Managed Beans

• The JSF CRUD Generator now applies default styles.

JPA

In NetBean 6.5, the Entity Classes from Database wizard has one additional panel to allow the user to configure the following mapping options:

• Association Fetch: can be default, eager or lazy. By default, it is default, meaning no fetch attribute will be added to the relationship annotations
• Collection Type: The collection type used for OneToMany and ManyToMany CMR fields. Can be java.util.Collection, java.util.List or java.util.Set. By default, it is java.util.Collection.
• Fully Qualified Database Table Names: if checked, catalog and schema attributes will be added on @Table. By default, it is not checked.
• Attributes for Regenerating Database Tables: if checked, nullable (when it is false), length (for String type), precision and scale (for decimal type) will be added on @Column. Unique constraints will be added on @Table if checked. By default, it is not checked.

The panel is at the last step of the wizard. It is optional.

UML

NetBeans Development is migrating UML to the NetBeans Visual Library. The majority of the planned features are now implemented in the release trunk and the Development is focused on stabilizing the code for release. The new UML will be available in M2. Please see UML Current Projects for additional information.

Mobility

Databinding

Mobility Data binding provides a simple and consistent way for applications to present and interact with data in the Visual Designer. It utilizes the Databinding libraries available in Netbeans Mobility. New custom component DataSet which provides data for UI components.

Supported components in Milstone 1:

• TextField ( Text, Label)
• ImageItem (Image, Label)
• DateField (Date, Label)
• StringItem (Text, Label)
• rest of the Items ( Label)

Databinding support in the custom property editors:

Generated code for empty DataSet:

Custom Component Support

Custom Component Support helps to create the Visual Mobile Designer Custom Components. It generates all of the necessary Custom Component infrastructure including: Module project Infrastructure, components descriptors and producers as well the layer.xml file.

New Project Custom Component wizard.

Generated project and classes with one component descriptor and one producer.

Add Mobile Custom Component wizard.

Full description of this feature i available here: Custom Components API Project Support - DRAFT

New SVG Support

Motivation is to extend group of existing SVG components to provide better support for creation of compelling UI on mobile platforms using SVG technology.

New components available in the SVG library:

• SVGForm
• Button
• RadioButton
• CheckBox
• ComboBox
• Label
• List
• Slider
• Spinner
• TextField

SVG Components in action:

Debugger

New Multithreaded Debugging Support

This is a summary description for the new Multithreaded Debugging Support that is available in M1 NB 6.5. These bits have been done as a first phase of the overall NB debugger redesign effort, which goal is to significantly improve the debugging workflow and usability.

Debugging Window

In order to improve UI for multithreaded debugging and also willing to reduce the number of debugger views, a new (unifying) debugger view is introduced. This view (referred as Debugging View) integrates current Sessions, Threads and Call Stack views being displayed in the Explorer group by default.

From the technical perspective, the Debug view is organized as (in general) a list of sessions, having each session as a list of threads, each suspended thread than expandable to its call stack and more. Debug view is customizable via context options only showing typically needed info by default. With the 'Suspend Table' switched on, any thread can be resumed/suspended by one click on the dedicated button.

If there is the debugger counter displayed in the editor and another thread encounters a breakpoint, the current thread will not be automatically switched. Instead, a non-modal panel is displayed in the bottom of Debugging view informing that there are new breakpoint hits waiting; there is also a drop-down button switching the debugger to the next (or selected) breakpoint hit. Having this non-modal notification, users are allowed to finish their debugging of current thread (e.g. expression evaluation) and switch to next breakpoint hit when it fits to the workflow.

Current Thread Chooser

When doing a multithreaded debugging, it is often needed to quickly switch between particular threads; e.g. when doing a stepping sequence in two threads alternately. For such purpose we introduce a new action--Current Thread Chooser (CTRL+8). In fact, it is an analogy to application switching common in OS environment. With this feature, it is really straightforward to revisit any thread for debugging or switch to a particular thread for the first time.

'Other Thread(s) Suspended Here' Gutter Navigation

Anytime the debugger displays the thread icon in the editor gutter, the user is informed that there is/are one or more suspended non-current thread(s) at this line. The list of these threads can be seen in the icon tooltip, and it is also possible to switch debugging to any of these threads via the context menu. Strictly speeking, it is the Source->Threads navigation available in the editor gutter.

Deadlock Detection

The debugger automatically searches for deadlock among all suspended threads. When a deadlock is detected, a non-modal notification is displayed having emphasized involved threads. Detailed monitor info is also available displayed in dedicated monitor nodes.

New Threading Model

In order to improve multithreaded debugging, we decided to change the way how debugger manages debuggee threads. The main issue related to current model (NB 6.1 and older) is likely the fact that any step resumes all threads regardless there are threads intentionally suspended by the user or not. This can be limiting e.g. in case of debugging race conditions or deadlock issues. The natural solution to this problem is to resume only the current thread leaving other threads suspended if they are (may have happened via breakpoints or Suspend action). Obviously, this change needs the default breakpoint to suspend only the breakpoint thread, otherwise stepping could lead to so-called Deadlock Caused by Debugger.

Current Model Summary (NB 6.1 and older):

• Default breakpoint suspends all threads.
• Step resumes all threads when invoked and suspends all threads when completed regardless there are threads intentionally suspended or not.
• Evaluation is done only resuming the current thread (by default), which may easily lead to 'deadlock caused by debugger' in current model.
• 'Step interrupted by a breakpoint' issue exists with default breakpoint.

New Model Summary:

• Default breakpoint only suspends breakpoint thread.
• Step only resumes current thread when invoked and suspends current thread when completed.
• Evaluation is done resuming the current thread (other threads unsuspended by default breakpoint or step). No deadlock caused by debugger might happen as far as no thread is explicitly suspended by the user (via suspend action or some breakpoint).
• 'Step interrupted by a breakpoint' issue does not exist with default breakpoint. (Except the stepping thread itself encounters a breakpoint.)

GUI Builder

ButtonGroup visualization

When you select a ButtonGroup or some component in a ButtonGroup then the GUI builder shows you which components belong into this group.

Preview in Nimbus look and feel

If you use JDK 6 Update 10 then you can preview your form in the new Nimbus look and feel. We have made this preview more reliable and accurate (within the limits of javax.swing.UIManager design). Besides the design preview you can also set the Nimbus look and feel for runtime - this is easily possible for Desktop Java Application projects in the Project Properties window (go to the Desktop App panel).

TreeModel editor

New TreeModel property editor allows you to prototype your JTree easily.

ListModel and ComboBoxModel usability enhancements

We rewrote property editors for ListModel and ComboBoxModel. It is much easier to use them by now.

Web Services

RESTful services from database

A new wizard allows for the creation of RESTful, JSR311-based services directly from database tables. This facility is in addition to the wizard that creates services from JPA entities.

Consuming popular SaaS services in Php

Web Services nodes in the Services tab of Netbeans 6.5 support Drag-n-drop to Php files as shown below.

C/C++

Code completion accuracy

Code completion accuracy is much improved in milestone 1 compared to NetBeans 6.1. There are very few known cases where an incorrect choice is presented. So the known "inaccuracy rate" is nearly 0. There are known situations where valid choices are not presented to the user. For a range of mid to large scale applications those cases (where valid choices are not shown) is under 5%. Work to further improve accuracy is ongoing.

Call Graph

Show all callers/callees of the selected function.

Direct call graph:

Reverse call graph:

Error highlighting and more types of semantic highlighting

C/C++ editors highlights basic errors. Semantic highlighting for typedefs, class fields and function names was added.

Ruby

• Rake
  • Rake Runner (http://wiki.netbeans.org/RubyRake)
  • infrastructure overhaul
    • internal unification brings more smooth workflow to users
• Debugger
  • support for conditional (expression) breakpoints
  • support for breakpoint on exception (catchpoint)
  • switched to the new engines versions
• Projects
  • useful pre-generated Rakefile (clean, gem, packages, rdoc, spec, test, .... tasks)
  • possibility to pass JVM options to the JRuby (e.g. -Djruby.objectspace.enabled=true)
• Platform
  • Rubinius Support
  • sudo support - 'gksu' so far (issue 128575)
  • Options for tweaking Gems fetching in Gem Manager (-a, -d)
• Rails
  • updated the bundled Rails to 2.1.0
  • support for running the Rails console in different environments
  • possibility to specify the version of Rails for new projects (in case there are more than one version installed)
  • support for 'destroy' in the Rails generator
• Test Runner
  • New Test Runner UI for displaying test results

这是在版本6.0beta2上的优化。经我实验，大大提高了NetBeans的启动速度.

1，修改英文netbeans界面字体大小，修改%Netbeans_home%\etc\netbeans.conf
在netbeans_default_options里加上 --fontsize 12

2，修改JVM内存配置（本机内存1G，不同内存大小不同设置）
在netbeans_default_options里加上 -J-Xmx512m，同时修改-J-Xms256m。
【说明】-J-Xms32m
此设置用于通知 Java 虚拟机将其初始堆大小设置为 32 MB。通过通知 JVM 它最初应该为堆分配多少内存，我们可以防止它随着 IDE 使用更多的内存而将堆增大。
【说明】-J-Xmx128m
此设置用于指定 Java 虚拟机应该用于堆的最大内存。对此数值设置硬性上限意味着 Java 进程不能使用比可用的物理 RAM 更多的内存。对于具有更多内存的系统可以提升此限制 - 128 MB 设置有助于确保 IDE 在 256MB 的系统上可靠地执行操作。注意：不要将此值设置为接近或大于系统中的物理 RAM 数，否则在主要回收过程中将导致频繁的交换空间操作。

3，在netbeans_default_options里修改 -J-XX:PermSize=20m
这是一个较特殊的 JVM 开关，但它也缩短了启动时间。此设置用于调整内存中“永久区域”（在这里保存类）的大小。由于我们知道所有 IDE 类均占用特定数量的内存，因此我们向 JVM 提示它将需要的内存数量。此设置消除了许多系统上启动过程中的主要垃圾回收事件。SunONE Studio 或包括更多模块的其他 IDE 的用户可能希望将此数值设置得更高些。

4，在netbeans_default_options里加上-J-Xverify:none
此开关用于关闭 Java 字节码验证，从而加快类加载，以及消除在启动过程中仅为验证目的而加载类的需要。此开关将显著缩短启动时间。

5，在Tools-Plugins-installed里面把不需要的模块去掉
我这里去掉了 Glashfish；JSF；CVS；Subversion等。速度就得到很大提高了。当然如果你的开发需要这些模块就不需要去掉了。

6，修改编辑器配置
把所有的Javadoc自动弹出窗口去掉，把所有自动完成延时设置为0，把所有自动完成大小写敏感去掉。
注：在netbeans6的JAVA代码编辑器设置里面默认没有设置代码自动完成的延时设置了。可以自己手动加入到配置文件C:\Documents and Settings\%USER_NAME%\.netbeans\6.0beta2\config\Editors\text\x-java下的properties.xml，加入
<property class="java.lang.Integer" name="completion-auto-popup-delay" value="1"/>
【说明】 preperties.xml文件默认不存在，只有在你修改了编辑器配置以后才会出现这个文件

环境设置
这一步是在NetBeans IDE内部设置。在 工具--选项--高级选项；
在 编辑器设置 中将 文本平滑   去掉（个人不喜欢这个，总感觉选上后有些字母边缘怪怪的）
在 编辑器设置--java编辑器设置 中将 自动完成弹出窗口延时 设置为1,选中自动弹出javadoc窗口
在 JAVA源代码 中将 错误标注限制 和 自动解析延迟 设置为1,另外 缺省编码 默认是GBK 建议可以改成 UTF-8.以便在移植源代码到非GBK编码平台的时候中文注释能正确显示。
在 IDE配置--建议框架 中 的3个延迟时间都改为 1

字体设置
默认情况下的NetBeans的字体真的很难看,可以将非注解的字体与字符串类型的全部设置为Courier New 14号字体，注释与字符串类型的字体设置为宋体 13号。设置完后是不是觉得很漂亮（不要打开 文本平滑 功能）

          1.NetBeans界面上的普通字体大小，可以通过配置NetBeans安装目录下netbeans.conf启动文件来实现，这个文件在<NetBeans>/etc目录下。缺省的NetBeans在使用Swing的缺省字体，大小为11，稍稍嫌小，如果要改成12，可以将文件中的下面一行：

netbeans_default_options="-J-Xms32m -J-Xmx256m -J-XX:PermSize=32m -J-XX:MaxPermSize=160m -J-Xverify:none -J-Dapple.laf.useScreenMenuBar=true"

          改成

netbeans_default_options="-J-Xms32m -J-Xmx256m -J-XX:PermSize=32m -J-XX:MaxPermSize=160m -J-Xverify:none -J-Dapple.laf.useScreenMenuBar=true --fontsize 12"

          另外，也可以通过设置Swing的一个控制字体的系统属性swing.useSystemFontSetting来实现：

netbeans_default_options="-J-Dswing.useSystemFontSettings=false -J-Xms32m -J-Xmx256m -J-XX:PermSize=32m -J-XX:MaxPermSize=160m -J-Xverify:none -J-Dapple.laf.useScreenMenuBar=true"

          2.编辑器的字体可以通过选项设置来实现，具体是Tools->Options->Fonts & Colors，这儿可以设置包含字体、前后背景等设置。刚转到NetBeans时，我就按照Eclipse和VS2003刚设置了一套设置，设置好了之后的NetBeans特别漂亮，一点都不输给Eclipse。

          3.字体锯齿问题，解决这个问题，首先你要使用Java6。Java6支持LCD和反走样(anti-alias)字体，安装Java6后，修改etc/netbeans.conf让NetBeans使用Java6。需要注意的是在Windows下需要明确打开操作系统的字体边缘平滑设置后，才起作用。设置方法是，右键点击桌面，选择外观->效果->使用下列方式使字体的边缘平滑->清晰，然后启动NetBeans就可以了。

          另外，我个人觉得NetBeans缺省的工具栏按钮太大，如果你和我有同样感觉，可以右键点击工具栏，从下拉菜单中选择Small Toolbar Icons。

你将缺省字体改为DialogInput 12就可以了。

NetBeans使用心得二：内存和垃圾收集机制配置

        NetBeans的缺省的内存配置偏低，只有128M，实际上Eclipse的缺省配置为256M，对于NetBeans这样拥有如此之多的功能，却才使用128M是不太合适的。曾经在别人的博客上看到，最佳的内存配置应该为物理内存的1/3，如果小于这个值，NetBeans就难以发挥全效，如果大于这个值就会造成操作系统内存抖动。就NetBeans5.5来说，官方网站上规定的最小内存是512M，推荐内存1G，这一点和其他Java IDE一样，比如Eclipse官方规定的最小内存居然是1G。这让我不得不叹息我们的电脑实在太落后了。我家里的工作机才256M，后来买了512M添上去，总共才768M，因此按照1/3原则，我把NetBeans设置为256M。如何设置这个值呢？同前文一样要设置启动文件 <NetBeans>/etc/netbeans.conf，打开启动文件，将netbeans_default_options一行中的-J-Xmx选项设置成256M就可以了，如下：

netbeans_default_options=="-J-Xms32m -J-Xmx256m -J-XX:PermSize=32m -J-XX:MaxPermSize=160m -J-Xverify:none -J-Dapple.laf.useScreenMenuBar=true"

         使用NetBeans的缺省配置，在长时间的运行后，往往会突然间僵住了，没有响应，这是因为JVM缺省的垃圾收集机制不使用增量式并行收集，而是隔断时间后，等内存垃圾积累到一定程度，完全锁定甚至暂停虚拟机，进行垃圾收集。可以将这种垃圾收集机制改成增量式并行收集，避免这种僵死。同样是改动netbeans_default_options，在行后加上：

netbeans_default_options=="-J-Xms32m -J-Xmx256m -J-XX:PermSize=32m -J-XX:MaxPermSize=160m -J-Xverify:none -J-Dapple.laf.useScreenMenuBar=true -J-XX:+UseConcMarkSweepGC -J-XX:+CMSClassUnloadingEnabled -J-XX:+CMSPermGenSweepingEnabled"

         总的来说，如果你懒得想这些，采用下面的配置比较不错：

netbeans_default_options="-J-Xms32m -J-Xmx256m -J-XX:PermSize=32m -J-XX:MaxPermSize=160m -J-Xverify:none -J-Dapple.laf.useScreenMenuBar=true -J-XX:+UseConcMarkSweepGC -J-XX:+CMSClassUnloadingEnabled -J-XX:+CMSPermGenSweepingEnabled --fontsize 12"

netbeans_default_options=="-J-Xms32m -J-Xmx256m0.....

J-Xms32m 等于J-Xmx256m时，运行比较顺畅

NetBeans使用心得三：保存配置和改变JDK

          NetBeans升级太快，经常需要下载新的版本安装，但一重新安装原来的辛辛苦苦的配置好了的东西都没有了。另外需要使用不同的JDK，但是重新卸载和安装netbeans又比较麻烦。如何解决这个问题？

          原来netbeans将用户的配置放在用户目录下的.netbeans目录中，在Windows下，用户目录是：

C:\Documents and Settings\<UserName>

          将该目录备份保存，可以避免重新配置的麻烦，安装新的NetBeans之后，将.netbeans中对应版本的配置拷贝到目标版本的目录小就可以了。比如我保存了NetBeans5.0的配置，现在安装了5.5，可以将原来.netbeans/5.0目录下的内容，覆盖.netbeans/5.5下的内容，你原来配置的内容包含当前workspace的状态就都转移过去了。

NetBeans使用心得四：Java平台、NetBeans平台、类库配置管理

         NetBeans项目通常来说要针对某个Java版本，NetBeans插件开发需要以来某个NetBeans平台，这些项目如果要使用第三方类库，都需要引用这些类库。NetBeans中提供了所谓Java运行时平台、NetBeans平台以及类库的配置管理。下面介绍一下如何配置和管理这些平台及类库：

1.Java平台管理：Tools->Java Platform Manager，缺省的有一个JDK的平台，如果需要添加其他版本的JDK，可以选择按钮Add Platform...，并在右边的Classes, Sources和Javadoc选择需要添加的类。再选择Add Platform这个按钮时，NetBeans会询问你JDK根目录，当找到并且选中这个目录，NetBeans会自动将Classes,Sources和Javadoc内容填好。一般如果有Sources了，可以不必选Javadoc，NetBeans会根据Sources自动生成Javadoc以便引用。Classes是用来编译和运行以及代码辅助使用的，Sources可以用于调试程序时跟踪代码，而Javadoc会被NetBeans总动索引到帮助系统(Help->Javadoc references)，以及代码辅助中显示帮助。可以肯定的说这样配置要比Eclipse方便的多。

2.和Java平台管理相似，NetBeans平台配置大体遵循上面步骤，选择Tools->NetBeans Platform Manager，然后的过程就和Java平台配置一样。

3.和Java平台和NetBeans平台配置类似，选择Tools->Library Manager配置类库。

配置好的Java运行时平台，NetBeans平台以及类库，可以通过右键选择项目的属性，在Library一栏，选择Java平台、NetBeans平台以及添加和删除第三方类库。或者展开项目树，在Libraries节点右键点击，选择New Library或者New Module Dependency。

NetBeans使用心得五：热键配置、模块管理及其他配置

         刚从其他IDE转到NetBeans后，有个不顺手的地方就是热键差别较大，非常常用的主要是代码辅助，在Eclipse是Ctrl+/，而这儿使用的是Ctrl+Space，很不幸的是大部分汉字输入法已经占用了这个热键。幸运的是NetBeans提供了修改热键的配置面板Tools->Options->Keymap。另外最新版本的NetBeans5.5还提供了Eclipse和Emacs的热键映射，这对于从eclipse和Emacs转过来的人来说无疑是天大的好消息，你不用在适应新的热键，只要在这儿选择Eclipse或者Emacs就可以了。

          另外你也可以添加新的热键，比如，我就添加了一个用于关闭工程的热键，热键配置中，选择File->Close Project，然后选择Add...按钮，选择Ctrl+Shift+Backspace，你就定义关闭工程的热键为Ctrl+Shift+Backspace。

NetBeans的模块管理负责各种插件的更新、下载、安装、卸载等。工具位于Tools->Module Manager和Update Center，这儿你可以很简单根据向导的提示更新、下载、安装以及卸载各种插件。

          其他常见配置都能在Tools->Options找到，包括：

1.General->View Java Packages as List/Tree，让你选择树或者列表的方式组织类包。

2.General->Web Browser配置缺省的浏览器。

3.General->Proxy配置Web代理，主要用于更新管理器。

4.General->Auto Update配置自动更新的方式以及频率。

5.General->Editor->General->Code Folding配置代码折叠选项。

6.General->Code Completion配置辅助代码选项：是否自动弹出、自动插入单独选项、大小写敏感、是否显示弃用代码。

7.General->Indention配置代码缩进选项。

8.General->Code Templates->定义各种快捷模式的模板

9.General->Macros配置宏变量。

          另外一些杂项可以在Miscellaneous和Advanced选项找到。常见的抱怨是辅助代码为何弹出那么慢，错误纠正为何出现那么慢，并且被认为是NetBeans慢的表现，实际这些都是可以配置的，并不是NetBeans造成的，这些配置缺省的延迟时间太长，给用户造成NetBeans速度很慢地错觉。这些设置在：

Tools->Options->Advanced Options->Editing->Editor Settings->Java Editor->Delay of Completion Window Auto Popup

Tools->Options->Advanced Options->Editing->Java Sources->Automatic Parsing Delay

           最后，如果你发现有些不想你预料的NetBeans行为，千万不要马上抱怨NetBeans不能这个，不能那个，很可能这又是一个不符合你以前习惯的地方，在配置面板找一找，也许就能找到你要的行为配置。

netbeans也有一个类似的快捷键：Ctrl + \

可以使用 IDE-HOME/etc/netbeans.conf

下表定义了可用于 IDE 的开关。

--help（或 -h）

打印常用启动参数的描述。

--jdkhome jdk-home-dir

使用指定的 JavaTM 2 JDK 版本，而不是缺省的 JDK。在 Microsoft Windows 系统上，IDE 启动程序在缺省情况下会查找注册表，使用最新的可用 JDK。

在升级 IDE 使用的 JDK 之前，应该备份用户目录。如果以后需要恢复到先前的 JDK，可以切换到已备份的用户目录，从而确保不丢失任何设置。

要切换 IDE 的用户目录，请使用 -userdir 开关，下面将对其进行详细介绍。

--cp:p additional-classpath

将指定类路径置于 IDE 的类路径之前。

--cp:a additional-classpath

将指定类路径附加到 IDE 的类路径上。

--open file

在源代码编辑器中打开文件。

--open file:line number

在源代码编辑器中打开文件，并将光标置于指定行上。

--laf UI-class-name

选择给定的类作为 IDE 的外观。以下是两个外观类的示例：

com.sun.java.swing.plaf.motif.MotifLookAndFeel

javax.swing.plaf.metal.MetalLookAndFeel

--fontsize size

设置 IDE 用户界面中的字体大小，以磅表示。如果未使用此选项，则字体大小为 11 磅。

--locale language[:country[:variant]]

激活指定的语言环境。

--userdir userdir

明确指定用户目录，该目录是存储用户设置的位置。

如果在 UNIX&reg; 环境中未使用此选项，则缺省情况下在 HOME 目录中设置用户目录。如果在 Microsoft Windows 系统上未设置此选项，则用户目录是第一次启动 IDE 时指定的目录。

可以在“关于”对话框中确定当前用户目录。选择“帮助”>“关于”。然后单击“详细信息”标签，并查看“用户目录”字段。

-J jvm-flags

将指定标记直接传递给 JVM 软件。

-J-Dsun.java2d.noddraw=true

防止使用 DirectX 进行呈现。此开关可能会防止在某些带有不合格图形卡的 Microsoft Windows 系统上出现问题。

-J-Dorg.netbeans.spi.java.project.support.ui.packageView.USE_TREE_VIEW=true

以基于目录的视图（而不是基于包的视图）显示“项目”窗口中的包。

URL https://substance-netbeans.dev.java.net/files/documents/4104/35292/org-jvnet-substance-netbeans.nbm

下载之后

工具-〉更新中心-〉手动下载安装的模块-〉添加-〉加入你刚下载文件-〉下一步知道结束

安装完毕之后单击视图菜单里面会多出几个子菜单，然后自己去看吧

如果我要设成java默认的风格要怎么样设，

能不能说清楚一点

找到文件 nb安装目录/etc/netbeans.conf

-laf UI-class-name

选择给定的类作为 IDE 的外观。以下是两个外观类的示例：

com.sun.java.swing.plaf.motif.MotifLookAndFeel

javax.swing.plaf.metal.MetalLookAndFeel

默认的是windows系统风格不用设置

javax.swing.plaf.metal.MetalLookAndFeel这个市金属的风格，是swing的风格

看看那一段，已经很清楚了

　　 原来一个再eclipse 下的web项目因为经常出兼容问题 打算转到Netbeans下，项目编码使用utf－8，再网上找了些资料，终于搞定了netbeans的编码设置：

　　1》打开项目的属性，设置编译参数： -encoding utf-8

　　 Project Properties -> Build -> Compiling Sources -> Additional Compiler Options -> "-encoding utf-8"

　　2》设置项目源文件的编码是 utf-8

　　 Select files, Window -> Properties -> Text -> Encoding -> "UTF-8".

　　3》设置 选项－－》高级--->java源文件设为utf-8

　　 Tools -> Options -> Options -> Editing -> Java Sources -> Export -> Default Encoding -> UTF-8.

　　搞定!

JDK6在Swing桌面程序上的改进很大(不说大家也知道!)

但默认配置下的NetBeans仍然 还是很慢。

下面讲讲我对NetBeans的配置看法

第一 调优JVM

    针对JVM的调优其实是最关键的一步,配置netbeans-5.5\etc\目录下的netbeans.conf文件,将netbeans_default_options替换如下

netbeans_default_options="-J-Xverify:none -J-Xms128m   -J-Xmx128m     -J-XX:CompileThreshold=10000   -J-XX:ReservedCodeCacheSize=100m   -J-XX:PermSize=120m    -J-XX:+UseConcMarkSweepGC -J-XX:+UseParNewGC     -J-XX:+UseFastAccessorMethods -J-XX:+UseThreadPriorities   -J-XX:+AggressiveOpts     -J-Dapple.laf.useScreenMenuBar=true     --fontsize 14 "

好长哦o(∩_∩)o...随便讲讲含义吧

-J-XX:CompileThreshold=10000   ：将10000个方法编译成本地代码（不利用JIT）

-J-XX:ReservedCodeCacheSize=100m ：设置缓存大小

-J-XX:+UseFastAccessorMethods   ：将所有getter / setter 转换成本地代码

第二 环境设置

   这一步是在NetBeans IDE内部设置。在 工具--选项--高级选项；

   在 编辑器设置 中将 文本平滑    去掉（个人不喜欢这个，总感觉选上后有些字母边缘怪怪的）

   在 编辑器设置--java编辑器设置 中将 自动完成弹出窗口延时 设置为1,选中自动弹出javadoc窗口

   在 JAVA源代码 中将 错误标注限制 和 自动解析延迟 设置为1,另外 缺省编码 默认是GBK 建议可以改成 UTF-8.以便在移植源代码到非GBK编码平台的时候中文注释能正确显示。

   在 IDE配置--建议框架 中 的3个延迟时间都改为 1

第三 字体设置

默认情况下的NetBeans的字体真的很难看,可以将非注解的字体与字符串类型的全部设置为Courier New 14号字体，注释与字符串类型的字体设置为宋体 13号。设置完后是不是觉得很漂亮（不要打开 文本平滑 功能）