Can't believe it, I actually fixed my test page with broken embeds and all that crap...!!
I started going into complicated stuff, for several DAYS of course, and then I fixed it all by reverting all of my changes, and doing a simple test.
I'd completely forgotten that swfobjects was hard to load from an Ajax page -- and ultimately, this is what an infinite scroller is; but internally, Wedge considers infinite scroll pages as 'normal' pages, so that it gets the proper rendering. That's a bit of a wrong thing to do, especially because in some places, infscroll needs the Ajax code path (e.g. embeds), and in others, it needs the non-Ajax code path. Very funny, really...
So, I just double-checked, and now all Flash embeds should properly work in infinite scroll pages, and thus NOT stop the new page from loading, and my friends, that is a frigging victory!
I also rewrote many things in the infscroll process, so that it sends MUCH less data per request; you can save up to 80% of the page data, if there's not much content in the next page. Otherwise, it's between 20% to 50%. Also executes a bit faster.
Tomorrow, I'm gonna give a try at pre-fetching the next page while marking the previous page (not the current page) as read, to ensure that one can safely stop reading through an infinitely scrolling page, and later come back through an Unread link, and find themselves on the page they were currently viewing at that point (i.e. last 15 posts in the infinite scroll page), which is cool. Well, I'm not very familiar with the markread code, so every little victory like this is good to me.
Phew... Then, it means I can keep the current implementation. And that it's going to become much more useful. :)
I started going into complicated stuff, for several DAYS of course, and then I fixed it all by reverting all of my changes, and doing a simple test.
I'd completely forgotten that swfobjects was hard to load from an Ajax page -- and ultimately, this is what an infinite scroller is; but internally, Wedge considers infinite scroll pages as 'normal' pages, so that it gets the proper rendering. That's a bit of a wrong thing to do, especially because in some places, infscroll needs the Ajax code path (e.g. embeds), and in others, it needs the non-Ajax code path. Very funny, really...
So, I just double-checked, and now all Flash embeds should properly work in infinite scroll pages, and thus NOT stop the new page from loading, and my friends, that is a frigging victory!
I also rewrote many things in the infscroll process, so that it sends MUCH less data per request; you can save up to 80% of the page data, if there's not much content in the next page. Otherwise, it's between 20% to 50%. Also executes a bit faster.
Tomorrow, I'm gonna give a try at pre-fetching the next page while marking the previous page (not the current page) as read, to ensure that one can safely stop reading through an infinitely scrolling page, and later come back through an Unread link, and find themselves on the page they were currently viewing at that point (i.e. last 15 posts in the infinite scroll page), which is cool. Well, I'm not very familiar with the markread code, so every little victory like this is good to me.
Phew... Then, it means I can keep the current implementation. And that it's going to become much more useful. :)
