ArnorBld
Posts: 12
|
| Posted: 12/25/2008, 7:43 PM |
|
Hi guys,
I used dtree (http://www.destroydrop.com/javascripts/tree/) on a website that I built for myself (http://www.itakefotos.com and http://www.itakefotos.com/links.php#Software bottom of the page) and it has worked very nicely for me. I have a project that I'm going to use CCS on and I need something to display data in a tree with unlimited nodes. This dTree is very simple. I build it from a recursive table in mySQL that has a SysID and ParentID that can relate a row in the table to multiple subrows (1:M) inside the same table. This gives me unlimited levels of tree nodes and works pretty well.
But, my main concern with this approach is speed - that tree has 61 nodes and 658 items (photos) in it. The code for the entire tree is loaded when the page loads so it takes a few seconds to load (the tree takes about 700 lines of code to load) The project I'm heading for could have anywhere from hundreds to several thousand nodes and performance is of concern.
My question is: Is there something comparable in CCS that I could use and would not be less intensive when loading the page?
If not: any tips on implementing something like this with CCS?
I'm new to CCS so I haven't discovered a fraction of the options that it offers and additional third party tools that may be available to accomplish something like this.
Any comments would be appreacited:)
Best regards,
_________________
Arnor Baldvinsson - Icetips Alta LLC |
 |
 |
jjrjr1
Posts: 942
|
| Posted: 12/26/2008, 9:52 AM |
|
Hi
First I would like to compliment you on your web site. Very Nice!!
On thing you could do in CCS to impleove page loading performance it to use the CCS Cache Page mode for the tree page. If the data for your trees do not change alot or rapidly over time this would greatly improve page loading.
BTW where did you get the code to read exif data from your images.
Have fun
John
_________________
John Real - More CodeCharge Studio Support at - http://CCSElite.com |
 |
 |
damian
Posts: 838
|
| Posted: 12/26/2008, 1:24 PM |
|
i would think that there isnt a significantly better approach
there is a certain amount of overhead in rules for how to display your links and then as you get more links the link code itself will continue to get bigger
opening the final image in another page or even in a div layer may appear to help as you would only load the tree once - still slow first time but then you dont reload it each time you close an image
_________________
if you found this post useful take the time to help someone else.... :)
|
 |
 |
ArnorBld
Posts: 12
|
| Posted: 12/27/2008, 8:17 PM |
|
Quote jjrjr1:
First I would like to compliment you on your web site. Very Nice!!
On thing you could do in CCS to impleove page loading performance it to use the CCS Cache Page mode for the tree page. If the data for your trees do not change alot or rapidly over time this would greatly improve page loading.
BTW where did you get the code to read exif data from your images.
Thanks for the comments:) The data in the tree in the new project will not change a lot. Could be considered quite static actually<g>
The Exif was pulled out by using FreeImage in a win32 program that I used to update the site with. However, if you look at my gallery (http://www.itakefotos.com/gallery/index.php - created with coppermine), which is php only it also extracts exif information from the jpeg that I upload. You can use the exif_read_data function to extract exif using php - see http://www.php.net/exif_read_data for more information:)
Best regards,
_________________
Arnor Baldvinsson - Icetips Alta LLC |
 |
 |
ArnorBld
Posts: 12
|
| Posted: 12/27/2008, 8:22 PM |
|
Hi,
Quote damian:
opening the final image in another page or even in a div layer may appear to help as you would only load the tree once - still slow first time but then you dont reload it each time you close an image
Thanks for the comments:) I'm not looking for a solution for _that_ particlular website, it is for a completely different project, but where I would like to present the data in a similar manner. You are correct, being able to use a layer or something so that the tree is only loaded once would help a lot. For what I'm going to use it I think it is unlikely that it will have as many nodes and items as the tree I have on that website, but you never know.
Best regards,
_________________
Arnor Baldvinsson - Icetips Alta LLC |
 |
 |
damian
Posts: 838
|
| Posted: 12/27/2008, 11:43 PM |
|
another suggestion is to try to load the dtree (or similar javascript) menu in a client side file so that it can be cached - eg not in a php file where it needs to be downloaded every time the page is called...
_________________
if you found this post useful take the time to help someone else.... :)
|
 |
 |
jjrjr1
Posts: 942
|
| Posted: 12/28/2008, 6:18 AM |
|
Hi
CCS has page cache functions built in. If your page is mostly static, set the page to cacheable. You will need to look at the CCS documentation sinceyou need to set up a table for the page to cache to. It is really simple and CCS takes care of it for you.
So your page will load very,very fast every time.
In fact this application is a perfect example when to use page cahcing in CCS.
Hope that helps
John
_________________
John Real - More CodeCharge Studio Support at - http://CCSElite.com |
 |
 |