Re: Software Architecture/Design

On 4 June 2010 15:26, <[email protected]> wrote:

> ----- "Morten Brodersen" <[email protected]> a écrit :
> Forgive me if I'm wrong, but this doesn't this approach limit the
> flexibility of the system ? I mean, if behaviors are called explicitely,
> then adding a behavior need changes in other place of the code (meaning in
> turn that beyond some limit, the code will be awfully difficult to
> maintain).
>
> It also seems difficult to me to build a data-driven approach on the top of
> this appraoch (but again, I might be wrong).
>
> Or am I missing something obvious ?
>
> -- Emmanuel Deloget
>
>
The system seems wonderful for data oriented approach (not data driven, that
means something different).
The important aspects of data oriented are maintained and although you would
have to change a "few things" whenever the data changes, it seems to me like
the POs are very safely encapsulated by their attachment to SOs but not each
other.

-- 
fabs();
Just because the world is full of people that think just like you, doesn't
mean the other ones can't be right.

_______________________________________________
Sweng-Gamedev mailing list
[email protected]
http://lists.midnightryder.com/listinfo.cgi/sweng-gamedev-midnightryder.com