Free swing sets software for linux

wingS is a servlet development framework for Web applications. wingS project features Swing-like components and utilizes Swing models, Swing events, and a very similar API.
A special LayoutManager allows you to place components using designer provided HTML templates. The HTML code generation of the components themself supports PLAF (Pluggable Look and Feel), so it is possible to create a different output, like plain HTML, HTML+CSS, and WML.
Enhancements:
- [WGS-198] - Exception in SSLider
- [WGS-214] - Redirects and Error Page handling broken
- [WGS-189] - Fix cookie- less session management
- [WGS-196] - Documentation Update

Swing AutoMenu is a automatic menu generator that makes it easy to create JBarMenus and popup menus from XML definitions when building GUIs in Swing.
Main features:
Bar/Popup menu
- menu item
- checkbox item
- radio button item/group
- separator
- submenus
- support icons
- named disable map
- event dispatcher
Popup menu
- invoker state item - a special item that can be enable/disable according the state returned by a named function from invoker
- invoker state check - a special item used to change some named invoker state
- hintlist - a special item that can dinamicaly build a submenu with given list itens from invoker
Enhancements:
- Some new dynamic functions were added, like a hintlist that get a list from the invoker object and builds a submenu.
- Putting a bar menu in your application can now be done very easily by using the ABarMenu class.

Java::Swing provides a Perl extension providing direct access to the Java Swing API.

Though you can write a Java program which is driven by Perl, some people may prefer to keep their Perl pure. This package lets you do that in manner similar to the way Perl/Tk and Gtk2:: provide access to their underlying libraries. This lets us code in our favorite language, while using the graphical interface capabilities of Java Swing.

Once you use Java::Swing, you can refer to javax.swing classes by their class name alone as if it name were a Perl package name. All class methods, including constructors, can be called as normal through this Perl package name.

But, if you like, you may also use Java::Swing named attribute construction, as shown for the second JTextField above. Simply supply a hash reference whose keys are attributes of the class with the proper values. Your object will be constructed by calling the empty argument constructor. Then the attribute values will be supplied by calling set accessors. So columns => 10 will translate into setColumns(10).

As of version 0.12, you may add an Object attribute to the constructor hash. Then Java::Swing will call the constructor on the underlying class which expects it, and then call set accessors for any additional attributes.

SWTSwing is a port of the SWT graphical toolkit to Swing. SWTSwing project brings portability, a bridge between Swing and SWT components, look and feel support and much more!
Go to www.eclipse.org to find more information about SWT.
Enhancements:
- This release implements more than 90% of the SWT API (against 70% in the previous version).
- It allows Eclipse 3.2 and several SWT-based applications to run quite decently.
- Moreover, SWTSwing now degrades properly to support older JREs, for example to allow running Eclipse on OS/2 with a Java 1.4.

