[TYPO3-ect] Dogma

Daniel Brüßler info at -remove-patchworking.de
Fri Jan 19 20:39:04 CET 2007


Hi Elmar,

just provided that the 20-char-limit can be blown away:

How can an extension "know" that an addon is installed (like
rss-feature) and when (before viewing something, instead of viewing
something) this addon has to be called?

kind regards
Daniel Brüßler



Elmar HInz schrieb:
> Am Thu, 18 Jan 2007 11:29:33 +0100 schrieb Daniel Brüßler:
> 
>> Hello Elmar,
>>
>> I like the idea very much to add "_newstuff" or "_addon_newstuff" as
>> extension to an extension. That looks like a file-path. ;-)
>>
> 
> Absolutely right. Like PEAR classnames they define a filepath.
> 
> Example: 
> ========
> 
>    tx_efaq_addons_rss
> 
> As independend addon it would be located in:
> 
>    ext/efaq_addons_rss/class.tx_efaq_addons_rss.php
> 
> If incorporated into the efaq extension it would be located in:
> 
>    ext/efaq/addons/class.tx_efaq_addons_rss.php
> 
> This shows the central idea of the system: 
> ==========================================
> 
>  1.) The user is free to contribute addons without the need to contact the
>    extension the author.
>  2.) The extension author is free to incorporate addons he likes into his
>    extension easily.
>  3.) By using a defined pattern for the addon pathes we are able to write
>    a wizard for to incorperate addons into extensions.
> 
> Now we get more order into TER:
> ===============================
> 
> Currently we have a NO-structure like this:
> 
>   xx_news
>   xx_newsplus           (feature)
>   xx_newsplusplus       (patch for feature)
>   yy_news               (combination of all xx_news ... ) 
>   yy_newsplus           (...)
>   yy_newsplusplus       (...)
>   (...)
>   xx_calendar           (...)
>   (...)
>   xx_downloads          (...)	
>   (....)
>   (x thousand feature dublicating extensions)  
> 
> Now we gain a hierarchie. A hierarchy gives us all advantages of
> tree navigation. Instead of a large list we get a tree that is
> autorganizing.
> 
>   news 
>      addon1
>      addon2
>      addon3
>   calendar
>      addon1
>      addon2
>      addon3
>   downloads
>      addon1
>      addon2
>      addon3
> 
> Because anybody can combine features in form of extension addons we don't
> need the hundreds of extensions of the type 
> 
> "allButOnlyTheNewsFeaturesIneededCombinedAndNeverMaintained"
> 
> 
>> What about "TNT"? Maybe something with "TYPO3 Network T." (what more
>> words than Tree starts with T?)
>>
> 
> TNT soonds cool.
> 
>> Extension Collaboration System (ECS) has a great name - because this
>> talks about sharing and colaborating with others.
>>
>  
> Regards
> 
> Elmar
> 
> 
> 
> 
>  


More information about the TYPO3-team-extension-coordination mailing list