## Working with Rich-Client Applications

The following table outlines the development cycle of rich-client applications, from creation to distribution.

Set up the application | Begin creating your application by using the module suite project template. Optionally, before going further, brand the application by providing a splash screen and other external customizations, as described in step 6 below.
Develop the application | Begin creating each distinct part of your application by using the module project template. Right-click a module project in the Projects window and choose New > File/Folder. In the New File wizard, choose the best NetBeans API template for your programming needs. After using a wizard, double-click the file that you would like to edit. Use the Source Editor to edit the file. Refer to the
Build the application | Choose Build > Build Main Project or right-click any project and choose Build Project.
Try out the application | Right-click a module suite project node and choose Run Project.
Brand the application | Right-click the module suite node in the Projects window and choose Properties. Use the Application panel and Splash Screen panel to brand the application. In the Application panel, specify a branding name for the executable, an application title for the title bar, and an icon for the Help | About dialog box. In the Splash Screen panel, specify a splash screen and a progress bar.
Distribute the application | You can distribute the application in one or both of the following ways: Create a ZIP Distribution Right-click the module suite node and choose Build ZIP Distribution. The application's executable and its clusters are packaged in a ZIP distribution. Distribute the ZIP file. Create a JNLP Application Right-click the module suite node and choose Build JNLP Application. The application's JNLP files are created. Put the JNLP application on a host.
Distribute updates to the application | Right-click the module suite project and choose Create NBMs. An NBM file is created for each module project in the module suite project. In addition, an autoupdate descriptor is created. Distribute the NBM file for installation via the Update Center wizard.

Legal Notices