[horde] Introduction

[mdean at kcnet.com]

> Quoting mdean at kcnet.com:
> 
> > Another thought I'm having is keeping DCL the way it is, but writing abstract
> > interfaces so it could be hooked into phpGroupWare and Horde (and ???)without 
> > modification.  This means I will have to create my own API for standalone, 
> > which really won't be a big deal.
> 
> To be honest, this sounds like either a waste of time or a nightmare to me, or 
> maybe both.

It would not be a waste of time to do this.  A nightmare?  Maybe.  But not a
waste of time.  As I said, it depends on the APIs.

> Sure. I'd like to see DCL - and for the most part, as many apps as are 
> interested - use the Horde framework. This may or may not entail using our 
> resources, but it'd be interesting to have some projects outside of our cvs 
> using the API - it'd make us think more about changing things, etc. And the 
> more apps, the more general/useful the API will be.

API aside, my thoughts are with the end users.  Not everyone will run Horde. 
Nor will they run phpGW.  I don't want anyone to say "I can't use DCL because it
(a) requires Horde (b) requires phpGW (c) doesn't integrate with phpGW (d)
doesn't integrate with Horde".  I already have several users that use phpGW that
want DCL to operate within that environment.  I sure there would be some Horde
users as well, that's why I bought up the abstraction to interface with DCL.  I
had never thought about that possibility until last night, and I do not want to
DCL to become explicitly tied to any environment.

I have some ideas already on abstracting pieces of DCL to operate within phpGW.
 If Horde's API is remotely similar or is equally modular, it may not be that
difficult of a task.  But I don't have enough info to make a good call on that yet.

Mike