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. Need a VERY fast tree

Need a VERY fast tree

Scheduled Pinned Locked Moved ASP.NET
csharpasp-netdata-structuressalesperformance
3 Posts 3 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.
  • D Offline
    D Offline
    DarrollWalsh
    wrote on last edited by
    #1

    Hey guys, I'm writing an ASP.NET C# web application that needs to quickly (as possible) display trees that are on the order of thousands of nodes. I know there are commercial solutions out there but have been directed that they are off limits. I have also been told that freeware versions are also a no go. This is partly due to the legalities of using them as well as customer direction. I've tried building the nodes on the fly but my implementation didn't seem to speed up the rendering of the tree. It just seems like the tree control that is included is very bloated and was not built for VERY large trees. If you can point me into the right direction I would appreciate it. Thanks to everyone! This site rocks!

    - Darroll

    C P 2 Replies Last reply
    0
    • D DarrollWalsh

      Hey guys, I'm writing an ASP.NET C# web application that needs to quickly (as possible) display trees that are on the order of thousands of nodes. I know there are commercial solutions out there but have been directed that they are off limits. I have also been told that freeware versions are also a no go. This is partly due to the legalities of using them as well as customer direction. I've tried building the nodes on the fly but my implementation didn't seem to speed up the rendering of the tree. It just seems like the tree control that is included is very bloated and was not built for VERY large trees. If you can point me into the right direction I would appreciate it. Thanks to everyone! This site rocks!

      - Darroll

      C Offline
      C Offline
      Christian Graus
      wrote on last edited by
      #2

      http://www.obout.com/t2/eServerSideEvents.aspx[^] I've used it, and it works well. They say it's the fastest on the market, but then, they would :-)

      Christian Graus - Microsoft MVP - C++ "I am working on a project that will convert a FORTRAN code to corresponding C++ code.I am not aware of FORTRAN syntax" ( spotted in the C++/CLI forum )

      1 Reply Last reply
      0
      • D DarrollWalsh

        Hey guys, I'm writing an ASP.NET C# web application that needs to quickly (as possible) display trees that are on the order of thousands of nodes. I know there are commercial solutions out there but have been directed that they are off limits. I have also been told that freeware versions are also a no go. This is partly due to the legalities of using them as well as customer direction. I've tried building the nodes on the fly but my implementation didn't seem to speed up the rendering of the tree. It just seems like the tree control that is included is very bloated and was not built for VERY large trees. If you can point me into the right direction I would appreciate it. Thanks to everyone! This site rocks!

        - Darroll

        P Offline
        P Offline
        Pete OHanlon
        wrote on last edited by
        #3

        How deep are you going with your nodes? It's common to just retrieve nodes down to the next depth and then when expanding a node, get the nodes two layers down from that. This means that the user sees the nodes that can be expanded. Here's a quick example:

        RootNode
        |-Level 1
        |-Level 2
        |-Level 2
        |-Level 2
        |-Level 1
        |-Level 2

        Now, imagine that you are expanding the first Level 1 node, you retrieve the nodes below Level 2 so that the user sees the appropriate visual cues:

        RootNode
        |-Level 1
        |-Level 2
        |-Level 3
        |-Level 3
        |-Level 2
        |-Level 2
        |-Level 3
        |-Level 3
        |-Level 3
        |-Level 1
        |-Level 2

        As you can see, you only get the information that you need so that you can keep the user happy. I hope that helps.

        Please visit http://www.readytogiveup.com/ and do something special today. Deja View - the feeling that you've seen this post before.

        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