formsess-devel Mailing List for Smarty based forms toolkit
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: <M...@rm...> - 2005-04-22 08:51:56
|
Hi guys,
Here is a patch to be able to use object oriented calls in formsess
code.
Index: FormsessFilter.class.php
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- FormsessFilter.class.php (revision 547)
+++ FormsessFilter.class.php (working copy)
@@ -81,13 +81,13 @@
//replace known two part tags (except of select) by one part tags
//with the value stored in the ouput attribute
$this->_source =3D preg_replace('%<fs:(' . implode('|',
- $this->_known_two_part_tags) . ')(\s.*?)?>(.*?)</fs:\1>%xsmi',
- '<fs:$1$2 tagcontent=3D"$3" />', $this->_source
+ $this->_known_two_part_tags) . ')((\s+\w+=3D"[^"]*")*)?>(.*?)</fs:=
\1>%xsmi',
+ '<fs:$1$3 tagcontent=3D"$4" />', $this->_source
);
// first, look for all <fs:(*)> tags
// @todo add a condition to check if we don't at the same time get a=
closing and inline closing tag
- if (!preg_match_all('!<(/?)fs:([\w]+)(.*?)?(/?)>!xsmi', $this->_sour=
ce, $fs_tags, PREG_SET_ORDER)) {
+ if (!preg_match_all('!<(/?)fs:(\w+)((\s+\w+=3D"[^"]*")*)(\s*/)?>!xsm=
i', $this->_source, $fs_tags, PREG_SET_ORDER)) {
$this->_smartyCommentsRestore();
return;
}
Best regards,
S=E9bastien Hordeaux
|
|
From: Marcel W. <wo...@wo...> - 2005-02-05 12:47:38
|
Hey Katana, I just wanted to give you some props! For the first time I used Formsess very intensively. I am really looking forward to the 2.0.0 release!! So congratulations for this really fine project! wojna Katana wrote: >Hello Philipp, > >First, sorry for not answering your email earlier; but now i'm back >for real in formsess business :) > >I know that checkboxes handling is not perfect yet. The way checkboxes >are handled in HTML / PHP is quite different from other fields _ but I >guess you know that already _ and i've not found a perfect method yet. > >Could you please summarize your approach ? I have some difficulties >putting myself in the right context for the piece of code below :) > > > >>Do you mind to exclude the .svn folders in your releases? >> >> >No, if there are/was .svn files in a release, it was an error. >The only releases where I leave .svn files are nightly builds, since >NB users are more likely to upgrade their version themselves with a >svn client. > > > >>I really like formsess - a great project. Looking forward >>to have a next stable release. >> >> >Thank you :) >Next stable... a stable release you mean ? j/k >anyway i will release 2.0.0 in a while, since i'm already working >almost fulltime on the trunk version with very, very neat new >features. > > > |
|
From: Katana <ka...@ka...> - 2004-12-05 18:40:46
|
Hello Philipp, First, sorry for not answering your email earlier; but now i'm back for real in formsess business :) I know that checkboxes handling is not perfect yet. The way checkboxes are handled in HTML / PHP is quite different from other fields _ but I guess you know that already _ and i've not found a perfect method yet. Could you please summarize your approach ? I have some difficulties putting myself in the right context for the piece of code below :) > Do you mind to exclude the .svn folders in your releases? No, if there are/was .svn files in a release, it was an error. The only releases where I leave .svn files are nightly builds, since NB users are more likely to upgrade their version themselves with a svn client. > I really like formsess - a great project. Looking forward > to have a next stable release. Thank you :) Next stable... a stable release you mean ? j/k anyway i will release 2.0.0 in a while, since i'm already working almost fulltime on the trunk version with very, very neat new features. -- Best regards, Katana mailto:ka...@ka... |
|
From: Katana <ka...@ka...> - 2004-12-03 16:21:50
|
Hello, First, I'd like to apologize about the amount of spam that was posted to this list... I have changed the list settings, and it should be much, much better now. I'll soon post an extensive email about what has been done lately in formsess, and I think that the new features & improvements are worth it :) -- Best regards, Katana mailto:ka...@ka... |
|
From: Philipp K. <pk...@pr...> - 2004-11-01 19:28:50
|
Hi there,
just short feedback:
assign with force=3Dtrue parameter doesn't work for me.
I need to _save_fields with empty values (checkboxes in html forms)
so I had to adapt this method:
<code>
function _save_fields($fields) {
if (!is_array($fields)) settype($fields, 'array');
foreach ($fields as $field) {
if($this->wasSubmitted())
{
// only save non empty values
$value =3D $this->_read_field_value($field);
$fieldkeys =3D $this->_parse_field_name($field);
$target =3D &$this->_dig_into_array($this->_sess_space['values'],
$fieldkeys, true);
$target =3D $value;
}
}
}
</code>
some for the method to read a value.
Do you mind to exclude the .svn folders in your releases?
I really like formsess - a great project. Looking forward
to have a next stable release.
Cheers, fips
--=20
-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/
|
|
From: Katana <ka...@ka...> - 2004-09-27 14:40:59
|
Hello Kirill, >> Here is what I had in mind: >> http://trac.formsess.waterproof.fr/cgi-bin/trac.cgi/ticket/5 >> >> (this is the announced new bug report interface, I have not announced >> its availability yet) Unfortunately no, since I didn't setup users account creation yet. Trac is extremely powerful and simple, but user auth relies on htaccess files, and I have to setup a method to create accounts first, I don't wanna give ticket creation permission to anonymous users. I can probably create accounts manually on demand for now if you want, i don't think hundred of users will request an account yet :) Katana |
|
From: Kirill V. <re...@or...> - 2004-09-25 06:04:26
|
> This is part of my TODO list. Do you think it should be part of the > 2.0.0 release ? I could probably add a ignoreWhiteSpaces parameter to > that validator. Yes, I think it should. > Here is what I had in mind: > http://trac.formsess.waterproof.fr/cgi-bin/trac.cgi/ticket/5 > > (this is the announced new bug report interface, I have not announced > its availability yet) It's really cool! Can we concern your message as official announce? :-) |
|
From: Katana <ka...@ka...> - 2004-09-21 12:28:37
|
Hello Kirill, > Should "empty" validator have option to check the value containing > whitespaces only? This is part of my TODO list. Do you think it should be part of the 2.0.0 release ? I could probably add a ignoreWhiteSpaces parameter to that validator. Here is what I had in mind: http://trac.formsess.waterproof.fr/cgi-bin/trac.cgi/ticket/5 (this is the announced new bug report interface, I have not announced its availability yet). -- Best regards, Katana mailto:ka...@ka... |
|
From: Kirill V. <re...@or...> - 2004-09-20 05:58:17
|
Hi, Should "empty" validator have option to check the value containing whitespaces only? Regards, Kirill Vasiliev |
|
From: Katana <ka...@ka...> - 2004-06-30 09:15:29
|
RP> $validFieldTypes arrays are defined in FormsessValidatorPHP RP> and FormsessValidatorJavascript child. But as far as I can RP> see they are never used in FormsessValidatorPHP. It should have been used, but obviously something is wrong with that. So you're right, at the moment they're not used, but it's a mistake :) -- Best regards, Katana mailto:ka...@ka... |
|
From: Raoul P. <pie...@wa...> - 2004-06-30 07:57:05
|
Hello, $validFieldTypes arrays are defined in FormsessValidatorPHP and = FormsessValidatorJavascript child. But as far as=20 I can see they are never used in FormsessValidatorPHP. am i right? If so why to keep them? Regards Pierre |
|
From: Katana <ka...@ka...> - 2004-06-27 17:32:56
|
DF> The documentation about the selected validator says that the attribut= e DF> to specify the number of selected options is named "count" (which mak= es DF> sense to me) in the code however it's named "selcount" (which doesn't DF> make much sense to me). DF> Any arguments against changing it into "count" in the code to match t= he DF> documentation? OK with me, selcount does not make that much sense. Katana mailto:ka...@ka... |
|
From: Katana <ka...@ka...> - 2004-06-27 17:32:55
|
Hi, I have renamed most validators to more verbose names, like the latest ones (isValidDate and so on). I have of course mapped the old names to the new ones so that there is no BC break. Here is the mapping list: isnotempty: empty, notempty ischecked: checked isvalidemail: email areidentical: identical isisbn: isbn hasselectedoption: selected haslength: size matchessyntax: syntax isvalidurl: url Two validators were not renamed since I'm not sure about how to name them : filesize and age. Any idea is welcome :) -- Best regards, Katana mailto:ka...@ka... |
|
From: David <da...@df...> - 2004-06-25 16:03:47
|
The documentation about the selected validator says that the attribute to specify the number of selected options is named "count" (which makes sense to me) in the code however it's named "selcount" (which doesn't make much sense to me). Any arguments against changing it into "count" in the code to match the documentation? - david |
|
From: David <da...@df...> - 2004-06-24 11:57:31
|
Hi,
when you use the smarty delimiters ({}) in your regexp you have to
enclose it by {literal} tags, so it should look like
<fs:validate field=3D"Plz" check=3D"syntax"
syntax=3D"/[0-9]{literal}{5}{/literal}/" />
- david
On Thu, 24 Jun 2004 13:39:36 +0200
"Wojna" <wo...@wo...> wrote:
> Hi folks!
>=20
> I was just testing the new Formsess 2 release as this error occured:
>=20
> Fatal error: Smarty error: [in adresse.tpl line 31]: syntax error:=20
> unrecognized tag: 5
> (Smarty_Compiler.class.php, line 403) in=20
> /usr/local/lib/php/Smarty/Smarty.class.php
> on line 1102
>=20
> I was wondering because in line 31 there is only a HTML-Tag:
>=20
> 30 <tr class=3D"content">
> 31 <td width=3D"120">PLZ *</td>
> 32 <td><fs:input type=3D"text" name=3D"Plz"=20
> style=3D"width:250px"/><fs:validate field=3D"Plz"
> check=3D"syntax" syntax=3D"/[0-9]{5}/"
> 33 message=3D"Bitte gib eine g=FCltige Postleitzahl ein!"=20
> /><fs:validate field=3D"Plz" check=3D"empty"
> 34 message=3D"Bitte gib eine g=FCltige Postleitzahl ein!"
> /></td> 35 </tr>
>=20
> According to the documentation input-type "text" is an allowed type.=20
> Maybe you can figure out
> what the error is.
>=20
> Best regards
> wojna
>=20
>=20
> --=20
> email: wo...@wo...
> home: www.diekomplettebandbreite.de
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email sponsored by Black Hat Briefings & Training.
> Attend Black Hat Briefings & Training, Las Vegas July 24-29 -=20
> digital self defense, top technical experts, no vendor pitches,=20
> unmatched networking opportunities. Visit www.blackhat.com
> _______________________________________________
> Formsess-devel mailing list
> For...@li...
> https://lists.sourceforge.net/lists/listinfo/formsess-devel
>=20
|
|
From: Wojna <wo...@wo...> - 2004-06-24 11:40:09
|
Hi folks!
I was just testing the new Formsess 2 release as this error occured:
Fatal error: Smarty error: [in adresse.tpl line 31]: syntax error:=20
unrecognized tag: 5
(Smarty_Compiler.class.php, line 403) in=20
/usr/local/lib/php/Smarty/Smarty.class.php
on line 1102
I was wondering because in line 31 there is only a HTML-Tag:
30 <tr class=3D"content">
31 <td width=3D"120">PLZ *</td>
32 <td><fs:input type=3D"text" name=3D"Plz"=20
style=3D"width:250px"/><fs:validate field=3D"Plz"
check=3D"syntax" syntax=3D"/[0-9]{5}/"
33 message=3D"Bitte gib eine g=FCltige Postleitzahl ein!"=20
/><fs:validate field=3D"Plz" check=3D"empty"
34 message=3D"Bitte gib eine g=FCltige Postleitzahl ein!" />=
</td>
35 </tr>
According to the documentation input-type "text" is an allowed type.=20
Maybe you can figure out
what the error is.
Best regards
wojna
--=20
email: wo...@wo...
home: www.diekomplettebandbreite.de
|
|
From: Katana <ka...@ka...> - 2004-06-18 12:30:10
|
RP> Anyway, an other bug: in FormsessFilter, RP> replace RP> var $_curren_tag; // current tag RP> with RP> var $_current_tag; // current tag Fixed in SVN, trunk (rev #516) Katana |
|
From: Raoul P. <pie...@wa...> - 2004-06-18 08:12:11
|
david,
> Thanks for reporting, I fixed that.
OK
> (without support for dynamical fieldnames, this is too=20
> advanced to make
> it into the 2.0.0 release imho)
Booo :-)
No one of the tree step changes I proposed have side effect. Neither the =
ones in the last email. It would have been a good foreseen work, even if =
I may not be able to give a finish patche for your next release.
Anyway, an other bug: in FormsessFilter,
replace
var $_curren_tag; // current tag
with
var $_current_tag; // current tag
Regards
Pierre
|
|
From: David <da...@df...> - 2004-06-17 09:23:28
|
Thanks for reporting, I fixed that.
(without support for dynamical fieldnames, this is too advanced to make
it into the 2.0.0 release imho)
- david
On Thu, 17 Jun 2004 10:22:56 +0200
"Raoul Pierre" <pie...@wa...> wrote:
> Hello,
>
> In Formsess SVN from 06/03/2004
>
> 1/ In FormsessValidatorJavascriptSyntax::addValidationCode
> Replace
> $this->addLine("// syntax validation for $fname");
> with
> $this->addLine("// syntax validation for $fieldName");
> or better
> $this->addLine( '// syntax validation for '
> . $this->_fsObject->_smartyEmbed('/literal')
> . $fieldName
> . $this->_fsObject->_smartyEmbed('literal')
> );
>
>
>
> 1/ In FormsessValidatorJavascriptChecked
>
> Replace
> $this->addLine("// checks if $fname is checked");
> with
> $this->addLine("// checks if $fieldName is checked");
> or better
> $this->addLine('// Checks if '
> . $this->_fsObject->_smartyEmbed('/literal')
> . $fieldName
> . $this->_fsObject->_smartyEmbed('literal')
> . ' is checked'
> );
>
> and
> $this->addLine(" if ($fieldVarStrin g[i].checked) {");
> with
> $this->addLine(" if ({$fieldVarString}[i].checked) {");
>
>
> Regards
>
> Pierre
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
> Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
> Conference, June 28 - July 1 at the Moscone Center in San Francisco,
> CA REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code
> NWMGYKND_______________________________________________
> Formsess-devel mailing list
> For...@li...
> https://lists.sourceforge.net/lists/listinfo/formsess-devel
>
|
|
From: Raoul P. <pie...@wa...> - 2004-06-17 08:23:47
|
Hello,
In Formsess SVN from 06/03/2004
1/ In FormsessValidatorJavascriptSyntax::addValidationCode
Replace
$this->addLine("// syntax validation for $fname");
with
$this->addLine("// syntax validation for $fieldName");
or better
$this->addLine( '// syntax validation for '
. $this->_fsObject->_smartyEmbed('/literal')
. $fieldName
. $this->_fsObject->_smartyEmbed('literal')
);
1/ In FormsessValidatorJavascriptChecked
=20
Replace
$this->addLine("// checks if $fname is checked");
with
$this->addLine("// checks if $fieldName is checked");
or better
$this->addLine('// Checks if '
. $this->_fsObject->_smartyEmbed('/literal')
. $fieldName
. $this->_fsObject->_smartyEmbed('literal')
. ' is checked'
);
=20
and
$this->addLine(" if ($fieldVarStrin g[i].checked) {");
with =20
$this->addLine(" if ({$fieldVarString}[i].checked) {");
=20
Regards
Pierre
|
|
From: David <da...@df...> - 2004-06-14 12:07:19
|
Labas Zilvinas,
the current developement version features some major changes and I
think the problem you described does not occur there anymore.
I recommend you to either pull the latest version from the subversion
repository or to download the latest snapshots both should be pretty stable.
- david
On Sun, 13 Jun 2004 15:36:30 +0000
Zilvinas Saltys <ar...@es...> wrote:
> Hello,
>
> I was trying to do the following:
>
> $new = $this->module->getNew($gid);
>
> $fs->reset();
> $fs->assignArray($new);
>
> $fs->assign('body', preg_replace('!<br.*>!iU', "",
> $fs->get_value('body')), true);
>
> Reassigning the body does not work in 2.0.0-pre. The assign function
> is in this chain:
>
> assign->_save_fields->_read_field_value
>
> In the read_field_value:
>
> // first check within the cached values so that we don't read twice
> if (isset($this->_fieldvalues[$field])) {
> return $this->_fieldvalues[$field];
> }
>
> This couses the problem. I was able to fix this by adding an elseif
> under the first if sentence:
>
> // If overwrite was not asked, we test if a value exists
> if (!$force && (isset($this->_sess_space['values'][$field]) &&
> !empty($this->_sess_space['values'][$field]))) {
> return;
> }
>
> elseif ($force && isset($this->_fieldvalues[$field]))
> {
> unset($this->_fieldvalues[$field]);
> }
>
> Maybe i fooled my self and this is not a bug and i don't know
> something :) Please tell me.
>
> Bye
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the new InstallShield X.
> >From Windows to Linux, servers to mobile, InstallShield X is the
> one installation-authoring solution that does it all. Learn more and
> evaluate today! http://www.installshield.com/Dev2Dev/0504
> _______________________________________________
> Formsess-devel mailing list
> For...@li...
> https://lists.sourceforge.net/lists/listinfo/formsess-devel
>
|
|
From: Zilvinas S. <ar...@es...> - 2004-06-13 12:36:43
|
Hello,
I was trying to do the following:
$new = $this->module->getNew($gid);
$fs->reset();
$fs->assignArray($new);
$fs->assign('body', preg_replace('!<br.*>!iU', "", $fs->get_value('body')), true);
Reassigning the body does not work in 2.0.0-pre. The assign function is in this chain:
assign->_save_fields->_read_field_value
In the read_field_value:
// first check within the cached values so that we don't read twice
if (isset($this->_fieldvalues[$field])) {
return $this->_fieldvalues[$field];
}
This couses the problem. I was able to fix this by adding an elseif under the first if sentence:
// If overwrite was not asked, we test if a value exists
if (!$force && (isset($this->_sess_space['values'][$field]) && !empty($this->_sess_space['values'][$field]))) {
return;
}
elseif ($force && isset($this->_fieldvalues[$field]))
{
unset($this->_fieldvalues[$field]);
}
Maybe i fooled my self and this is not a bug and i don't know something :) Please tell me.
Bye
|
|
From: Katana <ka...@ka...> - 2004-06-05 08:40:07
|
Hi both of you, > About test units/scripts: we don't have any (at least not that I know..) > Betrand? > I'm not familar with automated testing. Would you use PEAR's php unit(2)? > What kind of tests would you create for formsess? (maybe you can just > include your tests for the validate tag you talked about) Several times, I have been thinking about writing Unit Tests for formsess. But I have to admit that due to my very little experience in that domain, and to the "complexity" of formsess environnement, I don't really know how to do that. Formsess really has a specific architecture when compared to most libs (lots of different types of components: prefilter, validators, (php & js), tag functions, formsess class itself...). By example, testing if formsesss still parses a tag correctly requires 2 steps (prefilter => smarty function using tag class, and smarty function => html). And of course both operations imply lots of logic and can't be reduced to a single method / function. But of course I think that unit tests would be a good asset for the quality of the releases. Pierre, if you have any hint about how unit tests could be implemented for formsess, I would be glad to spend some time on it :) Bertrand |
|
From: Raoul P. <pie...@wa...> - 2004-06-05 07:35:57
|
Hello,
The third request is about the Formsess Input tag. Now we really start =
with the subject.
At the moment, the type of an input tag must be coded in the template. =
And so you can't easily shift between radio and checkbox types for =
exemple.
To do it we need to delay the type controls in FormsessTagInput::getTag.
The changes would be:
- create the smarty_function_fs_input function:
function smarty_function_fs_input($params, &$smarty) {
$type =3D $params['type'];
$fileName =3D 'fs_input_' .$type;
$functionName =3D 'smarty_function_'.$fileName;
unset($params['type']); =20
require_once $smarty->_get_plugin_filepath('function',$fileName);
=20
return $functionName($params, $smarty);
}=20
- remove the type controls from FormsessTagInput::getTag, that is the =
class becomes:
class FormsessTagInput extends FormsessTag {
=20
function getTag() {
$type =3D 'input_' . $this->getAttributeValue('type');
$this->setName($type);
=20
// create the string with the smarty delimiters and all =
attributes
$string =3D 'fs_input' .$this->glueAttributes(); // 'fs_input' =
here without tail underscore
return $this->getCaptures() . $this->smartyEmbed($string);
}
}
- convert string to array in smarty_function_fs_input_checkbox:
function smarty_function_fs_input_checkbox($params, &$smarty) {
[...] =20
if (in_array($value, (array)$itemValues)) {
$params['checked'] =3D 'checked';
}
[...] =20
- put the radio control in smarty_function_fs_input_radio:
=20
function smarty_function_fs_input_radio($params, &$smarty) {
$fs =3D& $GLOBALS['__fs_current'];
$name =3D $params['name'];
// the "value" attribute is mandatory for a radio button
if ( (! isSet($params['value']) || ($params['value'] =3D=3D '')) =
) {
return '[fs:radio] the value is mandatory for a <fs:input =
type=3D"radio"> tag';
}
[...] =20
Regards
Pierre
|
|
From: David <da...@df...> - 2004-06-04 14:44:26
|
Hello Pierre,
thanks for the feedback! I removed the uneeded code (just forgot it
yesterday) and modified the example to use the SmartyFormsess class in
libs/ to make it work again.
I cc'ed formsess-devel again, this might be interessting for others as
well..
About your proposal: In fact I did lots of work to allow smarty syntax
in most of the tag attributes to make formsess as flexible as possible.
The only attributes that must contain fixed values are those processed
by the prefilter.
It's type, name and check afaik, they're used to add the javascript
validation code (for this the field types must be checked).
I'd be happy to extend the flexibility however the formsess code should
be kept simple for both performance and maintance reason.
I'm looking forward to have a look at your proposal!
About test units/scripts: we don't have any (at least not that I know..)
Betrand?
I'm not familar with automated testing. Would you use PEAR's php unit(2)?
What kind of tests would you create for formsess? (maybe you can just
include your tests for the validate tag you talked about)
- david
On Fri, 4 Jun 2004 13:45:23 +0200
"Raoul Pierre" <pie...@wa...> wrote:
> Hello David,
>=20
> > I found some time to look over that again and it should really work
> > now.
> >=20
> > I don't have time to heavily test it at the moment. You could help a
> > lot by trying if it works for you now.
>=20
> First tests seem ok. Just remove
>=20
> elseif ($type =3D=3D 'input_checkbox') {=20
> //this matches both undefined and defined indexes
> if (preg_match('!\[(.*)\]$!', $this->getAttributeValue('name'),
> $m_offset)) {
> $this->setAttributeValue('cb_offset', $m_offset[1]);
> }
>=20
> from FormsessTagInput::getTag=20
>=20
> Or add somewhere in smarty_function_fs_input_checkbox the code:
> =20
> unset(params['cb_offset'])
>=20
> Note: now that Smarty_formsess.class.php is no more in Samples dir,
> the sample is broken. So I added a new Smarty_formsess.class.php file
> with...
>=20
> <?php
> require FORMSESS_SMARTY_PATH.'Smarty.class.php';
> require '../libs/SmartyFormsess.class.php';
>=20
> class Smarty_Formsess extends SmartyFormsess {
>=20
> function Smarty_formsess() {
> $this->SmartyFormsess();
> }
> }
> ?>
>=20
> > (I changed only that one file, so you could quickly grab it from
> > svn. If that's a problem tell me, then I can eMail it to you.)
>=20
> I have no more problem to access to the svn repository (the new text
> in the download page on Formsess Web site is now ok).=20
>=20
> For your information, I have tested the function.fs_input_checkbox.php
> file from 25-05-04's Formsess-Trunk.tgz and it was already ok for me.
> So ...
>=20
> *****
>=20
> I take advantage of this answer to ask your opinion about an idea.
>=20
> I am working on an program with a Presentation/Business/Data access
> layers pattern. I want to specify:
>=20
> - the validation of inputs from the Business layer (likely with some
> wrapping in the Presentation layer). All the knowledge about data has
> to be confined in the Business layer.
>=20
> - the type of HTML input from the workflow part of the Presentation
> layer.=20
>=20
> I'm working with Copix framework (http://copix.aston.fr). Copix is
> built on the MVC pattern. It uses heavely Smarty as template engine.
>=20
> About Formsess: I need to be able to set very late the value of
> attributs in the template tags. In fact nothing coded in the template
> itself: all the mandatory attributs must be specify by variable. Even
> the type of input tag.
>=20
> At the moment, it's not possible to do it with Formsess. I'm using the
> Formsess-Trunk.tgz from 25-05-04.
>=20
> >From a rapid look, I think it would not be too hard to improve
> >Formsess in this way. I have already tested some changes needed to
> >this (mainly by setting Smarty variable very late: at run time, from
> >the Smarty function).=20
>=20
> Currently I am working on the fs:validate itself. I think I will have
> some working and tested(=B0) version of fs:validate at the end of next
> week. In a first step, with some strong restrictions (as the
> impossibility to use the same variable to specify name of differents
> tags as soon as the first one has a validate tag), but easy to deal
> with.
>=20
> Are you interested by such a job? If yes, have you any recommandation
> on the way to sent it.
>=20
> Note (=B0): I didn't see any unit test class in the SVN repository. Have
> you any? If not, have you any test script(s)?
>=20
> Regards
>=20
> Pierre
>=20
>=20
>=20
|
