Re: [phpldapadmin] Fate of EntryWriter1 class
Deon George <[email protected]>
| Newsgroups | gmane.comp.ldap.davedap |
|---|---|
| Message-ID | <[email protected]> |
Hi Cri, Yes, a lot of the functions moved into PageRender and TemplateRender - I essentially merged Reader and Writer into PageRender. The functions related to Template rendering are in TemplateRender, and those relating to the query are in QueryRender, etc. The whole idea was that whenever an attribute or attribute type is rendered, it would also be rendered the same way (as part of a template, a query, adding a value, etc)... Additionally, the communications part of PLA was replaced with one that I use for some other work, simplifying the interaction with the LDAP server. (And since I maintain the same code in other projects, it was making it easier to debug). What changes have you made? ...deon ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ______________________________________ phpLDAPadmin development mailing list. To unsbuscribe: https://lists.sourceforge.net/lists/listinfo/phpldapadmin-devel http://phpldapadmin.sourceforge.net/