Spark Tree – faster, with icons and text colors

12 responses to “Spark Tree – faster, with icons and text colors”

1. JabbyPanda August 27, 2010 at 20:06 | PermalinkReply

   On the first glance, your implementation looks very good.

   Relying on mx.controls.treeClasses.DefaultDataDescriptor, that was cool.

   If your project is currently under development, I suggest to move your code to GitHub, may be you will gain some contributions… someday )

   1. Maxim August 28, 2010 at 16:42 | PermalinkReply

      Thanks ;)

2. Julien November 9, 2011 at 16:29 | PermalinkReply

   Hi,

   Your component seem very interresting. Unfortunatly, it doesn’t seem implement the “openitems” property as the mx tree do.

   Is there a way to do it easily ?

   Thanks

   1. Maxim November 10, 2011 at 21:48 | PermalinkReply

      Dear Julien,

      Thank you. The best way to get open nodes is:

      1. Get Spark Tree source code
      2. Open file TreeDataProvider.as
      3. Make openedBranchesVector or parentObjectsToOpenedBranches publicly accessible by changing their scope or adding a getter.
      4. Get them via TreeDataProvider(tree.dataProvider).openedBranchesVector

3. Stefan January 31, 2012 at 01:33 | PermalinkReply

   Hi,

   I’m trying to get the SparkTree working with Flex 4.6?
   Could you give me an advice how to do that?

   Many Thanks,
   Stefan

   1. Maxim January 31, 2012 at 20:20 | PermalinkReply

      Hi Stefan!

      Thank you for using Spark Tree. Try downloading https://github.com/downloads/kachurovskiy/Spark-Tree/SparkTree4.5.swc . I haven’t tested it with 4.6 yet, need to download new Builder and SDK and it takes a while.

4. Kim February 6, 2012 at 16:49 | PermalinkReply

   Hey there – at the moment, the tree automatically closes all child branches when closing a branch. Is it possible to prevent this?

   Many thanks – Kim

   1. Maxim February 8, 2012 at 22:19 | PermalinkReply

      Hi Kim! The only way you can do this is get the library source and modify it.

      P.S: You may have problems with memory leaks in this case if you will store links to open branches. You will need some hash-function or node ID.

      1. Kim February 10, 2012 at 18:27 | PermalinkReply

         Ha – There goes my hope for an easy fix!
         Will let you know how I get on :)

5. Kim February 10, 2012 at 19:28 | PermalinkReply

   Btw – have noticed an issue with using virtualLayout and itemRenderer recycling.
   If a selected item is scrolled out of view, when it is scrolled back into view it re-dispatches the ITEM_SELECTED event.

   I’ve fixed this by using useVirtualLayout=false when adding the component to my project, but maybe there’s a better way.

   Cheers – Kim

   1. Maxim February 11, 2012 at 09:11 | PermalinkReply

      Spark List does not have ITEM_SELECTED event. The closes event I can imagine is CHANGE, but it does not arrive twice if you scroll selected item out and in.

      I strongly discourage the use of useVirtualLayout=false because it will cause performance problems when list data size increase.

      If you can reproduce this bug on an empty project I will be glad to help you. Cheers!

6. Kim February 11, 2012 at 12:09 | PermalinkReply

   That explains a lot.. I’m working with an existing code base, so I assumed all the classes I had were part of the original SparkTree code.
   Apologies for the confusion. My tree implementation will probably max out at around 30 items, so it’s not a big issue for now.

   Thanks for taking the time to answer all my queries though :)

   Kim