Spring-RCPs mission is to provide an elegant way to build highly-configurable, GUI-standards-following rich-client applications faster by leveraging the Spring Framework, and a rich library of UI factories and support classes.
The Spring Rich Client Project (RCP) is a sub-project of The Spring Framework. Spring-RCPs mission is to provide an elegant way to build highly-configurable, GUI-standards-following rich-client applications faster by leveraging the Spring Framework, and a rich library of UI factories and support classes. Initial focus is on providing support for Swing applications but a goal of Spring-RCP is to be view agnostic as much as possible.
Spring Rich Client Projects goal is to provide a viable option for developers that need a platform and a best-practices guide for constructing Swing applications quickly.
Specifically, spring-richclient seeks to:
Provide a way to build structured, highly-configurable, GUI-standards-following Swing applications faster by leveraging the Spring Framework.
Foster integration with existing rich-client-related projects where it make sense. For example, jgoodies-forms and TableLayout are two good layout managers. We dont need to develop another one.
Adhere to the principles set forth by the Spring Framework--programming to interfaces; the importance of sound OO design, documentation, and testing.
Main features:
- A command framework that provides centralized configuration of Swing actions and appropriate handler registration based on the current active view. Command configuration, as well as action bar contribution policies (to menus or toolbars), can be defined centrally and externalized in Spring bean defintiions.
- A forms data binding and validation framework, for connecting edits made in your UI controls with your domain model automatically--with as you type feedback.
- Support for multiple window management, page configuration, and view management. The concepts here are inspired by Eclipses perspective/view constructs. Views can be defined in the Spring container, associated with one or more pages, and a default page can be configured to be loaded at startup.
- Common support classes addressing various rich client requirements including: well formed dialogs, wizards, input validation (typing hints and validation results reporting), button bars,internationalization, image/icon caching, progress monitoring, UI threading (classes cleanly promoting responsive UIs), treetable/property sheet, table sorting/high-volume table updates, GUI standards builders/helpers, help/about, etc.
Spring-rich adds value for people needing to develop Swing applications and do so in a way that promotes consistent, well-designed, configurable Swing applications. The spring-rich developers strongly feel the old days of Swing apps not looking native and not being performant or web-accessible are gone with JDK1.4.2 and 1.5 and webstart.
It is our belief the only problem with Swing is that there are a limited number of higher-level abstractions available that assist in making the toolkit simpler and easier to use, and a limited number of design best practices. The goal of spring-richclient is to provide that.
Enhancements:
- [RCP-400] - jgoodies forms not included as spring-rich dependencies
- Regression bug: icons on MessageAreaPane didnt show up

The Zeus Java Swing Components Library provides useful Swing components for easier GUI development. Zeus Java Swing Components Library uses only standard components to create widgets and standard patterns wherever possible.
It includes JConsole, a console replacement, JSplash, a splash screen implementation, TableSorter, which provides sorting for JTable using the tables headers, OutLookToolBar, makes JToolBar buttons resemble those of the Microsoft Outlook toolbar, WindowManager, which provides almost any functionality you need to manage all JInternalFrames within a JDesktop, SingleAppInstance, which provides a simple solution to the multiple application instances problem, SwingConfigurationManager, which provides data validation, and much more.
Enhancements:
- The old TableSorter was replaced, and all old related classes were deprecated.
- Functionality to dynamically resize a JTable based on its header and data was added.
- TypeSafe was upgraded with simple focus traversal using only the TAB key instead of CTRL+TAB for JTextArea, JTextPane, and JEditorPane.

WidgetServer (WiSer) is a Java/XML server-side GUI-framework which enables an application to run as either
- a monolithic application with a Swing GUI,
- a client/server application with a thin Swing client,
- or as an application with a rich Web client based on HTML and JavaScript
without any change!
The framework supports a mixed deployment mode, which enables one server to serve Swing clients and Web clients at the same time. A XML markup language helps to define an applications GUI.
Furthermore a common widget-based, object-oriented programming interface for Web and Swing GUIs is offered to the developer to control and assemble the GUI. This prevents from struggling with HTML, JavaScript and HTTP requests or from caring about the internals of Swing (e.g. Drag&Drop implementation).
For Swing client/server applications the framework cares for the client/server split as well as for the client/server communication including compression and security layers. The functionality of the Swing widget set is covered widely (and sometimes enhanced) in both (Swing and Web/HTML) client channels.
The project comes with a WYSIWYG GUI-builder which is completely build on the Wi.Ser-framework technology.
Main features:
- Support for internationalisation
- Standard widgets like inputfield, combobox, radiobuttons, ...
- Enhanced widgets like treeviews, table, tabbedpanes, splitpanes, ...
- XML configuration to separate GUI definition from application code
- Unified object oriented API for all targeted clients
- Support for drag&drop operations
- GridBagLayout and absolute positioning
- Support for MDI and SDI applications
- Multiple render/templatekits to support individual CIs and multiple browsers
- Preconfigured support for IE and Mozilla
- Snapshot render widget to use individual swing renderers within the framework
- DrawPane widget to create images on the fly
- GUI events like actionevent, clickevent, keyevent, ...can be received and handled on the serverside
- Plugin mechanism to exentd the framework
- Applications are deployed either into a standard servlet container
- or alternatively into the WidgetServer runtime
- Rich functionality for input validation
- GUI builder, examples and tutorial