Here's one good article:
http://talk-on-tech.blogspot.com/2008/12/wicket-neat-url-encoding-strategy-and.html
2009/1/8 Gwyn Evans <gwyn.ev...@gmail.com>:
> Not sure if it qualifies as enough of a topic, but would some form of
> overview/comparison/"when to use" syummary of the various URL coding
> strategies be worth considering?
>
> /Gwyn
>
> On Mon, Jan 5, 2009 at 8:37 AM, Jonathan Locke <jonathan.lo...@gmail.com>
> wrote:
>>
>>
>> well, i got bored enough over the break to sink some hours into
>> this and i'm liking what happened pretty well now. any other really
>> ugly problems people want neat solutions to? ;-)
>>
>>
>> Jonathan Locke wrote:
>>>
>>>
>>> yes. this is a good one, but it might be too big for the book...
>>> although i've been pondering the possibility of something more
>>> general which is more in the neighborhood of "arbitrarily-
>>> driven component factories" (where property editors and
>>> bean editors are specializations).
>>>
>>> for property/bean editors you may want to take a look
>>> at will faler's "wicket-rad" which does this already.
>>> although i don't know if it's as ideal as it could be yet,
>>> i think he'd like some help with it seems open to working
>>> with people.
>>>
>>> jon
>>>
>>>
>>> walnutmon wrote:
>>>>
>>>> A component that takes some domain object, and for every property
>>>> dynamically loads an appropriate form element.
>>>>
>>>> @Test
>>>> {
>>>> private class DomainObject{
>>>> List<Property1> prop1s;
>>>> Boolean prop2;
>>>> }
>>>> panel = new DynamicPropertyPanel(new DomainObject());
>>>> assertComponent("panel:form:formElement:0", DropDownChoice.class);
>>>> assertComponent("panel:form:formElement:1", Checkbox.class);
>>>>
>>>> //test customization
>>>> panel = new DynamicPropertyPanel(new DomainObject());
>>>> panel.setProperty("prop1s", RadioGroup.class);
>>>> assertComponent("panel:form:formElement:0", RadioGroup.class);
>>>> assertComponent("panel:form:formElement:1", Checkbox.class);
>>>> }
>>>>
>>>> My company would purchase several copies of the book if I recommended to
>>>> do so; which I would.
>>>>
>>>> Jonathan Locke wrote:
>>>>>
>>>>> Well, over the break here I've started something I swore I would never
>>>>> do again (well, two things, if you include the JavaOne talk I'm working
>>>>> on). I'm writing a (hopefully relatively short) book. It's called
>>>>> "Twenty-Six Wicket Tricks". Each trick in the book (lettered from A-Z)
>>>>> demonstrates something that people typically want to do and in the
>>>>> process builds a reusable and educational component. I've got 13 tricks
>>>>> coded up now and ideas for a handful more, but if there are any requests
>>>>> out there, please let me know. I'd also be interested in getting some
>>>>> idea how many people would be interested in this book (would provide
>>>>> some fuel for me to get it done). It does not cover any of the same
>>>>> ground as Wicket in Action (which you should buy if you have not
>>>>> already!), BTW. It's more of a companion to that book.
>>>>>
>>>>> Happy Holidays!
>>>>>
>>>>> Best,
>>>>>
>>>>> Jonathan
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Twenty-Six-Wicket-Tricks-tp21214357p21287125.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
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
