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

[Martin Kutschker]

Elmar Hinz schrieb:
> Hello,
> 
> what do you think about this draft:
> 
> Introduction
> ============
> 
> this is a proposal of a resultbrowser system, to make it easy to plugin
> and exchange resultbrowsers of different types. The basic idea is, that
> resultbrowsers are not build into the extensions any more. Instead they
> come as independent plugins that the adminitrotor can plugin directly
> below the listing plugin.

I like your second idea better.

> 
> So the resulting class looks like this:
> 
> class tx_resultbrowser_pipe{
> 	function pipeControllerKey($string = ''){...}
> 	function pipeTotalResults($integer = ''){...}
> 	function pipeResultsPerView($integer = ''){...}
> 	function pipeResultsCount($integer = ''){...}
> }
> 
> It is called in the static way.

Arg! I don't think that static methods are a good idea.

> 
> Motivation
> ==========
> 
> a) The resultbrowser within pi_base doesn't work for the page visitor in
>    a way he used it from typical internet pages.

Well, it sucks ;-)

> d) The extension coordination team want's to make pi_base obsolete.

Yes please :-)

> 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.

Masi