Free swing software for linux

SwingWT is a 100% pure Java library which aims to be a free implementation of Swing and AWT. Unlike Swing, SwingWT drives native peer widgets for your platform from SWT. You can see a screenshot of the basic SwingWT demo here (Linux/GTK2) and here (MacOSX).
Main features:
- More responsive GUIs and faster startup times
- Less RAM usage for applications
- Many developers prefer the Swing API
- Existing Swing applications dont need to be recoded
- Mature Swing UI designers can be used
- Developers deploying to *nix/Win32 can compile natively with GCJ and the applications can be distributed without a VM. Linux distribution makers could package many existing Java/Swing applications that previously could not be distributed in workable state.
- SWT components can be directly accessed through the API, allowing mix and match (make Eclipse plugins with Swing!)
- All platform benefits such as font sub-pixel decimation for LCD monitors (unavailable in Swing)
- Use Swing on mobile devices!
- The best of both worlds! New Swing components for JClosableTabbedPane, JCoolBar, JTaskTrayItem..
- A FREE implementation of Swing you can redistribute and modify to suit your own requirements
- Insulation from changes to the SWT APIs
- Insulation from differences between SWT platforms
Enhancements:
- This release contains many fixes and compatibility improvements, including support for AudioClip and SWT 3.2.

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.

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.

JCalendar is a Swing component for selecting a date. JCalendar is easy to configure, highly customizable, and has an attractive user interface. The distribution includes a demo application so that you can preview your customized component.
Main features:
- Easy to configure
- Highly customizable. See properties.
- Attractive user interface

Swing XML Authoring Tool is a Swing-based authoring tool for the quick and easy development of GUI Java applications.
It implements out-of-box a true MVC framework and uses XML to define the view (SwiXml is used as the XUL engine), BeanShell as a scripting language for the controller, and JXPath as the binding mechanism between the view and model.
Swing XML Authoring Tool provides a complete environment in which it is possible to almost write an entire Java Swing application without writing Java compiled code. The use of XPath makes it very simple to traverse the object tree of the applications business model.
It takes a lot of work to develop a Swing application, laying out and configuring GUI components, and then integrating them with the application functionality. SwiXAT addresses both of these issues by providing a framework based on a complete implementation of the MVC architectural pattern.
The benefits obtained by a such framework are the followings:
- Architectural Correctness: By adopting a true MVC (Model View Controller) based framework, it is very easy to correctly implement any UI application. Its not difficult to write a Java/Swing application, but whats very difficult is to build a good, well designed Swing application, where the adoption of the MVC paradigm permits to reduce the maintenance costs, thanks to the clean separation between the view and the application logic.
- Development Speed: The adoption of a framework reduces the development cost by providing out-of-box, well integrated and easy to use common features, like wizards, plugins, support for MDI interfaces, etc. Moreover, the use of XML to define the user interface, as well as the adoption of an interpreted scripting language, permits to implement the Code&Test development style, where the compilation time is reduced to zero.
- Code Reuse: The net separation between the view and the control logic permits to write reusable modules that can be combined in several manners. The developer is naturally induced to modularize the application and write reusable code, minimizing the effort of building new applications or adding new functionality to existing ones.
SwiXAT is all the above, and we hope youll appreciate our effort.

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

Todays applications tend to be skinnable: cdplayers, email notifiers, even operating systems. SkinLF project provides a skin system for Java programs.
Skin Look And Feel allows Java developers to write skinnable application using the Swing toolkit. Skin Look And Feel is able to read GTK (The Gimp Toolkit) and KDE (The K Desktop Environment) skins to enhance your application GUI controls such as Buttons, Checks, Radios, Scrollbars, Progress Bar, Lists, Tables, Internal Frames, Colors, Background Textures, Regular Windows. Skin Look And Feel (aka SkinLF) also includes NativeSkin to create irregular windows.
Enhancements:
- This version includes a patch addressing a threading issue in popup menu animation.
- Several changes were made to reduce a potential memory leak when using disabled buttons.
- SkinLF was updated to Laf-Plugin 0.2 (from https://laf-plugin.dev.java.net/).

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