I've had a few people email me asking about tree2 status so I'm
bumping this message to the top of the list for people to respond to.
Please see the archives for the original part of this thread.
sean
On 7/26/05, Sean Schofield [EMAIL PROTECTED] wrote:
Some of my larger tree2 forms are
That's a possibility.
We've gotten our lazy load to work as follows (which admittedly is
sub-optimal, since it doesn't use the navigation icon features built
into the component):
x:tree2 id=serverTree value=#{treeBacker.treeData} var=node
varNodeToggler=t
clientSideToggle=false
Some of my larger tree2 forms are incredibly
slow - even slower than the JIRA. As many other users, I approached
the problem with a lazy load mechanism.
It turned out the bottleneck was bandwidth.
One page was a 1.7 MB download. I am now extending the renderer
and using CSS instead of HTML
Some of my larger tree2 forms are incredibly slow - even slower than the
JIRA. As many other users, I approached the problem with a lazy load
mechanism.
It turned out the bottleneck was bandwidth. One page was a 1.7 MB download.
I am now extending the renderer and using CSS instead
