Joerg Heinicke wrote:
On 06.04.2004 09:20, Marc Portier wrote:
Joerg,
I realize that 'resting my case' is not enough...
some ideas:
this sounds like the operation 'selecting a row' should be an intrinsic feature of the repeater-widget
Yes, sounds reasonable.
In light of the above we could even consider sending repeaterID.radioID=row-identity (which would require to serialize-to-string somehow this identity?)
This not IMO ;-) I completely separate backend IDs from row IDs as the former ones might often be database IDs (general security concern). So my binding ATM often has a @unique-row-id="id" (still 2.1.4), but ID is only a wd:output in the definition and is not referred in the template. At least for the moment I have no use case where the mapping from row ID to backend ID does not match my requirements and so I'm hiding the backend IDs from the user.
+1
I'm still running around the hot soup of repeater-binding (in my head)
and your scenario (which I think is quite widespread) of the wd:output that never gets styled is for me an additional reason for having an intrinsic Identity property on each Reater.Row
with it you wouldn't even need to declare it in your form-definition since it really only has a purpose for the binding, and actually never really is a true/valid widget, or is it?
regards, -marc= -- Marc Portier http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center Read my weblog at http://blogs.cocoondev.org/mpo/ [EMAIL PROTECTED] [EMAIL PROTECTED]
