Site Contents
Wikispaces topics
Wikispaces topics
- Principles for Addons
- Documentation for Addons
- Addon components on this site
- Utility functions
- SiteTOC
- Remove Addon BRs
- Customizations & Fixes
- Notes about Wikispaces
- Tests
- WS features Test
- CSS
- Javascript
- Misc
- Collaboration/CMSs
- Notes on features
- Drupal investigations
- Drupal docs study
- Software development
- Fonts
- Java
- JavaScript/CSS
- Trees and TreeGrids
- JavaScript frameworks
- PHP
- Python
- Organization for common modules
- Packaging and deployment examined
- Packaging and deployment notes
- Distutils, setuptools, pip sleuthing
- Environment and Launcher
- Python features and libraries
- Miscellaneous
- Arduino and AVR
- Delphi
- Matlab
- ANTLR
- Process management
- Microsoft Access
- Linux
- Visio
- Economics
- "Making"
- Laser cutter notes
- Motor notes
- DIY Bio
- Includes
- For pages
- zhtml_pageinfo
- util_authordate (deprec)
- Test
- For pages
- Admin
- Addon Components, V.old
- Left-overs
Table of Contents
Revised by: gwideman, Jun 6, 2012 4:22 pm (3 revisions)
This page collects notes on getting oriented to desktop app structure in Java.
Frameworks for desktop applications
RCP = "Rich Client Platform"Swing Application Framework (JSR 296)
Better Swing Application Framework BSAF:
Spring RCP
Eclipse RCP
NetBeans Platform
JIDE
Tentative conclusion
The Swing conventions for components already provides a basic application framework, in that it includes a standard way to build a hierarchy of visual components, including management of their display, and event detection and dispatch. There are a number of higher-level services that a desktop app might need, but it seems that lack of agreement on what those should be has resulted in the open app framework initiatives (JSR 296 and spin-offs) stalling.So that leaves some commercial Desktop App Frameworks (eg: JIDE), and the app frameworks that are the basis of particular IDE applications, namely Eclipse RCP and NetBeans RCP.
Controls, components
AWT
Swing
JavaFX
SWT (Standard Widget Toolkit)
JIDE Swing components
Java Beans
A JavaBean is a Java Object that is serializable, has a 0-argument constructor, and allows access to properties using getter and setter methods. (Swing visual components are Java Beans.)Layout managers
"Layout manager" is the term for the component which positions and sizes the controls "on a form" (within a Frame? Panel?).GUI form "designers" or IDEs
Eclipse?
IntelliJ IDEA
NetBeans
JFormDesigner
JIDE
Data-aware components
Misc questions
In order to operate within a framework, controls or components presumably have to follow a particular convention (ie: offer a particular interface/API). What are the conventions?How does Beans fit in here?