I am glad that so many people start to debate in this topic. First of all I
need to explain my usecase:
it is indeed about a tree... I have a tree containing Roles (hierarchical
structure). There is a screen in which the user must select the Roles which
he want to assign to a user.
The logic
If I were to create that component, I probably would not extend from
CheckBox as both the model is semantically different and the rendering
is done a different way. Instead, I would extend FormComponent
directly. I also would not choose for a model that has
true/false/null, which would imo be no
you don't have to use ajax or somethingthe click can just be a img src tag replace You do need a hidden field and update what value is set on the backend the component should have a renderer something like the IChoiceRenderer
where you map the 3 states to your real object that you want in a
On 8/31/06, Johan Compagner [EMAIL PROTECTED] wrote:
you don't have to use ajax or something
the click can just be a img src tag replace
Technically, you don't have to, but as this typically is tree
functionality, it is wise - imho - to do so. Furthermore, on a click
you should update, as this
i dont think it is typically a tree functionality i would use such a componentfar most often in another area. Especially required checkboxes..I would like such a more general component (core or extentions)
johanOn 8/31/06, Eelco Hillenius [EMAIL PROTECTED] wrote:
On 8/31/06, Johan Compagner [EMAIL
I would like such a more general component (core or extentions)
I'm looking forward to whatever you come up with :)
Eelco
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly
Alex Objelean wrote:
The logic is simple: if you check a node - the checked Role is added to
the list of selected Roles, otherwise it is removed from the list. At the
same time, if you check a child - all the ancestors changes theirs state to
intermediate (if their current state is
you know what the limits of HTML are
suggest you look at w3c.org the HTML specs, and think about a realistic way
to solve your business needs.
Regards
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag
von Alex Objelean
Gesendet:
Well, thank you for your support :)... That's exactly what I needed!
Maybe I was not clear enough in my specification. If I would not say that I
need a tri-state checkbox, but a formComponent which looks like checkbox
(see here:
Unfortunately, the dropDownChoice component does not suite my needs.
The ideea with button seems to be a good ideea, why not use just input
type=button or button instead of input type=submit... The problem
is: should I reuse the Checkbox code by extending it or just extend Form
component and
compliant and safe for all
browsers...
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag
von Alex Objelean
Gesendet: Mittwoch, 30. August 2006 13:38
An: wicket-user@lists.sourceforge.net
Betreff: Re: [Wicket-user] Tri-state checkbox
: [Wicket-user] Tri-state checkbox Unfortunately, the dropDownChoice component does not suite my needs. The ideea with button seems to be a good ideea, why not use
just input type=button or button instead of input type=submit... The problem is: should I reuse the Checkbox code by extending
That's an interesting Widget! How would it work on the server side
though... what kind of model would it need.
I'd be interested to hear about how you plan to use it. It seems this
is a component you'd always use with a tree, correct? If so it would
just be a matter of letting the tree render the
:18An:
wicket-user@lists.sourceforge.netBetreff: Re: [Wicket-user]
Tri-state checkbox
too bad the point is not to submit the form on every click so input
type="submit" wont work.you need something to carry the value on form
submissions so you will need a hidden field. i would
- submitting the whole form IMHO is not a big
problem
Regards
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] Im Auftrag von Igor
VaynbergGesendet: Mittwoch, 30. August 2006 18:18An:
wicket-user@lists.sourceforge.netBetreff: Re: [Wicket-user]
Tri-state checkbox
too bad
I thought about something like this to represent null/yes/no, but figured it might confuse casual users.
-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag von Igor
VaynbergGesendet: Mittwoch, 30. August 2006 20:24An:
wicket-user@lists.sourceforge.netBetreff: Re: [Wicket-user]
Tri-state checkbox
if you havent noticed its 2006 and _javascript_ is as pervasive
if you havent noticed its 2006 and _javascript_ is as pervasive as
html
WRONG !!! - i know companies, that for example have JS disabled at ALL
of their systems - we have 2006 and thinking JS is everywhere is same as
thinking that no illness exists because you see no ill people on the
people (e.g.: blind)
the web was made for anyone, not just some
tecchies...
Regards,
Korbinian
Von:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] Im Auftrag von Igor
VaynbergGesendet: Mittwoch, 30. August 2006 20:55
An:
wicket-user@lists.sourceforge.netBetreff: Re: [Wicket-user
very true.
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag von Igor
VaynbergGesendet: Mittwoch, 30. August 2006 21:20An:
wicket-user@lists.sourceforge.netBetreff: Re: [Wicket-user]
Tri-state checkbox
all this really depends on the site you are building
the model could be simple:Boolean (null, true false)johanOn 8/30/06, Eelco Hillenius
[EMAIL PROTECTED] wrote:That's an interesting Widget! How would it work on the server side
though... what kind of model would it need.I'd be interested to hear about how you plan to use it. It seems thisis a
But it wouldn't be a direct model, as the indeterminate value would be
calculated from children, right?
I just wonder whether a seperate component like that would make sense
if - as I think - it is something you would only use in a tree.
Eelco
On 8/30/06, Johan Compagner [EMAIL PROTECTED]
not really.for example if you fill in a form (enquete) that has questionsthen you can have this:Do you think this is bad? Yes/No But the default is nothing (because there is no data) so there is no selection yet..
So the null thing is a not filled in question by the user.johanOn 8/30/06, Eelco
Yeah, you thought that up yourself :) I guess that *could* be a valid
use case, though it is entirely different than this
http://www.indigorose.com/webhelp/vp20/Program_Reference/Misc/Tri-state_Checkbox.htm
component.
Eelco
On 8/30/06, Johan Compagner [EMAIL PROTECTED] wrote:
not really.
for
On 8/30/06, Eelco Hillenius [EMAIL PROTECTED] wrote:
Yeah, you thought that up yourself :) I guess that *could* be a valid
use case, though it is entirely different than this
http://www.indigorose.com/webhelp/vp20/Program_Reference/Misc/Tri-state_Checkbox.htm
component.
Where the choice is
25 matches
Mail list logo
