Re: PHP Framework and FormBuilder crosslinks
| From: | Justin Patrin | Date: | Mon, 06 Dec 2004 22:34:34 +0000 |
| Subject: | Re: PHP Framework and FormBuilder crosslinks | ||
| References: | 1 | Groups: | php.pear.general |
| Request: | Send a blank email to pear-general+get-16060@lists.php.net to get a copy of this message | ||
On Mon, 06 Dec 2004 22:49:58 +0100, Rodrigo Alvarez <papipo@gmail.com> wrote:
> Hi all,
>
> I have some doubts:
>
> 1) Which PHP Frameworks do you know that use DB_DataObject and in
> general, PEAR packages to common tasks?. I only know Seagull, but I want
> to know if there are more, to compare them and pick one for my next project.
Never used any myself. Yawp is a package which combines lots of PEAR
packages but it's not a framework per-se.
>
> 2) I use FormBuilder with crosslinks. When form successfully submits and
> it is freezed, crosslinks appear as [ ], but selected ones aren't
> checked [x]. This only affects to display terms, not to database. I mean
> that FormBuilder works well, but crosslinks when form is freezed doesn't
> look as they should.
This is a known bug. I'm working on trying to fix it now, but it's
very sketchy as HTML_QF doesn't support setting checked/unckecked with
setdefaults and unchecked checkboxes are often not even submitted.
>
> 3) Some people don't use QuickForm and/or FormBuilder because their lack
> of performance (sometimes). Is there a way to cache them? For example,
> FormBuilder checks for last modification date of DataObject, and if
> needed, re-generates QuickForm object and caches it, if not, it reads
> all needed things from cache.
"Some people"? I haven't heard many complaints. One person has created
a bug report about its memory footprint, but there is no solution
proposed. FormBuilder is a very large pirce of code and has a *lot* of
auto-generation features. One way to speed things up is to use an
object code cache (such as Zend Optimizer or TurckMMCache). You could
easily create your own FormBuilder driver which saved Form objects in
a cache and checked for them. It's out of scope for FormBuilder to
handle this natively. You will likely have a problem with the element
values if you do this, so you'd have to be careful.
>
> Thanks,
>
> Rodrigo Alvarez.
>
--
Justin Patrin