rework the table view

[splitbrain]

We currently display all plugins in the table, when no filter was set. This results in a huge table and lots of data to transfer and process. And this problem is getting worse every day.

I think we should display a limited choice of plugins by default. I think the best choice here would be the most recently updated ones. Maybe with a way to switch to the most popular ones instead.

And most important: adding pagination would be a good idea. Only showing maybe 25 results per page or so.

Here are some crude mockups on how that might look like.

[AntoineTurmel]

+1 for this, any idea on how to handle tabs ? Visible/Hidden

should do the trick ?

[selfthinker]

Re: tabs, as one big point of this is to reduce loading time, I would not load everything and then just hide other than the active tab. I would prefer new requests. Later on those can additionally be AJAX requests.

@splitbrain, I haven't properly looked at this task yet, but will do later this week and give proper feedback.

[mprins]

@GeekShadow there's a tab plugin that uses jQuery ajax requests to load separate pages in tabs, it may be useful for an idea, if

a tab = a page and a page would have pagination this could just work

https://www.dokuwiki.org/plugin:tabinclude

[HakanS]

Some thoughts

1. How much AJAX could we use without leaving some users behind?
2. Shouldn't there be at least a search box on the first tab? Almost everyone otherwise needs one click more
3. I really don't like tabs (they always have too few items/page and I don't care to flip until page 3)
4. I really like the LinkedIn "people you may know" list, populated by AJAX calls as you scroll down
5. We should always allow an image, defaulting to some nice pic
6. KISS -> no need for author mail link in table.
7. (if not KISS) Use name as a link it should search for other ext. by same author
8. Probably no-one will notice the removal of links for search by type (admin, syntax etc)

[splitbrain]

1. AJAX should be used on top of the traditional page reload method just as we do in all our other plugins (unobstrusive JavaScript)
2. probably yes
3. You're talking about pagination there, not tabs. pagination is the only useful way to limit page loads when a lot of results are to be displayed
4. Infitite scroll is a nice gimmik, that could be added on top of the traditional pagination
5. that's what my mockup suggests
6. agreed
7. yes, that might actually be more useful than the email link
8. the links might not be important, to see which type of plugin something is is

[Chris--S]

+1 for 4 infinite scroll. I don't think its a gimmick, but a simpler interface than more traditional pagination. However, it does require a "back to top" link.

[selfthinker]

I'm quite disturbed that everyone likes infinite scroll here. :( As a user I absolutely hate it! It's very unusable and annoying and there is no way you can link to something with that on. For me it's a reason to stop using certain websites or services. In cases when I don't have a choice, I use a workaround (e.g. using m.twitter.com instead of twitter.com). I much prefer classic pagination (with results reloaded via AJAX to make it smoother).

[Chris--S]

As a user I like it. Its very usable. Why is a link a problem? Linking to a whole result page rather than page 5 makes sense to me. Links to individual items aren't changed.

[Klap-in]

This issue was in the old bug tracker as well:
https://bugs.dokuwiki.org/index.php?do=details&task_id=2641