tobyroworth / wbhb-blog Goto Github PK

The posts that are loaded at startup didn't appear at the first load until the 
page was scrolled.

It's likely that they weren't available until after positionChildren was fired

Ref: issue 1

The a6 class needs to clip its content, preferably in such a way that content 
can't be lost

The stories are added to the page in the order the AJAX requests return, rather 
than the order they were asked for.

This causes a problem when some stories are cached and others aren't.

To reproduce:

If first three articles in storylist are
*story1
*story2
*story1
Then they render as
*story1
*story1
*story2

However, if they are
*story1
*story2
*story2
They display as expected

A grid-type overview of all blog posts would save the user having to scroll 
through 100 items to reach older posts.

The current stories should appears to move into the grid as it is formed

The current AJAX code only loads placeholder data for pages.

The pages themselves will be HTML data

A new story is loaded every time the ">" button is pressed. However, if the "<" 
button is pressed, the counter/array handling the loading isn't adjusted 
accordingly, so stories start to stack up on the right (offscreen).

Javascript all needs comments, especially in the many cases where it's cryptic

Since wbhb-carosel was upgraded to use transforms, instead of position, the new 
items no longer come in gracefully, they just appear.

Some client functionality requires a servlet to take IDs as requests and return 
JSON story objects

I occasionally write several posts that for a series. There should be UI 
elements to assist viewing the series as a whole

The AJAX to load pages needs to be implmented in a such a way that each page of 
each story doesn't require a separate HTTP request, or can at least have an 
option to batch them.

On the server side this requires something to detect if all pages will be 
loaded, and something to batch them.

On the client side there may need to be a switch for batching, (acceptsBatching 
could be sent in the request, and there will need to be code to un-batch the 
pages

When the carosel tries to go past its last (or first) story it should bounce 
slightly, and possibly display a subtle message.

This could also be implemented for stories that haven't yet loaded, though the 
user should be given an indication that the story is trying to load, such a 
placeholder story with spinner.

When stories open up the scrollbar appears, and disappears when the story 
closes again.

This looks rubbish, and probably has implications for performance due to 
repaints etc

Dynamic loading of stories would be a lot cooler if it worked like magic - it 
should never load stories unnecessarily, but the story you need should always 
seem to be there when you want it

This issue was created by revision 9a13867682cf.

Implement a more intelligent cache of blog posts, instead of just keeping them 
in memory forever, to keep down memory usage.

More implementation detail in design doc

When new elements are added that get popped out of the shadow DOM they get 
rendered several times.

This is partly because of the way their style scoping works

The current workaround uses asyncMethod very badly - in theory an event could 
be latched onto, or a checkpoint waited for (needs research).

Elements could also be hidden until safe, then fade in

The posts should be able to be filtered based on their tags