[
https://issues.apache.org/jira/browse/OFBIZ-3815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877372#action_12877372
]
Sascha Rodekamp edited comment on OFBIZ-3815 at 6/10/10 4:24 AM:
-----------------------------------------------------------------
Hi Ankit, Erwan
thanks for testing.
jep i know ... slow motion tree, i'm a little bit sad about it.
I noticed this issue yesterday too and ask google.
The reason is a bug in the Tree code. The developer wrote that he fixes this
bug and it will be released in the stable 1.0 version which can be downloaded
in a few days. I hope that he provide this version ASAP.
[http://code.google.com/p/jstree/issues/detail?id=558]
The Tree has two option how he create the DOM Elements from the JSON Code.
Default: He renders all Elements at the start-up (here is the bug in the
library a timeout alert). The rendering of the tree is slower but after loading
the navigation is as fast as in the dojo tree.
Loading on demand: The option i choose. Here the tree only creates the visible
DOM Elements. When you navigate to a subcategory the DOM Sub Elements will be
created at the time you opened the parent. That's for sure slower.
I will change this after the new version is released. So that shouldn't be a
show stopper :-)
was (Author: sascha):
Hi Ankit, Erwan
thanks for testing.
jep i know ... slow motion tree, i'm a little bit sad about it.
I noticed this issue yesterday too and ask google.
The reason is a bug in the Tree code. The developer wrote that he fixes this
bug and it will be released in the stable 1.0 version which can be downloaded
in a few days. I hope that he provide this version ASAP.
The Tree has two option how he create the DOM Elements from the JSON Code.
Default: He renders all Elements at the start-up (here is the bug in the
library a timeout alert). The rendering of the tree is slower but after loading
the navigation is as fast as in the dojo tree.
Loading on demand: The option i choose. Here the tree only creates the visible
DOM Elements. When you navigate to a subcategory the DOM Sub Elements will be
created at the time you opened the parent. That's for sure slower.
I will change this after the new version is released. So that shouldn't be a
show stopper :-)
> Content Navigation Tree implemented with jQuery
> -----------------------------------------------
>
> Key: OFBIZ-3815
> URL: https://issues.apache.org/jira/browse/OFBIZ-3815
> Project: OFBiz
> Issue Type: Sub-task
> Components: content
> Reporter: Sascha Rodekamp
> Attachments: OFBIZ-3815_jqueryExample_ContentNavigation.patch,
> OFBIZ-3815_plugins.zip
>
>
> Hi,
> here is the first (test) patch for the jQuery implementation.
> I changed the content navigation tree for a first test:
> [https://localhost:8443/content/control/navigateContent]
> The implementation was much easier than expected :-)
> I choose the jsTree Plugin v. 1.0rc (in the next days their will be a final
> 1.0 release, that's why i choose the rc).
> [http://www.jstree.com/]
> I also added
> {code}
> jQuery.noConflict();
> {code}
> to the libary. That overwrites the '$( ... )' operator to prevent conflicts
> with prototype. This line can be deleted after prototype is totally replaced.
> For know we have to call jQuery via jQuery( .... ) instead of $( ... ).
> To apply the patch the zip file have to copied to /images/jquery/
> it contains a plugin folder with the jsTree plugin
> (should look like /images/jquery/plugins/jsTree)
> So long
> Sascha
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
