|
|
Index: Home | What Is Izumi | Misc Links | Random Thoughts | Too Much To Read | The Rant Vault | Quotes
Ah ah:
retrieving revision 1.141 retrieving revision 1.142 Merging differences between 1.141 and 1.142 rcsmerge: warning: conflicts during merge cvs update: conflicts found in Ralf
Elsewhere:
Stats for album Sam - Chris and sub-albums: 29,157,302 bytes used by 1,548 files in 42 folders
Outch :-)
(Victor Hugo)
Elle était déchaussée, elle était décoiffée,
Assise, les pieds nus, parmi les joncs penchants ;
Moi qui passais par là, je crus voir une fée,
Et je lui dis : Veux-tu t'en venir dans les champs ?
Elle me regarda de ce regard suprême
Qui reste à la beauté quand nous en triomphons,
Et je lui dis : Veux-tu, c'est le mois où l'on aime,
Veux-tu nous en aller sous les arbres profonds ?
Elle essuya ses pieds à l'herbe de la rive ;
Elle me regarda pour la seconde fois,
Et la belle folâtre alors devint pensive.
Oh ! comme les oiseaux chantaient au fond des bois !
Comme l'eau caressait doucement le rivage !
Je vis venir à moi, dans les grands roseaux verts,
La belle fille heureuse, effarée et sauvage,
Ses cheveux dans ses yeux, et riant au travers.
Another Sunday. ASOT rules. 181 and 182 :-).
And wow.
Joy. Sadness. Tears. Stress.
There's too much going on and he's not used to it.
Where is the little uneventful and cozy place?
Many things happened, not all according to the plan.
He's stressed here, he's stressed there.
Where is the fox and the rain, where is the box and the train?
Why don't they ask him how he feels?
They expect him to do this and that; sometimes he just can't.
He's read it all -- that's all theory and no practice.
He's not used to it and he just doesn't react well.
He tries to say it but they just start crying.
Nobody sees him cry.
Please support him. Be patient with him. He doesn't want to stop there.
He lost his cave. Last week Spiff was guiding him but he's gone now.
Yesterday he found his old cave again, somewhere on a distant world,
full of familiar monsters and friends.
Don't let him close the door to his cave,
for it takes a while to open it again.
Get closer to him.
Happy little rabbit,
running in the fields,
jumping over the spring.
Scolded little rabbit,
sad little rabbit,
hiding in his cave.
Grails is Groovy on Rails, the Groovy clone for Ruby on Rails.
Last week I was totally excited when I finally took a close look at Groovy so I decided to try to use Grails to develop some RAD database web-based front end. And boy was I disapointed.
Finally I ended up trying with Rails (aka Ruby on Rails) and that was it. In two days and a couple hundred of lines of code I had my functional SQL-based web site front end.
Now there's a story here and it's not about whether Groovy or Ruby and which one is good or bad. The fact is I wanted to use Groovy because of it being Java based, with the expectation that I was already familiar with the Java syntax so Groovy should be easy to pick up, right? On the other hand, I didn't care for learning Ruby's syntax.
In the end after spending several hours experimenting with both, Ruby was easier to use than Groovy despite it being a new syntax. The reason has unfortunately nothing to do with the technical merits of the languages (both are equivalent IMHO).
The real reason is the documentation and their respective web site.
Ruby's web site is developer-oriented, with direct links to various tutorials including the OnLAMP articles on Rails, direct link to javadoc-like Rails documentation for all classes and more important a wiki with tons of user feedback and tips.
The Groovy web site on the other hand lacks all of these. There are a couple of tutorials to get started with Groovy but these lack depth. Once I was past the initial step of installing Groovy and creating an empty Grails application, I was mostly left in the dark. Interestingly, the Grails tutorial starts talking right away about controllers and views without ever defining them. It's almost as if Grails was a pure Rails clone and the developers expected their users to be already familiar with Rails' terminology and the way of doing things (which I believe is exactly where the problem is.)
In the end one almost needs to learn Rails before starting to understand Grails. Which sounds to me like a lack of vision typical of open source projects. Anyone that checks out Grails might just end up frustrated like I did, go to Rails and once there just not come back to Grails.
This morning (or more exactly during the night) I started reading in detail about Groovy. Once again, RIG 2 may be the perfect target to experiment with this. Who can resists Java with closures?
As usual, I still think IDEs are the way to go and when it comes to Java-related stuff there's no way around Eclipse (well not unless you want to pay for IntelliJ, which seems like the next best thing, except I want free/open source stuff here for my tool chain.)
Consequently this morning I recompiled an updated version of the
Groovy plugin for Eclipse and made an
Eclipse Update Site for it.
To use it, you need Eclipse 3.1 with a JRE 1.5.0 then
go to Help > Software Updates > Find and Install,
select Search for new features to install and
create a New Remote Site with URL http://ralf.alfray.com/eclipse/.
This is based on the Groovy Eclipse plugin from CVS for version JSR 03 yet
I updated it with a Groovy JSR 04 jar. It's not an official distribution.
The only minor issue was a compilation error because the getSuperClassNode()
does not longer exists in ClassNode and needs to be renamed to getSuperClass().
If you want to rebuild your own plugin, follow the excellent directions on the Groovy plugin for Eclipse page as they are rather obvious. The instructions to create an Eclipse Update Site can be found in the PDE documentation that comes with Eclipse. The whole thing is extremely easy to do and straightforward.
Cozy Christmas by the fire, opening presents and enjoying a good meal.
First stroll around the block.
It seems like it all started a month ago. I still need some time to adjust. I'm now a proud father of twins. It still feels a bit like it's not me though.
Everything went so fast.
Friday, we went to the hospital, knowing we would stay for a little while.
Saturday was still full of uncertainties. Maybe today, maybe tomorrow... On the way back from home I manage to bump into another car.
Sunday, Sam & Chris are here!
Monday thru Thursday, we are literally living in the cocoon-like closed space of the hospital; we come and go as we want and visit Sam & Chris many times day & night. Nobody knows when we'll get home. All these nurses are fantastic and really helpful.
Friday, I manage to pick up the parents late at the airport. Everyone meets at the hospital.
Saturday, Chris comes back home in the afternoon. It's good to be back home!
Monday, Sam is back home too! This is very exciting, yet somehow I feel overly stressed only to get really depressed when some anonymous moron scratches the car on purpose (luckily MM helped to put this back in perspective and I got over it.)
Blog Archives:
Most recent posts
2005/12/12 - 2005/10/04
2005/09/25 - 2005/08/28
2005/08/28 - 2005/06/14
2005/06/11 - 2005/05/24
2005/05/17 - 2005/04/22
2005/04/14 - 2005/03/22
2005/03/18 - 2005/01/15
2005/01/13 - 2004/12/17
2004/12/16 - 2004/12/03
2004/12/02 - 2004/11/21
2004/11/21 - 2004/06/20
[RSS]
|
|
This work is licensed by Raphaël Moll under a Creative Commons License.
|
|
| Color Theme: | Gray | Blue | Black | Sand | Khaki | Egg | None |
|
|
|
|