[dev] [commits] Horde branch master updated. b2861a78cba958722b201eccbd1354548b7f625e

[Michael M Slusarz]

Quoting Jan Schneider <jan at horde.org>:

> Zitat von Gunnar Wrobel <p at rdus.de>:
>
>> Quoting Chuck Hagenbuch <chuck at horde.org>:
>>
>>> Quoting 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 agree with Jan that Horde_Element is too vague. I'm also not  
>>> sure that this should actually be a framework library, vs. an  
>>> actual app. An app called Elements (or components, or whatever)  
>>> would be less confusing imo.
>>
>> Ah, an application makes sense. Guess my tendency to place anything  
>> that is a PEAR package into framework/ is too strong.
>>
>> So in case I manage to further develop the package into something  
>> that manages/displays the "Horde elements/components" what would be  
>> your favorite name to go with? I'd prefer "Horde Elements" over  
>> "Horde Components" but I guess there might be other alternatives.
>
> I'm all for components, because this term has been well established  
> in PHP world already.

+1 for components.  Element is too generic for my tastes.

michael

-- 
___________________________________
Michael Slusarz [slusarz at horde.org]