It would be great to implement a pagebrowser in the pi3 result list.
#2 Updated by Jo Hasenau over 8 years ago
- Status changed from New to Accepted
I guess you mean ext:pagebrowse by Dmitry, which is not the kind of page browser I had in mind while discussing this with Rik.
I don't like the way of templating and the browser concept of this extension too much, which is why we will do something else from scratch most likely.
#3 Updated by Fedir RYKHTIK over 8 years ago
Exactly, thought about "pagebrowse". I'm agree with You, it's possible to make better. But the positive side : in my custom extension I used this extension, and it works well, as it should.
So You have always the choice : to develop something better and to spend time for it, or to use existing solution.
#4 Updated by Rik Willems over 8 years ago
Thanks for accepting this feature.
I had the same argument for using ext:pagebrowse. It works fine and quite easy. Jo has some specific features in mind that are not supported in ext:pagebrowse, as well as some technical remarks (as he mentions).
Looking at the hooks in ext:pagebrowse it should be possible to create the features Jo has in mind. It will save us work.
Another question is how it should exactly work. Currently the pi3 result list shows all configured tables separately with a max. Should all tables have their own pagebrowser or one for all?