[Typo3-dev] merging extensions?

[Wolfgang Klinger]

 *hiya!*
On 12:23 Fri 02 Apr     , Stig N. Jepsen wrote:
> When I install both of these extension, I will have some problems, because
> one of them replaces a function in the extension-class.

 That's a general problem, I don't address your specific problem here,
 but I would like to have some more "entry points" (don't know if that's
 the right name) in e.g. t3lib classes to extend certain functionality.

 Background:

 I wrote a "calendar_type" extension that allows for easy selection of
 dates in the backend (as a replacement for the standard date/time input
 field, a really handy little helper).

 For this to work I had to extend the following methods:
 
 t3lib_BEfunc
     getProcessedValue
     getProcessedValueExtra
 t3lib_TCEforms
    getSingleField
 t3lib_TCEmain
    checkValue

 Ok, fine, it works, but what if I want to have another such value-added
 service? They would overwrite each other and only one would work.

 Does anybody else need such mechanisms, maybe we can make a list, Kasper
 what do you think? (I think I read about this in some documentation??)
 Or is this something we should consider for 3.7 and talk about it later
 on (e.g. I would like to have this calender type, once I've made it
 publicly available, as input type in the kickstarter, I think there's
 a real demand for such enhancements in be editing, otherwise you would
 have to write a be module for every little custom feature)

 Please correct me if I've missed something 8-)
 
 bye
 Wolfgang