Re: suggestion

> The problem really with getting the pear web site out is that I think it > should have a strong integration with the new php web site. meaning, it > should tap into the user authentication (if there is any), tracking, design, > etc. ie, it should be an integrated component of the new php website (i > don't currently know what the status of the new site is). As far as > pear.php.net, there is already a database scheme layed out, as well as the > format for the pear documentation (and I have a temporary XSL stylesheet > lying around somewhere, which can change the XML into HTML quite nicely)... yes? none of those things prevents you from using binarycloud. binarycloud doesn't dictate very much about how you should do things. > What is really need for the pear website is db abstraction, for which, pear > has a strong DB layer, which supports (the database of choice :) MySQL, the > only other logic it needs to use (besides what's distributed with PHP > itself) is a templating engine, I've already got a basic one I've been > messing around with (akin to EasyTemplate), I haven't yet got a chance to > look at IntegratedTemplate yet (in the pear distribution)... but who not use binarycloud, given that it is complete, and flexible? binarycloud was designed specifically for building sites like pear.php.net. it sounds like you have not had a look at binarycloud, and are making assumptions about its use and intent. please have a look at http://www.binarycloud.com, download the code, etc. :) -alex