Sebastian wrote:
Dnia Mon, 19 Apr 2004 22:41:50 +0200, Marc Portier <[EMAIL PROTECTED]> napisał:^^^^^^^ did I? gosh :-$
<snip />
Ok. I've looked at C2.1.5. Lot of new stuff. It looks interesting. Saddly I'm not web developer anymore and don't have so much time to spend on it as I used to have. I just want to be align. Everything looks fine. I managed to get my beutiful NIP validator. And... I'm a little bit disapointed. Why? Because fail message on aggregatefield isn't working correctly. My model looks like:
<snip what="the elaborate sample snippet" />
Now, when I try to enter incorrect NIP it is validated and form won't be submited. That's correct. Saddly information that NIP is incorrect is not presented by '!'. Well if I'll provide letter insted of digit I will get '!' for incorrect field but I don't have '!' for whole aggregation. So if digits are correct form won't be submited and user won't get feedback why it happens. Is it possible to make it visible or is it a bug in cforms?
Since this error is on the aggregate-widget and that one is not actually on the template, there is no position where the (!) should be next to.
Therefor you need to explitely position it with a separate <ft:validation-error />
see also here: http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=108176649831199&w=2
and here:
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=107486651220426&w=2
and let's thank Vadim :-)
I think it is, I do hope you now also understand the 'danger' in this usage.
Hmm. Okey I agree. I just have an idea. Of course it is not possible with current implementation but it could be the way for multiforms. Consider that we have additional value stored in continuation session which will hold information about current view. Then we can add information to form template about views. I mean additional info for widget on which page it should be visible. Now, depending on current value of our variable stored in session cforms block can validate/trigger getting submited values/do other stuff only for widgets availiable for current view. Succesfuly validated form allow cforms to change value of variable stored in session and change current view. Leaving current continuation point would be possible only when user will go through all forms. In sucha solution we have both advantages from multiforms and continuation. Main idea was taken from XForms. I like almost everything about cforms but I think there were some good ideas also in XForms.
I'm quite sure that is the case...
I have to say the above explanation is quite dense, and it fails at making me see where this 'view' is different to the current 'form'
Isn't this really about just have a look at it differently, and mold your thoughts around what cforms offers?
In any case, maybe you could elaborate with some snippets of flowscript and form def files to hint at what you are implying...
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]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
