[jira] [Updated] (OFBIZ-6464) Consolidate name and partyId field of order/widget/ordermgr/CustRequestForms.xml#ListRequestRoles
[ https://issues.apache.org/jira/browse/OFBIZ-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Carlow updated OFBIZ-6464: Attachment: OFBIZ-6464_2.patch This patch fixes the last so that the consolidated partyId display-entity also-hidden=true, otherwise a primary key error occurs Consolidate name and partyId field of order/widget/ordermgr/CustRequestForms.xml#ListRequestRoles - Key: OFBIZ-6464 URL: https://issues.apache.org/jira/browse/OFBIZ-6464 Project: OFBiz Issue Type: Improvement Components: order Affects Versions: Trunk Reporter: Christian Carlow Priority: Minor Fix For: Upcoming Branch Attachments: OFBIZ-6464.patch, OFBIZ-6464_2.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6464) Consolidate name and partyId field of order/widget/ordermgr/CustRequestForms.xml#ListRequestRoles
[ https://issues.apache.org/jira/browse/OFBIZ-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14575922#comment-14575922 ] Christian Carlow commented on OFBIZ-6464: - Previous patch fixed in: trunk r1683949 Consolidate name and partyId field of order/widget/ordermgr/CustRequestForms.xml#ListRequestRoles - Key: OFBIZ-6464 URL: https://issues.apache.org/jira/browse/OFBIZ-6464 Project: OFBiz Issue Type: Improvement Components: order Affects Versions: Trunk Reporter: Christian Carlow Priority: Minor Fix For: Upcoming Branch Attachments: OFBIZ-6464.patch, OFBIZ-6464_2.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6463) ordermgr/control/deleteCustRequestParty should delete the record rather than updating the through date
[ https://issues.apache.org/jira/browse/OFBIZ-6463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14575925#comment-14575925 ] Christian Carlow commented on OFBIZ-6463: - Fixed in: trunk r1683953 ordermgr/control/deleteCustRequestParty should delete the record rather than updating the through date -- Key: OFBIZ-6463 URL: https://issues.apache.org/jira/browse/OFBIZ-6463 Project: OFBiz Issue Type: Improvement Components: order Affects Versions: Trunk Reporter: Christian Carlow Priority: Minor Fix For: Upcoming Branch Attachments: OFBIZ-6463.patch Users expect to be able to remove accidentally added faulty CustRequestParty but the current implementation only updates the through date when the delete button is clicked. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-6463) ordermgr/control/deleteCustRequestParty should delete the record rather than updating the through date
[ https://issues.apache.org/jira/browse/OFBIZ-6463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Carlow closed OFBIZ-6463. --- Resolution: Implemented Fix Version/s: Upcoming Branch ordermgr/control/deleteCustRequestParty should delete the record rather than updating the through date -- Key: OFBIZ-6463 URL: https://issues.apache.org/jira/browse/OFBIZ-6463 Project: OFBiz Issue Type: Improvement Components: order Affects Versions: Trunk Reporter: Christian Carlow Priority: Minor Fix For: Upcoming Branch Attachments: OFBIZ-6463.patch Users expect to be able to remove accidentally added faulty CustRequestParty but the current implementation only updates the through date when the delete button is clicked. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6463) ordermgr/control/deleteCustRequestParty should delete the record rather than updating the through date
[ https://issues.apache.org/jira/browse/OFBIZ-6463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14575938#comment-14575938 ] Pierre Smits commented on OFBIZ-6463: - Setting the through date on party expiration is default behaviour and part of GRC protocols. Having functions available for common order management officers to delete such records (even if added accidentally)undermines such protocols. Deletion of accidental records can always be done through functions in Webtools/entitymanagement. ordermgr/control/deleteCustRequestParty should delete the record rather than updating the through date -- Key: OFBIZ-6463 URL: https://issues.apache.org/jira/browse/OFBIZ-6463 Project: OFBiz Issue Type: Improvement Components: order Affects Versions: Trunk Reporter: Christian Carlow Priority: Minor Fix For: Upcoming Branch Attachments: OFBIZ-6463.patch Users expect to be able to remove accidentally added faulty CustRequestParty but the current implementation only updates the through date when the delete button is clicked. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-6462) Redisign ordermgr/control/EditQuoteRole to resemble ordermgr/control/requestroles
[ https://issues.apache.org/jira/browse/OFBIZ-6462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14575939#comment-14575939 ] Christian Carlow edited comment on OFBIZ-6462 at 6/6/15 8:59 PM: - Is it necessary to create a QuoteParty to replace QuoteRole as CustRequestParty was created to replace CustRequestRole or can fromDate and thruDate fields just be added? Are new entities created whenever extensions entail changes to primary key which would be the case for the fromDate? The expire functionality provided in OFBIZ-6463 cannot be implemented for this issue until this is resolved. was (Author: ofbizzer): Is is necessary to create a QuoteParty to replace QuoteRole as CustRequestParty was created to replace CustRequestRole or can fromDate and thruDate fields just be added? Are new entities created whenever extensions entail changes to primary key which would be the case for the fromDate? The expire functionality provided in OFBIZ-6463 cannot be implemented for this issue until this is resolved. Redisign ordermgr/control/EditQuoteRole to resemble ordermgr/control/requestroles - Key: OFBIZ-6462 URL: https://issues.apache.org/jira/browse/OFBIZ-6462 Project: OFBiz Issue Type: Improvement Components: order Affects Versions: Trunk Reporter: Christian Carlow Priority: Minor The quote role form requires the create button to unnecessarily be clicked before a new quote can be created and all roles are included in the dropdown rather than those only relevant for the quote. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6462) Redisign ordermgr/control/EditQuoteRole to resemble ordermgr/control/requestroles
[ https://issues.apache.org/jira/browse/OFBIZ-6462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14575939#comment-14575939 ] Christian Carlow commented on OFBIZ-6462: - Is is necessary to create a QuoteParty to replace QuoteRole as CustRequestParty was created to replace CustRequestRole or can fromDate and thruDate fields just be added? Are new entities created whenever extensions entail changes to primary key which would be the case for the fromDate? The expire functionality provided in OFBIZ-6463 cannot be implemented for this issue until this is resolved. Redisign ordermgr/control/EditQuoteRole to resemble ordermgr/control/requestroles - Key: OFBIZ-6462 URL: https://issues.apache.org/jira/browse/OFBIZ-6462 Project: OFBiz Issue Type: Improvement Components: order Affects Versions: Trunk Reporter: Christian Carlow Priority: Minor The quote role form requires the create button to unnecessarily be clicked before a new quote can be created and all roles are included in the dropdown rather than those only relevant for the quote. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Possible Documentation and help solutions - DITA
Hi Paul, I am starting to use DITA and really like it. But I can see your point regarding people being put off. It might be in a sense a bit too powerful for OFBiz and it takes a while to wrap your head around the concepts like maps, topics, etc ... I'm on the fence, maybe leaning slightly towards keeping DocBook, but if a PoC shows how DITA can shine, then why not! Taher Alkhateeb - Original Message - From: Paul Foxworthy p...@cohsoft.com.a Pau To: dev@ofbiz.apache.org Sent: Saturday, 6 June, 2015 9:10:28 AM Subject: Re: Possible Documentation and help solutions - DITA Sharan-F wrote I'm a bit unclear about what you are suggesting. * Is it about replacing the Docbook implementation we currently have within OFBiz with something else (e.g Asciidoc)? * Is it about extracting the Docbook content from what we currently have in OFBiz and then generating it into another format that we could possibly re-introduce? * Or is it something else? Hi Sharan, My suggestion is much more modest than that. I think there's no need to replace existing DocBook content, or to totally change the DocBook process we have. All I am suggesting is that people consider AsciiDoc as a first step when authoring help information. If they prefer to work with DocBook directly, fine. There are tools to transform AsciDoc into DocBook XML, such as AsciiDoctor (http://asciidoctor.org/), so in effect (correctly written) AsciiDoc *is* DocBook. I'll repeat the reasons why I like AsciiDoc. It's more human-readable than XML. You can write your documentation in any text editor. Both of these are important. In contrast, requiring XML and some more specialised tool is a barrier to entry, so less people could and would participate in documenting OFBiz. When I last looked into DITA quite a few years ago, it seemed to be a heavyweight thing that only made sense if you wanted multiple destinations and were willing to invest in proprietary tools like Framemaker, Oxygen or Arbortext. I am perfectly willing to believe that DITA is more complete than DocBook, and would allow better documentation, if only anyone was willing to invest the time, trouble and money to be able to use it. I'm pleased to hear there's now DITA support for Eclipse. Eclipse is not my favourite IDE, but I could be persuaded to use it. How much better would it be to say to potential contributors that they can use their favourite IDE or text editor, whatever that is? If everybody else loves DITA, I would work with it. But I worry that it will put many people off. Thanks Paul Foxworthy - -- Coherent Software Australia Pty Ltd http://www.coherentsoftware.com.au/ Bonsai ERP, the all-inclusive ERP system http://www.bonsaierp.com.au/ -- View this message in context: http://ofbiz.135035.n4.nabble.com/Possible-Documentation-and-help-solutions-DITA-tp4669377p4669576.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.
[jira] [Updated] (OFBIZ-6458) Upgrade OFBiz to Java JDK 8
[ https://issues.apache.org/jira/browse/OFBIZ-6458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taher Alkhateeb updated OFBIZ-6458: --- Attachment: OFBIZ-6458-04-update-README.patch Forgot to update the README file. So adding it as a forth patch since all the patches should be done together whenever infra is ready. Upgrade OFBiz to Java JDK 8 --- Key: OFBIZ-6458 URL: https://issues.apache.org/jira/browse/OFBIZ-6458 Project: OFBiz Issue Type: Improvement Affects Versions: Upcoming Branch Reporter: Taher Alkhateeb Assignee: Jacques Le Roux Priority: Critical Labels: java, jdk, jdk8, upgrade Fix For: Upcoming Branch Attachments: OFBIZ-6458-01-fix-test-errors.patch, OFBIZ-6458-02-fix-eclipse-compiler.patch, OFBIZ-6458-03-update-to-jdk8.patch, OFBIZ-6458-04-update-README.patch The following will be tracked through this JIRA: - upgrade the framework to JDK 8 and fix any errors - make sure that ./ant clean-all load-demo run-tests will run after the upgrade - upgrade the infrastructure and demo server to accommodate the new change -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Possible Documentation and help solutions - DITA
Sharan-F wrote I'm a bit unclear about what you are suggesting. * Is it about replacing the Docbook implementation we currently have within OFBiz with something else (e.g Asciidoc)? * Is it about extracting the Docbook content from what we currently have in OFBiz and then generating it into another format that we could possibly re-introduce? * Or is it something else? Hi Sharan, My suggestion is much more modest than that. I think there's no need to replace existing DocBook content, or to totally change the DocBook process we have. All I am suggesting is that people consider AsciiDoc as a first step when authoring help information. If they prefer to work with DocBook directly, fine. There are tools to transform AsciDoc into DocBook XML, such as AsciiDoctor (http://asciidoctor.org/), so in effect (correctly written) AsciiDoc *is* DocBook. I'll repeat the reasons why I like AsciiDoc. It's more human-readable than XML. You can write your documentation in any text editor. Both of these are important. In contrast, requiring XML and some more specialised tool is a barrier to entry, so less people could and would participate in documenting OFBiz. When I last looked into DITA quite a few years ago, it seemed to be a heavyweight thing that only made sense if you wanted multiple destinations and were willing to invest in proprietary tools like Framemaker, Oxygen or Arbortext. I am perfectly willing to believe that DITA is more complete than DocBook, and would allow better documentation, if only anyone was willing to invest the time, trouble and money to be able to use it. I'm pleased to hear there's now DITA support for Eclipse. Eclipse is not my favourite IDE, but I could be persuaded to use it. How much better would it be to say to potential contributors that they can use their favourite IDE or text editor, whatever that is? If everybody else loves DITA, I would work with it. But I worry that it will put many people off. Thanks Paul Foxworthy - -- Coherent Software Australia Pty Ltd http://www.coherentsoftware.com.au/ Bonsai ERP, the all-inclusive ERP system http://www.bonsaierp.com.au/ -- View this message in context: http://ofbiz.135035.n4.nabble.com/Possible-Documentation-and-help-solutions-DITA-tp4669377p4669576.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.
Re: Possible Documentation and help solutions - DITA
Sharan-F wrote Confluence is the Apache approved tools for wiki so we still need to work within this constraint for now. In any case – I think we firstly need to do some review of the all the documentation we have before we start structuring it. Hi Sharan, There is a free tool to import DocBook into Confluence : https://marketplace.atlassian.com/plugins/org.jboss.labs.confluence.plugin.docbook_import There's also a commercial one to go in the other direction: https://www.k15t.com/software/scroll-docbook-exporter/overview . *If* we wanted to use the wiki as a place to develop help, we could ask the vendor if they were willing to donate their product to an open source project. Cheers Paul Foxworthy - -- Coherent Software Australia Pty Ltd http://www.coherentsoftware.com.au/ Bonsai ERP, the all-inclusive ERP system http://www.bonsaierp.com.au/ -- View this message in context: http://ofbiz.135035.n4.nabble.com/Possible-Documentation-and-help-solutions-DITA-tp4669377p4669577.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.
Unable to take update or checkout
Hello, I am getting following error when taking update of any of the OFBiz code base(trunk or release branches): ashish@ashish:~/ofbiz-dev/ofbiz-14.12$ svn update Updating '.': svn: E175011: Repository moved permanently to 'https://svn.apache.org'; please relocate svn: E175009: Additional errors: svn: E175009: XML parsing failed: (301 Moved Permanently) It seems that ASF team is working on this issue and it will be rectified soon. Please refer below link: http://status.apache.org/ -- Kind Regards Ashish Vijaywargiya HotWax Systems - est. 1997
[jira] [Updated] (OFBIZ-6326) Pagination doesn't render well in Bootstrap Basic
[ https://issues.apache.org/jira/browse/OFBIZ-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-6326: Attachment: Screen Shot 2015-06-06 at 14.47.24.png The search/find screen in the party app shows a different kind of pagination. Pagination doesn't render well in Bootstrap Basic - Key: OFBIZ-6326 URL: https://issues.apache.org/jira/browse/OFBIZ-6326 Project: OFBiz Issue Type: Sub-task Components: themes Affects Versions: Bootstrap theme Reporter: Pierre Smits Assignee: Julien NICOLAS Labels: pagination Fix For: Bootstrap theme Attachments: Image 068.png, Screen Shot 2015-05-30 at 14.52.17.png, Screen Shot 2015-06-06 at 14.44.18.png, Screen Shot 2015-06-06 at 14.47.24.png When accessing an overview page (e.g. /catalog/control/FindProduct) with more than the default number of records to be shown, the pagination comes out garbled. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Unable to take update or checkout
Thanks for the update, Ashish. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Sat, Jun 6, 2015 at 11:47 AM, Ashish Vijaywargiya ashish.vijaywarg...@hotwaxsystems.com wrote: Hello, I am getting following error when taking update of any of the OFBiz code base(trunk or release branches): ashish@ashish:~/ofbiz-dev/ofbiz-14.12$ svn update Updating '.': svn: E175011: Repository moved permanently to 'https://svn.apache.org'; please relocate svn: E175009: Additional errors: svn: E175009: XML parsing failed: (301 Moved Permanently) It seems that ASF team is working on this issue and it will be rectified soon. Please refer below link: http://status.apache.org/ -- Kind Regards Ashish Vijaywargiya HotWax Systems - est. 1997
Re: Unable to take update or checkout
SVN service restored but some DNS related issue still persists. Thanks Regards — Deepak Dixit On Jun 6, 2015, at 4:01 PM, Pierre Smits pierre.sm...@gmail.com wrote: SVN services are restored, according to a message in the infra ml. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Sat, Jun 6, 2015 at 11:48 AM, Pierre Smits pierre.sm...@gmail.com wrote: Thanks for the update, Ashish. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Sat, Jun 6, 2015 at 11:47 AM, Ashish Vijaywargiya ashish.vijaywarg...@hotwaxsystems.com wrote: Hello, I am getting following error when taking update of any of the OFBiz code base(trunk or release branches): ashish@ashish:~/ofbiz-dev/ofbiz-14.12$ svn update Updating '.': svn: E175011: Repository moved permanently to 'https://svn.apache.org'; please relocate svn: E175009: Additional errors: svn: E175009: XML parsing failed: (301 Moved Permanently) It seems that ASF team is working on this issue and it will be rectified soon. Please refer below link: http://status.apache.org/ -- Kind Regards Ashish Vijaywargiya HotWax Systems - est. 1997
Re: Unable to take update or checkout
Still it is not working for me. ashish@ashish:~/ofbiz-dev/ofbiz-14.12$ svn update Updating '.': svn: E175011: Repository moved permanently to 'https://svn.apache.org'; please relocate svn: E175009: Additional errors: svn: E175009: XML parsing failed: (301 Moved Permanently) ashish@ashish:~/ofbiz-dev/ofbiz-14.12$ date Sat Jun 6 16:13:01 IST 2015 Kind Regards Ashish Vijaywargiya HotWax Systems - est. 1997 On Sat, Jun 6, 2015 at 4:01 PM, Pierre Smits pierre.sm...@gmail.com wrote: SVN services are restored, according to a message in the infra ml. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Sat, Jun 6, 2015 at 11:48 AM, Pierre Smits pierre.sm...@gmail.com wrote: Thanks for the update, Ashish. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Sat, Jun 6, 2015 at 11:47 AM, Ashish Vijaywargiya ashish.vijaywarg...@hotwaxsystems.com wrote: Hello, I am getting following error when taking update of any of the OFBiz code base(trunk or release branches): ashish@ashish:~/ofbiz-dev/ofbiz-14.12$ svn update Updating '.': svn: E175011: Repository moved permanently to 'https://svn.apache.org'; please relocate svn: E175009: Additional errors: svn: E175009: XML parsing failed: (301 Moved Permanently) It seems that ASF team is working on this issue and it will be rectified soon. Please refer below link: http://status.apache.org/ -- Kind Regards Ashish Vijaywargiya HotWax Systems - est. 1997
[jira] [Commented] (OFBIZ-6466) Lookup modal window is overlapped by top menu
[ https://issues.apache.org/jira/browse/OFBIZ-6466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14575714#comment-14575714 ] Pierre Smits commented on OFBIZ-6466: - The cause of the issue is that in the header.ftl (navbar-fixed-top) has been added in http://svn.apache.org/viewvc?view=revisionrevision=1683430 Lookup modal window is overlapped by top menu - Key: OFBIZ-6466 URL: https://issues.apache.org/jira/browse/OFBIZ-6466 Project: OFBiz Issue Type: Sub-task Components: themes Affects Versions: Bootstrap theme Reporter: Pierre Smits Attachments: Screen Shot 2015-06-06 at 14.30.50.png When opening a lookup window (modal window) the top menu is on top of the modal window. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-6467) Disentangle themes
Pierre Smits created OFBIZ-6467: --- Summary: Disentangle themes Key: OFBIZ-6467 URL: https://issues.apache.org/jira/browse/OFBIZ-6467 Project: OFBiz Issue Type: Sub-task Components: themes Affects Versions: Bootstrap theme Reporter: Pierre Smits Assignee: Pierre Smits Currently in the branch the two bootstrap styles (Basic and yellow 'Sunrise) are entwined. The effect is that when changes are implemented in one theme they alter the user experience in the other theme. It would be better to disentangle the 2 styles into separate themes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6450) Docbook and OFBIz Online Help
[ https://issues.apache.org/jira/browse/OFBIZ-6450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14575648#comment-14575648 ] Taher Alkhateeb commented on OFBIZ-6450: Hi Sharan, So a good start as indicated above would be to give us a broken place to start from with steps to re-produce as you discovered them. Docbook and OFBIz Online Help - Key: OFBIZ-6450 URL: https://issues.apache.org/jira/browse/OFBIZ-6450 Project: OFBiz Issue Type: Bug Reporter: Sharan Foga Jira created based on the steps suggested by Taher as follows: - First, we attempt to fix whatever is wrong in DocBook at the moment. If you can share exactly what you spotted then this would save us a lot of time in trying to dig to the problem. So a repeat process to identify the bugs from you would be great. - Second, we decide on a category structure for the sections of the documentation if we do not like the existing one - We also introduce or enforce a workflow that mandates an update of the documentation on each JIRA that affects functionality that requires documentation. For example, if we add or modify a screen in the party component, then we must provide the documentation for that screen before closing the JIRA for example. - As a last step we decide on the appropriate technology to move forward. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6450) Docbook and OFBIz Online Help
[ https://issues.apache.org/jira/browse/OFBIZ-6450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14575653#comment-14575653 ] Sharan Foga commented on OFBIZ-6450: Hi Taher. It's on my worklist for today. I'll start with the current trunk as the reference point. Docbook and OFBIz Online Help - Key: OFBIZ-6450 URL: https://issues.apache.org/jira/browse/OFBIZ-6450 Project: OFBiz Issue Type: Bug Reporter: Sharan Foga Jira created based on the steps suggested by Taher as follows: - First, we attempt to fix whatever is wrong in DocBook at the moment. If you can share exactly what you spotted then this would save us a lot of time in trying to dig to the problem. So a repeat process to identify the bugs from you would be great. - Second, we decide on a category structure for the sections of the documentation if we do not like the existing one - We also introduce or enforce a workflow that mandates an update of the documentation on each JIRA that affects functionality that requires documentation. For example, if we add or modify a screen in the party component, then we must provide the documentation for that screen before closing the JIRA for example. - As a last step we decide on the appropriate technology to move forward. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Unable to take update or checkout
SVN services are restored, according to a message in the infra ml. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Sat, Jun 6, 2015 at 11:48 AM, Pierre Smits pierre.sm...@gmail.com wrote: Thanks for the update, Ashish. Best regards, Pierre Smits *ORRTIZ.COM http://www.orrtiz.com* Services Solutions for Cloud- Based Manufacturing, Professional Services and Retail Trade http://www.orrtiz.com On Sat, Jun 6, 2015 at 11:47 AM, Ashish Vijaywargiya ashish.vijaywarg...@hotwaxsystems.com wrote: Hello, I am getting following error when taking update of any of the OFBiz code base(trunk or release branches): ashish@ashish:~/ofbiz-dev/ofbiz-14.12$ svn update Updating '.': svn: E175011: Repository moved permanently to 'https://svn.apache.org'; please relocate svn: E175009: Additional errors: svn: E175009: XML parsing failed: (301 Moved Permanently) It seems that ASF team is working on this issue and it will be rectified soon. Please refer below link: http://status.apache.org/ -- Kind Regards Ashish Vijaywargiya HotWax Systems - est. 1997
[jira] [Updated] (OFBIZ-6466) Lookup modal window is overlapped by top menu
[ https://issues.apache.org/jira/browse/OFBIZ-6466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-6466: Attachment: Screen Shot 2015-06-06 at 14.30.50.png See attached image. Lookup modal window is overlapped by top menu - Key: OFBIZ-6466 URL: https://issues.apache.org/jira/browse/OFBIZ-6466 Project: OFBiz Issue Type: Sub-task Components: themes Affects Versions: Bootstrap theme Reporter: Pierre Smits Attachments: Screen Shot 2015-06-06 at 14.30.50.png When opening a lookup window (modal window) the top menu is on top of the modal window. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-6466) Lookup modal window is overlapped by top menu
Pierre Smits created OFBIZ-6466: --- Summary: Lookup modal window is overlapped by top menu Key: OFBIZ-6466 URL: https://issues.apache.org/jira/browse/OFBIZ-6466 Project: OFBiz Issue Type: Sub-task Components: themes Affects Versions: Bootstrap theme Reporter: Pierre Smits Attachments: Screen Shot 2015-06-06 at 14.30.50.png When opening a lookup window (modal window) the top menu is on top of the modal window. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6326) Pagination doesn't render well in Bootstrap Basic
[ https://issues.apache.org/jira/browse/OFBIZ-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-6326: Attachment: Screen Shot 2015-06-06 at 14.44.18.png When looking at another screen with enough entity records in the database the pagination is rendered correctly. See attached image. Is the reported issue only related to the search/find screen regarding products in the catalog app? Pagination doesn't render well in Bootstrap Basic - Key: OFBIZ-6326 URL: https://issues.apache.org/jira/browse/OFBIZ-6326 Project: OFBiz Issue Type: Sub-task Components: themes Affects Versions: Bootstrap theme Reporter: Pierre Smits Assignee: Julien NICOLAS Labels: pagination Fix For: Bootstrap theme Attachments: Image 068.png, Screen Shot 2015-05-30 at 14.52.17.png, Screen Shot 2015-06-06 at 14.44.18.png When accessing an overview page (e.g. /catalog/control/FindProduct) with more than the default number of records to be shown, the pagination comes out garbled. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6456) Make auto-fields-entity sort by field type by default
[ https://issues.apache.org/jira/browse/OFBIZ-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14575784#comment-14575784 ] Christian Carlow commented on OFBIZ-6456: - The patch may need to be revised again to better handle the order in which hyperlinks appear. For example, at ordermgr/control/requestitems, the custRequestItemSeqId hyperlink gets rendered at the end of the form/grid list but before it was the first field to appear. A workaround is to set custRequestItemSeqId as display and add a dedicated edit button but this would probably have to be done for various ItemSeq forms. Extending form widgets to allow overriding the default field type sequence rendering with something like field-seq attribute may be a solution. Make auto-fields-entity sort by field type by default --- Key: OFBIZ-6456 URL: https://issues.apache.org/jira/browse/OFBIZ-6456 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Christian Carlow Attachments: OFBIZ-6456_2.patch IMO, form widgets are generally easier to interpret when the field types are sorted by type but this has to be done manually using sort-order. I propose improving auto-fields-entity to sort fields by type by default such as text, then dates, then numbers, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6456) Make auto-fields-entity sort by field type by default
[ https://issues.apache.org/jira/browse/OFBIZ-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Carlow updated OFBIZ-6456: Attachment: OFBIZ-6456_3.patch This patches employs the new ModelField.type tracking for ModelFormFieldBuilder of OFBIZ-6468 so that id type fields that are hyperlinks are rendered at the beginning of the field sequence instead of at the end. Make auto-fields-entity sort by field type by default --- Key: OFBIZ-6456 URL: https://issues.apache.org/jira/browse/OFBIZ-6456 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Christian Carlow Attachments: OFBIZ-6456_3.patch IMO, form widgets are generally easier to interpret when the field types are sorted by type but this has to be done manually using sort-order. I propose improving auto-fields-entity to sort fields by type by default such as text, then dates, then numbers, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6468) Add support for ModelForm.type tracking from ModelFormFieldBuilder
[ https://issues.apache.org/jira/browse/OFBIZ-6468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Carlow updated OFBIZ-6468: Priority: Minor (was: Major) Issue Type: Improvement (was: Bug) Add support for ModelForm.type tracking from ModelFormFieldBuilder -- Key: OFBIZ-6468 URL: https://issues.apache.org/jira/browse/OFBIZ-6468 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Christian Carlow Priority: Minor This could be done by adding ModelFormFieldBuilder.modelField as new member for tracking the entire ModelField object or if thats overkill adding ModelFormFieldBuilder.modelFieldType for just the type. This functionality would provide a way for OFBIZ-6456 to ignore the default field sequence sort for id type fields that are hyperlinks which typically appear as beginning fields. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6456) Make auto-fields-entity sort by field type by default
[ https://issues.apache.org/jira/browse/OFBIZ-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14575799#comment-14575799 ] Christian Carlow commented on OFBIZ-6456: - Ignoring the default hyperlink field sequence sort for id type fields identified by the auto-fields-entity seems the simplest solution. I'll work on this and resubmit the patch. Make auto-fields-entity sort by field type by default --- Key: OFBIZ-6456 URL: https://issues.apache.org/jira/browse/OFBIZ-6456 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Christian Carlow Attachments: OFBIZ-6456_2.patch IMO, form widgets are generally easier to interpret when the field types are sorted by type but this has to be done manually using sort-order. I propose improving auto-fields-entity to sort fields by type by default such as text, then dates, then numbers, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-6468) Add support for ModelForm.type tracking from ModelFormFieldBuilder
Christian Carlow created OFBIZ-6468: --- Summary: Add support for ModelForm.type tracking from ModelFormFieldBuilder Key: OFBIZ-6468 URL: https://issues.apache.org/jira/browse/OFBIZ-6468 Project: OFBiz Issue Type: Bug Components: framework Affects Versions: Trunk Reporter: Christian Carlow This could be done by adding ModelFormFieldBuilder.modelField as new member for tracking the entire ModelField object or if thats overkill adding ModelFormFieldBuilder.modelFieldType for just the type. This functionality would provide a way for OFBIZ-6456 to ignore the default field sequence sort for id type fields that are hyperlinks which typically appear as beginning fields. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6450) Docbook and OFBIz Online Help
[ https://issues.apache.org/jira/browse/OFBIZ-6450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14575831#comment-14575831 ] Sharan Foga commented on OFBIZ-6450: Hi Taher I've been looking at the help and all the component documentation help files seem to use the docbook section (recursive section) tag. I can't find any chapter tags or even the book tag in any of the files I've looked at. There must be a book tag somewhere! When I was doing the HR documentation – (from the Webhelp addon) it had been written as a complete docbook book with chapters, sect1, sect2 etc. - I had tried to copy it into the HELP_HR.xml and it didnt work (i.e wouldnt display) - I also tried to copy some of the sect1 and sect2 and that didnt work either (i.e wouldnt display) I think these could be explained by not being allowed to nest any chapters or sect1 and sect2 tags into a section tag. - I also tried to use some of the text formatting commands just as a line somewhere within the section eg. paraemphasis role=bold Nodes In the Company Tree/emphasis/para but this didnt work either. The text was displayed but it wasn't displayed in bold. I also tried some of the mediaobject and screenshot tags and they didnt work either. The only tags that seem to work within a section tag are the following: title para itemizedlist If I had to guess I would say that it sounds like our docbook structure is built only on recursive section tags which could explain the limitations I've experienced. Docbook and OFBIz Online Help - Key: OFBIZ-6450 URL: https://issues.apache.org/jira/browse/OFBIZ-6450 Project: OFBiz Issue Type: Bug Reporter: Sharan Foga Jira created based on the steps suggested by Taher as follows: - First, we attempt to fix whatever is wrong in DocBook at the moment. If you can share exactly what you spotted then this would save us a lot of time in trying to dig to the problem. So a repeat process to identify the bugs from you would be great. - Second, we decide on a category structure for the sections of the documentation if we do not like the existing one - We also introduce or enforce a workflow that mandates an update of the documentation on each JIRA that affects functionality that requires documentation. For example, if we add or modify a screen in the party component, then we must provide the documentation for that screen before closing the JIRA for example. - As a last step we decide on the appropriate technology to move forward. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6456) Make auto-fields-entity sort by field type by default
[ https://issues.apache.org/jira/browse/OFBIZ-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Carlow updated OFBIZ-6456: Attachment: (was: OFBIZ-6456_2.patch) Make auto-fields-entity sort by field type by default --- Key: OFBIZ-6456 URL: https://issues.apache.org/jira/browse/OFBIZ-6456 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Christian Carlow IMO, form widgets are generally easier to interpret when the field types are sorted by type but this has to be done manually using sort-order. I propose improving auto-fields-entity to sort fields by type by default such as text, then dates, then numbers, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6468) Add support for ModelForm.type tracking from ModelFormFieldBuilder
[ https://issues.apache.org/jira/browse/OFBIZ-6468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Carlow updated OFBIZ-6468: Attachment: OFBIZ-6468_2.patch This patch adds modelFieldType string as member to ModelFormFieldBuilder class to track the original ModelField.type of auto-fields-entity. Add support for ModelForm.type tracking from ModelFormFieldBuilder -- Key: OFBIZ-6468 URL: https://issues.apache.org/jira/browse/OFBIZ-6468 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Christian Carlow Priority: Minor Attachments: OFBIZ-6468_2.patch This could be done by adding ModelFormFieldBuilder.modelField as new member for tracking the entire ModelField object or if thats overkill adding ModelFormFieldBuilder.modelFieldType for just the type. This functionality would provide a way for OFBIZ-6456 to ignore the default field sequence sort for id type fields that are hyperlinks which typically appear as beginning fields. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6463) ordermgr/control/deleteCustRequestParty should delete the record rather than updating the through date
[ https://issues.apache.org/jira/browse/OFBIZ-6463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14575950#comment-14575950 ] Pierre Smits commented on OFBIZ-6463: - This can indeed be done in a separate and new issue. ordermgr/control/deleteCustRequestParty should delete the record rather than updating the through date -- Key: OFBIZ-6463 URL: https://issues.apache.org/jira/browse/OFBIZ-6463 Project: OFBiz Issue Type: Improvement Components: order Affects Versions: Trunk Reporter: Christian Carlow Priority: Minor Fix For: Upcoming Branch Attachments: OFBIZ-6463.patch Users expect to be able to remove accidentally added faulty CustRequestParty but the current implementation only updates the through date when the delete button is clicked. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: References for DITA as a tool for on-line help
OK DITA seems powerful but not an easy tool to work with (not only because of XML verbosity but also tags and concepts to learn) Sincerely the examples in http://fr.wikipedia.org/wiki/Darwin_Information_Typing_Architecture frightens me a bit (and remembers me how verbose is XML) We would need to convince the community it's the gith tool for OFBiz documentation... and more... Also I wonder if we simply don't know Docbook enough to be really able to compare them... What would be the cost of moving from DocBook to DITA in OFBiz? Is http://www.dita-ot.org/ of value? Found this by change https://doconv.readthedocs.org/en/latest/features.html With http://www.dita-ot.org/2.0/readme/dita2docbook.html this would allow to mix tools (I think we should go that way, but have a tool of reference in OFBiz, still to choose if we don't keep Docbook) Jacques Le 05/06/2015 16:13, Ron Wheeler a écrit : I have found another great reference for planning a DITA project in order to maximize the possibilities for reuse. http://www.stilo.com/article-dita-reuse-conversion-together/ It is useful reading if you want reverse engineer some ideas about where the big benefits will come from DITA. For example, it talks about creating a warehouse for conrefs where is recommends writing fragments conrefs that are included by name. It suggests that these should be used for * GUI objects, fields, buttons, icons * Frequently used steps, with step results and info * All your notes and warnings * Pre-requisites that are commonly mentioned, like having administrative privileges * Boilerplate - legal, copyright, notices, When you think about each of these as a multilingual fragment that can be called in by referencing a key, you can see that this a) reduces translation - translate the key once and every place it is referenced has the translation done b) improves consistency c) makes customization a lot simpler - if you have changed a field label or button label, you only have to change the conref once and it is changed in your documentation. There is also a discussion on using keys. If we define variables such as version numbers, it makes it easier to ensure that versions (Java, Tomcat, OFBiz, etc.) are consistent everywhere with a single variable to change. If URLs are keys, you only have to change one key when a web page or file moves. Keys can also be used to select or exclude content which will make it easier for System Integrators to prepare manuals related to different configurations - include or exclude e-commerce, control industry specific content, etc. It has specific ideas about how to plan and execute a conversion. Ron - Original Message - From: Ron Wheeler rwhee...@artifact-software.com To: dev dev@ofbiz.apache.org Sent: Thursday, 4 June, 2015 6:14:56 PM Subject: References for DITA as a tool for on-line help http://www.slideshare.net/abelsp/using-dita-for-online-help Slideshare has a lot of other presentations on DITA http://en.wikipedia.org/wiki/Darwin_Information_Typing_Architecture Short with Hello World example http://en.wikipedia.org/wiki/Online_help Alternatives for producing on-line help - DocBooks and DITA considered together since they are closely related http://www.ditawriter.com/sample-dita-produced-output/ Has links to actual documents produced from DITA sources. https://www.oasis-open.org/committees/download.php/30122/DHSC_BestPractices_November20_rdr.pdf exhaustive article on ways to deliver help authored by DITA tools. It shows that an investment in DITA content will always be protected even if the OFBiz UI and help delivery technology changes. Table of Contents *Introduction to the DITA Help Best Practices Guide* *Developing DITA-based Help for Existing Help Environments* -Arbortext Digital Media Publisher -Eclipse Help -CSHelp Plug-in -Eclipse_CSH Plug-in for Dynamic Context-Sensitive Help -Eclipse Help -Leximation AIR Help Plug-in -Microsoft HTMLHelp -Context-Sensitive Help using the Enhanced HTML (htmlhelp2) Plug-In -The DITA Open Toolkit HTMLHelp Transform *Developing Custom DITA-based Help Systems** *-DHTML Effects in HTML Generated from DITA -DITA-OT Plug-ins -HTMLSearch Plug-in -TOCJS and TOCJSBIS Plug-ins -Dynamic Rendering of DITA into XHTML -JavaScript-Based Context Sensitive Help -WinANT Options Supporting HTML-Based Output -WinANT Options Supporting Microsoft® HTML Help *Developing DITA-based Help for Existing Help Authoring Tools** *-Converting DITA Content to WebHelp using RoboHelp® There are a lot more articles on using DITA content in On-line help. The same content is available for other uses. Ron
[jira] [Commented] (OFBIZ-6463) ordermgr/control/deleteCustRequestParty should delete the record rather than updating the through date
[ https://issues.apache.org/jira/browse/OFBIZ-6463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14575973#comment-14575973 ] Jacques Le Roux commented on OFBIZ-6463: A well organised organisation should also always have at least a daily backup of at least essential data (the all DB for OFBiz). Without (at least) a daily backup you are sure to fail one day... ordermgr/control/deleteCustRequestParty should delete the record rather than updating the through date -- Key: OFBIZ-6463 URL: https://issues.apache.org/jira/browse/OFBIZ-6463 Project: OFBiz Issue Type: Improvement Components: order Affects Versions: Trunk Reporter: Christian Carlow Priority: Minor Fix For: Upcoming Branch Attachments: OFBIZ-6463.patch Users expect to be able to remove accidentally added faulty CustRequestParty but the current implementation only updates the through date when the delete button is clicked. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6362) Move js css references from CommonDecorator(s) to themes
[ https://issues.apache.org/jira/browse/OFBIZ-6362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-6362: Attachment: OFBIZ-6362-sunrise-theme.patch Adding the Bootstrap based Sunrise Theme as a patch file. Move js css references from CommonDecorator(s) to themes -- Key: OFBIZ-6362 URL: https://issues.apache.org/jira/browse/OFBIZ-6362 Project: OFBiz Issue Type: Sub-task Components: framework Affects Versions: Trunk, Upcoming Branch Reporter: Pierre Smits Assignee: Adrian Crum Priority: Minor Attachments: OFBIZ-6263-BlueLight-header.ftl.patch, OFBIZ-6362-BizznessTime-header.ftl.patch, OFBIZ-6362-BizznessTimeThemeData.xml.patch, OFBIZ-6362-BlueLightThemeData.xml.patch, OFBIZ-6362-CommonScreens.xml.patch, OFBIZ-6362-DroppingCrumbs-header.ftl.patch, OFBIZ-6362-DroppingCrumbsThemeData.xml.patch, OFBIZ-6362-FlatGrey-header.ftl.patch, OFBIZ-6362-FlatGreyThemeData.xml.patch, OFBIZ-6362-Tomahawk-header.ftl.patch, OFBIZ-6362-TomahawkThemeData.xml.patch, OFBIZ-6362-bbasic-theme.patch, OFBIZ-6362-sunrise-theme.patch, bbasic.zip, sunrise.zip -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6467) Disentangle themes
[ https://issues.apache.org/jira/browse/OFBIZ-6467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14575947#comment-14575947 ] Pierre Smits commented on OFBIZ-6467: - The disentanglement of the Bootstrap based Sunrise theme has been added to the OFBIZ-6362 issue. Disentangle themes -- Key: OFBIZ-6467 URL: https://issues.apache.org/jira/browse/OFBIZ-6467 Project: OFBiz Issue Type: Sub-task Components: themes Affects Versions: Bootstrap theme Reporter: Pierre Smits Assignee: Pierre Smits Currently in the branch the two bootstrap styles (Basic and yellow 'Sunrise) are entwined. The effect is that when changes are implemented in one theme they alter the user experience in the other theme. It would be better to disentangle the 2 styles into separate themes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6362) Move js css references from CommonDecorator(s) to themes
[ https://issues.apache.org/jira/browse/OFBIZ-6362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-6362: Attachment: bbasic.zip This zip file contains the Bootstrap based Basic theme that was developed as part of the Bootstrap theme through the OFBIZ-5840 issue. Move js css references from CommonDecorator(s) to themes -- Key: OFBIZ-6362 URL: https://issues.apache.org/jira/browse/OFBIZ-6362 Project: OFBiz Issue Type: Sub-task Components: framework Affects Versions: Trunk, Upcoming Branch Reporter: Pierre Smits Assignee: Adrian Crum Priority: Minor Attachments: OFBIZ-6263-BlueLight-header.ftl.patch, OFBIZ-6362-BizznessTime-header.ftl.patch, OFBIZ-6362-BizznessTimeThemeData.xml.patch, OFBIZ-6362-BlueLightThemeData.xml.patch, OFBIZ-6362-CommonScreens.xml.patch, OFBIZ-6362-DroppingCrumbs-header.ftl.patch, OFBIZ-6362-DroppingCrumbsThemeData.xml.patch, OFBIZ-6362-FlatGrey-header.ftl.patch, OFBIZ-6362-FlatGreyThemeData.xml.patch, OFBIZ-6362-Tomahawk-header.ftl.patch, OFBIZ-6362-TomahawkThemeData.xml.patch, bbasic.zip, sunrise.zip -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6467) Disentangle themes
[ https://issues.apache.org/jira/browse/OFBIZ-6467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14575988#comment-14575988 ] Pierre Smits commented on OFBIZ-6467: - The disentanglement of the Bootstrap based Basic theme has been added to the OFBIZ-6362 issue. Disentangle themes -- Key: OFBIZ-6467 URL: https://issues.apache.org/jira/browse/OFBIZ-6467 Project: OFBiz Issue Type: Sub-task Components: themes Affects Versions: Bootstrap theme Reporter: Pierre Smits Assignee: Pierre Smits Currently in the branch the two bootstrap styles (Basic and yellow 'Sunrise) are entwined. The effect is that when changes are implemented in one theme they alter the user experience in the other theme. It would be better to disentangle the 2 styles into separate themes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6462) Redesign ordermgr/control/EditQuoteRole to resemble ordermgr/control/requestroles
[ https://issues.apache.org/jira/browse/OFBIZ-6462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Carlow updated OFBIZ-6462: Summary: Redesign ordermgr/control/EditQuoteRole to resemble ordermgr/control/requestroles (was: Redisign ordermgr/control/EditQuoteRole to resemble ordermgr/control/requestroles) Redesign ordermgr/control/EditQuoteRole to resemble ordermgr/control/requestroles - Key: OFBIZ-6462 URL: https://issues.apache.org/jira/browse/OFBIZ-6462 Project: OFBiz Issue Type: Improvement Components: order Affects Versions: Trunk Reporter: Christian Carlow Priority: Minor The quote role form requires the create button to unnecessarily be clicked before a new quote can be created and all roles are included in the dropdown rather than those only relevant for the quote. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6463) ordermgr/control/deleteCustRequestParty should delete the record rather than updating the through date
[ https://issues.apache.org/jira/browse/OFBIZ-6463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14575943#comment-14575943 ] Christian Carlow commented on OFBIZ-6463: - Hey Pierre, So the delete button and service should be removed? Should that be created as a separate issue? ordermgr/control/deleteCustRequestParty should delete the record rather than updating the through date -- Key: OFBIZ-6463 URL: https://issues.apache.org/jira/browse/OFBIZ-6463 Project: OFBiz Issue Type: Improvement Components: order Affects Versions: Trunk Reporter: Christian Carlow Priority: Minor Fix For: Upcoming Branch Attachments: OFBIZ-6463.patch Users expect to be able to remove accidentally added faulty CustRequestParty but the current implementation only updates the through date when the delete button is clicked. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6463) ordermgr/control/deleteCustRequestParty should delete the record rather than updating the through date
[ https://issues.apache.org/jira/browse/OFBIZ-6463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14575946#comment-14575946 ] Christian Carlow commented on OFBIZ-6463: - Also Pierre, QuoteRoles allows for delete and hasn't been replaced by an entity such as QuoteParty to allow for expiry so it also breaks the GRC protocols you mentioned. ordermgr/control/deleteCustRequestParty should delete the record rather than updating the through date -- Key: OFBIZ-6463 URL: https://issues.apache.org/jira/browse/OFBIZ-6463 Project: OFBiz Issue Type: Improvement Components: order Affects Versions: Trunk Reporter: Christian Carlow Priority: Minor Fix For: Upcoming Branch Attachments: OFBIZ-6463.patch Users expect to be able to remove accidentally added faulty CustRequestParty but the current implementation only updates the through date when the delete button is clicked. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6362) Move js css references from CommonDecorator(s) to themes
[ https://issues.apache.org/jira/browse/OFBIZ-6362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-6362: Attachment: sunrise.zip This zip file contains the Bootstrap based Sunrise theme that was developed as part of the Bootstrap theme through the OFBIZ-5840 issue. Move js css references from CommonDecorator(s) to themes -- Key: OFBIZ-6362 URL: https://issues.apache.org/jira/browse/OFBIZ-6362 Project: OFBiz Issue Type: Sub-task Components: framework Affects Versions: Trunk, Upcoming Branch Reporter: Pierre Smits Assignee: Adrian Crum Priority: Minor Attachments: OFBIZ-6263-BlueLight-header.ftl.patch, OFBIZ-6362-BizznessTime-header.ftl.patch, OFBIZ-6362-BizznessTimeThemeData.xml.patch, OFBIZ-6362-BlueLightThemeData.xml.patch, OFBIZ-6362-CommonScreens.xml.patch, OFBIZ-6362-DroppingCrumbs-header.ftl.patch, OFBIZ-6362-DroppingCrumbsThemeData.xml.patch, OFBIZ-6362-FlatGrey-header.ftl.patch, OFBIZ-6362-FlatGreyThemeData.xml.patch, OFBIZ-6362-Tomahawk-header.ftl.patch, OFBIZ-6362-TomahawkThemeData.xml.patch, sunrise.zip -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6463) ordermgr/control/deleteCustRequestParty should delete the record rather than updating the through date
[ https://issues.apache.org/jira/browse/OFBIZ-6463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14575956#comment-14575956 ] Christian Carlow commented on OFBIZ-6463: - Awesome. Thanks Pierre I'll follow OFBIZ-5959 for future role development. ordermgr/control/deleteCustRequestParty should delete the record rather than updating the through date -- Key: OFBIZ-6463 URL: https://issues.apache.org/jira/browse/OFBIZ-6463 Project: OFBiz Issue Type: Improvement Components: order Affects Versions: Trunk Reporter: Christian Carlow Priority: Minor Fix For: Upcoming Branch Attachments: OFBIZ-6463.patch Users expect to be able to remove accidentally added faulty CustRequestParty but the current implementation only updates the through date when the delete button is clicked. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6450) Docbook and OFBIz Online Help
[ https://issues.apache.org/jira/browse/OFBIZ-6450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14575969#comment-14575969 ] Jacques Le Roux commented on OFBIZ-6450: It also maybe explains why people prefer DITA for online helps and Docbook for books (as its name suggests;)) Docbook and OFBIz Online Help - Key: OFBIZ-6450 URL: https://issues.apache.org/jira/browse/OFBIZ-6450 Project: OFBiz Issue Type: Bug Reporter: Sharan Foga Jira created based on the steps suggested by Taher as follows: - First, we attempt to fix whatever is wrong in DocBook at the moment. If you can share exactly what you spotted then this would save us a lot of time in trying to dig to the problem. So a repeat process to identify the bugs from you would be great. - Second, we decide on a category structure for the sections of the documentation if we do not like the existing one - We also introduce or enforce a workflow that mandates an update of the documentation on each JIRA that affects functionality that requires documentation. For example, if we add or modify a screen in the party component, then we must provide the documentation for that screen before closing the JIRA for example. - As a last step we decide on the appropriate technology to move forward. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (OFBIZ-6324) Have clickable 'Applications' present the drop-down menu of applications
[ https://issues.apache.org/jira/browse/OFBIZ-6324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits resolved OFBIZ-6324. - Resolution: Done Closing this issue as resolved. See the Bootstrap Basic Theme attached as zip in OFBIZ-6362. Have clickable 'Applications' present the drop-down menu of applications Key: OFBIZ-6324 URL: https://issues.apache.org/jira/browse/OFBIZ-6324 Project: OFBiz Issue Type: Sub-task Affects Versions: Bootstrap theme Reporter: Pierre Smits Assignee: Pierre Smits Currently, when using the boot-strap theme the user has to click on the + symbol beside the clickable 'Applications' to get the drop-down menu of available applications. And the 'Applications' clickable doesn't do anything. However, it would deliver a better user experience when the drop-down menu is presented when the user clicks the 'Applications' clickable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6362) Move js css references from CommonDecorator(s) to themes
[ https://issues.apache.org/jira/browse/OFBIZ-6362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-6362: Attachment: OFBIZ-6362-bbasic-theme.patch Adding the Bootstrap Basic Theme as a patch file. Move js css references from CommonDecorator(s) to themes -- Key: OFBIZ-6362 URL: https://issues.apache.org/jira/browse/OFBIZ-6362 Project: OFBiz Issue Type: Sub-task Components: framework Affects Versions: Trunk, Upcoming Branch Reporter: Pierre Smits Assignee: Adrian Crum Priority: Minor Attachments: OFBIZ-6263-BlueLight-header.ftl.patch, OFBIZ-6362-BizznessTime-header.ftl.patch, OFBIZ-6362-BizznessTimeThemeData.xml.patch, OFBIZ-6362-BlueLightThemeData.xml.patch, OFBIZ-6362-CommonScreens.xml.patch, OFBIZ-6362-DroppingCrumbs-header.ftl.patch, OFBIZ-6362-DroppingCrumbsThemeData.xml.patch, OFBIZ-6362-FlatGrey-header.ftl.patch, OFBIZ-6362-FlatGreyThemeData.xml.patch, OFBIZ-6362-Tomahawk-header.ftl.patch, OFBIZ-6362-TomahawkThemeData.xml.patch, OFBIZ-6362-bbasic-theme.patch, bbasic.zip, sunrise.zip -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-6467) Disentangle themes
[ https://issues.apache.org/jira/browse/OFBIZ-6467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits closed OFBIZ-6467. --- Resolution: Done Disentangle themes -- Key: OFBIZ-6467 URL: https://issues.apache.org/jira/browse/OFBIZ-6467 Project: OFBiz Issue Type: Sub-task Components: themes Affects Versions: Bootstrap theme Reporter: Pierre Smits Assignee: Pierre Smits Currently in the branch the two bootstrap styles (Basic and yellow 'Sunrise) are entwined. The effect is that when changes are implemented in one theme they alter the user experience in the other theme. It would be better to disentangle the 2 styles into separate themes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6463) ordermgr/control/deleteCustRequestParty should delete the record rather than updating the through date
[ https://issues.apache.org/jira/browse/OFBIZ-6463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14575953#comment-14575953 ] Pierre Smits commented on OFBIZ-6463: - I have created a placeholder issue regarding the improvement of the various roles and their associated functions in relation to their lifespan aspects. See OFBIZ-5959 ordermgr/control/deleteCustRequestParty should delete the record rather than updating the through date -- Key: OFBIZ-6463 URL: https://issues.apache.org/jira/browse/OFBIZ-6463 Project: OFBiz Issue Type: Improvement Components: order Affects Versions: Trunk Reporter: Christian Carlow Priority: Minor Fix For: Upcoming Branch Attachments: OFBIZ-6463.patch Users expect to be able to remove accidentally added faulty CustRequestParty but the current implementation only updates the through date when the delete button is clicked. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Possible Documentation and help solutions - DITA
Le 06/06/2015 08:10, Paul Foxworthy a écrit : Sharan-F wrote I'm a bit unclear about what you are suggesting. * Is it about replacing the Docbook implementation we currently have within OFBiz with something else (e.g Asciidoc)? * Is it about extracting the Docbook content from what we currently have in OFBiz and then generating it into another format that we could possibly re-introduce? * Or is it something else? Hi Sharan, My suggestion is much more modest than that. I think there's no need to replace existing DocBook content, or to totally change the DocBook process we have. All I am suggesting is that people consider AsciiDoc as a first step when authoring help information. If they prefer to work with DocBook directly, fine. There are tools to transform AsciDoc into DocBook XML, such as AsciiDoctor (http://asciidoctor.org/), so in effect (correctly written) AsciiDoc *is* DocBook. I'll repeat the reasons why I like AsciiDoc. It's more human-readable than XML. You can write your documentation in any text editor. Both of these are important. In contrast, requiring XML and some more specialised tool is a barrier to entry, so less people could and would participate in documenting OFBiz. That's exactly the point indeed, thanks to stress that Paul. When I last looked into DITA quite a few years ago, it seemed to be a heavyweight thing that only made sense if you wanted multiple destinations This seems to answer to my question just asked to Ron on the user ML. So you think Docbook (more aimed to create book when DITA is more of online help kind, I read) or AsciiDoc are not able to OOTB deliver in this way? and were willing to invest in proprietary tools like Framemaker, Oxygen or Arbortext. I am perfectly willing to believe that DITA is more complete than DocBook, and would allow better documentation, if only anyone was willing to invest the time, trouble and money to be able to use it. I'm pleased to hear there's now DITA support for Eclipse. Eclipse is not my favourite IDE, but I could be persuaded to use it. How much better would it be to say to potential contributors that they can use their favourite IDE or text editor, whatever that is? If everybody else loves DITA, I would work with it. But I worry that it will put many people off. That's the point we need to clarify... Jacques Thanks Paul Foxworthy - -- Coherent Software Australia Pty Ltd http://www.coherentsoftware.com.au/ Bonsai ERP, the all-inclusive ERP system http://www.bonsaierp.com.au/ -- View this message in context: http://ofbiz.135035.n4.nabble.com/Possible-Documentation-and-help-solutions-DITA-tp4669377p4669576.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.
Re: Possible Documentation and help solutions - DITA
Thanks Taher, Let's see... Jacques Le 06/06/2015 11:19, Taher Alkhateeb a écrit : Hi Paul, I am starting to use DITA and really like it. But I can see your point regarding people being put off. It might be in a sense a bit too powerful for OFBiz and it takes a while to wrap your head around the concepts like maps, topics, etc ... I'm on the fence, maybe leaning slightly towards keeping DocBook, but if a PoC shows how DITA can shine, then why not! Taher Alkhateeb - Original Message - From: Paul Foxworthy p...@cohsoft.com.a Pau To: dev@ofbiz.apache.org Sent: Saturday, 6 June, 2015 9:10:28 AM Subject: Re: Possible Documentation and help solutions - DITA Sharan-F wrote I'm a bit unclear about what you are suggesting. * Is it about replacing the Docbook implementation we currently have within OFBiz with something else (e.g Asciidoc)? * Is it about extracting the Docbook content from what we currently have in OFBiz and then generating it into another format that we could possibly re-introduce? * Or is it something else? Hi Sharan, My suggestion is much more modest than that. I think there's no need to replace existing DocBook content, or to totally change the DocBook process we have. All I am suggesting is that people consider AsciiDoc as a first step when authoring help information. If they prefer to work with DocBook directly, fine. There are tools to transform AsciDoc into DocBook XML, such as AsciiDoctor (http://asciidoctor.org/), so in effect (correctly written) AsciiDoc *is* DocBook. I'll repeat the reasons why I like AsciiDoc. It's more human-readable than XML. You can write your documentation in any text editor. Both of these are important. In contrast, requiring XML and some more specialised tool is a barrier to entry, so less people could and would participate in documenting OFBiz. When I last looked into DITA quite a few years ago, it seemed to be a heavyweight thing that only made sense if you wanted multiple destinations and were willing to invest in proprietary tools like Framemaker, Oxygen or Arbortext. I am perfectly willing to believe that DITA is more complete than DocBook, and would allow better documentation, if only anyone was willing to invest the time, trouble and money to be able to use it. I'm pleased to hear there's now DITA support for Eclipse. Eclipse is not my favourite IDE, but I could be persuaded to use it. How much better would it be to say to potential contributors that they can use their favourite IDE or text editor, whatever that is? If everybody else loves DITA, I would work with it. But I worry that it will put many people off. Thanks Paul Foxworthy -
Re: References for DITA as a tool for on-line help
Le 06/06/2015 23:33, Jacques Le Roux a écrit : OK DITA seems powerful but not an easy tool to work with (not only because of XML verbosity but also tags and concepts to learn) Sincerely the examples in http://fr.wikipedia.org/wiki/Darwin_Information_Typing_Architecture frightens me a bit (and remembers me how verbose is XML) We would need to convince the community it's the gith tool for OFBiz documentation... and more... Also I wonder if we simply don't know Docbook enough to be really able to compare them... What would be the cost of moving from DocBook to DITA in OFBiz? Is http://www.dita-ot.org/ of value? Found this by change https://doconv.readthedocs.org/en/latest/features.html With http://www.dita-ot.org/2.0/readme/dita2docbook.html this would allow to mix tools (I think we should go that way, but have a tool of reference in OFBiz, still to choose if we don't keep Docbook) Actually the question is how much these converters are reliable... Only a POC can demonstrate... Jacques Jacques Le 05/06/2015 16:13, Ron Wheeler a écrit : I have found another great reference for planning a DITA project in order to maximize the possibilities for reuse. http://www.stilo.com/article-dita-reuse-conversion-together/ It is useful reading if you want reverse engineer some ideas about where the big benefits will come from DITA. For example, it talks about creating a warehouse for conrefs where is recommends writing fragments conrefs that are included by name. It suggests that these should be used for * GUI objects, fields, buttons, icons * Frequently used steps, with step results and info * All your notes and warnings * Pre-requisites that are commonly mentioned, like having administrative privileges * Boilerplate - legal, copyright, notices, When you think about each of these as a multilingual fragment that can be called in by referencing a key, you can see that this a) reduces translation - translate the key once and every place it is referenced has the translation done b) improves consistency c) makes customization a lot simpler - if you have changed a field label or button label, you only have to change the conref once and it is changed in your documentation. There is also a discussion on using keys. If we define variables such as version numbers, it makes it easier to ensure that versions (Java, Tomcat, OFBiz, etc.) are consistent everywhere with a single variable to change. If URLs are keys, you only have to change one key when a web page or file moves. Keys can also be used to select or exclude content which will make it easier for System Integrators to prepare manuals related to different configurations - include or exclude e-commerce, control industry specific content, etc. It has specific ideas about how to plan and execute a conversion. Ron - Original Message - From: Ron Wheeler rwhee...@artifact-software.com To: dev dev@ofbiz.apache.org Sent: Thursday, 4 June, 2015 6:14:56 PM Subject: References for DITA as a tool for on-line help http://www.slideshare.net/abelsp/using-dita-for-online-help Slideshare has a lot of other presentations on DITA http://en.wikipedia.org/wiki/Darwin_Information_Typing_Architecture Short with Hello World example http://en.wikipedia.org/wiki/Online_help Alternatives for producing on-line help - DocBooks and DITA considered together since they are closely related http://www.ditawriter.com/sample-dita-produced-output/ Has links to actual documents produced from DITA sources. https://www.oasis-open.org/committees/download.php/30122/DHSC_BestPractices_November20_rdr.pdf exhaustive article on ways to deliver help authored by DITA tools. It shows that an investment in DITA content will always be protected even if the OFBiz UI and help delivery technology changes. Table of Contents *Introduction to the DITA Help Best Practices Guide* *Developing DITA-based Help for Existing Help Environments* -Arbortext Digital Media Publisher -Eclipse Help -CSHelp Plug-in -Eclipse_CSH Plug-in for Dynamic Context-Sensitive Help -Eclipse Help -Leximation AIR Help Plug-in -Microsoft HTMLHelp -Context-Sensitive Help using the Enhanced HTML (htmlhelp2) Plug-In -The DITA Open Toolkit HTMLHelp Transform *Developing Custom DITA-based Help Systems** *-DHTML Effects in HTML Generated from DITA -DITA-OT Plug-ins -HTMLSearch Plug-in -TOCJS and TOCJSBIS Plug-ins -Dynamic Rendering of DITA into XHTML -JavaScript-Based Context Sensitive Help -WinANT Options Supporting HTML-Based Output -WinANT Options Supporting Microsoft® HTML Help *Developing DITA-based Help for Existing Help Authoring Tools** *-Converting DITA Content to WebHelp using RoboHelp® There are a lot more articles on using DITA content in On-line help. The same content is available for other uses. Ron
[jira] [Commented] (OFBIZ-6444) Postal Address PDF Formatter Screen Problems
[ https://issues.apache.org/jira/browse/OFBIZ-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14575967#comment-14575967 ] Jacques Le Roux commented on OFBIZ-6444: Thanks, I will double-chech tomorrow, sounds good so far :) Postal Address PDF Formatter Screen Problems Key: OFBIZ-6444 URL: https://issues.apache.org/jira/browse/OFBIZ-6444 Project: OFBiz Issue Type: Bug Components: party Affects Versions: Release Branch 12.04, Release Branch 13.07, Release Branch 14.12, Trunk Reporter: Forrest Rae Attachments: OFBIZ-6444.patch A couple updates are needed to the postalAddressPdfFormatter screen: First, the screen template is set to use the HTML renderer which results in this error in the log: [java] 2015-06-03 13:44:53,400 |0.0.0.0-8009-exec-13 |ModelScreenWidget |W| In platform-dependent could not find template for xsl-fo, using the one for html. Second, the various PostalAddress.fo.ftl files do not escape XML properly, and addresses with an in them end up causing a FreeMarker template error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6456) Make auto-fields-entity sort by field type by default
[ https://issues.apache.org/jira/browse/OFBIZ-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14575970#comment-14575970 ] Jacques Le Roux commented on OFBIZ-6456: +1 Make auto-fields-entity sort by field type by default --- Key: OFBIZ-6456 URL: https://issues.apache.org/jira/browse/OFBIZ-6456 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Christian Carlow Attachments: OFBIZ-6469_2.patch IMO, form widgets are generally easier to interpret when the field types are sorted by type but this has to be done manually using sort-order. I propose improving auto-fields-entity to sort fields by type by default such as text, then dates, then numbers, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (OFBIZ-6324) Have clickable 'Applications' present the drop-down menu of applications
[ https://issues.apache.org/jira/browse/OFBIZ-6324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits reassigned OFBIZ-6324: --- Assignee: Pierre Smits (was: Julien NICOLAS) Have clickable 'Applications' present the drop-down menu of applications Key: OFBIZ-6324 URL: https://issues.apache.org/jira/browse/OFBIZ-6324 Project: OFBiz Issue Type: Sub-task Affects Versions: Bootstrap theme Reporter: Pierre Smits Assignee: Pierre Smits Currently, when using the boot-strap theme the user has to click on the + symbol beside the clickable 'Applications' to get the drop-down menu of available applications. And the 'Applications' clickable doesn't do anything. However, it would deliver a better user experience when the drop-down menu is presented when the user clicks the 'Applications' clickable. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6462) Redesign ordermgr/control/EditQuoteRole to resemble ordermgr/control/requestroles
[ https://issues.apache.org/jira/browse/OFBIZ-6462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Carlow updated OFBIZ-6462: Attachment: OFBIZ-6462_2.patch This patch replaces QuoteRole with QuoteParty as was done for CustRequestRole with CustRequestParty. QuoteRole was moved to order/entitydef/entitymodel_old.xml as OldQuoteRole. The roleTypeId dropdown was limited to the same options as available for cust requests instead of displaying all roles. The copy quote, create order from quote services, and ecommerce app were also changed to handle the new entity. The upgrade service migrateQuoteRole has not been created yet. Does it need to be included before the patch can be applied and the issue closed or can it be handled by another issue? Redesign ordermgr/control/EditQuoteRole to resemble ordermgr/control/requestroles - Key: OFBIZ-6462 URL: https://issues.apache.org/jira/browse/OFBIZ-6462 Project: OFBiz Issue Type: Improvement Components: order Affects Versions: Trunk Reporter: Christian Carlow Priority: Minor Attachments: OFBIZ-6462_2.patch The quote role form requires the create button to unnecessarily be clicked before a new quote can be created and all roles are included in the dropdown rather than those only relevant for the quote. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6456) Make auto-fields-entity sort by field type by default
[ https://issues.apache.org/jira/browse/OFBIZ-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Carlow updated OFBIZ-6456: Attachment: OFBIZ-6469_2.patch Patch OFBIZ_6469_2.patch refactors the original patches that were submitted for this issue so that the same default field sequence sort functionality is handled for both auto-fields-entity and auto-fields-service Make auto-fields-entity sort by field type by default --- Key: OFBIZ-6456 URL: https://issues.apache.org/jira/browse/OFBIZ-6456 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Christian Carlow Attachments: OFBIZ-6469_2.patch IMO, form widgets are generally easier to interpret when the field types are sorted by type but this has to be done manually using sort-order. I propose improving auto-fields-entity to sort fields by type by default such as text, then dates, then numbers, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6456) Make auto-fields-entity sort by field type by default
[ https://issues.apache.org/jira/browse/OFBIZ-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14575884#comment-14575884 ] Christian Carlow commented on OFBIZ-6456: - Thanks for the review Adrian. This issue was primarily created to make find forms appear cleaner but it does effect input fields as well. I thought it would be easier for users to interpret forms if they saw types such as date fields grouped together in the same area instead of spread out throughout the form in whatever order they were defined in entitymodel. I'm trying to automate the cleanup of various forms that employ auto-fields-entity and auto-fields-service that otherwise require using sort-order or changing the order in which fields are defined in model entity which could require a lot of work. I see your point about most relevant fields appearing first speeding up data entry. Many entities have typeId fields which are typically the second most important fields but my code would render them at the end since they are commonly rendered as dropdowns. I'll probably close the issue for now as won't fix. If ever needed I suppose it could be activated globally with a setting or with an attribute extension for auto-fields-entity or auto-fields-service. Make auto-fields-entity sort by field type by default --- Key: OFBIZ-6456 URL: https://issues.apache.org/jira/browse/OFBIZ-6456 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Christian Carlow Attachments: OFBIZ-6469_2.patch IMO, form widgets are generally easier to interpret when the field types are sorted by type but this has to be done manually using sort-order. I propose improving auto-fields-entity to sort fields by type by default such as text, then dates, then numbers, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-6469) Make auto-fields-service sort by field type by default
[ https://issues.apache.org/jira/browse/OFBIZ-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Carlow closed OFBIZ-6469. --- Resolution: Won't Fix Make auto-fields-service sort by field type by default Key: OFBIZ-6469 URL: https://issues.apache.org/jira/browse/OFBIZ-6469 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Christian Carlow Attachments: OFBIZ-6469_2.patch auto-fields-service should sort fields by type by default as will be done for auto-fields-entity of OFBIZ-6456. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-6468) Add support for ModelFormField.type tracking from ModelFormFieldBuilder
[ https://issues.apache.org/jira/browse/OFBIZ-6468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Carlow closed OFBIZ-6468. --- Resolution: Won't Fix Closing because dependent issues are being closed as won't fix so no longer necessary. Add support for ModelFormField.type tracking from ModelFormFieldBuilder --- Key: OFBIZ-6468 URL: https://issues.apache.org/jira/browse/OFBIZ-6468 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Christian Carlow Priority: Minor Attachments: OFBIZ-6468_2.patch This could be done by adding ModelFormFieldBuilder.modelField as new member for tracking the entire ModelField object or if thats overkill adding ModelFormFieldBuilder.modelFieldType for just the type. This functionality would provide a way for OFBIZ-6456 to ignore the default field sequence sort for id type fields that are hyperlinks which typically appear as beginning fields. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-6456) Make auto-fields-entity sort by field type by default
[ https://issues.apache.org/jira/browse/OFBIZ-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Carlow closed OFBIZ-6456. --- Resolution: Won't Fix Make auto-fields-entity sort by field type by default --- Key: OFBIZ-6456 URL: https://issues.apache.org/jira/browse/OFBIZ-6456 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Christian Carlow Attachments: OFBIZ-6469_2.patch IMO, form widgets are generally easier to interpret when the field types are sorted by type but this has to be done manually using sort-order. I propose improving auto-fields-entity to sort fields by type by default such as text, then dates, then numbers, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6456) Make auto-fields-entity sort by field type by default
[ https://issues.apache.org/jira/browse/OFBIZ-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Carlow updated OFBIZ-6456: Attachment: (was: OFBIZ-6456_3.patch) Make auto-fields-entity sort by field type by default --- Key: OFBIZ-6456 URL: https://issues.apache.org/jira/browse/OFBIZ-6456 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Christian Carlow IMO, form widgets are generally easier to interpret when the field types are sorted by type but this has to be done manually using sort-order. I propose improving auto-fields-entity to sort fields by type by default such as text, then dates, then numbers, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6469) Make auto-fields-service sort by field type by default
[ https://issues.apache.org/jira/browse/OFBIZ-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14575865#comment-14575865 ] Christian Carlow commented on OFBIZ-6469: - This issue depends on OFBIZ-6468 to provide the way for ModelFormFieldBuilder to determine the original ModelField.type. Make auto-fields-service sort by field type by default Key: OFBIZ-6469 URL: https://issues.apache.org/jira/browse/OFBIZ-6469 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Christian Carlow Attachments: OFBIZ-6469_2.patch auto-fields-service should sort fields by type by default as will be done for auto-fields-entity of OFBIZ-6456. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-6469) Make auto-fields-service sort by field type by default
Christian Carlow created OFBIZ-6469: --- Summary: Make auto-fields-service sort by field type by default Key: OFBIZ-6469 URL: https://issues.apache.org/jira/browse/OFBIZ-6469 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Christian Carlow auto-fields-service should sort fields by type by default as will be done for auto-fields-entity of OFBIZ-6456. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6469) Make auto-fields-service sort by field type by default
[ https://issues.apache.org/jira/browse/OFBIZ-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Carlow updated OFBIZ-6469: Summary: Make auto-fields-service sort by field type by default (was: Make auto-fields-service sort by field type by default) Make auto-fields-service sort by field type by default Key: OFBIZ-6469 URL: https://issues.apache.org/jira/browse/OFBIZ-6469 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Christian Carlow auto-fields-service should sort fields by type by default as will be done for auto-fields-entity of OFBIZ-6456. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6468) Add support for ModelFormField.type tracking from ModelFormFieldBuilder
[ https://issues.apache.org/jira/browse/OFBIZ-6468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adrian Crum updated OFBIZ-6468: --- Summary: Add support for ModelFormField.type tracking from ModelFormFieldBuilder (was: Add support for ModelForm.type tracking from ModelFormFieldBuilder) Add support for ModelFormField.type tracking from ModelFormFieldBuilder --- Key: OFBIZ-6468 URL: https://issues.apache.org/jira/browse/OFBIZ-6468 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Christian Carlow Priority: Minor Attachments: OFBIZ-6468_2.patch This could be done by adding ModelFormFieldBuilder.modelField as new member for tracking the entire ModelField object or if thats overkill adding ModelFormFieldBuilder.modelFieldType for just the type. This functionality would provide a way for OFBIZ-6456 to ignore the default field sequence sort for id type fields that are hyperlinks which typically appear as beginning fields. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-6456) Make auto-fields-entity sort by field type by default
[ https://issues.apache.org/jira/browse/OFBIZ-6456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14575857#comment-14575857 ] Adrian Crum commented on OFBIZ-6456: I don't agree that sorting input fields by type is easier to interpret. From my perspective, fields that are most relevant should appear first, followed by fields that are less relevant, and then fields that are least relevant should appear last. That approach allows a user to enter only relevant data, and then skip the rest of the form. Make auto-fields-entity sort by field type by default --- Key: OFBIZ-6456 URL: https://issues.apache.org/jira/browse/OFBIZ-6456 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Christian Carlow Attachments: OFBIZ-6456_3.patch IMO, form widgets are generally easier to interpret when the field types are sorted by type but this has to be done manually using sort-order. I propose improving auto-fields-entity to sort fields by type by default such as text, then dates, then numbers, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6469) Make auto-fields-service sort by field type by default
[ https://issues.apache.org/jira/browse/OFBIZ-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Carlow updated OFBIZ-6469: Attachment: OFBIZ-6469_2.patch This patch refactors OFBIZ-6456 so that the default field sequence sort functionality is handled by both auto-fields-entity and auto-fields-service. Make auto-fields-service sort by field type by default Key: OFBIZ-6469 URL: https://issues.apache.org/jira/browse/OFBIZ-6469 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Trunk Reporter: Christian Carlow Attachments: OFBIZ-6469_2.patch auto-fields-service should sort fields by type by default as will be done for auto-fields-entity of OFBIZ-6456. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
