2. Rich Client
•In a client server architecture the term rich client is used for
clients .
•Data Processing occurs mainly on the client side.
•Graphical user interface.
•Extendable via plug-in and modules.
•Typically developed on top of framework.
3. Rich Client Platform
•A rich client platform is an application lifecycle environment, a
basis for desktop applications.
•Most desktop applications have similar features, such as
•menus, toolbars, status bars, data displays, the saving and
loading of user-specific data and configurations,
internationalization, help systems, etc.
•Rich client platform provides a framework with which these
features can quickly and simply be put together.
5. The Need For NetBeans Platform
Don’t write another framework, Please
Rest in Piece Home made Frameworks
6. NetBeans Platform
For Rich client development
•100% Java
• No necessary 3rd party libraries
•Swing
• The most standard java toolkit
•Module System
• NetBeans-specific modules system
• Standard OSGI module system
•Build System
• Ant , Maven
•JDK Support
• So many JARs from the NetBeans platform are in the JDK too.
7. Why Need Modular Application?
What if this is
Your
Application codebase?
8. Why Need Modular Application?
What if this is
Your
Application codebase?
9. The Need For Modular Application
•Application get more complex
• Simplifies scalability in terms of requirements
•Assembled from pieces
•Developed by distributed teams
• Helps to keep codebases maintainable
• More flexibility, less coupling.
•Good architecture
• Know dependencies
• Manage dependencies
In a client server architecture the term rich client is used for clients where the data processing occurs
mainly on the client side.
Often rich clients are applications that are extendable via plugins and modules. In this way, rich clients are able to solve
more than one problem.
Most desktop applications have similar features, such as menus, toolbars, status bars, progress visualizations,
Why we need NetBeans platform, Because if we making or maintaining our own framework to build rich client applications, it is just waste of cost and time.
The NetBeans IDE is a very good example of a modular rich client application. This is picture of conceptual structure of the NetBeans IDE, here you can see it build on netbeans platform, on top of it contain Netbeans ide specific modules,
NetBeans runtime container, ensuring that the application always starts up in a consistent state.
NetBeans Platform makes many API modules and service provider interface (SPI) modules available,