similarities :
rendering -> graphic library -> plaform AWT -> SWING -> NETBEANS PLATFORM -> jsr 296 SWT -> JFACE -> eclipse rcp
the rendering toolkit provides the main features for drawing canvas, tags, text, combobox, ...
the graphics library introduces MVC templates, higher-level components (sortable tables, date picker ...)
platform helping modular applications consisting of modules, expanding the capabilities of other modules. It also adds enterprise features such as background tasks, deployment solution, help mechanism, saving settings, ...
difference
swt:
- appearance,
- own implementation resource (font, images, ...) must be deleted by the developer. layers on top (jface, eclipse) is trying to limit the leak of these resources.
- most OS supported.
- Swt components may contain awt / swing components
- constructor-based api for container / component relationship (new child (parent))
awt / swing:
- jvm implementation implements a specific os implementation
- unless you use a different look, you see that the application is not native
- api compilation for container / component relationship (parent.add (child))
eclipse:
- based on osgi to host plugins;
- this provides reliable dependency resolution, multiple versions, ...)
netbeans rcp:
- specific implementation for plugins not using osgi repeatedly.
mestachs
source share