://www.nabble.com/cancel-buttons-tp16083133p16083133.html
Sent from the Wicket - Dev mailing list archive at Nabble.com.
with this issue. true, it is
yet-another-class-in-core (or extensions would be fine), but i think it
might be nice.
--
View this message in context:
http://www.nabble.com/cancel-buttons-tp16083133p16083133.html
Sent from the Wicket - Dev mailing list archive at Nabble.com
.
--
View this message in context:
http://www.nabble.com/cancel-buttons-tp16083133p16083133.html
Sent from the Wicket - Dev mailing list archive at Nabble.com.
--
Resizable and reorderable grid components.
http://www.inmethod.com
such that they
setDefaultFormProcessing(false). this would be a discoverable and
self-documenting way of dealing with this issue. true, it is
yet-another-class-in-core (or extensions would be fine), but i think it
might be nice.
--
View this message in context:
http://www.nabble.com/cancel-buttons
(or extensions would be fine), but i
think it
might be nice.
--
View this message in context:
http://www.nabble.com/cancel-buttons-tp16083133p16083133.html
Sent from the Wicket - Dev mailing list archive at Nabble.com.
--
Resizable and reorderable grid
.
--
View this message in context:
http://www.nabble.com/cancel-buttons-tp16083133p16083133.html
Sent from the Wicket - Dev mailing list archive at Nabble.com.
--
Resizable and reorderable grid components.
http://www.inmethod.com
true. otoh, a newbie may not know that. giving them a couple cancel button
subclasses would be very obvious.
The problem with providing easy components like this is not only that
it expands Wicket's surface area, but also that it doesn't encourage
people to think about extending components
