[TYPO3-ect] Draft: Proposal of a resultbrowser pipe

[Elmar Hinz]

Martin Kutschker wrote:
>> Discussion
>> ==========
>>
>> This draft specifies a way, to place resultbrowsers as plugins below
>> listing plugins. I propose to define a second interface of the service
>> type, that makes it possible to access resultbrowsers as objects and to
>> bind them into the listing extension directly. Any resultbrowser can
>> implement both interfaces, but it must not.
> 
> This is the idea I like. But if pipes and services can live in parallel
> then the better.

Hello Martin,

yes pipes and services can live side by side. I think they should.
Kasper  would call the service way a "nobrainer", because it's so clear
to everybody.

The pipe is rather an "addon". The reason why I like to have the
possibiltiy of an independent plugin is, that people without TS knowlage
can configure it by flexform.

I could build this flexform also into the listing extension, but than I
need to do that for every listing extension I build and would be
dependent on a single resultbroswer again.

The best solution would be, if the pagebrowser could deliver a flexform
through the service, so that is displayed as an own sheet within the
listing plugin. That would really be an interesting task for dynamic
flexforms. Maybe Thomas Hempel is reading this lines and likes to come
up with a proposal for this kind of service.

Regards

Elmar