Re: [eGroupWare-core] presentation/ bo-so layer standardization

[Carsten W. <wo...@eg...>]

Hi,

On Friday 15 April 2005 15:23, Vinicius Cubas Brand wrote:
> Also, our BO/SO class need some documentation, that we should do after this
> rush period finishes. But basically I like it because it creates a standard
> where it is easier and more natural to do good OO code over it. For
> instance, here is the full code of an class of our entities, that have a
> lot of methods like read, write, update, relate with other entities etc.:
>
> class bo_role extends bo_entity
> {
> function bo_role()
> {
> $this->bo_entity('role');
> }
> }
>
> So all one need to implement is very specific methods. In reality this is
> an inherited class of a entity. We've thought in an entity model, where the
> relationships are set between entities with methods of relation and other
> base methods implemented in the API classes. Another great difference is
> that there is no more the boundary of an application for an entity (at
> least not so strong).

I agree that a better inheritance-structure would help the egw-API to avoid 
code-duplication and make features available to the modules more easily. I'm 
sure, there will be more discussion on that, as soon as we see some of your 
code in cvs.

Cheers,
Carsten

-- 
THE K Desktop Environment:  http://www.kde.org  mailto:wo...@kd...
My very own little site  :  http://www.wolffcarsten.de