||This article includes a list of references, related reading or external links, but its sources remain unclear because it lacks inline citations. (February 2014)|
||This article may require cleanup to meet Wikipedia's quality standards. (September 2008)|
|Original author(s)||Danno Ferrin, Andres Almiray, James Williams|
|Initial release||September 10, 2008|
|Stable release||2.2.0 / March 1, 2015|
|Type||Rich Client Platform|
|License||Apache License 2.0|
Griffon is an open source rich client platform framework which uses the Groovy programming language (which is in turn based on the Java platform). Griffon is intended to be a high-productivity framework by rewarding use of the Model-View-Controller paradigm, providing a stand-alone development environment and hiding much of the configuration detail from the developer. A significant portion of the build environment is directly derived from the Grails codebase and hence follows many of its conventions.
The first release is the fruit of the effort by the Groovy Swing team and an attempt to take the best of rapid application development, as indicated by its Grails-like structure, the agility of Groovy, and the availability of components for Swing.
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-app <APP_NAME>
The 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.
Griffon can be extended with the use of plugins. Plugins provide run-time access to testing libraries such as Easyb and FEST, and all widget libraries besides core Swing are provided as plugins. The plugin system allows for a wide range of additions, for example
- Polyglot Programming with Clojure, Scala, JavaFX and Erlang.
- Additional UI toolkits - SWT, JavaFX, Pivot, GTK
- SQL and NoSQL datastores like Berkleydb, CouchDB, Db4O, Neo4j, NeoDatis, Memcached and Riak.
- 2D and 3D games using popular Java libraries like jME (JMonkeyEngine), LWJGL, Slick2D, JOGL and Processing.
Features that would eventually become integral parts of Griffon (UI builders) were featured in these books:
- Groovy In Action (published by Manning)
- Beginning Groovy and Grails
Books that cover Griffon:
- Griffon In Action (published by Manning)
- Beginning Groovy, Grails and Griffon
- GroovyMag for Groovy and Grails developers
- Article by Guillaume Laforge (Project Lead of the Groovy Language) : Griffon shows its claws: Grails-like rich Swing client framework released
- Articles by the Griffon team : Griffon and Greet: Starting to get Groovy Revisiting the hidden threading rule, Griffon takes flight, Awakening the Griffon
- Article by a technical writer in the NetBeans Docs team at Sun Microsystems: Notes on Converting NetBeans Grails Support to NetBeans Griffon Support, The 5 Best Things About Griffon , Griffon: Identifying the Dark Underbelly of Java