Re: EGS/Postgresql - Was Re: [Web-erp-developers] Cheap

[Stins, D. <DR...@Zi...>]

Jake,

Thanks for your comments.

I am not a fan of pear:db. I prefer to use standard sql. That is already a
big step for portability + the clean and mean weberp script ConnectDB.inc.
So it should not be too hard to port web-erp to another db engine.

Smarty might be interesting, but I am already glad when css is optimal used.

Multiple company support is interesting.

Does it also support ldap (nds)?

with best regards,

Dick Stins

----- Original Message -----
From: "Jake Stride" <ns...@us...>
To: <web...@li...>
Sent: Sunday, September 19, 2004 7:41 PM
Subject: Re: EGS/Postgresql - Was Re: [Web-erp-developers] Cheap


> Stins, Dick wrote:
>
> >Jake,
> >
> >I think that common functions which are needed in weberp and in your crm
> >software should be encapsulated in classes, so you do not need to know
where
> >the information is comming from (postgres or mysql).
> >
>
> At the moment it kind of should be in that it uses PEAR:DB for
abstraction.
>
> > When you want to
> >integrate web-erp and your crm software, you still need to integrate the
> >authentication and the address books processing and ....
> >The design of these issues should be loosely connected or we should
create
> >one big project (wegs-erp?).
> >
> >
> That could be interesting and worthwhile, is it something people may be
> interested in?
>
> >The same for all your code which needs views. Those should be
encapsulated
> >in classes, so it's easy to write an alternative for mysql
> >(allthough when you are able to run mysql  with maxdb, then probably you
can
> >use views).
> >
> >I even recommend to develop an architecture with:
> >- front end layer
> >
> >
>
> Smarty for templating
>
> >- business rule layer
> >
> >
> System is written as classes
>
> >- database trigger layer
> >- database layer
> >
> >
> PEAR
>
> >This helps to be in control of you own code, reuse of code, increase
> >portability for you code (like porting to other databases: sql server,
> >firebird, oracle).
> >
> >
>
> EGS should work in oracle without much trouble because of PEAR:DB
>
> >An example of an architecture like this is:
> >http://sourceforge.net/projects/seagull/
> >
> >
>
> I did have a look at these, the problem is that EGS authentication is
> more complicated that this. It is written as an ASP application so that
> several companies can use the same server/DB etc.
>
> IE in egs one company can login and create there own users and groups
> and insert data etc that another company cannot see.
>
> Jake
>
> >With best regards,
> >
> >Dick Stins
> >