For Java developers writing GUI layouts by hand that wants simplicity, power and automatic per platform fidelity, that are dissatisfied with the current layout managers in Swing and SWT, MiGLayout solves all your layout problems. Unlike JGoodies' FormLayout and Clearthought's TableLayout - MiGLayout solves all your layouts with equal ease in a way that is easy to change and maintain. You will understand how the layout will look like when looking at the code.
MiGLayout is the most versatile and flexible Swing and SWT Layout Manager for Java, yet it is very easy to learn and use. It is using String or API type-checked constraints to format the layout. MiGLayout can produce flowing, grid based, absolute (with links), grouped and docking layouts. You will never have to switch to another layout manager ever again! MiGLayout is created to be to manually coded layouts what Matisse/GroupLayout is to IDE supported visual layouts.
Java SwingBuilder is an implementation of a Java Builder geared towards building UI interfaces using Java Swing.
Details
The main class is org.javabuilders.swing.SwingBuilder. It loads the object definition from a YAML file that is in the same package and has the same base name as the calling Java class. So, if you're building org.test.MyFrame.java it will look for org.test.MyFrame.yaml for the object build file (similar to the convention the Apache Wicket web framework uses).
We all know how long it can take to learn a new DTD, XML schema, or an object model for an object-relational mapping. Some of these documents can be 20 pages or longer, and while XML is undoubtedly useful, let's face it - reading through 20 pages of XML is not a walk in the park.
This is why we created Linguine Maps.
Linguine Maps is an open-source Java library that conducts programmatic visualization of various text files, generating from them easy-to-understand entity-relation diagrams. With a diagram it will take you and your team minutes now, instead of perhaps hours, to get familiar with new schema, object-relational mappings, or DTDs. And you can always go back to the source files when more details are needed. Curious what this looks like? There is an image gallery with many samples!
All diagrams produced by the Linguine Maps are precise reflection of the source code. There is absolutely no manual work! It is fully automatic! Try it online now!
In this release we support programmatic visualization for:
* WSDL; for these files we draw relations between service, ports and port types
* Apache ANT build files; for these files we draw task dependency diagrams
* Document Type Definition (DTD) for XML documents; for these files we draw relations between various entities and their attributes
* Apache ObJectRelationBridge (OJB) mapping files; for these files we draw UML-style class diagrams
* Hibernate mapping files; for these files we draw UML-style class diagrams
Programmatic visualization offers a very effective communication tool for software development teams. Integrated into the build process?, it helps to keep documentation up to date automatically. All members of your development team now can have a common set of visual documents, constructed automatically from the source code. The idea was floating around for a while, but we find that our approach has a key advantage.
Foxtrot is an easy and powerful API to use threads with the JavaTM Foundation Classes (JFC/Swing).
The Foxtrot API are based on a new concept, the Synchronous Model, that allow you to easily integrate in your Swing code time-consuming operations without incurring in "GUI-freeze" problem, typical of Swing applications.
While other solutions have been developed to solve this problem, being the SwingWorker (see also here for an update) the most known, they are all based on the Asynchronous Model which, for non-trivial Swing applications, carries several problems such as code asymmetry, bad code readability and difficult exception handling.
The Foxtrot API cleanly solves the problems that solutions based on the Asynchronous Model have, and it's simpler to use.
Your Swing code will immediately benefit of:
* code symmetry and readability
* easy exception handling
* improved mantainability
My talk was on building an application that rescued princesses. The goal was to give interaction designers some insight into how game design might be applied to the domain of more utilitarian applications. The talk was recorded and should be up sometime this week. When it appears online, I'll link to the video from this post.
Pivot is an open-source framework for building high-quality, cross-platform applications that are deployable both via the web and to the desktop. It began as an R&D effort at VMware but has now been made available to the community as an option for developers who want to build rich internet (RIA) applications in Java.
Sample Pivot application
Pivot applications are written using a combination of Java and XML and can be run either as an applet or as a standalone (optionally offline) desktop application. While Pivot was designed to be familiar to web developers who have experience building AJAX applications using HTML, CSS, and JavaScript, it provides a much richer set of standard widgets than HTML, and allows developers to create sophisticated user experiences much more quickly and easily. Pivot will also seem familiar to Swing developers, as both Swing and Pivot are based on Java2D and employ a model-view-controller (MVC) architecture to separate component data from presentation. However, Pivot includes additional features that make building modern GUI applications much easier, including declarative UI, data binding, effects and transitions, and web services integration.
I'm Kirill Grouchnikov and this blog is about user interfaces, imaging and related topics. Half the time i spend writing the code i create new bugs, and the rest i try to chase and fix them without creating too many new ones. For now it seems to be a lost battle.
Sage lets you build rich, highly functional, cross platform web-enabled desktop applications and applets by simply marking up the UI and attaching JavaScript (or Ruby, Python, etc.) event handlers. You simply point sage to a URL and it downloads the markup and accompanying scripts and renders the application or applet in real-time (the same way a browser renders documents). All that is required to run Sage is a Java Virtual Machine (v1.5 or later, v1.6 preferred).
[fleXive] is a JavaEE 5 open source (LGPL 2.1 or higher) framework for the development of complex and evolving (web-)applications. It speeds up development by easing many tedious and repetitive programming tasks and helping to keep your application(s) flexible during the development-cycle and in production.
Based on the latest industry-standards like EJB 3, JSF, etc. [fleXive] should be your choice for building up your own new application.