Re: Account Request : phpHtmlLib
| From: | walt boring | Date: | Thu, 12 Jun 2003 23:23:37 +0000 |
| Subject: | Re: Account Request : phpHtmlLib | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-17364@lists.php.net to get a copy of this message | ||
Klaus Guenther wrote:
Hello, First let me say that I have a big problem with the name. PhpHtmlLib basically claims to be the whole HTML category. So that would need to be changed. --I don't have a problem with changing the name. I can do a redirect on the web page to the newname. :) The lib was created a while back before PEAR really took off, and it was originally meant just for building/rendering HTML, but it is a LOT more then that now. I would like to maintain compatibility with the current project though. The classes don't have phphtmllib in any of their names, so its not that big of a deal.
It can build XML tags/documents, SVG, WML, HTML/XHTML among others. Breaking it up into sperate packages makes sense as long as its still under the same base package.I know that PEAR has the HTML classes, but I believe phpHtmlLib has a lot to offer for PEAR users. According to the FAQ, PEAR can contain "competing" classes/libs, so I thought I'd ask.It seems to me that you should break it up into various elements or else call it a template system (e.g., HTML_Template_PhpHtmlLib). However, you also have the possibility of creating a package of the existing solution that can be installed using the PEAR installer, without being part of PEAR. That sounds like the best solution to me. ---well, its not an HTML templating system, so it would be confusing to place it as such.
package, but I do understand the pain of that suggestion. Walt** <http://pear.php.net/package-info.php?pacid=166>The problem I have is where does phphtmllib fit in PEAR. phphtmllit seems to fit under the HTML as well as the XMLproject spaces, but its much more then just that. I would like to propose a new category called UI, which phptmllib would live under. This would be a generic top level category for building interfaces with php. The GTK classes could live under there, as well as any future classes that are used for building interfaces.As for the UI category... it sounds interesting... and could contain all template classes, etc. In principle, I think it would be a good thing, but recategorizing classes would be a mess. ----- It would only mean moving 1 class so far that I see, which is the Gtk_VarDump