Re: QuickForm isn't

I realize that the name attribute will normally accept "[]", but it strikes me as more work to keep separate name and id attributes then to force everything to work with the valid ID chars. I see what you mean about the name attribute != NAME DTD token. The confusing text is here: http://www.w3.org/TR/REC-html40/types.html#type-name I'm using the an extension of the regular Array renderer, then just passing that to Smarty. The extension provides nested group support, better label support, and access key support. The only additional code that is loaded between 0.50 secs and 0.85 secs is: require_once 'HTML/QuickForm/checkbox.php'; require_once 'HTML/QuickForm/text.php'; require_once 'HTML/QuickForm/submit.php'; ~Seth On Oct 11, 2006, at 1:16 PM, Alexey Borzov wrote:

Hi, Seth Price wrote:

I don't have the specific example that I was referring to (30+ seconds render), it and its traces have since been optimized/deleted.

Were you using ArraySmarty renderer, by chance?

But, as an example, the page I'm working on now takes ~0.25 seconds to render when there is no content. (PowerMac G5, ~2GHz, faster than my normal dev machine) This is when require_once()ing my extension of Smarty, and a custom mapping class which is 5k+ lines of code. When I require_once() my extension of QuickForm, similar to what I previously linked to, the render time (with no QF creation) doubles (~0.50 secs). This is a good part of that code bloat that I ranted about. If I then create the form (no QF validate()), the time jumps again to ~0.85 seconds. If I then validate(), render, and print my QuickForm, the time increases marginally (~0.88 secs). That's *triple* my render time when I _only_ have the overhead of PEAR's DB connection, map object creation, and a Smarty include()/fetch(). (Note that the validation is only partially implemented, due to afore mentioned problems with QuickForm rules. Actual validation time would be even greater.)

Well, the numbers you provided show clearly that most of the time is spent on loading and parsing the PHP files. Install some bytecode cache. --PEAR General Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php