Hey, The goal is to make a fully pluggable address book. So that if I want to use something other than LDAP or the native roundcube address book, I can quickly integrate a new address book using the interface I want to make.
So to the end user, there won't be any changes. But it'll open up the address book to easier development of third party address books. David On Thu, 13 Mar 2008 14:18:06 +0100, [EMAIL PROTECTED] wrote: > On Wed, Mar 12, 2008 at 11:30 PM, <[EMAIL PROTECTED]> wrote: >> Hello, >> >> Here are the changes I would like to propose to the address book: >> >> 1. Have an address book factory Class which will return the list of > address >> books ( for column that appears with ldap ) >> 2. Create an interface class for working with address book - Each > Address >> Book class will have a method to report it's capability ( predictive > text, >> list, search etc... ) >> 3. The factory will load the correct class for called address book, and >> return the object. >> >> Roundcube will work with the interface defined by the interface class. >> >> These are the changes I would like to perform to the address book and > they >> will not be PHP4 compatible. >> >> What do you guys think? > > Hey David, > > this sounds all good. PHP4 is of no concern anymore. Though 0.1.1 > bugfix release will likely support it, the rest of RoundCube will move > to PHP5. > I don't know exactly what you are trying to do, so if you don't feel > like doing it anyway, maybe send some class skeletons to the list. I > am sure though this is heading in the right direction! > > Thanks, > Till _______________________________________________ List info: http://lists.roundcube.net/dev/
