View RSS Feed

Java Swing

Pluggable look-and-feel architecture

Rate this Entry
by , 04-26-2012 at 07:38 PM (903 Views)
Look and feel, plugable architecture of swing provides one component API, with no dictation of look and feel. A default look and feel set is provided by the swing toolkit. API is considered as “open”, a design which allows additionally developers to make new implementations of look and feel, either by extension of present look and feel or by creating a new one. Pluggable look and feel is although extensible but it was designed intentionally at that level lower than basic component API. This is done in a way that intricate details are not needed to be understood by the developers for building Swing GUIs.

Developers are not advised to create look and feel implementations. PL&F is considered as quite powerful sort of feature for application’s subset which develops a unique identity. GUIs are ideally created by PL&F which are accessible to the disabled users, like those users who don’t have ability to use the mouse etc.
Pluggable Look and feel means that implementation of component which deals with look (presentation) & feels (event handling) has been delegated for separate UI that might change during runtime.

Submit "Pluggable look-and-feel architecture" to Facebook Submit "Pluggable look-and-feel architecture" to Digg Submit "Pluggable look-and-feel architecture" to del.icio.us Submit "Pluggable look-and-feel architecture" to StumbleUpon Submit "Pluggable look-and-feel architecture" to Google

Comments