Re: Invoices & Clients

Quoting Jeremy Oddo <[email protected]>:

> I know I'm a bit daft, but it seems like there's a design flaw to have
> add-on modules that REQUIRE other add-on modules.  It's my feeling that
> modules SHOULD be able to work by themselves under the horde framework.

Sure, but to do certain things, they require other modules.

> Seems that juno, turba, whups should NOT require one another BUT use a
> central database to pass info back and forth.

Ugh. The point of the architecture we have is that any application can use
Turba's api, and ALSO that any application could implement the same API as
turba (the registry methods), and then be dropped in and used instead of
Turba automatically.

> Furthermore, it seems like turba (and maybe even whups) is now becoming a
> conduit of sorts between several modules.  Perhaps it would be better to
> bring that UNDER the horde-hood, so to speak.

If we moved every piece of functionality that other apps use into Horde,
we'd just have Horde, and it would be a completely unmanageable *beast*.

-chuck

--
Charles Hagenbuch, <[email protected]>
The alligators were there, too, in a bathtub inside the house.


-- 
hermes mailing list
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: [email protected]