was [OGo-Users] Ogo and ERP or CRM

 >> I read in a previous post that Chris stated that Ogo shouldn't 
become bloatware and that the issue was integration, actually I think 
this is the good way to go.

>
> Well, I do not. OGo is very modular so whether you want to have a 
> feature or not can be controlled by installing or not installing a 
> certain module. Eg you can't access the invoice stuff because the 
> invoice module isn't installed - that doesn't bloat the setup of 
> non-invoice users in no way.
>
>
yes this is proper design. :)

arch design 101
the ability to clearly integrate with other entities is critical to 
adoption of any software.
integration relies on modularity.
ogo is modular from the ground up.
bloat comes from monolithic architecture. ( and marketing dept ) :)

in open source one must be modular, because module development proceeds 
in parallel.
as long as the interfaces remain consistent between modules, 
everything's ok.

kelley g
http://toasterz.com
http://exchangekiller.com

-- 
OpenGroupware.org Discussion [email protected]
http://mail.opengroupware.org/mailman/listinfo/discuss