Comments on: Groovy DSL steps http://www.warneronstine.com/2007/06/05/groovy-dsl-steps/ Where technology and art disappear Wed, 17 Nov 2010 10:52:45 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Graeme Rocher http://www.warneronstine.com/2007/06/05/groovy-dsl-steps/comment-page-1/#comment-108 Graeme Rocher Thu, 01 Jan 1970 00:00:00 +0000 nteresting, though I find that in the beginning it seems like a good idea to extend BuilderSupport, but later you realise it is too limiting and overriding invokeMethod is far more flexible as far as the syntax options you have available to you It of course depends on the DSL you are writing Cheers Graeme nteresting, though I find that in the beginning it seems like a good
idea to extend BuilderSupport, but later you realise it is too
limiting and overriding invokeMethod is far more flexible as far as
the syntax options you have available to you

It of course depends on the DSL you are writing

Cheers
Graeme

]]> By: Warner Onstine http://www.warneronstine.com/2007/06/05/groovy-dsl-steps/comment-page-1/#comment-109 Warner Onstine Thu, 01 Jan 1970 00:00:00 +0000 This comment came from [Guillaume Laforge](http://glaforge.free.fr/weblog/) (Groovy lead) on the Groovy users list: >This is a nice wrap-up of the steps to follow. The thing I feel is missing a little is the "invention" of the DSL in itself with the end-user. I think we have to stress that part more. You have to know what's possible to do with Groovy in terms of DSL, you have to speak at length with your users, and incrementally design on paper (or on screen) what the DSL will look like. I think this step should be emphasized a bit more in the approach. This comment came from [Guillaume Laforge](http://glaforge.free.fr/weblog/) (Groovy lead) on the Groovy users list:
>This is a nice wrap-up of the steps to follow.
The thing I feel is missing a little is the “invention” of the DSL in
itself with the end-user.
I think we have to stress that part more.
You have to know what’s possible to do with Groovy in terms of DSL, you have to speak at length with your users, and incrementally design on paper (or on screen) what the DSL will look like.
I think this step should be emphasized a bit more in the approach.

]]> By: Warner Onstine http://www.warneronstine.com/2007/06/05/groovy-dsl-steps/comment-page-1/#comment-110 Warner Onstine Thu, 01 Jan 1970 00:00:00 +0000 Guillaume, I definitely agree. I wanted to come up with some basics, but the user-level involvement definitely has to be there. It's hidden right now in the Prototype phase I talk about, but should be more fully discussed in a future post. I have several posts in my head right now so I'll jot this down as one to write up ;-) Guillaume, I definitely agree. I wanted to come up with some basics, but the user-level involvement definitely has to be there. It’s hidden right now in the Prototype phase I talk about, but should be more fully discussed in a future post. I have several posts in my head right now so I’ll jot this down as one to write up ;-)

]]> By: Leo http://www.warneronstine.com/2007/06/05/groovy-dsl-steps/comment-page-1/#comment-111 Leo Thu, 01 Jan 1970 00:00:00 +0000 Hey, Warner. I left made a response on <a href="http://u.arizona.edu/~przybyls/2007/06/embedding-internal-dsl-using-kuali.html">my blog here.</a>. It's always a great idea to outline a systematic approach like you have. A lot of people fail to do that, and they end up buying books that tell them how just to get that much out of it. Very good. I hope it helps a lot of people. Hey, Warner. I left made a response on my blog here.. It’s always a great idea to outline a systematic approach like you have. A lot of people fail to do that, and they end up buying books that tell them how just to get that much out of it. Very good. I hope it helps a lot of people.

]]>