Geertjan's Blog

  • September 12, 2008

The 5 Best Things About Griffon

Geertjan Wielenga
Product Manager
I created the whole NetBeans API Javadoc viewer described in Flying with Griffon in NetBeans IDE 6.5 (Dev), using my tweaked Grails modules. The Swing application and applet are created via the same "griffon run-app" process, with this result:

However, the application (i.e., Swing application, applet, and JNLP) could have been created without NetBeans IDE, of course. Simply follow the steps described there from a command prompt, with a text pad, and you'll end up with the same result. The NetBeans IDE modules do nothing magical for Griffon (same with Grails), other than provide a GUI which replaces the command prompt.

And here's what I like best about Griffon so far:

  1. I can use Groovy.
  2. I can reuse everything I learned from Grails.
  3. I am almost forced to think in an MVC-way about my Swing application.
  4. At the end, for no extra effort whatsoever, I not only have a Swing application, but also an applet and a JNLP application.
  5. Griffon is under active development by people who know what they're doing, having learned from the successes and mistakes of Swing, in a modern context, so I'm expecting the best of all worlds within a single framework.

Join the discussion

Comments ( 2 )
  • KoW Saturday, September 13, 2008

    Wow, this looks like a killer framework! Jeez, yet another one to try...

    What do you think are the competitors (meaning swing based RAD frameworks)?

  • David Rozenberg Saturday, September 13, 2008

    I am surprised to read your comment that you were forced to think in an MVC-way as if you as everybody else thinks differently. It is the only way we all deal with each other and the environment. Statements that anybody is not using MVC looks ridiculous to me. You need to think why 30 yesr ago when MVC was invented the author did not publish his findings and did not do that for 15 years. Only the GoF book tried to popularize it, but in a very narrowed fashion (based on the perception of the Smalltalk team).

Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.