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

[Christian Welzel]

Martin Kutschker wrote:

> Nice, but the browserService should not restrict itself to SQL queries.
> IMHO it's the job of the calling code to provide the data, and not the job
> of the browser.

Of cause. This was only an example :)
It would definitely be better to feed an array of result-rows
or result-objects into the pagebrowser.

What i forgot to mention: the actual output of the browser
could get configured by TS (COA) or a callback-function
into the calling object.

function main() {
  data = db->getSelect('*', 'foo', where);
  b = getInstanceofService("resultbrowser");
  b->setData(data);
  b->setRenderObj(TS[foo][renderObj.];
  // or b->setRenderFunc(this->renderfunc);
  if(!b->showResults()) {
    // no page browsing mode
    // perhaps single view or armageddon.
  }
}

Another cool thingy would be a new TS-object RESULTBROWSER which acts 
like CONTENT but also does the resultbrowser rendering.

-- 
 MfG, Christian Welzel

  GPG-Key:     http://www.camlann.de/key.asc
  Fingerprint: 4F50 19BF 3346 36A6 CFA9 DBDC C268 6D24 70A1 AD15