|
Wednesday 02 November 2005 2:43:51 am
Bo Henriksen just discovered the first issue with this extension here is is original posting:
Nice but with some problems.
by Bo Henriksen on 02/11/2005 at 10:03:13 am
Rating: Good
On my smaller site, i really can't decide if I like this extension or Kristian Hole's dynamic menu better. But on my extremely large site they both have some problems, but Christians is faster, and is showing all the items.
I have around 4200 images in my media folders, and some of the subfolders contains up to 700 images, this makes the standard eZ menu impossible to use. This extension can't open the three for the large folders, and is very slow on the medium sized folders (around 200 items).
He has the problem of having lots of object assigned to single nodes, meaning some nodes in is content tree has 200+ children (eg. the image folder in the media library).
This is something that can't be handled well - even with ajax, as we still have to fetch many object at the same time. Now the extension gives one possible solution to this issue. You can simply hide every single image via the "HideClasses[]=image" option the extension provides. But this maybe isn't what you want, because it won't show any image in the tree anymore (anywhere in the admin siteaccess).
What could be done:
1. Adding an option to hide children of specific nodes (additionally only if they are from a specific class) 2. Adding an option allowing you to show only nodes in the tree that have children 3. Adding an logic that can be configured to hide nodes in the tree on specific criteria
It hink the third might be our solution. This is how I think the logic could be:
Check how many nodes are in the tree, if there are more than X (set X in config) but them by their class names in different virtual folders, showing up in the menu by opening the node with the many objects.
So opening that node by clicking the + won't show all X+ objects the folder has, but all different types of classes the objects in the folder has. Could look like this:
|-Media
|+ Files [normal folder]
|+ Streams [normal folder]
|- Images [normal folder]
|+ 278 Images ["virtual folder"]
|- Galleries [normal folder]
|+ 1412 Images ["virtual folder"]
Now when you open the "1412 Images" virtual folder we shouldn't show the 1412 Images instantly, as we wouldn't get around the original problem. So we need to put them in other virtual folders, like this:
|-Media
|+ Files [normal folder]
|+ Streams [normal folder]
|- Images [normal folder]
|- 278 Images ["class V-folder"]
|+ Alphabetical ["sorting V-folder"]
|+ Time published ["sorting V-folder"]
|+ Published by ["sorting V-folder"]
|+ Time modified ["sorting V-folder"]
|+ Modified by ["sorting V-folder"]
|- Galleries [normal folder]
|+ 1412 Images ["virtual folder"]
Wehre the single sorting virtual folders could look like this:
|- 278 Images
|- Alphabetical
|+ a-g
|+ g-hung
|+ hunk-z
|- Time published
|+ May 2003
|+ January 2005
|+ April 2005
|- Published by
|+ Administrator User
|+ Hans Hauer
|+ Max Mustermann
|+ Time modified
|+ Modified by
Of course we need a split up again, e.g. if many of those object were published in January 2005. This might be split down by weeks, days, hours, minutes, etc.
This could be possible for date sorting, but it would be much work and I don't know how it would influence the speed of the tree. So I prefer a setting allowing you to specify how many object should be in a virtual folder resulting in this:
|- January 2005
|+ 1-49
|+ 50-99
|+ 99-126
...seems someone has to write a specification for this...
I'll try to get some human resources at Young Media Concepts for this - but if anyone of yours want to work on this (or any other thing related to the tree menu), just get in touch with us via:
join-treedevel [a-sign] ymc.ch
Any feedback is welcome, Daniel.
</code>
Daniel Beyer
_________________________________
YMC AG
Kreuzlingen, Switzerland
web: www.ymc.ch
____________________________________
|
