[suspicious - maybe spam] [PEPr] Comment on HTML::HTML_FormPersister

From: Date: Tue, 18 Jan 2005 16:57:55 +0000
Subject: [suspicious - maybe spam] [PEPr] Comment on HTML::HTML_FormPersister
References: 1  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-35583@lists.php.net to get a copy of this message
Dmitry Koterov (http://pear.php.net/user/koteroff) has commented on the proposal for HTML::HTML_FormPersister. Comment: a) As I googled, flexyparser is written in C - http://devel.akbkhome.com/svn/index.php/akpear/flexyparser/ - and it needs dl() to load - it is not supported on most virtual hostings. HTML_Template_Flexy is complete templating system, it uses its own ideology to work with. Tidy does not support callbañks (as I know) and loaded by default only in PHP5 (not in PHP4) - same troubles with hostings (not everybody could allow himself to use own machine fully dedicated to his site :-). b) About performance. Caching is not needed - ideologically. Class works with ANY HTML generated by ANY type of code (manual-written or generated by template system- no matter). But you shouldn't take care about performance, because HTML_SemiParsed DOES NOT parse input HTML completely. It searches for few tags and parses them only. For example, it searches for "<INPUT", "<SELECT" etc. sequences in HTML and then, if found, performs callbacks. PCRE regular expressions are extremely fast in these cases and gives us no overheat if page contains no form elements (for example). So, if you have not so many form elements in your page (<20), performance is not a problem at all. c) About "seperation of input and rendering". If user have entered some text in the form, afrer submission he expects that these texts will stay uncganged (if this form is shown again, as it performed in most cases). Getting and user-defined input processing is the task of controller, and it could still be performed as usual. No changes. d) About "difficult to register callbacks" - I do not understand, please work out in detail. e) Words about "code from include" is not understood too - please itemize. Maybe you said about flip-fields? They are not so necessary and could be excluded from the package, because they only simplify working with <select multiple> elements, no more. Proposal information: http://pear.php.net/pepr/pepr-proposal-show.php?id=193 -- Sent by PEPr, the automatic proposal system at http://pear.php.net

« previous php.pear.dev (#35583) next »