Re: New Wicket Grails Plug-in Available + about the Groovy wicket builder
I was just wondering if someone can tell me what is the benefit of using Wicket rather than just using grails for you view layer? Hi Wicket users! We've published a new version of the Wicket plugin for Grails that works with Wicket 1.3. See announcement here: http://docs.codehaus.org/display/GRAILS/2008/03/04/Wicket+1.3+Grails+Plug-in+Released -- View this message in context: http://www.nabble.com/New-Wicket-Grails-Plug-in-Available-%2B-about-the-Groovy-wicket-builder-tp15828796p22217634.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
RE: New Wicket Grails Plug-in Available + about the Groovy wicket builder
Anonymous inner classes are nice for their brevity but they are not
required. You can declare those as concrete classes. I'm not too sure
about Groovy but you should be able to put them in the same file.
-Original Message-
From: JulianS [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 22, 2008 4:36 PM
To: users@wicket.apache.org
Subject: Re: New Wicket Grails Plug-in Available + about the Groovy
wicket builder
I just tried this plugin for the first time and I got the example to
run. But
as soon as I tried to do something as simple as loop through a list of
items, it all came unstuck (code below). It seems to me like the
mismatch
between Wicket's use of anonymous inner classes and Groovy's lack of
support
for them is a deal breaker. You either have to reduce your usage of
Wicket
in Groovy code to preexisting Wicket components that were built in Java
(like the Label below), or you have to use a Groovy builder that emits
Java
code, which then gets compiled. Am I missing something? I hope so, I'd
love
to use GORM and Wicket together.
HomePage.groovy:
public class HelloPage extends WebPage
{
public HelloPage(final PageParameters parameters) {
add(new Label("message", "If you see this message wicket is
properly
configured and running!"));
add(new Loop("repeat", Book.list( 10 )))
{
@Override
protected void populateItem(LoopItem item)
{
Book book = (Book)
item.getModelObject();
item.setModel(new
CompoundPropertyModel(book));
item.add(new Label("name"));
}
}
}
}
Julian
--
View this message in context:
http://www.nabble.com/New-Wicket-Grails-Plug-in-Available-%2B-about-the-
Groovy-wicket-builder-tp15828796p18598173.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
_
The information contained in this message is proprietary and/or confidential.
If you are not the
intended recipient, please: (i) delete the message and all copies; (ii) do not
disclose,
distribute or use the message in any manner; and (iii) notify the sender
immediately. In addition,
please be aware that any message addressed to our domain is subject to
archiving and review by
persons other than the intended recipient. Thank you.
_
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: New Wicket Grails Plug-in Available + about the Groovy wicket builder
I just tried this plugin for the first time and I got the example to run. But
as soon as I tried to do something as simple as loop through a list of
items, it all came unstuck (code below). It seems to me like the mismatch
between Wicket's use of anonymous inner classes and Groovy's lack of support
for them is a deal breaker. You either have to reduce your usage of Wicket
in Groovy code to preexisting Wicket components that were built in Java
(like the Label below), or you have to use a Groovy builder that emits Java
code, which then gets compiled. Am I missing something? I hope so, I'd love
to use GORM and Wicket together.
HomePage.groovy:
public class HelloPage extends WebPage
{
public HelloPage(final PageParameters parameters) {
add(new Label("message", "If you see this message wicket is properly
configured and running!"));
add(new Loop("repeat", Book.list( 10 )))
{
@Override
protected void populateItem(LoopItem item)
{
Book book = (Book) item.getModelObject();
item.setModel(new CompoundPropertyModel(book));
item.add(new Label("name"));
}
}
}
}
Julian
--
View this message in context:
http://www.nabble.com/New-Wicket-Grails-Plug-in-Available-%2B-about-the-Groovy-wicket-builder-tp15828796p18598173.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: New Wicket Grails Plug-in Available + about the Groovy wicket builder
Is this for real? =) Wow! This really makes my day. I'll have to check this out. Having Groovy take care of "hot reloading" Pages seems like a *MUCH* better solution than what we have today (spotty reloading of java classes through the JVM). On Tue, Mar 4, 2008 at 8:49 AM, graemer <[EMAIL PROTECTED]> wrote: > > Hi Wicket users! > > We've published a new version of the Wicket plugin for Grails that works > with Wicket 1.3. See announcement here: > > http://docs.codehaus.org/display/GRAILS/2008/03/04/Wicket+1.3+Grails+Plug-in+Released > > And more info here: http://docs.codehaus.org/display/GRAILS/Wicket+Plugin > > One thing I wanted to do at some point was integration the Wicket Groovy > builder (http://wicketstuff.org/confluence/display/STUFFWIKI/WicketBuilder) > but it seems that the code in SVN head is out of the date and the 1.3 branch > here has been removed: > > > https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/branches/wicket-1.3/wicket-contrib-groovy > > Is there any version of the code that works with 1.3? If not are the > original developers of the plug-in interested in porting it to 1.3 and > including it in the Grails wicket plugin? > > Cheers! > Graeme > -- > View this message in context: > http://www.nabble.com/New-Wicket-Grails-Plug-in-Available-%2B-about-the-Groovy-wicket-builder-tp15828796p15828796.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
