Re: suggestion
| From: | Alex Black | Date: | Fri, 19 Jan 2001 20:11:21 +0000 |
| Subject: | Re: suggestion | ||
| References: | 1 | Groups: | php.pear |
| Request: | Send a blank email to php-pear+get-1070@lists.php.net to get a copy of this message | ||
how far along is the development of the "new php website"?
I know the pear site is two pages right now, which are ancient.
-alex
--
Alex Black, Head Monkey
enigma@turingstudio.com
The Turing Studio, Inc.
http://www.turingstudio.com
vox+510.666.0074
fax+510.666.0093
Saul Zaentz Film Center
2600 Tenth St Suite 433
Berkeley, CA 94710-2522
> From: Sterling.Hughes@pentap.net ("Sterling Hughes")
> Organization: Pentap Technologies
> Newsgroups: php.pear
> Date: 19 Jan 2001 02:57:26 -0800
> Subject: Re: [PHP-PEAR] suggestion
>
>
> "Alex Black" <enigma@turingstudio.com> wrote in message
> news:B68CD700.1003F%enigma@turingstudio.com...
>>> 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.
>>
>>
>
> I have taken a look at it...
>
> Its a development platform for web sites... It might be something that the
> developer's of the new PHP web site might consider using, however, what I'm
> saying is that the PEAR site should not have a platform like that, instead
> it should tie into the new PHP website's authentication, etc... If the new
> PHP web site uses binarycloud for the site, then yes, pear can indirectly
> use it, yes, of course. But pear shouldn't have its own system, but rather
> be integrated as a part of the PHP website. Ie, the major flaw I see of
> CPAN is its not directly tied to Perl.com, but rather separate. I think
> PEAR should be tied into the new PHP web site and they should ideally all
> come together and work...
>
> -Sterling
>
>
>
> --
> PHP Extension and Add-on Repository (PEAR) mailing list.
> Documentation can be found at http://pear.php.net/doc/pear.html
> To unsubscribe, e-mail: php-pear-unsubscribe@lists.php.net from the
> mail address you subscribed with.
>