formsess-devel Mailing List for Smarty based forms toolkit (Page 2)
Status: Beta
Brought to you by:
mrkatana
Menu
▾
▴
formsess-devel — Developpement suggestions, bug reports...
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
(9) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(2) |
Feb
(24) |
Mar
(4) |
Apr
(15) |
May
(41) |
Jun
(16) |
Jul
|
Aug
|
Sep
(4) |
Oct
|
Nov
(1) |
Dec
(2) |
| 2005 |
Jan
|
Feb
(1) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: David <da...@df...> - 2004-05-26 12:23:56
|
Hello, much work has been done on the developement version and some new features have been added. There's still some work to do before we can release the new version but we published a new snapshot for those of you who want to help testing or already use the new features. The snapshot was tested and should work flawless in most cases. Please report bugs to the mailinglist or on the sourceforge project page. Information about important changes and new features is available at http://formsess.sourceforge.net/about-2.0.php - david |
|
From: David <da...@df...> - 2004-05-24 12:38:08
|
> I think it is OK, and it is almost what I had in mind. However, I will > write _ sooner or later _ that FormsessController class so that > application wide options might be set without having to set them > everytime you create an instance. Would that be compatible to the smarty approach I suggest? It's just that to 'learn formsess' itself is not an easy task, and since the users already know smarty.. > But how do you think these options will be set when no instance of the > class is created, e.g. when you only use <fs:form> in the template ? I'm not sure. What about providing accepting the classname as an optional parameter to enableFormsess()? (which would set a constant internally) |
|
From: Raoul P. <pie...@wa...> - 2004-05-24 12:19:23
|
Hello, > this is an interessting idea, but we really need to release a new > version as soon as possible, so bigger new features like that will = only > be discussed and intergrated after the next release. >=20 > Could you add a wishlist item to the sourceforge.net tracker? OK Regards Pierre >=20 > - david >=20 > On Sat, 22 May 2004 15:07:40 +0200 > "Raoul Pierre" <pie...@wa...> wrote: >=20 > > Hello, > >=20 > > If I'm right, at the moment the only way to put many validate tags > > together is > >=20 > > <fs:validate field=3D"toto" .../> > > <fs:validate field=3D"toto" .../> > > ... > > <fs:validate field=3D"toto" .../> > >=20 > > and the logic operator between tags is then "AND". > >=20 > > I think it would be a nice thing if we can do more wide logic = calculus > > with validate tags. > > Something like: > >=20 > > <fs:validate field=3D"toto" check=3D"A" /> <!-- by default, it's a = AND > > operator --> > > <fs:validate field=3D"toto" check=3D"B" logic=3D"or"/> > > <fs:validate field=3D"toto" logic=3D"open"/> <!-- by default, check > > attribut is empty? --> > > <fs:validate field=3D"toto" check=3D"C" logic=3D"and"/> > > <fs:validate field=3D"toto" check=3D"" logic=3D"open"/> > > <fs:validate field=3D"toto" check=3D"D" logic=3D"or"/> > > <fs:validate field=3D"toto" check=3D"E" logic=3D"close"/> > > <fs:validate field=3D"toto" check=3D"" logic=3D"close"/> > >=20 > > for logic formula: A . B + (C . (D+E)) |
|
From: <ka...@ka...> - 2004-05-24 12:01:06
|
> I added (g|s)etOption time ago to set formsess options. However they > became important only recently when some more options were added. > (before you could only toggle the js validation). > > Calling setOption several times after instanciating the formsess > class sucks so we need a way to easily set side-wide preferences. > > Bertrand, you wanted to add that additional configuration class, nothing > happend with that however. ;) > > I suggest to make all options properties of the formsess class, they way > it's with smarty. You could easily define your own class extending > formsess only with different properties set. > (just the way we do it with smarty) > > This is simple, powerful and (which is most important imho) familar to > smarty users. > > What do you think? I think it is OK, and it is almost what I had in mind. However, I will write _ sooner or later _ that FormsessController class so that application wide options might be set without having to set them everytime you create an instance. But how do you think these options will be set when no instance of the class is created, e.g. when you only use <fs:form> in the template ? Katana |
|
From: David <da...@df...> - 2004-05-24 09:43:21
|
Hello, I added (g|s)etOption time ago to set formsess options. However they became important only recently when some more options were added. (before you could only toggle the js validation). Calling setOption several times after instanciating the formsess class sucks so we need a way to easily set side-wide preferences. Bertrand, you wanted to add that additional configuration class, nothing happend with that however. ;) I suggest to make all options properties of the formsess class, they way it's with smarty. You could easily define your own class extending formsess only with different properties set. (just the way we do it with smarty) This is simple, powerful and (which is most important imho) familar to smarty users. What do you think? - david |
|
From: David <da...@df...> - 2004-05-24 07:17:56
|
Can you test this with a recent version (svn)? A lot of work has been done in
this area. (and iirc this should work now)
- david
On Sun, 23 May 2004 13:56:21 +0200
"Raoul Pierre" <pie...@wa...> wrote:
> Hello,
>
> I'm testing the Formsess from Formsess-Trunck.tgz (23-01-04).
>
> When I try the input tag with type checkbox, and I use array as name,
> the values given in assign instruction are not used to generate
> checked attributs. Example :
>
> $_fs->assign('cb1', array(1,2), true);
> $_fs->assign('cb2', array('one'=>1,'tree'=>3), true);
>
> with
>
> <fs:input type="checkbox" name="cb1[]" value="1" />
> <fs:input type="checkbox" name="cb2[tree]" value="3" />
>
> and no checked tag...
>
> When I look at smarty_function_fs_input_checkbox, there is:
>
> if (isset($params['cb_offset'])) {
> // cb_offset: the getname is the name without the offset within
> the
> brackets at the end
> //we don't need that atm, because getValue needs the []
> //$getname = substr($name, 0, (strlen($name) - 2 -
> strlen($params['cb_offset'])));
> $cb_offset = $params['cb_offset'];
> unset($params['cb_offset']);
> }
>
> //not need atm, see above
> //if (!isset($getname)) {
> // $getname = $name;
> //
>
> //must be changed later, to use $getname instead of name
> $item_value = $fs->getValue($name);
>
> so...
>
> But I don't understand why it's not possible to do it now. With:
>
> if (isset($params['cb_offset'])) {
> // cb_offset: the getname is the name without the offset within
> the
> brackets at the end
> //we don't need that atm, because getValue needs the []
> // !? getValue doesn't work with "[...]"
> $cb_offset = $params['cb_offset'];
> $getname = substr($name, 0, (strlen($name) - 2 -
> strlen($cb_offset))); unset($params['cb_offset']);
> }
> else{
> $getname = $name;
> }
> $item_value = $fs->getValue($getname);
>
>
> it seems OK.
>
>
> Regards
>
> Pierre
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: Oracle 10g
> Get certified on the hottest thing ever to hit the market... Oracle
> 10g. Take an Oracle 10g class now, and we'll give you the exam FREE.
> http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
> _______________________________________________
> Formsess-devel mailing list
> For...@li...
> https://lists.sourceforge.net/lists/listinfo/formsess-devel
>
|
|
From: David <da...@df...> - 2004-05-23 19:26:28
|
Alright, I'm gonna add that options.. > Yes, both sounds good. How / where do we set / store these options ? There're already Formsess::(s|g)etOption(), the only option until now was enableJsValidation however. The options are stored in a simple array, that could be changed if needed however.. - david |
|
From: Katana <ka...@ka...> - 2004-05-23 14:04:16
|
> With that there's no need to save fields on validation imho but it might
> be usefull bc and some people might want that feature.
> So what do you think about a global formsess option 'saveOnValidate'?
> (i already added that but i can be changed of course)
>
> Similar to that i would also like to add a 'unsaveOnFailedCheck' option.
Yes, both sounds good. How / where do we set / store these options ?
> I think for the beginning it would be sufficient to adjust that things
> on form level rather than on every single field.
> We could still add an attribute that changes the same thing for a single
> field but i would prefer to concentrate on getting ready to release
> rather than adding more and more features.
Yes, global is ok.
> We still didn't get any further with the password field.
> What do you think, should we add an attribute or just another global
> formsess option ('keepPassordFields')?
> I'd prefer the seccond.
The 2nd is ok with me. Making it false by default should match most
users requirements.
Katana
|
|
From: Raoul P. <pie...@wa...> - 2004-05-23 11:59:43
|
Hello,
I'm testing the Formsess from Formsess-Trunck.tgz (23-01-04).
When I try the input tag with type checkbox, and I use array as name, the
values given in assign instruction are not used to generate checked
attributs. Example :
$_fs->assign('cb1', array(1,2), true);
$_fs->assign('cb2', array('one'=>1,'tree'=>3), true);
with
<fs:input type="checkbox" name="cb1[]" value="1" />
<fs:input type="checkbox" name="cb2[tree]" value="3" />
and no checked tag...
When I look at smarty_function_fs_input_checkbox, there is:
if (isset($params['cb_offset'])) {
// cb_offset: the getname is the name without the offset within the
brackets at the end
//we don't need that atm, because getValue needs the []
//$getname = substr($name, 0, (strlen($name) - 2 -
strlen($params['cb_offset'])));
$cb_offset = $params['cb_offset'];
unset($params['cb_offset']);
}
//not need atm, see above
//if (!isset($getname)) {
// $getname = $name;
//
//must be changed later, to use $getname instead of name
$item_value = $fs->getValue($name);
so...
But I don't understand why it's not possible to do it now. With:
if (isset($params['cb_offset'])) {
// cb_offset: the getname is the name without the offset within the
brackets at the end
//we don't need that atm, because getValue needs the []
// !? getValue doesn't work with "[...]"
$cb_offset = $params['cb_offset'];
$getname = substr($name, 0, (strlen($name) - 2 - strlen($cb_offset)));
unset($params['cb_offset']);
}
else{
$getname = $name;
}
$item_value = $fs->getValue($getname);
it seems OK.
Regards
Pierre
|
|
From: David <da...@df...> - 2004-05-23 10:21:42
|
> Maybe we could add it for all fields but default it to yes for all the
>
> fields but password.
> what about autoSave=(bool) ? The only thing I don't like about
> autoSave is that it is not auto since you have to run a validator on
> the field first... Any better idea ?
I changed getValue() now to read also from the form data.
With that there's no need to save fields on validation imho but it might
be usefull bc and some people might want that feature.
So what do you think about a global formsess option 'saveOnValidate'?
(i already added that but i can be changed of course)
Similar to that i would also like to add a 'unsaveOnFailedCheck' option.
I think for the beginning it would be sufficient to adjust that things
on form level rather than on every single field.
We could still add an attribute that changes the same thing for a single
field but i would prefer to concentrate on getting ready to release
rather than adding more and more features.
We still didn't get any further with the password field.
What do you think, should we add an attribute or just another global
formsess option ('keepPassordFields')?
I'd prefer the seccond.
- david
|
|
From: David <da...@df...> - 2004-05-23 10:12:25
|
Hello, this is an interessting idea, but we really need to release a new version as soon as possible, so bigger new features like that will only be discussed and intergrated after the next release. Could you add a wishlist item to the sourceforge.net tracker? - david On Sat, 22 May 2004 15:07:40 +0200 "Raoul Pierre" <pie...@wa...> wrote: > Hello, > > If I'm right, at the moment the only way to put many validate tags > together is > > <fs:validate field="toto" .../> > <fs:validate field="toto" .../> > ... > <fs:validate field="toto" .../> > > and the logic operator between tags is then "AND". > > I think it would be a nice thing if we can do more wide logic calculus > with validate tags. > Something like: > > <fs:validate field="toto" check="A" /> <!-- by default, it's a AND > operator --> > <fs:validate field="toto" check="B" logic="or"/> > <fs:validate field="toto" logic="open"/> <!-- by default, check > attribut is empty? --> > <fs:validate field="toto" check="C" logic="and"/> > <fs:validate field="toto" check="" logic="open"/> > <fs:validate field="toto" check="D" logic="or"/> > <fs:validate field="toto" check="E" logic="close"/> > <fs:validate field="toto" check="" logic="close"/> > > for logic formula: A . B + (C . (D+E)) > > Regards > > Pierre > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: Oracle 10g > Get certified on the hottest thing ever to hit the market... Oracle > 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. > http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click > _______________________________________________ > Formsess-devel mailing list > For...@li... > https://lists.sourceforge.net/lists/listinfo/formsess-devel > |
|
From: David <da...@df...> - 2004-05-23 10:05:47
|
Hello, this is already fixed in svn but thanks for the report anyway! (It would be a great help if you could check out the latest version from svn and report bugs on that) ;) - david On Sat, 22 May 2004 22:52:46 +0200 "Raoul Pierre" <pie...@wa...> wrote: > Hello > > I'm testing the Formsess from Formsess-Trunck.tgz (23-01-04). > > I get a warning message "Call-time pass-by-reference..." with the line > 313 of FormsessFilter.class.php : > > $tagParser = new $tagFilterClass(&$this); > > Regards > > Pierre > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: Oracle 10g > Get certified on the hottest thing ever to hit the market... Oracle > 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. > http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click > _______________________________________________ > Formsess-devel mailing list > For...@li... > https://lists.sourceforge.net/lists/listinfo/formsess-devel > |
|
From: Raoul P. <pie...@wa...> - 2004-05-23 09:49:19
|
> > Execute: Checkout > > Error while performing action: PROPFIND request failed on > > '/formsess/src/trunk' > > PROPFIND of '/formsess/src/trunk': could not connect to server > > (http://svn.phpedit.net:8080) > > Ready > Hmmm not really. > Just tried > $ svn ls http://svn.phpedit.net:8080/formsess/src/trunk > > and it returned > CHANGELOG > INSTALL > LGPL.txt > TODO > libs/ > samples/ I got the same thing with: - svn with the command line above - RapidSVN - TutoiseSVN I'm working under Windows XP Pro. > > "could not connect to server" looks like a DNS error to me... can you > resolve the domain name ? Euhhhh, this is beyond my level of comprehension ;-) The only thing I think about is: with TutoiseSVN and its Repository Browser, everything is ok (I can brownse the repository with IE) but only after an "anonymous" login. So I try svn log --username anonymous http://svn.phpedit.net:8080/formsess/src/trunk but always with the same message. Regards Pierre |
|
From: Raoul P. <pie...@wa...> - 2004-05-22 20:56:09
|
Hello
I'm testing the Formsess from Formsess-Trunck.tgz (23-01-04).
I get a warning message "Call-time pass-by-reference..." with the line 313
of FormsessFilter.class.php :
$tagParser = new $tagFilterClass(&$this);
Regards
Pierre
|
|
From: Katana <ka...@ka...> - 2004-05-22 19:40:33
|
> Execute: Checkout > Error while performing action: PROPFIND request failed on > '/formsess/src/trunk' > PROPFIND of '/formsess/src/trunk': could not connect to server > (http://svn.phpedit.net:8080) > Ready Hmmm not really. Just tried $ svn ls http://svn.phpedit.net:8080/formsess/src/trunk and it returned CHANGELOG INSTALL LGPL.txt TODO libs/ samples/ "could not connect to server" looks like a DNS error to me... can you resolve the domain name ? Katana |
|
From: Raoul P. <pie...@wa...> - 2004-05-22 18:15:40
|
Hello, I tried to checkout FormSess but I got this message: Execute: Checkout Error while performing action: PROPFIND request failed on '/formsess/src/trunk' PROPFIND of '/formsess/src/trunk': could not connect to server (http://svn.phpedit.net:8080) Ready Any idea? Regards Pierre PS: sorry for the noise with my last message. I think it wasn't received as I didn't see it on the ML. |
|
From: David <da...@df...> - 2004-05-22 15:37:12
|
> But how would you handle the fact of having to save all the form data
> when a check fails ?
> It is necessary since the form will have to be
> displayed again. Then reset() will be necessary anyway since form data
>
> might have been saved anyway...
Well, you could use one-script forms like that:
$fs = &new Formsess(..);
if ($fs->wasSubmitted() && !$fs->hasErrors()) {
doSomethingWithTheFormData();
// and redirect to another page
} else {
$smarty->display(myform.tpl);
}
Which 'loops' as long until there're no errors left and the form data is
processed.
No need for save at all anymore, since the smarty functions, executed
with display use getValue which directly reads from the form data. :-)
If you use different scripts for displaying the form and processing the
data, nothing would change at all. (except that you could use getValue()
before saving) You will still need to save() and reset().
|
|
From: Katana <ka...@ka...> - 2004-05-22 15:10:38
|
>>Hmmm... but what's the difference between "auto-saving form data" and >>"saving data in the session" ? There is no other data container that the >>session is there ? Or do you just mean change Formsess::getValue() so >>that it does not take the values from the session but from the form data >>itself ? > > Yes. (you might want to read my email again). ;) Hmm yes. Indeed. Sorry 'bout that. So yes, I agree, that would be a more logical way. Much more logical. And indeed there is no reason to save data if they're just gonna be used in the current script and reseted at the end. But how would you handle the fact of having to save all the form data when a check fails ? It is necessary since the form will have to be displayed again. Then reset() will be necessary anyway since form data might have been saved anyway... Katana |
|
From: David <da...@df...> - 2004-05-22 13:19:44
|
On Sat, 22 May 2004 14:56:42 +0200 Katana <ka...@ka...> wrote: > > The suggestion about autoSave brought me to one idea: > > why not auto-save the form data whenever a form is submitted and use > > save() only for saving the data in the session? > Hmmm... but what's the difference between "auto-saving form data" and > "saving data in the session" ? There is no other data container that the > session is there ? Or do you just mean change Formsess::getValue() so > that it does not take the values from the session but from the form data > itself ? Yes. (you might want to read my email again). ;) |
|
From: Raoul P. <pie...@wa...> - 2004-05-22 13:11:05
|
Hello, If I'm right, at the moment the only way to put many validate tags together is <fs:validate field="toto" .../> <fs:validate field="toto" .../> ... <fs:validate field="toto" .../> and the logic operator between tags is then "AND". I think it would be a nice thing if we can do more wide logic calculus with validate tags. Something like: <fs:validate field="toto" check="A" /> <!-- by default, it's a AND operator --> <fs:validate field="toto" check="B" logic="or"/> <fs:validate field="toto" logic="open"/> <!-- by default, check attribut is empty? --> <fs:validate field="toto" check="C" logic="and"/> <fs:validate field="toto" check="" logic="open"/> <fs:validate field="toto" check="D" logic="or"/> <fs:validate field="toto" check="E" logic="close"/> <fs:validate field="toto" check="" logic="close"/> for logic formula: A . B + (C . (D+E)) Regards Pierre |
|
From: Katana <ka...@ka...> - 2004-05-22 12:50:47
|
> The suggestion about autoSave brought me to one idea: > why not auto-save the form data whenever a form is submitted and use > save() only for saving the data in the session? Hmmm... but what's the difference between "auto-saving form data" and "saving data in the session" ? There is no other data container that the session is there ? Or do you just mean change Formsess::getValue() so that it does not take the values from the session but from the form data itself ? Katana |
|
From: <ben...@id...> - 2004-05-22 12:41:02
|
Dear Open Source developer I am doing a research project on "Fun and Software Development" in which I kindly invite you to participate. You will find the online survey under http://fasd.ethz.ch/qsf/. The questionnaire consists of 53 questions and you will need about 15 minutes to complete it. With the FASD project (Fun and Software Development) we want to define the motivational significance of fun when software developers decide to engage in Open Source projects. What is special about our research project is that a similar survey is planned with software developers in commercial firms. This procedure allows the immediate comparison between the involved individuals and the conditions of production of these two development models. Thus we hope to obtain substantial new insights to the phenomenon of Open Source Development. With many thanks for your participation, Benno Luthiger PS: The results of the survey will be published under http://www.isu.unizh.ch/fuehrung/blprojects/FASD/. We have set up the mailing list fa...@we... for this study. Please see http://fasd.ethz.ch/qsf/mailinglist_en.html for registration to this mailing list. _______________________________________________________________________ Benno Luthiger Swiss Federal Institute of Technology Zurich 8092 Zurich Mail: benno.luthiger(at)id.ethz.ch _______________________________________________________________________ |
|
From: Raoul P. <pie...@wa...> - 2004-05-19 17:20:51
|
Hello, If I'm right, at the moment the only way to put many validate tags = together is <fs:validate field=3D"toto" .../> =20 <fs:validate field=3D"toto" .../> =20 ... <fs:validate field=3D"toto" .../> =20 and the logic operator between tags is then "AND". I think it would be a nice thing if we can do more wide logic calculus = with validate tags. Something like: <fs:validate field=3D"toto" check=3D"A" /> <!-- by default, it's a AND = operator --> <fs:validate field=3D"toto" check=3D"B" logic=3D"or"/> =20 <fs:validate field=3D"toto" logic=3D"open"/> <!-- by default, check = attribut is empty? --> =20 <fs:validate field=3D"toto" check=3D"C" logic=3D"and"/> =20 <fs:validate field=3D"toto" check=3D"" logic=3D"open"/> =20 <fs:validate field=3D"toto" check=3D"D" logic=3D"or"/> =20 <fs:validate field=3D"toto" check=3D"E" logic=3D"close"/> =20 <fs:validate field=3D"toto" check=3D"" logic=3D"close"/>=20 for logic formula: A . B + (C . (D+E)) Regards Pierre |
|
From: David <da...@df...> - 2004-05-19 15:50:15
|
The suggestion about autoSave brought me to one idea: why not auto-save the form data whenever a form is submitted and use save() only for saving the data in the session? That would solve some frequent mistakes: - people forget to call saveAll() and wonder why getValue() doesn't return anything - people don't reset() the form after processing the data, so all values are still filled in when the visitor comes back to the form again. What I suggest is not really to auto-save the form data but rather change getValue() to read from the form data and only fall back to the session data if the form was not submitted. save() would only be needed if the form data is neede on another page again. I would also remove the field saving from check(), since form data can be read without being saved before. I think that would be a major improvement and increase usability a lot. About the password field: I would not change anything about saving but rather change only the smarty function to not add the value attribute (unless the keepvalue or whatever attribute is preset). - david On Sat, 15 May 2004 20:42:08 +0200 Katana <ka...@ka...> wrote: > > we've been talking about not keeping values in password fields for > > security reason time ago. > > > > I'll change that in the next days. I'll also add an attribute to > > tell if the value should be kept (default no). How should it be > > called? I'm for keepvalue. > This attribute would only exist for password fields right ? > Maybe we could add it for all fields but default it to yes for all the > > fields but password. > what about autoSave=(bool) ? The only thing I don't like about > autoSave is that it is not auto since you have to run a validator on > the field first... Any better idea ? > > Bertrand > > > ------------------------------------------------------- > This SF.Net email is sponsored by: SourceForge.net Broadband > Sign-up now for SourceForge Broadband and get the fastest > 6.0/768 connection for only $19.95/mo for the first 3 months! > http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click > _______________________________________________ > Formsess-devel mailing list > For...@li... > https://lists.sourceforge.net/lists/listinfo/formsess-devel > |
|
From: Raoul P. <pie...@wa...> - 2004-05-19 13:26:07
|
> message interessant, =E0 =E9tudier; ceci dit tu pourrais le renvoyer = sur > for...@li... ? L'autre d=E9veloppeur serait = sans > doute int=E9ress=E9, de m=EAme que les autres personnes suivant cette = liste. >=20 > Merci, >=20 > Bertrand OK. See below: If I'm right, at the moment the only way to put many validate tags = together is <fs:validate field=3D"toto" .../> =20 <fs:validate field=3D"toto" .../> =20 ... <fs:validate field=3D"toto" .../> =20 and the logic operator between tags is then "AND". I think it would be a nice thing if we can do more wide logic calculus = with validate tags. Something like: <fs:validate field=3D"toto" check=3D"A" /> <!-- by default, it's a AND = operator --> <fs:validate field=3D"toto" check=3D"B" logic=3D"or"/> =20 <fs:validate field=3D"toto" logic=3D"open"/> <!-- by default, check = attribut is empty? --> =20 <fs:validate field=3D"toto" check=3D"C" logic=3D"and"/> =20 <fs:validate field=3D"toto" check=3D"" logic=3D"open"/> =20 <fs:validate field=3D"toto" check=3D"D" logic=3D"or"/> =20 <fs:validate field=3D"toto" check=3D"E" logic=3D"close"/> =20 <fs:validate field=3D"toto" check=3D"" logic=3D"close"/>=20 for logic formula: A . B + (C . (D+E)) |
