Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Web Development
  3. ASP.NET
  4. Help Handling Treeview

Help Handling Treeview

Scheduled Pinned Locked Moved ASP.NET
helpquestion
3 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • O Offline
    O Offline
    obymathew
    wrote on last edited by
    #1

    :confused:I have this case: My page has a treeview control which can go on upto 1000(or more but not practically needed) level of nodes. On clicking a node i have to show an entry form in a panel next to treeview(this page not use frame)which itself has multiple web dropdowns and list boxes. Its very slow to populate(uses the viewstate) Can anyone suggest a better way to maintain its state? will fragment caching help? >>>>

    P 1 Reply Last reply
    0
    • O obymathew

      :confused:I have this case: My page has a treeview control which can go on upto 1000(or more but not practically needed) level of nodes. On clicking a node i have to show an entry form in a panel next to treeview(this page not use frame)which itself has multiple web dropdowns and list boxes. Its very slow to populate(uses the viewstate) Can anyone suggest a better way to maintain its state? will fragment caching help? >>>>

      P Offline
      P Offline
      Paul Watson
      wrote on last edited by
      #2

      >will fragment caching help? Definitely. Only hit the database to regenerate the HTML of the tree when it changes or the cache expires. Do things like "current page", expanding, collapsing etc. using JavaScript. If however you find the HTML for your tree is getting too big then write it out to a JS file and include that client side. It is not as pretty and it won't be in the view-source but it will then cache and the user won't have to download it each time. regards, Paul Watson South Africa Michael Dunn wrote: "except the sod who voted this a 1, NO SOUP FOR YOU" Crikey! ain't life grand?

      O 1 Reply Last reply
      0
      • P Paul Watson

        >will fragment caching help? Definitely. Only hit the database to regenerate the HTML of the tree when it changes or the cache expires. Do things like "current page", expanding, collapsing etc. using JavaScript. If however you find the HTML for your tree is getting too big then write it out to a JS file and include that client side. It is not as pretty and it won't be in the view-source but it will then cache and the user won't have to download it each time. regards, Paul Watson South Africa Michael Dunn wrote: "except the sod who voted this a 1, NO SOUP FOR YOU" Crikey! ain't life grand?

        O Offline
        O Offline
        obymathew
        wrote on last edited by
        #3

        hi thanx watson. i will try that:-D

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups