[ https://issues.apache.org/jira/browse/OFBIZ-3815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12906875#action_12906875 ] Jacques Le Roux commented on OFBIZ-3815: ---------------------------------------- Sascha, I had just a quick look at sortable, indeed it would be a better choice. I will have to have a new look because in the examples I did not find exactly what I'm looking for. Did you look at the example I put in in the jQuery branch? 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=12907120#action_12907120 ] Sascha Rodekamp commented on OFBIZ-3815: ---------------------------------------- Hi Jacques, not yet. I'm in London this week (to do a few workshops), during all the work here i didn't found time. But i will be back in my office on friday and than have look. 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=12920298#action_12920298 ] Jacques Le Roux commented on OFBIZ-3815: ---------------------------------------- Hi Sascha, # I did not find the multiple feature in sortable (demonstrated at webtools/control/LinkGeos and example/control/FormWidgetExamples) so I keep asmselect # Look like we will have to wait longer than expected for a release of jstree, I propose to use the current > 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=12920464#action_12920464 ] Sascha Rodekamp commented on OFBIZ-3815: ---------------------------------------- Hi Jacques, for me it's totally ok to use the RC2. It seems that it work without problems and i don't think that there will be no API or major changes to the final version. So in my opinion we can apply the patch and update the lib when the final version is released. 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=12925106#action_12925106 ] Jacques Le Roux commented on OFBIZ-3815: ---------------------------------------- Plugins commited at revision: 1027707 > 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=12925111#action_12925111 ] Jacques Le Roux commented on OFBIZ-3815: ---------------------------------------- Hi Guys, I think we have an issue, could you please check https://localhost:8443/content/control/WebSiteCms?webSiteId=CmsSite 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=12925113#action_12925113 ] Jacques Le Roux commented on OFBIZ-3815: ---------------------------------------- To remember: delete the old prototype/ dojo folders * framework/images/webapp/images/calendarDateSelect * framework/images/webapp/images/dijit * framework/images/webapp/images/dojo * framework/images/webapp/images/dojox * framework/images/webapp/images/prototypejs > 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=12925757#action_12925757 ] Sascha Rodekamp commented on OFBIZ-3815: ---------------------------------------- Hi guys, here are a few more issues, we only have migrated the ContentNav.ftl But we missed the nav.ftl, DisplayContentNav.ftl, WebsiteCMSContent.ftl and WebSiteCMSNav.ftl. They are all similar to our POC Tree and i hope that is not to much work to migrate them, i asked Ankit if he can support me with a few lines of code. Cheers 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:all-tabpanel ] Sascha Rodekamp updated OFBIZ-3815: ----------------------------------- Attachment: OFBIZ-3815_ContentNavigationMigration_part1.patch Hi Guys, here a patch from yesterday night. I did a little modification to Ankits patch for the contentNav.ftl (The Tree Labels wasn't not HTML decoded looks a little bit strange ;))+ And i added the Tree for the Help Popup and for the dataResource nav.ftl This patch doesn't migrate the tree and the dojo code in WebsiteCMSContent.ftl and WebSiteCMSNav.ftl (Sorry but i hadn't enough time yesterday evening :-( But i hope Ankit or me will found time at the WE. Have a good day Cheers 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_ContentNavigationMigration_part1.patch, 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=12926484#action_12926484 ] Jacques Le Roux commented on OFBIZ-3815: ---------------------------------------- The folders above have been deleted at revision: 1028925 > 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_ContentNavigationMigration_part1.patch, 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=12926571#action_12926571 ] Sascha Rodekamp commented on OFBIZ-3815: ---------------------------------------- Thanks Jacques, yes the update take hours (i'm kidding) :-) > 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_ContentNavigationMigration_part1.patch, 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:all-tabpanel ] Sascha Rodekamp updated OFBIZ-3815: ----------------------------------- Attachment: OFBIZ-3815_WebSiteCMSMigration_part2.patch OFBIZ-3815_elrteEditorPlugin.zip Hi guys, so finally i migrated the last WebCms Content Screens. I added the jsTree for the CMS Web Site Page and replace the old dojo WYSIWYG Editor with the one editor from elrte [http://elrte.org/]. To apply the patch: 1.) Copy the files from the zip archive into the jquery/plugin folder 2.) apply the patch file OFBIZ-3815_ContentNavigationMigration_part1.patch 3.) apply the patch file OFBIZ-3815_WebSiteCMSMigration_part2.patch One issue regarding the new editor occurred which i want first discuss. When i write my text and store it with the Editor everything is fine, the HTML code is stored in the electronicText Table. But when i reload the site and the editor get the stored data from the DB i.e. {code} <p>Dummy Text</p> {code} Freemarker encode the <p> Tag in HTML Save Characters (works as designed :-)). So we need a method which decodes the HTML Save output into normal HTML output to let the editor handle the data the right way. So We need something like 'encodeXmlValue' (the other way round). Any Ideas or preferences? Have a good evening 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_ContentNavigationMigration_part1.patch, OFBIZ-3815_elrteEditorPlugin.zip, OFBIZ-3815_jqueryExample_ContentNavigation.patch, OFBIZ-3815_jqueryExample_ContentNavigation.patch, OFBIZ-3815_plugins.zip, OFBIZ-3815_plugins.zip, OFBIZ-3815_WebSiteCMSMigration_part2.patch, 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=12927930#action_12927930 ] Jacques Le Roux commented on OFBIZ-3815: ---------------------------------------- Hi Sascha, Why and how did you chosse elRTE? Could you give us some elements? 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_ContentNavigationMigration_part1.patch, OFBIZ-3815_elrteEditorPlugin.zip, OFBIZ-3815_jqueryExample_ContentNavigation.patch, OFBIZ-3815_jqueryExample_ContentNavigation.patch, OFBIZ-3815_plugins.zip, OFBIZ-3815_plugins.zip, OFBIZ-3815_WebSiteCMSMigration_part2.patch, 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=12927935#action_12927935 ] Sascha Rodekamp commented on OFBIZ-3815: ---------------------------------------- we spoke about elRTE a few days and i find it was the best looking open source editor i found with the right license. > 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_ContentNavigationMigration_part1.patch, OFBIZ-3815_elrteEditorPlugin.zip, OFBIZ-3815_jqueryExample_ContentNavigation.patch, OFBIZ-3815_jqueryExample_ContentNavigation.patch, OFBIZ-3815_plugins.zip, OFBIZ-3815_plugins.zip, OFBIZ-3815_WebSiteCMSMigration_part2.patch, 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=12928270#action_12928270 ] Jacques Le Roux commented on OFBIZ-3815: ---------------------------------------- I had a closer look at and I like it too. The reasons: * it looks good: http://elrte.org/demo (though I don't like much how it formats the source - see source tab - but I agree that's minor and for instance [cleditor|http://premiumsoftware.net/cleditor] does not do better) * it is written with jQuery and jQuery-UI only * It has many Translations OOTB, and is easily localizable * It has been tested in Firefox 3.5+, Internet Explorer 7 & 8, Safari 4, Opera 10 and Chrome * BSD licensed There are other opinions http://stackoverflow.com/questions/1141073/whats-the-best-wysiwyg-editor-for-use-with-jquery I noticed experimental RTL feature for jwysiwyg http://akzhan.github.com/jwysiwyg/examples/07-enable-rtl.html but did not find how it works and it looks poor compared with elRTE (it's extendable but we are not much interested, we need something ready OOTB). I found http://aloha-editor.com (HTML5 editor) surprising, but I did not experiment a lot, for instance I did not find how to edit images...) To summarize elRTE has only one drawback: even minified it's still 160 kB, but we will load it only on purpose. I have updated jquery-ui to 1.8.6 (from 1.8.2, current elrte embeds 1.8.5). BTW Sascha, why did you remove the i18n js files? Also I guess we don't need ui-themes because they are already in framework\images\webapp\images\jquery\ui\css (also do we really need them?) On the size side: I have removed ui-development-bundle. Do we need framework\images\webapp\images\jquery\plugins\validate\lib? I don't think so. Even it's not a big deal (since it's only place taken on disk, not loaded with OFBiz), I think it's better to prune as much as possible. If we look back to Dojo and Prototype, they were respectively 4.3 MB and 311 kB, calendarselect being 44 kB, htmledit 27 kB and flotr 309 kB (flot is almost the same) Now we have 2.4 MB for all jQuery, plugins being 2 MB of it. If we look at memory footprint though, jQuery alone [according to wikipedia|http://en.wikipedia.org/wiki/Comparison_of_JavaScript_frameworks] is (24 kB minified & gzipped) but with plugins is more than Prototype-script.aculo.us (46�278 kB) and even Dojo (28 kB minified & gzipped). For Dojo I'm a bit suprised, I guess it needs more with the src sub-directories, like plugins for 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_ContentNavigationMigration_part1.patch, OFBIZ-3815_elrteEditorPlugin.zip, OFBIZ-3815_jqueryExample_ContentNavigation.patch, OFBIZ-3815_jqueryExample_ContentNavigation.patch, OFBIZ-3815_plugins.zip, OFBIZ-3815_plugins.zip, OFBIZ-3815_WebSiteCMSMigration_part2.patch, 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=12928273#action_12928273 ] Jacques Le Roux commented on OFBIZ-3815: ---------------------------------------- Ha, for ui-themes in in framework\images\webapp\images\jquery\ui\css I guess we need them for the calendar... > 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_ContentNavigationMigration_part1.patch, OFBIZ-3815_elrteEditorPlugin.zip, OFBIZ-3815_jqueryExample_ContentNavigation.patch, OFBIZ-3815_jqueryExample_ContentNavigation.patch, OFBIZ-3815_plugins.zip, OFBIZ-3815_plugins.zip, OFBIZ-3815_WebSiteCMSMigration_part2.patch, 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=12928956#action_12928956 ] Sascha Rodekamp commented on OFBIZ-3815: ---------------------------------------- Ha Jacques, thanks for that. Good Job to compare anything. I had also a quick look to the jQuery ui folder. and before we merge we have to clean up anyways. I have also a patch for the Window Lookup decorator [OFBIZ-3933], but to avoid creating the patch file twice (because of conflicts) i wait until you have commited these Content Tree / Editor Stuff :-) Cheers 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_ContentNavigationMigration_part1.patch, OFBIZ-3815_elrteEditorPlugin.zip, OFBIZ-3815_jqueryExample_ContentNavigation.patch, OFBIZ-3815_jqueryExample_ContentNavigation.patch, OFBIZ-3815_plugins.zip, OFBIZ-3815_plugins.zip, OFBIZ-3815_WebSiteCMSMigration_part2.patch, 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:all-tabpanel ] Jacques Le Roux reassigned OFBIZ-3815: -------------------------------------- Assignee: Jacques Le Roux (was: Erwan de FERRIERES) > 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: Jacques Le Roux > Fix For: jQuery > > Attachments: OFBIZ-3815_ContentNavigationMigration_part1.patch, OFBIZ-3815_elrteEditorPlugin.zip, OFBIZ-3815_jqueryExample_ContentNavigation.patch, OFBIZ-3815_jqueryExample_ContentNavigation.patch, OFBIZ-3815_plugins.zip, OFBIZ-3815_plugins.zip, OFBIZ-3815_WebSiteCMSMigration_part2.patch, 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 |