Re: RFC with pepr
| From: | Nuno Lopes | Date: | Fri, 06 Aug 2004 15:19:35 +0000 |
| Subject: | Re: RFC with pepr | ||
| References: | 1 | Groups: | php.doc.web |
| Request: | Send a blank email to doc-web+get-145@lists.php.net to get a copy of this message | ||
> Hi all,
>
> Today I've been messing around with pepr for the RFC system...
>
> Now I have a few questions.
>
> Pepr uses PEAR classes for almost everything.
> for the database, for the forms, for access permissions and a bbcode
parser
>
> Now I, and I guess others, would like to know how we want things.
>
> Do we want to use (PEAR) classes for
>
> - the database (SQLite) connection and related functions
> - for the forms
> - for permissions, Damblan is used for this at pear.php.net
>
> and if we don't, how will we do it?
>
> - create our own or use the default sqlite functions (we could create a
class
> with simple functions ($db->connect(),$db->query(),$db->escape()) and use
> that in every file)
> - create simple functions for the forms (like
addTextField(),addTextArea()),
> or do we just use html
I think we don't need to use PEAR classes. If we decide to use Pepr, we need
to use the the PEAR classes it needs (there is no point in rewriting them).
For the DB access, I think we don't need any external class.
> - do we use the magiccookie login info and an array for the admins
(in_array,
> simple but bugs.php.net also does this)
The permission system we are going to use is the magic cookie. The master
server has already a script to let us authenticate the users (which has the
token broken). It won't be difficult to write (I can do that), and it won't
use any PEAR classes.
Nuno