Howdy All,
There's a question at the end of this long intro:
I've been evaluating and comparing a number of Web frameworks again,
particularly at this time Wicket (which I have looked at previously
and tried out) and Django (which I am new to but comes highly
recommended).
I very much like the way Wicket has a complete (yes, I think complete
is a good description) separation of the (X)HTML and Java code. It's
fantastic when you want graphic designers to design the pages (with
dummy data as well).
I'm over the idea of using a complex template language, even the
simplified (presentation only) template language used in Django (so I
don't wish to go near JSF and I'm even a little negative on Tapestry
which has a similar minimal template language).
Django on the other hand use the dynamic language Python which makes
writing apps easier (and shorter). It also seems to make it very easy
to create more powerful applications by combining smaller
"applications" (e.g. it includes a powerful automatic CRUD interface).
I know Wicket makes it very easy to develop components and there are
some component libraries (e.g. Wicket Stuff) but it doesn't seem like
there are as many (high level components) as Django or that they are
as easy to integrate (that's just my perception).
So when I was looking at the Wikipedia comparison on Web frameworks I
noticed something. There doesn't seem to be a pull (component-based)
Web framework that uses a dynamic programming language (like Groovy,
Ruby or Python). Grok seems too left field.
Django, RoR and Grails are all push (request-based) Web frameworks
and, as I mentioned above, use template languages to varying degrees.
So I was thinking a pull (component-based) Web framework like Wicket
but using a dynamic language could be a great move.
A quick Google showed me that some work has been done with Groovy
(wicket-contrib-groovy) and the WicketBuilder by Kevin Galligan.
However, Kevin seems to have moved on to Seam and wicket-contrib-
groovy seems to be no longer supported.
From what I saw of WicketBuilder it seems it has a lot of potential
to make Wicket development more dynamic (with the
GroovyClassResolver), reduce the code required to write Wicket
applications, and even make them clearer with no overhead when deployed.
So my question is: what is the status (now and going forward) with
regards to using Groovy to develop with Wicket? I know there has been
much discussion of generifying Wicket but perhaps moving to a dynamic
language could be an alternative future.
Of course, using Groovy with Wicket wouldn't require the framework
itself to be implemented in Groovy or even that everyone uses Groovy.
And, as you all probably know Groovy can easily call an Java class
library.
So what do people think about Groovy and Wicket?
Cheers,
Ashley.
Some relevant URLs:
<http://wicketstuff.org/confluence/display/STUFFWIKI/WicketBuilder>
<http://www.kgalligan.com/wicketgroovy-setup>
<http://www.kgalligan.com/wicketgroovy-simplepage>
<http://bigheadco.blogspot.com/2007/03/wicket-and-groovy.html>
<http://people.byte-code.com/dpanelli/2008/02/04/groovy-wicket/>
--
Ashley Aitken
04 1226-8159 (Mb)
08 9368-5505 (Ph)
Perth, Western Australia
Skype/iChat: MrHatken (GMT + 8hrs!)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
