[dev] Using Horde components individually.

[Jon Wood]

On Mon, 2003-03-31 at 04:42, Chuck Hagenbuch wrote:
> Well, you have a couple of options.
> 
> Make sure you're using the CVS HEAD code, whatever you choose.
> 
I learnt that lesson when I tried the framework on it's own :P

> First of all, there is a CMS in Horde CVS - giapeto. It may not meet your
> needs, but if it's even close, it would be great if you wanted to work with
> it, adding features. It uses Auth/Perms/Groups pretty well already, but it
> does need a lot of work. It'd be great to get more people spending time on
> it - I mean to, one of these days.
Looking good, I'm going for a community style site, but the idea of
writing the other parts as Horde apps seems appealing having taken a
quick look around the Giapeto code - I've always been put off in the
past by things like IMP and Turba that are hard to jump into :P

I'll definately look into using it though. Expect more confused requests
from me in the future as I get used to the framework :P

> Second, you can write it as a Horde app and simply ignore the standard Horde
> UI - use the registry for any tie-ins you want, use a different login
> screen, ignore the summary, etc. Include libraries and use them like you
> would in any other Horde app, with a different face on it all.
Forgot you could do that - there's the odd thing I need to work out
(like how to get a new theme installed), but I think I can pick things
up as I go along, and it'll certainly make more sense than re-writing
the Perms system.

> Or, you can help us start packaging more and more of our libs, and then use
> them like you would any other PEAR packages.
> 
> That help at all?
Heaps, expect some Giapeto updates soon, since I've already spotted a
couple of things I'd like to change.

Jon
> 
> -chuck
> 
> --
> Charles Hagenbuch, <chuck at horde.org>
> "... It is not more light we need, but more warmth! We die of cold, not of
> darkness. It is not the night that kills, but the frost." - Miguel de
> Unamuno