[TYPO3-ect] RFC: Result Browser Service for lib/div - part 1 + 2

[Franz Koch]

Hi,

>> 4. Resultbrowser types: dropdown and link list
>>
>> Example of dropdown:
>>
>> ------------
>> Hits 1  - 10
>> Hits 11 - 20
>> Hits 21 - 28
>> ------------
>>
>> Example of link list:
>>
>> << <  5  6  7  8  9  > >>
>> ...

I think the possible types should not be limited. I'd suggest a view service or something like that which can be easily extended with new view-types. If the views are limited there will soon be the same problem with pagebrowsers in TER than with gallerys, calendars etc.

I could also think of such a view:

< next        pages 1 ... 5 6 7 8 ... 43        previous >


or any other variation maybe with ajax, XML (for flash?) or whatever.



In addition a guideline/rule should be set, that in extensions the view-type is NEVER hardcoded and must be configurable with TS or be overriden by a global preset for view-types in the service itself (or whatever). It'll also be nice if the configuration of the pagebrowser could be the same in every extensions flexform - but TYPO3 lacks for such intelligent features (hope that's better in v5). 

Even better would be that no extension would have to be aware of the existence of the pagebrowser as long as it uses special coding guidelines (or maybe lib/div queries) for the result-handling. Wouldn't it be nice if extensions of general interest (pagebrowser, rating, commenting) could be attached to any other extension just by activating a checkbox that is instantly provided everywhere as soon as the extension (e.g. pagebrowser-MVC) is installed? Sorry - I'm dreaming.

-- 
Kind regards,
Franz Koch