Events & Blog Engine: new pager

[rickybanister]

Instead of pagination, we are going to do a 'previous' 'today' and 'next' navigation.

When a user comes to the events page they will see events starting with Today. It should display 20 or so events. The next button above and below the events list will show them numbers 20-40 and so on. The previous button will show the 20 events before today, and so on.

The today button will always bring them back to the default view starting with today's events, display the upcoming 20.

[anonymous]

events pager

[geoffd]

Dan, sit down with Rick some time this week and see if you can close this ticket.

[geoffd]

After reworking the paging in the Media section, we want to bring that over to the events and blog. (Also, the new calendar navigation and pager makes some of this previous strategy unnecessary.)

Going forward:
We want to allow people to switch between showing 20,50 and 100 posts.
We also want them to see the total number of posts in context the filter view they are in .
See screenshot.

Dan, please make that possible and reassign to John for styling.

Error: Macro Image(Screen shot 2010-10-22 at 11.04.00 AM) failed

Attachment 'ticket:363: Screen shot 2010-10-22 at 11.04.00 AM' does not exist.

[tboutell]

Progress in [2545]: we have a decent testbed now thanks to apostrophe-blog:generate-test-posts

Also [2546] moves page fixtures to the project level and adds blog and events engines pages so you can reload fixtures, generate test posts and get straight to work

[tboutell]

Implemented in [2547]. Reassigning to John for styling.

The 50 and 100 blog post per page views are very memory intensive and take a noticeable while even on my machine. Are we sure this is a useful feature? I can't picture wanting to look at 100 posts at a time. They are not pictures, so I'm not leveraging my visual cortex or anything. Please opine.

[geoffd]

We were looking to be consistent across media, blog and events. Your point on the demand on memory is worth considering, though.

What if we focus on always showing an excerpt when viewing 50 or 100 per page. Will that help?

[tboutell]

I just don't see this as mission critical 1.5rc driven by anticipated needs etc. It's a consistency thing, but it's consistency between two very different animals. When you look at 100 photos this makes sense because you are applying the power of your visual cortex to almost instantly spot one of those many images. When you look at 100 blog posts you fall asleep

Excerpts might help the memory/time situation somewhat, but would require more new code to be written to deal with rendering with a different set of templates for each setting (20 vs 50 vs 100). Which makes the branch even later. And if we need this on a client project it's fairly straightforward to do it there. So I just don't see it. I humbly submit that this is a "think it over and maybe do it for 1.6" ticket and I should back out the changes already made.

[tboutell]

Consistency is important -- the goal of this ticket
Not crushing the server is important -- means we shouldn't do a straight 100-posts view
Cutting the branch is important -- time to stop implementing brand new features like a title-only or excerpt view (also we wanted to simplify the blog plugin templating)

We are not going to get there if we don't start saying "no" to some stuff.

So this is our qualified "no" after talking to Rick John and Jake:

The pager *will* be visually consistent with the media pager, including showing the total # of posts and the # of posts that you can see. The # of posts you can see just won't be part of a set of options. It'll be informational only ("page 4 of 20 pages of 20 posts each, okay, now I really know where I am").

That gives us a logical place to start enhancing in 1.6.

I'm accepting this ticket, I'll hit it by borrowing from the media repo's markup and CSS and put this to bed. The goal is to cut the branch today.

[tboutell]

Styled blog post pager to be visually consistent with media pager (#363) although not quite as featureful as originally hoped for 1.5, we'll do more in 1.6. I am opening a 1.6 ticket to do more thinking and testing-out in that area.

[2557]

[geoffd]

I think you meant the pager from ticket #226

Good solution for 1.5

[tboutell]

Some of this was not committed until [2559]