i dont see anything wrong with it.
-igor
On Mon, Mar 30, 2009 at 3:07 PM, T P D wrote:
> Well, actually, I have done it, by abstracting out the rendering by having
> onTagComponent and onTagComponentBody, in a class derived from
> AbstractSingleSelectChoice, delegate to a GOF Strategy Pattern.
>
Well, actually, I have done it, by abstracting out the rendering by
having onTagComponent and onTagComponentBody, in a class derived from
AbstractSingleSelectChoice, delegate to a GOF Strategy Pattern.
I then have four strategies: one each for dropdown, dropdownlist, and
radiochoice, and a fou
there isnt anything really stopping you from doing this. afaict you
already have all the wicket hooks to do this.
-igor
On Mon, Mar 30, 2009 at 2:15 PM, T P D wrote:
> What I really like about Wicket is that it -- much more than JSPs -- allows
> the separation of HTML markup from Java code. No "
What I really like about Wicket is that it -- much more than JSPs --
allows the separation of HTML markup from Java code. No "c:if"ing with a
Domain Specific Language like JTSL (or Velocity macros) inside HTML
markup and side-by-side with javascript. In Wicket, in contrast, HTML
markup contains
