{"id":84,"date":"2009-04-01T21:32:52","date_gmt":"2009-04-02T06:32:52","guid":{"rendered":"https:\/\/www.kellyrob99.com\/blog\/?p=84"},"modified":"2009-04-21T20:21:28","modified_gmt":"2009-04-22T05:21:28","slug":"the-first-two-chapters-of-griffon-in-action","status":"publish","type":"post","link":"https:\/\/www.kellyrob99.com\/blog\/2009\/04\/01\/the-first-two-chapters-of-griffon-in-action\/","title":{"rendered":"The first two chapters of Griffon In Action"},"content":{"rendered":"

Documentation up until now has been sparse to be sure, but judging by the first two chapters of the MEAP<\/a> for Griffon in Action<\/a>, this book is going to be worth every penny.<\/p>\n

I’ve experimented a bit with Griffon<\/a> a bit lately, but still being somewhat of a Groovy<\/a> noob, I don’t think that the full impact hit me until I started reading the book. Maybe part of the problem is not that it’s hard to understand, but that it’s hard to believe that it’s so easy.<\/p>\n

A very clearly defined way of separating the classic MVC<\/a>. Injection of views, models, controllers – all available by convention not by annotation, xml configuration or even having to a refer to a component by name. The transparent access to a variety of builder actions through plugins makes a large toolset available with little or no cost. Clear architectural boundaries exist that guide you to where your code should be developed. The Griffon framework, created with gracious acknowledgement to its forerunner Grails<\/a> strives to do one thing above all – make Swing easy.<\/p>\n

The power and versatility of Swing has always been obvious to me. The ‘magic sauce’ that makes large scale Java Swing applications behave in any sane way has been a little more hazy. The advent of SwingWorker and other enhancements to the Swing toolset and the availability of better documentation have certainly made the landscape a lot more tolerable, but at the end of the day, it’s still hard to even find good examples of large Swing apps to use as a guideline(well at least it has been for me.) On the other side of the spectrum, I’m not sure there IS such a thing as a small Swing app. The amount of boilerplate code required is cumbersame, to say the least, and between anonymous inner classes for actions\/listeners and correct handling of business logic and the EDT<\/a> by the time you’ve finished doing anything moderately significant you’re already a couple 1000 lines in.<\/p>\n

Griffon takes all that and hides it behind a curtain. Expanding on the already powerful SwingBuilder capabilities, it provides a quick and easy way to develop complex Swing applications. Utilizing @Binding to provide easy view\/model interaction and baking the Observer pattern right into the framework make it beyond simple to deal with GUI<\/a> events. And the pattern for dealing with EDT issues couldn’t be much more straightforward.<\/p>\n

\r\n\r\ndoOutside {\r\n.... do whatever you need to do off of the EDT\r\ndoLater { ... come back to the EDT when you're done to update widgets }\r\n}\r\n\r\n<\/pre>\n
I’m pretty sure that’s an easy enough pattern that I will never again forget the cost of doing… well pretty much anything that takes +1 second while blocking the EDT.<\/p>\n
Personally, I’ve run into a couple of unexpected results when trying to utilize the webstart version of the application, but other than that everything has worked exactly as advertised. And at the end of the day I’m willing to chalk that up to my misuse of the system. I’ll tell you for sure when I get to that chapter of the book. Which will probably be about 2 days after the authors publish it.<\/p>\n
\ud83d\ude42<\/p>\n
So far my impression of the pre-release chapters of the book are pretty good – well written, clear and above all – the code samples work. Kudos to the authors Andres Almiray<\/a>, Danno Ferrin<\/a> and Geertjan Wielenga<\/a>.  Look forward to the rest of the book boys, and to writing some new Swing apps with Griffon!<\/p>\n
\"Reblog<\/a>