|
From: | Alejandro Borges |
Subject: | Re: [Phpgroupware-developers] phpGW NetxtGen and further developm ent path |
Date: | Thu, 01 Apr 2004 15:39:27 -0600 |
User-agent: | Mozilla Thunderbird 0.5 (X11/20040304) |
Christian Boettger - Mailings wrote:
Well... nextgen is XML aware all over the place, and as far as i know, a standard argument set and functions at the business logic level will be enforced even for just coding an app in it. So, the IPC should be in there BY DESIGN! (which is the right way to do it anyhow).Hi, <snip>Would be even easier if the IPC stuff (ipc manager + the (in this case simple) IPC interface classes for each app) goes into nextgen as well.
All 16 apps that want to migrate to head should have IPC, and really, head should implement IPC as a core feature of every app. Here is the thing. The greatest value of the IPC is that its a standard api for add/edit/delete for generic data. We need that in head, in 16 and in nextgen as a concept (if not the exact same code), because its what allows for really extensible and reusable api and applications.but first, we must have the apps in bextgen to migrate to; and those are missing apart from the core apps... and not many head/.16 apps do currentlyhave IPC interface classes.
CB
[Prev in Thread] | Current Thread | [Next in Thread] |