Overview
Griffon aims to reduce the typical confusion that occurs with traditional Swing development. Due to the MVC structure of Griffon, developers never have to go searching for files or be confused on how to start a new project. Everything begins with:
griffon create-appThe generated project follows this structure:
%PROJECT_HOME% + griffon-app + conf ---> location of configuration artifacts like builder configuration + keys ---> keys for code signing + webstart ---> webstart and applet config + controllers ---> location of controller classes + i18n ---> location of message bundles for i18n + lifecycle ---> location of lifecycle scripts + models ---> location of model classes + resources ---> location of non code resources (images, etc) + views ---> location of view classes + lib + scripts ---> scripts + src + main ---> optional; location for Groovy and Java source files (of types other than those in griffon-app/*)The builder infrastructure enables seamless integration of different widget libraries such as Swing, JIDE, and SwingX.
Griffon’s built-in scripts include targets for desktop, webstart, and applets. The baseline requirement is Java 5 or higher.
In the first release, three sample applications are included :
- Greet, a Groovy Twitter client featured in the JavaOne 2009 Script Bowl,
- FontPicker, an application to view the available fonts on one's machine,
- SwingPad, a lightweight designer application for Griffon user interfaces.
Read more about this topic: Griffon (framework)