One possible option is only loading the top end nodes with initial load and
then AJAXing the rest of the tree, which will allow painting without getting
rid of the page content the person is viewing (still slow, but misdirected
like any good magician ;->). I would also consider looking at sites that do
this (try the free trials) like Books 24x7 and Safari. View source may give
you some clues.
--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA
Subscribe to my blog
http://feeds.feedburner.com/GregoryBeamer#
or just read it:
http://feeds.feedburner.com/GregoryBeamer
********************************************
| Think outside the box! |
********************************************
"Chris" <co*****@gmail.comwrote in message
news:ca**********************************@73g2000h sx.googlegroups.com...
Hi Folks-
I'm using a treeview to display a table of contents for a book. There
are chapters, subchapters, sub-sub chapters, etc. Since there are a
few levels, I've set up threads to handle chunks of the list, and this
works well to get around the whole nested loop (foreach) problem when
building a treeview. My problem is, for books with large amounts of
chapters (one book has 71, for example), the page load time is
horrendous. I've disabled as much viewstate stuff as I can, and
that's helped, but it's still slow. Does anyone have any suggestions
on how I can trim down the amount of junk in the html source?
