Hi, On Fri, Jul 18, 2014 at 7:43 PM, Garret Wilson <[email protected]> wrote:
> On 7/18/2014 3:05 AM, Sven Meier wrote: > >> Hi, >> >> 3.5) Improve the javadoc and deprecate the class too, so users know they >> should move away from it. >> > > Why should users move away from it if they like that behavior? If this > class were generalized, it would be useful to say "have this component wrap > itself is <foo> and </foo> when it is disabled". Wicket shouldn't force > specialized HTML on users, but shouldn't discourage them from it, either. > > My philosophy is: Wicket should produce plain HTML out of the box, but > provide the tools so that developers can easily customize the output via > declarative behaviors, resorting to subclassing components only as a last > resort. > Try to create a reusable Behavior that: 1) by default does what Wicket 6.x does (i.e. <a> -> <span>, wrap in <em>) 2) optionally prevents 1) 3) optionally adds a special class to the tag 4) optionally adds disabled="disabled" to the tag 5) optionally just removes 'href' from <a> (as per W3C recommendation) 6) is open enough so that a sub-class does something custom It will be a big and rather complex Behavior which will try to do many things and an application will use just of them. I prefer the Unix-style: do 1 thing and do it as simple as possible. If second thing is needed then create a second tool (i.e. behavior) > > Just my opinion---as you can see I have lots of them. :) I hope you find > some of them helpful. > > Cheers, > > Garret >
