|
|
8.1.3 AdventNet Bean Builder Experience
AdventNet Bean Builder is an Integrated Development Environment (IDE) tool, which is used for rapid development of UI based applications. You can just have some idea about the look of your application and sit with the IDE, and you will have the desired application built with in no time. Let us see in brief, the process of developing a complete application.
When you start developing any application, the first step is to gather the requirements for the application. Once the requirements are gathered, you can start developing. The various steps in the development life-cycle of an application are:
Having the requirements in mind you must proceed with the initial design of the application. The desired layout of the screen components, the expected output format and the scope / limitation of the application are to be decided upon. The IDE would help you to select the appropriate layout for the components. Bean builder has a very effective handling for the complex set of layouts provided by java. You can change layouts and fix the right one for your application.
After the design is completed, you can start developing the application.
With the initial design in place, you can start the development. Some of the important factors that you must consider while designing any screen are as follows.
Most of the commonly used screen components are there for you in the form of java beans. You can use these beans to develop your own UI for the application. You can configure these bean properties to suit your need.
You can write the code to handle the interaction between different beans in the connection wizard. It is very user friendly to handle the communication between beans.
You can also construct the menus, popup menus and the toolbars using the Screen Menu Configuration UI.
Thus the complete development can be done using the options in the IDE. On completing the screen development, the java source files are generated automatically. Thus your effort on coding is totally eliminated. Later you can check for the proper functioning of the application.
Another major step in the application development life-cycle is to check for the desired / targeted functionality in the application. A complete deployment feel / simulation is provided for you to test each and every Screen of type Panel, Dialog, NMSPanel, Frame or NMSFrame as individual Applications or Applets. This helps you to visualize the resultant application, well before the actual / real-time deployment of the application.
Now that the application is complete, you may have to maintain it for future reference. You can use the versioning system to save your project files. Bean Builder provides you with an integrated CVS (Concurrent Versioning System), for easy maintenance.
The next step is to package and deploy the application in the real-time environment.
Packaging can be done in two ways namely a NAR packaging and a stand-alone packaging. You can package the application for Web NMS by creating a NAR, which can be easily deployed. In this type of packaging you can either do a general or a device specific packaging for Web NMS. You can also create a stand-alone package.
Thus the complete development life-cycle is covered in a broad perspective. For further details on how to achieve the various steps above, you can refer to the corresponding sections inside the document.
|
|