Geertjan's Blog

  • September 24, 2008

2nd Attempt at Griffon Support

Geertjan Wielenga
Product Manager
I got tired of seeing the Grails icon whenever I was working with Griffon, so fashioned my own Griffon icon and then recreated the whole set of modules from scratch, with a completely fresh check out from hg. I.e., the first time I did everything on a hunch: I had the hunch that getting from Grails support to Griffon support would be a matter of branding. This time, I knew that was true, so went about it all a bit more carefully and have come up with a more reliable result. Still a few problems to fix though. Also, the Griffon support should, ideally, work in the same IDE as where Grails is found (though that's not a hard requirement, I think). So, enough things to do.

Meantime, here are the screenshots. You start with the project template:

...which creates your application and opens it inside the IDE. This time, the logical view is much better than before, with more nodes displayed:

There are many menu items on the project node, such as 'Run' and 'Compile' and so on, which all work. Similarly, on the folder-level, you can choose menu items which pop up GUIs for creating the Griffon artifacts, like controller, views, etc, via the actual Griffon scripts in the official Griffon distro that do the work under the hood. I'm hoping to be able to make some kind of distribution available in the Plugin Portal soon.

Join the discussion

Comments ( 2 )
  • Mark Chance Wednesday, September 24, 2008


    That would be VERY nice! I am quite excited about the prospects of Griffon - finally making GUI developement, especially with Swing, at long last, not exceedingly tedious. (I could go into how I was just waiting for an excuse to jump into Python or Scala - if only there was explained some cool thing that either of those did for Gui/Swing development...)

    I actually like and have had reasonably good luck with the Gui Building in NB 6.x/JDK 1.6 - but a) it's still a lot of code, even if it is generated and there seems to be a bug where if you change the base class of a JPanel form for instance, it can't re-load the form... and b) MigLayout might solve a layout issue where I want the components to all expand proportionally on re-size.

    I had just started through your last cookbook for NB support, and made it to step four before getting overwhelmed/tired/etc.

    BTW - I tried the nbgriffonsupport page at java.net, but although I logged in, I was not authorized to view the page. Are we still waiting for some sort of approval that Allan was alluding to?

    Staying tuned...


  • Todd Thursday, September 25, 2008

    How does Griffon compare with the NetBeans RCP? When would you use one over the other?

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