This time, I wanna write about one book that I’m reading, this is ‘Griffon in action’ wrote by Andres Almiray and Danno Ferrin. This review describes chapters 1 and 2 …

It’s surprising how the book begins. The authors introduce us to the code immediately with the creation and running of a Griffon application: the trip of 1000 miles in one step begins…

BTW, it was awesome how the Griffon App take the natural look and feel in MacOSX, yeah!!! this mean the menu in the top of the screen and the body in the rest of the app with the aqua style…

The authors’ singular style is something important to highlight ’cause it’s funny, entertained and friendly. In addition to this, they explain of a very detailed way and step to step the development of the application.

I looked at the Griffon’s MVC very similar to Grails in structure (they’re cousins :P), however, how they communicate between them(in the MVC way) is different because they go in group. This means that the relation MVC in Griffon is  one view per controller and one domain in each group. In the other hand, Grails can use more than one domain class in controllers or views, In my opinion Grails have many very familiar concepts with Griffon

Also, the book covers the convention over configuration paradigm in a few and is applied in many parts of a Griffon App with specific folders and patterns in names of the components that we’re developing…

The authors spent working with the @Bindable annotation, this is a point essential in this chapter because it’s a very powerful tool that we allow to control the behavior of one component. This annotation is part of the AST transformations (I’ve worked with some ones like @Grab and without a doubt they’re incredible)

This chapter explains some Groovy stuff with detail to the newbies, that’s cool, Java developers can easily understand it and introduce themselves in the Groovy World :P(yeah! more groovy developers now in desktop)

It’s important to mention that all of this finally is Java, so we have the support in the JVM and all the API’s that nowadays we know and we can add them without problems, Java is a nice place to make desktop apps, but I remember when introduce myself in this kind of apps, well!!! It was a challenge to do some of them and add some behavior, paint the layout, and run it, oh my threads!!! ‘Somebody gives me another thread in my mind to think the UI and behavior at the same time’ I thought…

The bad: In Java we have to deal with some issues like ceremony in the language, UI definition  complexity, app structure, life cycle, build management(a lot, if we’re building desktop, applet’s or to webstart)

The good: Griffon avoids those traps and my knowledge in Grails helps me a lot to understand in one look how it’s structured all the Griffon App’s

After, in the second chapter I learned about the ABC of Griffon, this is:

Application.groovy, Builder.groovy, BuildConfig.groovy and Config.groovy

Each one is very important because it defines how the app is showed, assembled and runned, with all of this, I saw in detail the Griffon’s directory structure.  Also, in this chapter I can see where to put my source files, how to configure my app, how to add some external libraries and a lil’ of testing, with all of this, I explored some of the commands that we have available to work.

Something that we have to deal (also) in Java is about to be careful with the life cycle of desktop app’s (when init resources, when to release it, when it’s ready to use them), well, with Griffon all of that is solved, in some section of this chapter explain in a better way how to organize and manage an app, since the creation until I stopped it.

I`ll continue reading the book `cause my next review will be about the next 4 chapters, dealing with MVC in depth and the MVC groups..

comments powered by Disqus