[dev] [commits] Horde branch master updated. b2861a78cba958722b201eccbd1354548b7f625e
Jan Schneider
jan at horde.org
Mon Aug 23 13:04:28 UTC 2010
Zitat von Gunnar Wrobel <p at rdus.de>:
> Quoting Jan Schneider <jan at horde.org>:
>
>> Zitat von Gunnar Wrobel <p at rdus.de>:
>>
>>
>>> The general idea of the Horde_Element package is to provide tools for
>>> managing Horde "Elements" which I consider to be PEAR based packages
>>> from the framework (and maybe later also the applications). While I'm
>>> currently focusing on the basics I think it would make sense to later
>>> add methods that allow publishing the elements better than via
>>> pear.horde.org.
>>
>> Why not naming it Horde_Package then? Seems more intuitive, and
>> Horde_Element is really too generic IMO. We already have
>> Horde_Xml_Element for example.
>
> Sure, Horde_Package describes what the package should do (or is
> doing). I was just searching for something that sounds better.
>
> I think that the packages in the Horde framework provide very
> valuable tools that have been underrated while being part of Horde
> 3. Of course this was in part due to the fact that the packages were
> not as independent as they can be. Something that has improved a lot
> in Horde 4.
>
> And what I'd like to see for Horde 4 is that we improve on the
> visibility of those components. I'm thinking in the direction of
> http://components.symfony-project.org/
>
> No, I'm not saying we should select weird animals for our packages
> :) I just like the general idea of featuring some of the packages as
> clear stand alone components with some documentation, examples, the
> usual PEAR stuff, maybe some API docs, definitely continuous
> integration results etc... I believe that packages like Horde_Date,
> Horde_Imap_Client, Horde_Injector, etc. all need a lot more exposure.
Yes, that's the idea behind the tons of work that has been put into
removing dependencies (especially by Michael).
Jan.
--
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/
More information about the dev
mailing list