Re: unified db?

Lukas Smith wrote: > I do have time to pearify Metabase. I looked over the API of metabase. It is a clear API from what I can tell so far. I thought the prefix of Metabase on all the function calls was distracting and made the function names too verbose (an API usability issue?). What about this: $mb->MetabaseGetBooleanFieldValue becomes the more PEAR like $mb->getBooleanFieldValue To convert the API to a PEAR naming style I think a general rule would be to eliminate the Metabase tag and lowercase the first letter of the next word. After the API conversion, I would then try see if PEAR::DB and Metabase can live harmoneously together in a deeper sense then just a common looking API. For example, can the same $db object access PEAR DB methods and Metabase methods. Adding some core Metabase methods first might work - enough to demonstrate that metabase functionality is now accessible in PEAR DB in a useful fashion. I have no idea if this approach will work however without doing more research on the matter. What did you have in mind for PEARifying Metabase? Regards, Paul Meagher > Best regards, > Lukas Smith > smith@dybnet.de > _______________________________ > DybNet Internet Solutions GbR > Alt Moabit 89 > 10559 Berlin > Germany > Tel. : +49 30 83 22 50 00 > Fax : +49 30 83 22 50 07 > www.dybnet.de info@dybnet.de > _______________________________ > > > > -- > PEAR Development Mailing List (http://pear.php.net/) > To unsubscribe, e-mail: pear-dev-unsubscribe@lists.php.net > For additional commands, e-mail: pear-dev-help@lists.php.net > To contact the list administrators, e-mail: php-list-admin@lists.php.net > >