Expandable Trees [for Anime Views]
Posted: Tue Apr 03, 2007 9:37 pm
First off, my thanks for the continued reliability and funtionality of this great service!
I browse lots of sites, some like Microsoft's Technet, which have these excellent expandable trees implemented in various ways. The idea would be to use them on anime main pages and all other pages that use expandable items. [EditRar: this bit was added, right?]
Here is one good example:
http://www.mattkruse.com/javascript/mktree/
This Google search finds lots of code samples:
http://www.google.com/search?q=html+cod ... le+tree%22
The great thing about the expandable trees, is that when a user clicks the + sign next to an item, it pops out instantly rather than requesting data from the server. This means instant browsing, and also has the advantage that the entire page loads rather than just parts.
Since HTML is compressed in transmission, the additional overhead of sending the entire tree rather than parts, is largely offset by the better compression that is achieved by a larger textsize.
Also, a server sending many small pages is more latency-constrained than raw datarate constrained, so this prevents lots of small requests by coalescing them into a single send.
Plus, users get significantly improved response times, especially through slower or busy connections.
[EditRar: Putting this random rant back to how it was]
I browse lots of sites, some like Microsoft's Technet, which have these excellent expandable trees implemented in various ways. The idea would be to use them on anime main pages and all other pages that use expandable items. [EditRar: this bit was added, right?]
Here is one good example:
http://www.mattkruse.com/javascript/mktree/
This Google search finds lots of code samples:
http://www.google.com/search?q=html+cod ... le+tree%22
The great thing about the expandable trees, is that when a user clicks the + sign next to an item, it pops out instantly rather than requesting data from the server. This means instant browsing, and also has the advantage that the entire page loads rather than just parts.
Since HTML is compressed in transmission, the additional overhead of sending the entire tree rather than parts, is largely offset by the better compression that is achieved by a larger textsize.
Also, a server sending many small pages is more latency-constrained than raw datarate constrained, so this prevents lots of small requests by coalescing them into a single send.
Plus, users get significantly improved response times, especially through slower or busy connections.
[EditRar: Putting this random rant back to how it was]