Re: idea of an array/callback storage
Matthias Nothhaft <[email protected]> Sun, 06 Nov 2005 23:44:41 +0100
| Newsgroups | gmane.comp.php.pear.liveuser |
|---|---|
| Message-ID | <[email protected]> |
Lukas Kahwe Smith schrieb:
> Matthias Nothhaft wrote:
>
>> Arnaud Limbourg schrieb:
>>
>>
>>> We need documentation :)
>>>
>>>
>>>
>>
>> The worst thing is that several doc comments are incomplete or obsolete.
>> That makes it very hard for people like me that did not write any line
>> of the code to understand what's going on. :-(
>> So it is even harder for "foreign people" to write documentation ;-)
>
>
> yeah that is indeed a problem ..
> please report any issues you find ..
One example: LiveUser/Perm/Storage/MDB2.php --> several methods have
no docs what they do - only parameters docs
>
> as for the original question .. with a little tweaking (essentially
> passing the auth container to the permFactory() so that we could have
> a container that just returns the original auth container back as a
> reference) method we should be able to do this and maybe with a little
> __call() magic you could re-use the current containers for the part
> and only overload specific methods. so in this case you would have an
> auth container that aggerates existing auth and perm containers and
> partially overloads.
Well, I simply need the possibility to setup some pre-defined users and
rights without a database for rapid prototyping.
I thought it would be nice to cope with that problem by providing "array
countainers" for auth and perm !?
So I could simply write some arrays like
$users = array(
1 => array('handle' => 'peter', 'passwd' => 'hd83hd8'),
2 => array('handle' => 'paul', 'passwd' => 'j924uh2')
)
$perms = array(
1 => array('...
Terrible... I just wanted to write an array example for the Perm, but I
can't! Your doc comments of the admin perm storage only tell me to "set
$data" - but what the hell is $data ??? no (at least not enough)
information about possible/allowed fields... :-(
You did a great work - no question, I love it. But you keep people away
from that great work by the lack of complete doc comments. ;-)
It is no problem for people to look into the code and read the comments.
But if missing comments force me to know the package and the database
schema inside out, the fun is over ;-)
Ok... I don't want to complain. Just a try to request for complete
comments ;-)
Regards,
Matthias