With "optimized enough" I meant applying tricks like lazy-loading and
event delegation to the current treeview plugin. It doesn't do that
much anyway, so there is no point in writing a seperate plugin.
Event delegation would be rather straight forward, but the actual
issue is the DOM manipulation:
Unfortunately my JavaScript knowledge is not up to par to understand
exactly what's going on when the cookie persistence is processed, so I
fail to grasp what's going on exactly. But doesn't it make sense to
have treeview itself set the expanded nodes to 'collapsible' once they
have been expanded?
Not really. "prerendered" is a performance optimization, and as such a
trade-off. The best solution would be a treeview that is optimized
enough itself to not needing the prerendered option. But that isn't a
workaround and involves much more work.
Jörn
On Tue, Oct 7, 2008 at 9:59 AM, pjdevries <[
Thanks Jörn.
I was afraid you might say something like that :( Apart from not
knowing how to do that, it will also make my servers side code more
complex. Can you think of any other nifty work around?
On Oct 6, 7:01 pm, "Jörn Zaefferer" <[EMAIL PROTECTED]>
wrote:
> If you use prerendered, you ha
If you use prerendered, you have to read the cookie on the serverside
and render the tree accordingly. Otherwise you have to disable
prerendered to be able to use cookie persistence.
Jörn
On Mon, Oct 6, 2008 at 6:08 PM, pjdevries <[EMAIL PROTECTED]> wrote:
>
> I'm using treeview (version 1.4.1) w
5 matches
Mail list logo
