Nifty 1.3 has been released
// June 26th, 2011 // Uncategorized
Nifty 1.3 is done! Finally!
Get it here:
- Nifty 1.3 Download Folder at sf.net
- Nifty 1.3 Maven Projects Page (You can browse the JavaDoc online here)
When you’re using Maven, you can simply add our sf.net Nifty Maven Repo to your pom.xml:
and then you can add this dependency:
lessvoid nifty 1.3
Here are some quick informations about 1.3.
Lots of Changes
There have been well over 200 changes! Nifty 1.3 fixes a lot of bugs and adds a lot of new features.
To summarize Nifty 1.3 you could say this is the “controls” release of Nifty. Nifty 1.3 was mainly targeted on improving and extending the nifty-default-controls project. The existing controls have been revised/rewritten and lots of new controls have been added. You can find an overview and details about the new controls in the Nifty wiki.
If you’ve used controls with Nifty 1.2 then you’ll need to update your projects since the 1.3 controls are not backward compatible with the old ones :/ Well, the XML part is still working the same but interacting with the controls from Java has changed.
Besides this most of the Nifty core elements (Panel, Image, Text) should work as before. The only difference is that the label element has now been removed and replaced by a label control. So when you’ve used labels before you need to change them as well. This was described before in a former blog post too.
Another new feature is the Java Builder pattern that you can use to create GUIs from Java without any XML at all. This feature was described in a former blog post and has now been extended to work with all of the new controls and with the build-in core elements alike.
And a new Demo of course
And here is the Nifty 1.3 controls demo:
If you’re unable to run the demo above, you can watch the video instead:
More in future blogs posts…
PS: Nifty 1.3 will put the support for the nifty-style-grey on hold for some time. This means that this alternative style is currently not updated to be compatible with 1.3. This is just because of lack of time. We might eventually come back to that style later or if we find a maintainer for that style. Interessted? Contact me!