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 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. |
[ https://issues.apache.org/jira/browse/OFBIZ-3815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sascha Rodekamp updated OFBIZ-3815: ----------------------------------- Attachment: OFBIZ-3815_jqueryExample_ContentNavigation.patch OFBIZ-3815_plugins.zip > 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-3815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877341#action_12877341 ] Ankit Jain commented on OFBIZ-3815: ----------------------------------- Hi Sascha, I tested your patch and its cool, tree is working fine. Good starting! Regards: Ankit Jain > 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-3815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877366#action_12877366 ] Erwan de FERRIERES commented on OFBIZ-3815: ------------------------------------------- Hi Sascha, just tried, very nice looking. Just to slow to open when clicking on a content (the prototype version is far more quicker). Cheers > 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-3815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877372#action_12877372 ] Sascha Rodekamp commented on OFBIZ-3815: ---------------------------------------- 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. |
In reply to this post by Nicolas Malin (Jira)
[ 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-3815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-3815: -------------------------------------- Assignee: Jacques Le Roux > 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 > Assignee: Jacques Le Roux > 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-3815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877377#action_12877377 ] Jacques Le Roux commented on OFBIZ-3815: ---------------------------------------- Thanks Sascha, Ankit, Erwan, I will wait the new version before commiting... > 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 > Assignee: Jacques Le Roux > 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-3815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877379#action_12877379 ] Erwan de FERRIERES commented on OFBIZ-3815: ------------------------------------------- I had the same thing in mind... But you assigned it to you before me ! So, wait and see ! Cheers; > 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 > Assignee: Jacques Le Roux > 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-3815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877385#action_12877385 ] Jacques Le Roux commented on OFBIZ-3815: ---------------------------------------- Erwan, If you have a chance to commit before me (not only this issue but all under OFBIZ-3814 as well), go ahead. I should be pretty busy the next 3 weeks, thanks! > 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 > Assignee: Jacques Le Roux > 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-3815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erwan de FERRIERES reassigned OFBIZ-3815: ----------------------------------------- Assignee: Erwan de FERRIERES (was: Jacques Le Roux) > 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 > Assignee: Erwan de FERRIERES > 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-3815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux updated OFBIZ-3815: ----------------------------------- Fix Version/s: jQuery Affects Version/s: jQuery > 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 > Affects Versions: jQuery > Reporter: Sascha Rodekamp > Assignee: Erwan de FERRIERES > Fix For: jQuery > > 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-3815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sascha Rodekamp updated OFBIZ-3815: ----------------------------------- Attachment: OFBIZ-3815_plugins.zip OFBIZ-3815_jqueryExample_ContentNavigation.patch Hey, here is the promise Tree update. In the current version the Tree widget is as fast as the dojo one. :-D Have a good day. Sascha > 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 > Affects Versions: jQuery > Reporter: Sascha Rodekamp > Assignee: Erwan de FERRIERES > Fix For: jQuery > > Attachments: OFBIZ-3815_jqueryExample_ContentNavigation.patch, OFBIZ-3815_jqueryExample_ContentNavigation.patch, OFBIZ-3815_plugins.zip, 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-3815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12887334#action_12887334 ] Erwan de FERRIERES commented on OFBIZ-3815: ------------------------------------------- Thanks Sascha, I'm just waiting for the 1.0 version of the jstree plugin... They published a new rc.. so wait and see ! > 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 > Affects Versions: jQuery > Reporter: Sascha Rodekamp > Assignee: Erwan de FERRIERES > Fix For: jQuery > > Attachments: OFBIZ-3815_jqueryExample_ContentNavigation.patch, OFBIZ-3815_jqueryExample_ContentNavigation.patch, OFBIZ-3815_plugins.zip, 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-3815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12887335#action_12887335 ] Sascha Rodekamp commented on OFBIZ-3815: ---------------------------------------- Jepok no problem :-) The rc2 works a lot better than the rc1. So i think the final release will be out soon. > 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 > Affects Versions: jQuery > Reporter: Sascha Rodekamp > Assignee: Erwan de FERRIERES > Fix For: jQuery > > Attachments: OFBIZ-3815_jqueryExample_ContentNavigation.patch, OFBIZ-3815_jqueryExample_ContentNavigation.patch, OFBIZ-3815_plugins.zip, 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-3815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ankit Jain updated OFBIZ-3815: ------------------------------ Attachment: OFBIZ_3815 Hello Folks, I have updated the Sascha's Patch and now all the tree functionality is working as it was in Dojo. Ankit Jain :) > 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 > Affects Versions: jQuery > Reporter: Sascha Rodekamp > Assignee: Erwan de FERRIERES > Fix For: jQuery > > Attachments: OFBIZ-3815_jqueryExample_ContentNavigation.patch, OFBIZ-3815_jqueryExample_ContentNavigation.patch, OFBIZ-3815_plugins.zip, OFBIZ-3815_plugins.zip, OFBIZ_3815 > > > 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-3815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12906517#action_12906517 ] Erwan de FERRIERES commented on OFBIZ-3815: ------------------------------------------- Hi Ankit, I'm just waiting for the final 1.0 version of jsTree to integrate your patch ! Cheers, > 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 > Affects Versions: jQuery > Reporter: Sascha Rodekamp > Assignee: Erwan de FERRIERES > Fix For: jQuery > > Attachments: OFBIZ-3815_jqueryExample_ContentNavigation.patch, OFBIZ-3815_jqueryExample_ContentNavigation.patch, OFBIZ-3815_plugins.zip, OFBIZ-3815_plugins.zip, OFBIZ_3815 > > > 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-3815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12906694#action_12906694 ] Sascha Rodekamp commented on OFBIZ-3815: ---------------------------------------- Hey Ankit, thanks for the update, you're code looks good to me. It would be great to i18n the labels from the context menu. Hopefully the guy releases the final version of the tree soon. Thanks for you're help. Have a good day Sascha > 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 > Affects Versions: jQuery > Reporter: Sascha Rodekamp > Assignee: Erwan de FERRIERES > Fix For: jQuery > > Attachments: OFBIZ-3815_jqueryExample_ContentNavigation.patch, OFBIZ-3815_jqueryExample_ContentNavigation.patch, OFBIZ-3815_plugins.zip, OFBIZ-3815_plugins.zip, OFBIZ_3815 > > > 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-3815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12906758#action_12906758 ] Jacques Le Roux commented on OFBIZ-3815: ---------------------------------------- Hi Guys, Note that I have used a beta for asmselect. I believe it's the best available alternative. I have also to i18n there... Also we have to check about references in LICENCE, are really only libs (here *.js) necessary (I guess so but I had no time to check...)? Even with only *.js there is still work for jQuery.ui, and some plugins :/ Though I just checked and for dojo it was only ofbiz/trunk/framework/images/webapp/images/dojo/* I wonder if it's legit... I think we should not keep any demos, etc. It's quickly deprecated and always better online... Less files is better... Thanks > 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 > Affects Versions: jQuery > Reporter: Sascha Rodekamp > Assignee: Erwan de FERRIERES > Fix For: jQuery > > Attachments: OFBIZ-3815_jqueryExample_ContentNavigation.patch, OFBIZ-3815_jqueryExample_ContentNavigation.patch, OFBIZ-3815_plugins.zip, OFBIZ-3815_plugins.zip, OFBIZ_3815 > > > 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. |
In reply to this post by Nicolas Malin (Jira)
[ https://issues.apache.org/jira/browse/OFBIZ-3815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12906761#action_12906761 ] Sascha Rodekamp commented on OFBIZ-3815: ---------------------------------------- Jep Jacques, we (I) should avoid keeping this example stuff. But instead of using asmselect, i would prefer to use the jQuery UI sortable functionality [http://jqueryui.com/demos/sortable/]. It provide the same functions as the asmselect but it's easier to maintain if we use the jQuery UI modules ... :-) > 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 > Affects Versions: jQuery > Reporter: Sascha Rodekamp > Assignee: Erwan de FERRIERES > Fix For: jQuery > > Attachments: OFBIZ-3815_jqueryExample_ContentNavigation.patch, OFBIZ-3815_jqueryExample_ContentNavigation.patch, OFBIZ-3815_plugins.zip, OFBIZ-3815_plugins.zip, OFBIZ_3815 > > > 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. |
Free forum by Nabble | Edit this page |