Re: Account Request : phpHtmlLib

Hi! Well, sometime ago there was a heated discussion here about a separate HTML_Select class vs. using a HTML_QuickForm_select. I made the following proposal http://marc.theaimsgroup.com/?l=pear-dev&m=105343287215263&w=2 : ------------------------------- Let me suggest some more modular packages: HTML_Textarea HTML_Input_Hidden HTML_Input_Checkbox HTML_Input_Checkbox_Collection HTML_Input_Checkbox_Collection_With_Javascript_Validation and, last but not least HTML_BR ------------------------------- but was immediately told to shut up. I am really glad to see that such useful modularity is implemented (including even HTML_BR) in phpHtmlLib that is being now seriously (?) proposed to PEAR. Harry Fuecks wrote:

Personally I think phpHTMLLib excellent and should definately be part of PEAR in some form. It has the potential to help us parse ASP.NET pages, something which I've experimented with here: http://www.sitepointforums.com/showthread.php?threadid=112379

As I am good at spotting conspiracies, I think this is a conspiracy of SitePoint community to bring "bloat" to PEAR, as they are very fond of discussing said "bloat" and need to have something to back up their claims: http://sitepointforums.com/showthread.php?threadid=112753 Harry, do you really think that phpHtmlLib has a good OO design, which SitePoint members are so fond of? What design pattern can be used to get rid of having a class for each possible HTML tag?