[TYPO3-v4] TCA Valueslider Wizard

[Ernesto Baschny [cron IT]]

Tolleiv.Nietsch schrieb am 13.03.2011 18:21:
> Am 13.03.2011 17:58, schrieb Steffen Kamper:
>>
>> don't you think this depends on easy-to-use? I'd use that always eg with
>> time entry.
>>
> 
> As I said - nice to have nothing else. I never felt that I need a slider
> for anything in the backend yet. Having it in an extension would imho
> not reduce the ease of use too much (once the extension is installed).
> If that's the case we should maybe think about better APIs for
> extensions to provide good wizards instead of adding all kinds of
> wizards to the Core.
> 
> Of course I would not block the RFC for that, just wanted to raise my
> concerns.

It's the same situation we had before e.g. with the "datepicker" or the
"tcatree": There used to be "custom solutions" in external extensions
providing such a functionality, but who wants to depend on a third party
extension for their core task?

Being in core means that it's maintained by the "core team", and as such
will always work after a upgrade, will always be available and will get
attention in case of security concerns, or when new APIs are introduced
in the core.

The tcatree is a classic example here: Everybody was constructing their
own "tree" element (tt_news had it, and most copied the code from it). I
can imagine that there were are extensions providing this functionality
as a "library". But I wouldn't feel comfortable using it because who
knows if it would still work on the next release? Or if the maintainer
is even still interested in working on it.

Now that's in the core, this is *the API* and noone needs to feel the
need to risk their stable extensions by depending on some third party
extension which has an unclear future.

So I am +1 in adding this kind of technology in our main API: Of course
not everybody needs it, but a rich core API helps developers provide
stable third party extensions.

This said, as soon as we have a clear concept of "A-class extensions"
(endorsed and maintained *like the core*, but shipped through the TER),
we can think about outsourcing rarely used core components.

Cheers,
Ernesto