Re: Widget or not Widget? [Was Re: Addons for OFBiz]
Several issues have been registered recently to migrate specific ftl functions to widgets. And patches have been attached. These just need a review and get committed. Yes, the use of ftl functionality is overwhelming. Even when it is not needed at all. E.g. defining standard screenlet functionality. And, for sure, it was the best (easiest?) choice for the contributor at the moment of creation to get to the desired solution (think functionality and/or time constraints). Like widgets, the ftl functions serve a purpose. It is not either widgets or ftl, but and widgets and ftl. But both techs should be applied wisely and not mere for convenience sake. When talking about moving from ftl to widgets (where possible), it all starts with registering the improvement issue in JIRA. 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 Thu, May 14, 2015 at 1:22 PM, Gavin Mabie kwikst...@gmail.com wrote: Hi Community I have not been able to continue the work on the bootstrap theme for the past few months now and therefore resisted the urge to comment on various threads in the mailing list about matters related. So maybe apologies are in order. Having said that, these are my thoughts: 1. The UI, specifically HTML is as important as any other part of the framework and should consequently be treated as such by the community. 2. Many projects with lesser architectural soundness but with sexy UIs' have proven successful purely based on the UI. The Ofbiz architectural framework rocks, but it not enough has been done to project this graphically. The look and feel of the ecommerce app has not been upgraded for more than half a decade now. This may be the reason why some are looking towards integrating with other ecommerce projects. The Ofbiz ecommerce app isn't bad - the demo just looks bad. 3. Graphical designers can easily write their own UI, as alluded to by Adrian. This regardless of the Javascript framework you would like to use. You can write your own widget templates and incorporate that in your theme. It's possible. 4. The elephant in the room is the significant amount of raw ftl widgets present in the current demos. This is where I got stuck with the bootstrap development. We cannot move the theme forward without dealing with raw ftl. I suspect that the same might be true for any other J'S framework. Any volunteers? 5. Following on the previous point, developing a UI based on vogue JS frameworks will be extremely difficult if we are concerned about breaking older themes. Maybe it is time for a clean break. So, this is my proposal: 1. Let's bodly adopt bootstrap. If there are any proponents of any other framework, let them bring it forward so we can all discuss and work on it. 2. Put aside a sprint event to deal with raw ftls scattered all over and get these converted into properly defined widgets. 3. Produce a more sexy ecommerce UI (this is critical to the Ofbiz brand). There are other issues - but this I feel should be prioritised. Regards Gavin On 14 May 2015 12:20 PM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: Below are some, but this question is more to shake things a bit and know what people think I think everybody will agree that the Entity Engine is the gem of this project, follows the Service Engine. I believe, though less polished, the widgets are 3rnd, but that's only my opinion and I'd really like to know others Jacques Le 14/05/2015 10:45, Pierre Smits a écrit : But what are the proposals? Where can these be found? 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 Thu, May 14, 2015 at 9:14 AM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: Actually maybe I'm misunderstanding you and I also want to clarify with everybody. I will try to be brief and right to the point! Do you (we) want to replace the widgets by something like Ean and Anil proposed many times, or do we want to improve them using these new tools? Jacques Le 13/05/2015 22:15, Julien NICOLAS a écrit : Le 13/05/2015 16:35, Jacques Le Roux a écrit : Le 13/05/2015 15:04, Julien NICOLAS a écrit : Hello Pierre, Le 13/05/2015 12:35, Pierre Smits a écrit : For what it is worth, the BOOTSTRAP_theme dev branch is a other way to enhance the user experience. Unfortunately the work is not done yet. The problem is that the GUI is a demo GUI. Then all the time you spend to solve all GUI problems, will potentially lost because nobody use it (and when I say that I think in particular to the order screen that is a nightmare...). It's better that OFBiz embedded GUI web framework (like bootstrap but not only, it can be
[jira] [Created] (OFBIZ-6363) Upload of PartyContent produces an error.
Pierre Smits created OFBIZ-6363: --- Summary: Upload of PartyContent produces an error. Key: OFBIZ-6363 URL: https://issues.apache.org/jira/browse/OFBIZ-6363 Project: OFBiz Issue Type: Bug Components: content, party Affects Versions: Trunk Reporter: Pierre Smits When uploading content in a party profile, the selected file doesn't get uploaded, in stead an error is produced. -- 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 ] Adrian Crum updated OFBIZ-6362: --- Priority: Minor (was: Major) Affects Version/s: Upcoming Branch 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: Pierre Smits 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-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 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Widget or not Widget? [Was Re: Addons for OFBiz]
Thanks both for clarifying, exactly my thoughts, happy we are on the same page :) More (different) opinions? Jacques Le 14/05/2015 13:53, Pierre Smits a écrit : Several issues have been registered recently to migrate specific ftl functions to widgets. And patches have been attached. These just need a review and get committed. Yes, the use of ftl functionality is overwhelming. Even when it is not needed at all. E.g. defining standard screenlet functionality. And, for sure, it was the best (easiest?) choice for the contributor at the moment of creation to get to the desired solution (think functionality and/or time constraints). Like widgets, the ftl functions serve a purpose. It is not either widgets or ftl, but and widgets and ftl. But both techs should be applied wisely and not mere for convenience sake. When talking about moving from ftl to widgets (where possible), it all starts with registering the improvement issue in JIRA. 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 Thu, May 14, 2015 at 1:22 PM, Gavin Mabie kwikst...@gmail.com wrote: Hi Community I have not been able to continue the work on the bootstrap theme for the past few months now and therefore resisted the urge to comment on various threads in the mailing list about matters related. So maybe apologies are in order. Having said that, these are my thoughts: 1. The UI, specifically HTML is as important as any other part of the framework and should consequently be treated as such by the community. 2. Many projects with lesser architectural soundness but with sexy UIs' have proven successful purely based on the UI. The Ofbiz architectural framework rocks, but it not enough has been done to project this graphically. The look and feel of the ecommerce app has not been upgraded for more than half a decade now. This may be the reason why some are looking towards integrating with other ecommerce projects. The Ofbiz ecommerce app isn't bad - the demo just looks bad. 3. Graphical designers can easily write their own UI, as alluded to by Adrian. This regardless of the Javascript framework you would like to use. You can write your own widget templates and incorporate that in your theme. It's possible. 4. The elephant in the room is the significant amount of raw ftl widgets present in the current demos. This is where I got stuck with the bootstrap development. We cannot move the theme forward without dealing with raw ftl. I suspect that the same might be true for any other J'S framework. Any volunteers? 5. Following on the previous point, developing a UI based on vogue JS frameworks will be extremely difficult if we are concerned about breaking older themes. Maybe it is time for a clean break. So, this is my proposal: 1. Let's bodly adopt bootstrap. If there are any proponents of any other framework, let them bring it forward so we can all discuss and work on it. 2. Put aside a sprint event to deal with raw ftls scattered all over and get these converted into properly defined widgets. 3. Produce a more sexy ecommerce UI (this is critical to the Ofbiz brand). There are other issues - but this I feel should be prioritised. Regards Gavin On 14 May 2015 12:20 PM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: Below are some, but this question is more to shake things a bit and know what people think I think everybody will agree that the Entity Engine is the gem of this project, follows the Service Engine. I believe, though less polished, the widgets are 3rnd, but that's only my opinion and I'd really like to know others Jacques Le 14/05/2015 10:45, Pierre Smits a écrit : But what are the proposals? Where can these be found? 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 Thu, May 14, 2015 at 9:14 AM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: Actually maybe I'm misunderstanding you and I also want to clarify with everybody. I will try to be brief and right to the point! Do you (we) want to replace the widgets by something like Ean and Anil proposed many times, or do we want to improve them using these new tools? Jacques Le 13/05/2015 22:15, Julien NICOLAS a écrit : Le 13/05/2015 16:35, Jacques Le Roux a écrit : Le 13/05/2015 15:04, Julien NICOLAS a écrit : Hello Pierre, Le 13/05/2015 12:35, Pierre Smits a écrit : For what it is worth, the BOOTSTRAP_theme dev branch is a other way to enhance the user experience. Unfortunately the work is not done yet. The problem is that the GUI is a demo GUI. Then all the time you spend to solve all GUI problems, will potentially lost because nobody use it (and when I say that I think in particular to the order screen that is a nightmare...). It's better that OFBiz embedded GUI web
[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14543727#comment-14543727 ] Pierre Smits commented on OFBIZ-6362: - Question: How shall we deal with the 'screen name=SimpleDecorator'? Have a simple theme for this? Or? 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: Pierre Smits 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-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 -- 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-TomahawkThemeData.xml.patch OFBIZ-6362-Tomahawk-header.ftl.patch These patches address the Tomahawk theme 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 Reporter: Pierre Smits Assignee: Pierre Smits 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-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 -- 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-BizznessTimeThemeData.xml.patch OFBIZ-6362-BizznessTime-header.ftl.patch These patches address the BizznessTime theme 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 Reporter: Pierre Smits Assignee: Pierre Smits Attachments: OFBIZ-6263-BlueLight-header.ftl.patch, OFBIZ-6362-BizznessTime-header.ftl.patch, OFBIZ-6362-BizznessTimeThemeData.xml.patch, OFBIZ-6362-BlueLightThemeData.xml.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6363) Upload of PartyContent produces an error.
[ https://issues.apache.org/jira/browse/OFBIZ-6363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Smits updated OFBIZ-6363: Attachment: OFBIZ-6363-trunk-error.rtf This file shows part of the log regarding the error. Upload of PartyContent produces an error. - Key: OFBIZ-6363 URL: https://issues.apache.org/jira/browse/OFBIZ-6363 Project: OFBiz Issue Type: Bug Components: content, party Affects Versions: Trunk Reporter: Pierre Smits Attachments: OFBIZ-6363-trunk-error.rtf When uploading content in a party profile, the selected file doesn't get uploaded, in stead an error is produced. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-6364) Viewing party content should open in a new window
Pierre Smits created OFBIZ-6364: --- Summary: Viewing party content should open in a new window Key: OFBIZ-6364 URL: https://issues.apache.org/jira/browse/OFBIZ-6364 Project: OFBiz Issue Type: Improvement Components: party Affects Versions: Trunk Reporter: Pierre Smits Currently, when the user clicks on the 'view' button to view the content in a party profile the item is shown in the same screen. However, for a better ux this should open in a new window. -- 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-FlatGreyThemeData.xml.patch OFBIZ-6362-FlatGrey-header.ftl.patch These patches address the FlatGrey theme 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 Reporter: Pierre Smits Assignee: Pierre Smits 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-DroppingCrumbs-header.ftl.patch, OFBIZ-6362-DroppingCrumbsThemeData.xml.patch, OFBIZ-6362-FlatGrey-header.ftl.patch, OFBIZ-6362-FlatGreyThemeData.xml.patch -- 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-CommonScreens.xml.patch This patch addresses the removal of hard coded css and javascript references in CommonScreens.xml, regarding: * screen name=GlobalActions * screen name=LookupDecorator screen name=SimpleDecorator is not adjusted for now. 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: Pierre Smits 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 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14543706#comment-14543706 ] Adrian Crum commented on OFBIZ-6362: Pierre, Thank you for working on this. When you are finished, please assign it to me. 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: Pierre Smits 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-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 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14543709#comment-14543709 ] Pierre Smits commented on OFBIZ-6362: - Thanks Adrian. Will do. 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: Pierre Smits 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-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 -- 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-DroppingCrumbsThemeData.xml.patch OFBIZ-6362-DroppingCrumbs-header.ftl.patch These patches address the DroppingCrumbs theme. 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 Reporter: Pierre Smits Assignee: Pierre Smits 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-DroppingCrumbs-header.ftl.patch, OFBIZ-6362-DroppingCrumbsThemeData.xml.patch -- 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-6263-BlueLight-header.ftl.patch This patch addresses the issue of loading of some javascript files twice. 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 Reporter: Pierre Smits Assignee: Pierre Smits Attachments: OFBIZ-6263-BlueLight-header.ftl.patch, OFBIZ-6362-BlueLightThemeData.xml.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
buildbot success in ASF Buildbot on ofbiz-trunk
The Buildbot has detected a restored build on builder ofbiz-trunk while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/ofbiz-trunk/builds/872 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: lares_ubuntu Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz-commit' triggered this build Build Source Stamp: [branch ofbiz/trunk] 1679394 Blamelist: jleroux Build succeeded! Sincerely, -The Buildbot
Re: Widget or not Widget? [Was Re: Addons for OFBiz]
There has been interest lately in using a REST interface to the OFBiz service engine - so the UI can be pure client-side JavaScript, and the UI is updated dynamically using XML or JSON calls to the REST API. That design would be a huge task, but it could create a truly impressive UI. I will refer to that approach as REST+JSON. Replacing widgets with something else has been discussed for years, yet they are still here. Many man-years have been invested in the screen widgets, so there is a lot of inertia behind them. Replacing them will be a huge task. The complaints about screen widgets are usually: 1. They are OFBiz-specific and are poorly documented, so new developers find them difficult to use. 2. I can't do xyz with a screen widget. We can fix #1 easily by adding documentation to the widget schemas, and by improving the Hot-Tos on the wiki. We can fix #2 by adding support for xyz. This is one of the advantages of screen widgets - since it is ours (and not an external library) we can change it whenever and however we please. The advantages of using screen widgets are: 1. Rapid application development. You can do a lot with a few lines of XML. 2. Screen widgets define a general layout, so they can be reused for non-UI purposes - like reports and data export. A recurring comment is You can use widgets for back office applications, but not for eCommerce sites. I don't agree with that. I built a very slick and information-rich CRM application using widgets only, and I believe anyone can build a competitive eCommerce site using them. You just have to be willing to learn how to exploit their capabilities (re: complaint #1). In a REST+JSON design, we could port/adapt the advantages of screen widgets - like building forms based on entity models or service models. The challenge will be finding a way to reuse things for reports and data export like we currently do with widgets. That effort would be similar to the previous Groovy integration - where we took the cool advantages of Mini-language and ported them to a Groovy DSL. Personally, I don't have a preference. If someone comes up with an alternate approach and implements it, then I will use it. Meanwhile, I will continue to improve the screen widgets. Adrian Crum Sandglass Software www.sandglass-software.com On 5/14/2015 12:14 AM, Jacques Le Roux wrote: Actually maybe I'm misunderstanding you and I also want to clarify with everybody. I will try to be brief and right to the point! Do you (we) want to replace the widgets by something like Ean and Anil proposed many times, or do we want to improve them using these new tools? Jacques Le 13/05/2015 22:15, Julien NICOLAS a écrit : Le 13/05/2015 16:35, Jacques Le Roux a écrit : Le 13/05/2015 15:04, Julien NICOLAS a écrit : Hello Pierre, Le 13/05/2015 12:35, Pierre Smits a écrit : For what it is worth, the BOOTSTRAP_theme dev branch is a other way to enhance the user experience. Unfortunately the work is not done yet. The problem is that the GUI is a demo GUI. Then all the time you spend to solve all GUI problems, will potentially lost because nobody use it (and when I say that I think in particular to the order screen that is a nightmare...). It's better that OFBiz embedded GUI web framework (like bootstrap but not only, it can be bootstrap based tool for dashboard, etc.) and a documentation on how to use it. I don't know if nobody is using it (I guess some are ;)), but I believe a lot are reusing parts of it. The idea is not only to provide a demo but also to provide ideas, bricks to be reused. Did you wrote your own totally from scratch :-o (I guess not even considering ideas) ? Is the BOOTSTRAP_theme dev branch not a way to embed one HTML, CSS, and JavaScript framework and use its artefacts inside widgets? What are actually the parts you found so bad? I mean if you need to adapt the actual visual theme to bootstrap, it may take a lot of time but the gain is very low. It will be more interesting to add tool (like bootstrap or some js tool or widget) and use it for the future demo screen. To have a good screen render by using a new HTML/CSS/JS framework (like bootstrap), you must to define your global solution rendering and create GUI specifications that contain all visual cases. If we speak about create a bootstrap theme not for demo but for a good user experience, we'll have to create the GUI specifications first. Then we need a GUI developer group that define the guidance and validate new screen. In my opinion, changing colour of the actual demo GUI is a waste of time. But use new feature for new demo screen, that change the demo version into a patchwork but it's not a problem :) How the widgets are generated, the CSS class used, how js is used inside of that, etc. ? If we go this way (embed a HTML framework in OFBiz) I remember some proposed to use rather foundation, we would need to pick one and only one. Like wed did with jQuery as the main js
[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14543947#comment-14543947 ] Adrian Crum commented on OFBIZ-6362: The SimpleDecorator can be treated the same as GlobalDecorator. 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: Pierre Smits 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 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Widget or not Widget? [Was Re: Addons for OFBiz]
I agree with the gem ranking level at which widgets are placed and find it a worthy effort to convert as much FTL to widgets as possible because widgets extremely faster to interpret than FTL files. However, sometimes the framework has to be extended to support all of the FTL features which adds some inconveniency (less polished). Moqui supports widgets similar to OFBiz also which suggests its value. On Thu, 2015-05-14 at 12:20 +0200, Jacques Le Roux wrote: Below are some, but this question is more to shake things a bit and know what people think I think everybody will agree that the Entity Engine is the gem of this project, follows the Service Engine. I believe, though less polished, the widgets are 3rnd, but that's only my opinion and I'd really like to know others Jacques Le 14/05/2015 10:45, Pierre Smits a écrit : But what are the proposals? Where can these be found? 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 Thu, May 14, 2015 at 9:14 AM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: Actually maybe I'm misunderstanding you and I also want to clarify with everybody. I will try to be brief and right to the point! Do you (we) want to replace the widgets by something like Ean and Anil proposed many times, or do we want to improve them using these new tools? Jacques Le 13/05/2015 22:15, Julien NICOLAS a écrit : Le 13/05/2015 16:35, Jacques Le Roux a écrit : Le 13/05/2015 15:04, Julien NICOLAS a écrit : Hello Pierre, Le 13/05/2015 12:35, Pierre Smits a écrit : For what it is worth, the BOOTSTRAP_theme dev branch is a other way to enhance the user experience. Unfortunately the work is not done yet. The problem is that the GUI is a demo GUI. Then all the time you spend to solve all GUI problems, will potentially lost because nobody use it (and when I say that I think in particular to the order screen that is a nightmare...). It's better that OFBiz embedded GUI web framework (like bootstrap but not only, it can be bootstrap based tool for dashboard, etc.) and a documentation on how to use it. I don't know if nobody is using it (I guess some are ;)), but I believe a lot are reusing parts of it. The idea is not only to provide a demo but also to provide ideas, bricks to be reused. Did you wrote your own totally from scratch :-o (I guess not even considering ideas) ? Is the BOOTSTRAP_theme dev branch not a way to embed one HTML, CSS, and JavaScript framework and use its artefacts inside widgets? What are actually the parts you found so bad? I mean if you need to adapt the actual visual theme to bootstrap, it may take a lot of time but the gain is very low. It will be more interesting to add tool (like bootstrap or some js tool or widget) and use it for the future demo screen. To have a good screen render by using a new HTML/CSS/JS framework (like bootstrap), you must to define your global solution rendering and create GUI specifications that contain all visual cases. If we speak about create a bootstrap theme not for demo but for a good user experience, we'll have to create the GUI specifications first. Then we need a GUI developer group that define the guidance and validate new screen. In my opinion, changing colour of the actual demo GUI is a waste of time. But use new feature for new demo screen, that change the demo version into a patchwork but it's not a problem :) How the widgets are generated, the CSS class used, how js is used inside of that, etc. ? If we go this way (embed a HTML framework in OFBiz) I remember some proposed to use rather foundation, we would need to pick one and only one. Like wed did with jQuery as the main js lib that BTW we need to keep! I agree. We have to make the choice of a framework and use it. But we can keep in mind that maybe somebody want use another one so we can have detail documentation to explain how to change it. Another point, prefer to use heritage for the default css class. And with the next add-on management, it may be possible to have a specific add-on by css framework ;) Also some have proposed to get further and use something like Angular https://issues.apache.org/jira/browse/OFBIZ-5040?focusedCommentId=13887287 or Backbone https://issues.apache.org/jira/browse/OFBIZ-5522?focusedCommentId=13885989 you name it... https://cordova.apache.org/ (aka PhoneGap) is also worth considering see https://cwiki.apache.org/confluence/download/attachments/48792051/mobile_web.pdf?version=1modificationDate=1429534402000api=v2 PhoneGap is a very interesting project but I'm not sure that a phone app is a priority but it's only my opinion :D We need to make delicate choices and quickly, time is flying... So
[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14544310#comment-14544310 ] Pierre Smits commented on OFBIZ-6362: - Those lines are not referencing jquery directly, but some java code in JsLanguageFilesMapping.java and JsLanguageFileMappingCreator.java, referencing template JsLanguageFilesMapping.ftl Cleaning up lines 147-151 and potentially (re)moving the code in JsLanguageFilesMapping.java, JsLanguageFileMappingCreator.java and JsLanguageFilesMapping.ftl will require more effort and should be assessed independently in a separate 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: Pierre Smits 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 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (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: Comment: was deleted (was: Those lines are not referencing jquery directly, but some java code in JsLanguageFilesMapping.java and JsLanguageFileMappingCreator.java, referencing template JsLanguageFilesMapping.ftl) 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: Pierre Smits 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 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-6367) Clean up SimpleDecorator regarding css and js references
Pierre Smits created OFBIZ-6367:
---
Summary: Clean up SimpleDecorator regarding css and js references
Key: OFBIZ-6367
URL: https://issues.apache.org/jira/browse/OFBIZ-6367
Project: OFBiz
Issue Type: Sub-task
Reporter: Pierre Smits
This includes cleanup of included ftl files
{code}
htmlhtml-template
location=component://common/webcommon/includes/simple.ftl//html
xsl-fohtml-template
location=component://common/webcommon/includes/simple.fo.ftl//xsl-fo
xmlhtml-template
location=component://common/webcommon/includes/minimal-decorator.ftl//xml
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OFBIZ-6365) processWorkEffortEventReminders never called to trigger work effort reminder emails
[ https://issues.apache.org/jira/browse/OFBIZ-6365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Carlow updated OFBIZ-6365: Summary: processWorkEffortEventReminders never called to trigger work effort reminder emails (was: processWorkEffortEventReminders never called trigger email work effort reminders) processWorkEffortEventReminders never called to trigger work effort reminder emails --- Key: OFBIZ-6365 URL: https://issues.apache.org/jira/browse/OFBIZ-6365 Project: OFBiz Issue Type: Improvement Components: workeffort Affects Versions: Trunk Reporter: Christian Carlow -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-6366) Allow processWorkEffortEventReminders email screen to be rendered and printed as PDF
Christian Carlow created OFBIZ-6366: --- Summary: Allow processWorkEffortEventReminders email screen to be rendered and printed as PDF Key: OFBIZ-6366 URL: https://issues.apache.org/jira/browse/OFBIZ-6366 Project: OFBiz Issue Type: Improvement Components: workeffort Affects Versions: Trunk Reporter: Christian Carlow To more easily render the email screen as PDF, the FTL file should be replaced with widgets. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-6365) processWorkEffortEventReminders never called trigger email work effort reminders
Christian Carlow created OFBIZ-6365: --- Summary: processWorkEffortEventReminders never called trigger email work effort reminders Key: OFBIZ-6365 URL: https://issues.apache.org/jira/browse/OFBIZ-6365 Project: OFBiz Issue Type: Improvement Components: workeffort Affects Versions: Trunk Reporter: Christian Carlow -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14544199#comment-14544199 ] Adrian Crum commented on OFBIZ-6362: JQuery is still referenced in the Global Decorator - lines 147-151. Those lines will need to be moved to the theme's header.ftl 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: Pierre Smits 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 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14544254#comment-14544254 ] Pierre Smits commented on OFBIZ-6362: - Those lines are not referencing jquery directly, but some java code in JsLanguageFilesMapping.java and JsLanguageFileMappingCreator.java, referencing template JsLanguageFilesMapping.ftl 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: Pierre Smits 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 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14544316#comment-14544316 ] Pierre Smits commented on OFBIZ-6362: - The issue OFBIZ-6367 has been created to address this. 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: Pierre Smits 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 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14544299#comment-14544299 ] Pierre Smits commented on OFBIZ-6362: - Adjustment of the SimpleDecorator needs to be done in a separate issue, as it impacts more than just the screen in CommonScreens.xml. 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: Pierre Smits 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 -- 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: Assignee: Adrian Crum (was: Pierre Smits) 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 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-6368) Empty availabilityStatusId widget dropdown for statusTypeId WEFA_AVAILABILITY of ProductionRunTaskFixedAssets and AddProductionRunTaskFixedAsset
Christian Carlow created OFBIZ-6368: --- Summary: Empty availabilityStatusId widget dropdown for statusTypeId WEFA_AVAILABILITY of ProductionRunTaskFixedAssets and AddProductionRunTaskFixedAsset Key: OFBIZ-6368 URL: https://issues.apache.org/jira/browse/OFBIZ-6368 Project: OFBiz Issue Type: Improvement Components: manufacturing Affects Versions: Trunk Reporter: Christian Carlow -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-6368) Empty availabilityStatusId widget dropdown for statusTypeId WEFA_AVAILABILITY of ProductionRunTaskFixedAssets and AddProductionRunTaskFixedAsset
[ https://issues.apache.org/jira/browse/OFBIZ-6368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Carlow updated OFBIZ-6368: Attachment: OFBIZ-6368.patch Empty availabilityStatusId widget dropdown for statusTypeId WEFA_AVAILABILITY of ProductionRunTaskFixedAssets and AddProductionRunTaskFixedAsset Key: OFBIZ-6368 URL: https://issues.apache.org/jira/browse/OFBIZ-6368 Project: OFBiz Issue Type: Improvement Components: manufacturing Affects Versions: Trunk Reporter: Christian Carlow Attachments: OFBIZ-6368.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: [VOTE] [RELEASE] Apache OFBiz 13.07.02 - third attempt
+1 - Darrell -- View this message in context: http://ofbiz.135035.n4.nabble.com/VOTE-RELEASE-Apache-OFBiz-13-07-02-third-attempt-tp4668261p4668308.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.
Re: [VOTE] [RELEASE] Apache OFBiz 13.07.02 - third attempt
+1 Thanks Regards -- Deepak Dixit www.hotwaxsystems.com On Fri, May 15, 2015 at 6:50 AM, Darrell Donati darrellof...@gmail.com wrote: +1 - Darrell -- View this message in context: http://ofbiz.135035.n4.nabble.com/VOTE-RELEASE-Apache-OFBiz-13-07-02-third-attempt-tp4668261p4668308.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.
Re: [VOTE] [RELEASE] Apache OFBiz 13.07.02 - third attempt
+1 -- Kind Regards Ashish Vijaywargiya HotWax Systems - est. 1997 http://www.hotwaxsystems.com/ On Thu, May 14, 2015 at 3:40 PM, Jacopo Cappellato jacopo.cappell...@hotwaxsystems.com wrote: Let's try again! This is the vote thread to release a new bug fix release for the release13.07 branch. This new release, Apache OFBiz 13.07.02 will supersede previous releases from the same branch. The release files can be downloaded from here: https://dist.apache.org/repos/dist/dev/ofbiz/ * apache-ofbiz-13.07.02.zip: the release archive * apache-ofbiz-13.07.02.zip.md5, apache-ofbiz-13.07.02.zip.sha: hashes * apache-ofbiz-13.07.02.zip.asc: the detached signature file * KEYS: text file with keys Please download and test the zip file and its signatures (for instructions on testing the signatures see http://www.apache.org/info/verification.html ). Release notes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310500version=12328788 Vote: [ +1] release as Apache OFBiz 13.07.02 [ -1] do not release This vote will be open for 5 days. For more details about this process please read http://www.apache.org/foundation/voting.html Kind Regards, Jacopo
Re: Widget or not Widget? [Was Re: Addons for OFBiz]
Hi Community I have not been able to continue the work on the bootstrap theme for the past few months now and therefore resisted the urge to comment on various threads in the mailing list about matters related. So maybe apologies are in order. Having said that, these are my thoughts: 1. The UI, specifically HTML is as important as any other part of the framework and should consequently be treated as such by the community. 2. Many projects with lesser architectural soundness but with sexy UIs' have proven successful purely based on the UI. The Ofbiz architectural framework rocks, but it not enough has been done to project this graphically. The look and feel of the ecommerce app has not been upgraded for more than half a decade now. This may be the reason why some are looking towards integrating with other ecommerce projects. The Ofbiz ecommerce app isn't bad - the demo just looks bad. 3. Graphical designers can easily write their own UI, as alluded to by Adrian. This regardless of the Javascript framework you would like to use. You can write your own widget templates and incorporate that in your theme. It's possible. 4. The elephant in the room is the significant amount of raw ftl widgets present in the current demos. This is where I got stuck with the bootstrap development. We cannot move the theme forward without dealing with raw ftl. I suspect that the same might be true for any other J'S framework. Any volunteers? 5. Following on the previous point, developing a UI based on vogue JS frameworks will be extremely difficult if we are concerned about breaking older themes. Maybe it is time for a clean break. So, this is my proposal: 1. Let's bodly adopt bootstrap. If there are any proponents of any other framework, let them bring it forward so we can all discuss and work on it. 2. Put aside a sprint event to deal with raw ftls scattered all over and get these converted into properly defined widgets. 3. Produce a more sexy ecommerce UI (this is critical to the Ofbiz brand). There are other issues - but this I feel should be prioritised. Regards Gavin On 14 May 2015 12:20 PM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: Below are some, but this question is more to shake things a bit and know what people think I think everybody will agree that the Entity Engine is the gem of this project, follows the Service Engine. I believe, though less polished, the widgets are 3rnd, but that's only my opinion and I'd really like to know others Jacques Le 14/05/2015 10:45, Pierre Smits a écrit : But what are the proposals? Where can these be found? 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 Thu, May 14, 2015 at 9:14 AM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: Actually maybe I'm misunderstanding you and I also want to clarify with everybody. I will try to be brief and right to the point! Do you (we) want to replace the widgets by something like Ean and Anil proposed many times, or do we want to improve them using these new tools? Jacques Le 13/05/2015 22:15, Julien NICOLAS a écrit : Le 13/05/2015 16:35, Jacques Le Roux a écrit : Le 13/05/2015 15:04, Julien NICOLAS a écrit : Hello Pierre, Le 13/05/2015 12:35, Pierre Smits a écrit : For what it is worth, the BOOTSTRAP_theme dev branch is a other way to enhance the user experience. Unfortunately the work is not done yet. The problem is that the GUI is a demo GUI. Then all the time you spend to solve all GUI problems, will potentially lost because nobody use it (and when I say that I think in particular to the order screen that is a nightmare...). It's better that OFBiz embedded GUI web framework (like bootstrap but not only, it can be bootstrap based tool for dashboard, etc.) and a documentation on how to use it. I don't know if nobody is using it (I guess some are ;)), but I believe a lot are reusing parts of it. The idea is not only to provide a demo but also to provide ideas, bricks to be reused. Did you wrote your own totally from scratch :-o (I guess not even considering ideas) ? Is the BOOTSTRAP_theme dev branch not a way to embed one HTML, CSS, and JavaScript framework and use its artefacts inside widgets? What are actually the parts you found so bad? I mean if you need to adapt the actual visual theme to bootstrap, it may take a lot of time but the gain is very low. It will be more interesting to add tool (like bootstrap or some js tool or widget) and use it for the future demo screen. To have a good screen render by using a new HTML/CSS/JS framework (like bootstrap), you must to define your global solution rendering and create GUI specifications that contain all visual cases. If we speak about create a bootstrap theme not for demo but for a good user experience, we'll have to create the GUI specifications
[jira] [Created] (OFBIZ-6369) Corrected the order in which invoice and payment transactions are created
Jacopo Cappellato created OFBIZ-6369: Summary: Corrected the order in which invoice and payment transactions are created Key: OFBIZ-6369 URL: https://issues.apache.org/jira/browse/OFBIZ-6369 Project: OFBiz Issue Type: Bug Components: accounting Reporter: Jacopo Cappellato Fix For: 14.12.01, 12.04.06, 13.07.02, Upcoming Branch Fixed the order in which invoice and payment transactions are created. Payment transactions were being created prior to invoice transactions, It causes confusion for accountants in real world. It was a seca execution order which was causing the issue on setInvoiceStatus. Moved the trigger on setInvoiceStatus for checkInvoicePaymentApplications and capturePaymentsByInvoice from secas.xml to secas_invoice.xml, so that we do invoice transactions prior to payment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: svn commit: r1675852 - in /ofbiz/trunk/applications/accounting/servicedef: secas.xml secas_invoice.xml
Done: https://issues.apache.org/jira/browse/OFBIZ-6369 Jacopo On Apr 28, 2015, at 9:16 AM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: Hi Pranay, That's cool, but is it not worth a Jira for releases logs? Thanks Jacques Le 24/04/2015 15:29, pran...@apache.org a écrit : Author: pranayp Date: Fri Apr 24 13:29:56 2015 New Revision: 1675852 URL: http://svn.apache.org/r1675852 Log: Fixed the order in which invoice and payment transactions are created. Payment transactions were being created prior to invoice transactions, It causes confusion for accountants in real world. It was a seca execution order which was causing the issue on setInvoiceStatus. Moved the trigger on setInvoiceStatus for checkInvoicePaymentApplications and capturePaymentsByInvoice from secas.xml to secas_invoice.xml, so that we do invoice transactions prior to payment. Modified: ofbiz/trunk/applications/accounting/servicedef/secas.xml ofbiz/trunk/applications/accounting/servicedef/secas_invoice.xml Modified: ofbiz/trunk/applications/accounting/servicedef/secas.xml URL: http://svn.apache.org/viewvc/ofbiz/trunk/applications/accounting/servicedef/secas.xml?rev=1675852r1=1675851r2=1675852view=diff == --- ofbiz/trunk/applications/accounting/servicedef/secas.xml (original) +++ ofbiz/trunk/applications/accounting/servicedef/secas.xml Fri Apr 24 13:29:56 2015 @@ -158,13 +158,4 @@ under the License. condition field-name=productTypeId operator=equals value=ASSET_USAGE/ action service=createFixedAssetAndLinkToProduct mode=sync/ /eca - -eca service=setInvoiceStatus event=commit -condition field-name=invoiceId operator=is-not-empty/ -condition field-name=statusId operator=equals value=INVOICE_READY/ -condition field-name=oldStatusId operator=not-equals value=INVOICE_READY/ -condition field-name=oldStatusId operator=not-equals value=INVOICE_PAID/ -action service=checkInvoicePaymentApplications mode=sync/ -action service=capturePaymentsByInvoice mode=sync/ -/eca /service-eca Modified: ofbiz/trunk/applications/accounting/servicedef/secas_invoice.xml URL: http://svn.apache.org/viewvc/ofbiz/trunk/applications/accounting/servicedef/secas_invoice.xml?rev=1675852r1=1675851r2=1675852view=diff == --- ofbiz/trunk/applications/accounting/servicedef/secas_invoice.xml (original) +++ ofbiz/trunk/applications/accounting/servicedef/secas_invoice.xml Fri Apr 24 13:29:56 2015 @@ -47,4 +47,12 @@ under the License. action service=createMatchingPaymentApplication mode=sync/ /eca +eca service=setInvoiceStatus event=commit +condition field-name=invoiceId operator=is-not-empty/ +condition field-name=statusId operator=equals value=INVOICE_READY/ +condition field-name=oldStatusId operator=not-equals value=INVOICE_READY/ +condition field-name=oldStatusId operator=not-equals value=INVOICE_PAID/ +action service=checkInvoicePaymentApplications mode=sync/ +action service=capturePaymentsByInvoice mode=sync/ +/eca /service-eca
[jira] [Closed] (OFBIZ-6369) Corrected the order in which invoice and payment transactions are created
[ https://issues.apache.org/jira/browse/OFBIZ-6369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacopo Cappellato closed OFBIZ-6369. Resolution: Fixed Assignee: Pranay Pandey Fixed by Pranay Pandey with revisions: trunk - 1675852 14.12 - 1675869 13.07 - 1675871 12.04 - 1675873 Corrected the order in which invoice and payment transactions are created - Key: OFBIZ-6369 URL: https://issues.apache.org/jira/browse/OFBIZ-6369 Project: OFBiz Issue Type: Bug Components: accounting Reporter: Jacopo Cappellato Assignee: Pranay Pandey Fix For: 14.12.01, 12.04.06, 13.07.02, Upcoming Branch Fixed the order in which invoice and payment transactions are created. Payment transactions were being created prior to invoice transactions, It causes confusion for accountants in real world. It was a seca execution order which was causing the issue on setInvoiceStatus. Moved the trigger on setInvoiceStatus for checkInvoicePaymentApplications and capturePaymentsByInvoice from secas.xml to secas_invoice.xml, so that we do invoice transactions prior to payment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-6370) Removed unused commons-cli 1.2 jar
Jacopo Cappellato created OFBIZ-6370: Summary: Removed unused commons-cli 1.2 jar Key: OFBIZ-6370 URL: https://issues.apache.org/jira/browse/OFBIZ-6370 Project: OFBiz Issue Type: Improvement Components: framework Reporter: Jacopo Cappellato Assignee: Jacopo Cappellato Priority: Minor Fix For: 14.12.01, 13.07.02, Upcoming Branch Removed unused commons-cli jar: barcode4j has an optional dependency on it but only if used from the command line (which is not the case in OFBiz); Groovy has a dependency on Commons CLI, antlr, asm but it uses a copy of them bundled in groovy-all jar, so removing the pathelements set for the ant path id groovy.class.path. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (OFBIZ-6370) Removed unused commons-cli 1.2 jar
[ https://issues.apache.org/jira/browse/OFBIZ-6370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacopo Cappellato closed OFBIZ-6370. Resolution: Fixed Removed with the following commits: trunk - 1677597 14.12 - 1677599 13.07 - 1679324 Removed unused commons-cli 1.2 jar -- Key: OFBIZ-6370 URL: https://issues.apache.org/jira/browse/OFBIZ-6370 Project: OFBiz Issue Type: Improvement Components: framework Reporter: Jacopo Cappellato Assignee: Jacopo Cappellato Priority: Minor Fix For: 14.12.01, 13.07.02, Upcoming Branch Removed unused commons-cli jar: barcode4j has an optional dependency on it but only if used from the command line (which is not the case in OFBiz); Groovy has a dependency on Commons CLI, antlr, asm but it uses a copy of them bundled in groovy-all jar, so removing the pathelements set for the ant path id groovy.class.path. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Visual Themes
Yes, thanks Adrian for clarification, much appreciated! Jacques Le 13/05/2015 17:07, Pierre Smits a écrit : Thanks Adrian for bringing the progress back to our attention. It is appreciated. 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 Wed, May 13, 2015 at 5:02 PM, Adrian Crum adrian.c...@sandglass-software.com wrote: Here is a summary of the current Visual Theme implementation (so we are all on the same page): I introduced a feature in the bootstrap branch (then ported to trunk) that allows a visual theme to specify its own templates for rendering. This allows a theme to generate any HTML flavor it requires. In the trunk I introduced a visitor pattern to the screen widgets - which opens things up even more. (In my local copy, I have a rendering engine based on visitors that is incomplete - I hope to commit it someday.) There is a flaw in the current implementation that needs to be fixed: the hard-coded JS libraries and other files in the Global Decorator. That block of code should be converted to visual theme resources - so no specific libraries are referenced in the Global Decorator. The visual theme feature allows a graphics designer to specify JS libraries, CSS libraries, and rendering templates - in effect decoupling visual themes from the framework's rendering engine. As far as I can tell, there is nothing preventing a graphics designer from creating any UI they want using any tool they want. Adrian Crum Sandglass Software www.sandglass-software.com On 5/13/2015 7:35 AM, Jacques Le Roux wrote: Le 13/05/2015 15:04, Julien NICOLAS a écrit : Hello Pierre, Le 13/05/2015 12:35, Pierre Smits a écrit : For what it is worth, the BOOTSTRAP_theme dev branch is a other way to enhance the user experience. Unfortunately the work is not done yet. The problem is that the GUI is a demo GUI. Then all the time you spend to solve all GUI problems, will potentially lost because nobody use it (and when I say that I think in particular to the order screen that is a nightmare...). It's better that OFBiz embedded GUI web framework (like bootstrap but not only, it can be bootstrap based tool for dashboard, etc.) and a documentation on how to use it. I don't know if nobody is using it (I guess some are ;)), but I believe a lot are reusing parts of it. The idea is not only to provide a demo but also to provide ideas, bricks to be reused. Did you wrote your own totally from scratch :-o (I guess not even considering ideas) ? Is the BOOTSTRAP_theme dev branch not a way to embed one HTML, CSS, and JavaScript framework and use its artefacts inside widgets? What are actually the parts you found so bad? How the widgets are generated, the CSS class used, how js is used inside of that, etc. ? If we go this way (embed a HTML framework in OFBiz) I remember some proposed to use rather foundation, we would need to pick one and only one. Like wed did with jQuery as the main js lib that BTW we need to keep! Also some have proposed to get further and use something like Angular https://issues.apache.org/jira/browse/OFBIZ-5040?focusedCommentId=13887287 or Backbone https://issues.apache.org/jira/browse/OFBIZ-5522?focusedCommentId=13885989 you name it... https://cordova.apache.org/ (aka PhoneGap) is also worth considering see https://cwiki.apache.org/confluence/download/attachments/48792051/mobile_web.pdf?version=1modificationDate=1429534402000api=v2 We need to make delicate choices and quickly, time is flying... Jacques
Widget or not Widget? [Was Re: Addons for OFBiz]
Actually maybe I'm misunderstanding you and I also want to clarify with everybody. I will try to be brief and right to the point! Do you (we) want to replace the widgets by something like Ean and Anil proposed many times, or do we want to improve them using these new tools? Jacques Le 13/05/2015 22:15, Julien NICOLAS a écrit : Le 13/05/2015 16:35, Jacques Le Roux a écrit : Le 13/05/2015 15:04, Julien NICOLAS a écrit : Hello Pierre, Le 13/05/2015 12:35, Pierre Smits a écrit : For what it is worth, the BOOTSTRAP_theme dev branch is a other way to enhance the user experience. Unfortunately the work is not done yet. The problem is that the GUI is a demo GUI. Then all the time you spend to solve all GUI problems, will potentially lost because nobody use it (and when I say that I think in particular to the order screen that is a nightmare...). It's better that OFBiz embedded GUI web framework (like bootstrap but not only, it can be bootstrap based tool for dashboard, etc.) and a documentation on how to use it. I don't know if nobody is using it (I guess some are ;)), but I believe a lot are reusing parts of it. The idea is not only to provide a demo but also to provide ideas, bricks to be reused. Did you wrote your own totally from scratch :-o (I guess not even considering ideas) ? Is the BOOTSTRAP_theme dev branch not a way to embed one HTML, CSS, and JavaScript framework and use its artefacts inside widgets? What are actually the parts you found so bad? I mean if you need to adapt the actual visual theme to bootstrap, it may take a lot of time but the gain is very low. It will be more interesting to add tool (like bootstrap or some js tool or widget) and use it for the future demo screen. To have a good screen render by using a new HTML/CSS/JS framework (like bootstrap), you must to define your global solution rendering and create GUI specifications that contain all visual cases. If we speak about create a bootstrap theme not for demo but for a good user experience, we'll have to create the GUI specifications first. Then we need a GUI developer group that define the guidance and validate new screen. In my opinion, changing colour of the actual demo GUI is a waste of time. But use new feature for new demo screen, that change the demo version into a patchwork but it's not a problem :) How the widgets are generated, the CSS class used, how js is used inside of that, etc. ? If we go this way (embed a HTML framework in OFBiz) I remember some proposed to use rather foundation, we would need to pick one and only one. Like wed did with jQuery as the main js lib that BTW we need to keep! I agree. We have to make the choice of a framework and use it. But we can keep in mind that maybe somebody want use another one so we can have detail documentation to explain how to change it. Another point, prefer to use heritage for the default css class. And with the next add-on management, it may be possible to have a specific add-on by css framework ;) Also some have proposed to get further and use something like Angular https://issues.apache.org/jira/browse/OFBIZ-5040?focusedCommentId=13887287 or Backbone https://issues.apache.org/jira/browse/OFBIZ-5522?focusedCommentId=13885989 you name it... https://cordova.apache.org/ (aka PhoneGap) is also worth considering see https://cwiki.apache.org/confluence/download/attachments/48792051/mobile_web.pdf?version=1modificationDate=1429534402000api=v2 PhoneGap is a very interesting project but I'm not sure that a phone app is a priority but it's only my opinion :D We need to make delicate choices and quickly, time is flying... So true... Julien. Jacques
[jira] [Created] (OFBIZ-6362) Move js css references from CommonDecorator(s) to themes
Pierre Smits created OFBIZ-6362: --- Summary: 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 Reporter: Pierre Smits -- This message was sent by Atlassian JIRA (v6.3.4#6332)
buildbot exception in ASF Buildbot on ofbiz-trunk
The Buildbot has detected a build exception on builder ofbiz-trunk while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/ofbiz-trunk/builds/870 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: lares_ubuntu Build Reason: The AnyBranchScheduler scheduler named 'on-ofbiz-commit' triggered this build Build Source Stamp: [branch ofbiz/trunk] 1679322 Blamelist: jleroux BUILD FAILED: exception upload_3 Sincerely, -The Buildbot
Re: Widget or not Widget? [Was Re: Addons for OFBiz]
But what are the proposals? Where can these be found? 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 Thu, May 14, 2015 at 9:14 AM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: Actually maybe I'm misunderstanding you and I also want to clarify with everybody. I will try to be brief and right to the point! Do you (we) want to replace the widgets by something like Ean and Anil proposed many times, or do we want to improve them using these new tools? Jacques Le 13/05/2015 22:15, Julien NICOLAS a écrit : Le 13/05/2015 16:35, Jacques Le Roux a écrit : Le 13/05/2015 15:04, Julien NICOLAS a écrit : Hello Pierre, Le 13/05/2015 12:35, Pierre Smits a écrit : For what it is worth, the BOOTSTRAP_theme dev branch is a other way to enhance the user experience. Unfortunately the work is not done yet. The problem is that the GUI is a demo GUI. Then all the time you spend to solve all GUI problems, will potentially lost because nobody use it (and when I say that I think in particular to the order screen that is a nightmare...). It's better that OFBiz embedded GUI web framework (like bootstrap but not only, it can be bootstrap based tool for dashboard, etc.) and a documentation on how to use it. I don't know if nobody is using it (I guess some are ;)), but I believe a lot are reusing parts of it. The idea is not only to provide a demo but also to provide ideas, bricks to be reused. Did you wrote your own totally from scratch :-o (I guess not even considering ideas) ? Is the BOOTSTRAP_theme dev branch not a way to embed one HTML, CSS, and JavaScript framework and use its artefacts inside widgets? What are actually the parts you found so bad? I mean if you need to adapt the actual visual theme to bootstrap, it may take a lot of time but the gain is very low. It will be more interesting to add tool (like bootstrap or some js tool or widget) and use it for the future demo screen. To have a good screen render by using a new HTML/CSS/JS framework (like bootstrap), you must to define your global solution rendering and create GUI specifications that contain all visual cases. If we speak about create a bootstrap theme not for demo but for a good user experience, we'll have to create the GUI specifications first. Then we need a GUI developer group that define the guidance and validate new screen. In my opinion, changing colour of the actual demo GUI is a waste of time. But use new feature for new demo screen, that change the demo version into a patchwork but it's not a problem :) How the widgets are generated, the CSS class used, how js is used inside of that, etc. ? If we go this way (embed a HTML framework in OFBiz) I remember some proposed to use rather foundation, we would need to pick one and only one. Like wed did with jQuery as the main js lib that BTW we need to keep! I agree. We have to make the choice of a framework and use it. But we can keep in mind that maybe somebody want use another one so we can have detail documentation to explain how to change it. Another point, prefer to use heritage for the default css class. And with the next add-on management, it may be possible to have a specific add-on by css framework ;) Also some have proposed to get further and use something like Angular https://issues.apache.org/jira/browse/OFBIZ-5040?focusedCommentId=13887287 or Backbone https://issues.apache.org/jira/browse/OFBIZ-5522?focusedCommentId=13885989 you name it... https://cordova.apache.org/ (aka PhoneGap) is also worth considering see https://cwiki.apache.org/confluence/download/attachments/48792051/mobile_web.pdf?version=1modificationDate=1429534402000api=v2 PhoneGap is a very interesting project but I'm not sure that a phone app is a priority but it's only my opinion :D We need to make delicate choices and quickly, time is flying... So true... Julien. Jacques
[jira] [Commented] (OFBIZ-6332) Replacing bsh code with Groovy code
[ https://issues.apache.org/jira/browse/OFBIZ-6332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14543476#comment-14543476 ] Jacques Le Roux commented on OFBIZ-6332: Great, BTW when changing from BSH to groovy it would have been better to change from amp; and such to and such. But no worries that can be done automatically with a S/R in Eclipse there after ;) Replacing bsh code with Groovy code --- Key: OFBIZ-6332 URL: https://issues.apache.org/jira/browse/OFBIZ-6332 Project: OFBiz Issue Type: Improvement Components: ALL APPLICATIONS Affects Versions: Trunk Reporter: Pierre Smits This is a placeholder issue to capture related issues to regarding replacing existing beanshell code with Groovy code. It helps planning and communicating. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (OFBIZ-6332) Replacing bsh code with Groovy code
[
https://issues.apache.org/jira/browse/OFBIZ-6332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14543476#comment-14543476
]
Jacques Le Roux edited comment on OFBIZ-6332 at 5/14/15 10:52 AM:
--
Great, BTW when changing from BSH to groovy it would have been better to change
from {noformat}amp;{noformat} and such to and such.
But no worries that can be done automatically with a S/R in Eclipse there after
;)
was (Author: jacques.le.roux):
Great, BTW when changing from BSH to groovy it would have been better to change
from amp; and such to and such.
But no worries that can be done automatically with a S/R in Eclipse there after
;)
Replacing bsh code with Groovy code
---
Key: OFBIZ-6332
URL: https://issues.apache.org/jira/browse/OFBIZ-6332
Project: OFBiz
Issue Type: Improvement
Components: ALL APPLICATIONS
Affects Versions: Trunk
Reporter: Pierre Smits
This is a placeholder issue to capture related issues to regarding replacing
existing beanshell code with Groovy code. It helps planning and communicating.
--
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-BlueLightThemeData.xml.patch This patch addresses the bluelight theme 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 Reporter: Pierre Smits Assignee: Pierre Smits Attachments: OFBIZ-6362-BlueLightThemeData.xml.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (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 reassigned OFBIZ-6362: --- Assignee: Pierre Smits 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 Reporter: Pierre Smits Assignee: Pierre Smits -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: About the tutorial
It's a pity nobody cares about this tutorial. Wrong or not up to date documentation is worse than no documentation. Moreover this tutorial is/was a most important piece for newcomers discovery. Still hoping feedback... Jacques Le 09/05/2015 11:41, Jacques Le Roux a écrit : Hi All, Adrian, Adrian I have looked at your ApacheCon 15 presentation, good it has been advertised on the user ML! One point, I read: The Best Practice to follow is: “When a screen is split up into multiple templates or screens thedata preparation action should be associated only with the individualsmall screen that it prepares data for. This makes it easier to move templates and content pieces around and reuse them in many places. “ In other words, the data preparation logic should be contained within the screen widget that renders it –including forms, menus, and trees. But the tutorial found on the Wiki: https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Tutorial+-+A+Beginners+Development+Guide does not follow this best practice –the data preparation is done in the screen and not in the form that displays the data. Consequently, that form is not reusable –it will be empty (not contain any data) if it is used in any other screen. It seems that the Hotwax System contribution policy has changed and this is no longer maintained by them (was mostly Pranay). Pranay, HS team, could you please confirm this tutorial is no longer maintained by you and if we should rather link a page on HS blog? Of course I'm not thinking about only the point Adrian outlined, but in general. Thanks Jacques
Re: About the tutorial
Hello Jacques, Please hold on for sometime. Pranay is on leave since last few days and I am sure he will post comment here as he is back to work. I hope you are not in hurry? Thanks! -- Kind Regards Ashish Vijaywargiya HotWax Systems - est. 1997 On Thu, May 14, 2015 at 3:04 PM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: It's a pity nobody cares about this tutorial. Wrong or not up to date documentation is worse than no documentation. Moreover this tutorial is/was a most important piece for newcomers discovery. Still hoping feedback... Jacques Le 09/05/2015 11:41, Jacques Le Roux a écrit : Hi All, Adrian, Adrian I have looked at your ApacheCon 15 presentation, good it has been advertised on the user ML! One point, I read: The Best Practice to follow is: “When a screen is split up into multiple templates or screens thedata preparation action should be associated only with the individualsmall screen that it prepares data for. This makes it easier to move templates and content pieces around and reuse them in many places. “ In other words, the data preparation logic should be contained within the screen widget that renders it –including forms, menus, and trees. But the tutorial found on the Wiki: https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Tutorial+-+A+Beginners+Development+Guide does not follow this best practice –the data preparation is done in the screen and not in the form that displays the data. Consequently, that form is not reusable –it will be empty (not contain any data) if it is used in any other screen. It seems that the Hotwax System contribution policy has changed and this is no longer maintained by them (was mostly Pranay). Pranay, HS team, could you please confirm this tutorial is no longer maintained by you and if we should rather link a page on HS blog? Of course I'm not thinking about only the point Adrian outlined, but in general. Thanks Jacques
Re: svn commit: r1675852 - in /ofbiz/trunk/applications/accounting/servicedef: secas.xml secas_invoice.xml
Hi Pranay, I think you are ignoring me, not sure why though :/ Is it intrusive to ask? Thanks Jacques Le 06/05/2015 19:53, Jacques Le Roux a écrit : Hi Pranay, Any chances, or is it out of subject? Jacques Le 28/04/2015 09:16, Jacques Le Roux a écrit : Hi Pranay, That's cool, but is it not worth a Jira for releases logs? Thanks Jacques Le 24/04/2015 15:29, pran...@apache.org a écrit : Author: pranayp Date: Fri Apr 24 13:29:56 2015 New Revision: 1675852 URL: http://svn.apache.org/r1675852 Log: Fixed the order in which invoice and payment transactions are created. Payment transactions were being created prior to invoice transactions, It causes confusion for accountants in real world. It was a seca execution order which was causing the issue on setInvoiceStatus. Moved the trigger on setInvoiceStatus for checkInvoicePaymentApplications and capturePaymentsByInvoice from secas.xml to secas_invoice.xml, so that we do invoice transactions prior to payment. Modified: ofbiz/trunk/applications/accounting/servicedef/secas.xml ofbiz/trunk/applications/accounting/servicedef/secas_invoice.xml Modified: ofbiz/trunk/applications/accounting/servicedef/secas.xml URL: http://svn.apache.org/viewvc/ofbiz/trunk/applications/accounting/servicedef/secas.xml?rev=1675852r1=1675851r2=1675852view=diff == --- ofbiz/trunk/applications/accounting/servicedef/secas.xml (original) +++ ofbiz/trunk/applications/accounting/servicedef/secas.xml Fri Apr 24 13:29:56 2015 @@ -158,13 +158,4 @@ under the License. condition field-name=productTypeId operator=equals value=ASSET_USAGE/ action service=createFixedAssetAndLinkToProduct mode=sync/ /eca - -eca service=setInvoiceStatus event=commit -condition field-name=invoiceId operator=is-not-empty/ -condition field-name=statusId operator=equals value=INVOICE_READY/ -condition field-name=oldStatusId operator=not-equals value=INVOICE_READY/ -condition field-name=oldStatusId operator=not-equals value=INVOICE_PAID/ -action service=checkInvoicePaymentApplications mode=sync/ -action service=capturePaymentsByInvoice mode=sync/ -/eca /service-eca Modified: ofbiz/trunk/applications/accounting/servicedef/secas_invoice.xml URL: http://svn.apache.org/viewvc/ofbiz/trunk/applications/accounting/servicedef/secas_invoice.xml?rev=1675852r1=1675851r2=1675852view=diff == --- ofbiz/trunk/applications/accounting/servicedef/secas_invoice.xml (original) +++ ofbiz/trunk/applications/accounting/servicedef/secas_invoice.xml Fri Apr 24 13:29:56 2015 @@ -47,4 +47,12 @@ under the License. action service=createMatchingPaymentApplication mode=sync/ /eca +eca service=setInvoiceStatus event=commit +condition field-name=invoiceId operator=is-not-empty/ +condition field-name=statusId operator=equals value=INVOICE_READY/ +condition field-name=oldStatusId operator=not-equals value=INVOICE_READY/ +condition field-name=oldStatusId operator=not-equals value=INVOICE_PAID/ +action service=checkInvoicePaymentApplications mode=sync/ +action service=capturePaymentsByInvoice mode=sync/ +/eca /service-eca
[VOTE] [RELEASE] Apache OFBiz 13.07.02 - third attempt
Let's try again! This is the vote thread to release a new bug fix release for the release13.07 branch. This new release, Apache OFBiz 13.07.02 will supersede previous releases from the same branch. The release files can be downloaded from here: https://dist.apache.org/repos/dist/dev/ofbiz/ * apache-ofbiz-13.07.02.zip: the release archive * apache-ofbiz-13.07.02.zip.md5, apache-ofbiz-13.07.02.zip.sha: hashes * apache-ofbiz-13.07.02.zip.asc: the detached signature file * KEYS: text file with keys Please download and test the zip file and its signatures (for instructions on testing the signatures see http://www.apache.org/info/verification.html). Release notes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310500version=12328788 Vote: [ +1] release as Apache OFBiz 13.07.02 [ -1] do not release This vote will be open for 5 days. For more details about this process please read http://www.apache.org/foundation/voting.html Kind Regards, Jacopo
Re: Widget or not Widget? [Was Re: Addons for OFBiz]
Below are some, but this question is more to shake things a bit and know what people think I think everybody will agree that the Entity Engine is the gem of this project, follows the Service Engine. I believe, though less polished, the widgets are 3rnd, but that's only my opinion and I'd really like to know others Jacques Le 14/05/2015 10:45, Pierre Smits a écrit : But what are the proposals? Where can these be found? 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 Thu, May 14, 2015 at 9:14 AM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: Actually maybe I'm misunderstanding you and I also want to clarify with everybody. I will try to be brief and right to the point! Do you (we) want to replace the widgets by something like Ean and Anil proposed many times, or do we want to improve them using these new tools? Jacques Le 13/05/2015 22:15, Julien NICOLAS a écrit : Le 13/05/2015 16:35, Jacques Le Roux a écrit : Le 13/05/2015 15:04, Julien NICOLAS a écrit : Hello Pierre, Le 13/05/2015 12:35, Pierre Smits a écrit : For what it is worth, the BOOTSTRAP_theme dev branch is a other way to enhance the user experience. Unfortunately the work is not done yet. The problem is that the GUI is a demo GUI. Then all the time you spend to solve all GUI problems, will potentially lost because nobody use it (and when I say that I think in particular to the order screen that is a nightmare...). It's better that OFBiz embedded GUI web framework (like bootstrap but not only, it can be bootstrap based tool for dashboard, etc.) and a documentation on how to use it. I don't know if nobody is using it (I guess some are ;)), but I believe a lot are reusing parts of it. The idea is not only to provide a demo but also to provide ideas, bricks to be reused. Did you wrote your own totally from scratch :-o (I guess not even considering ideas) ? Is the BOOTSTRAP_theme dev branch not a way to embed one HTML, CSS, and JavaScript framework and use its artefacts inside widgets? What are actually the parts you found so bad? I mean if you need to adapt the actual visual theme to bootstrap, it may take a lot of time but the gain is very low. It will be more interesting to add tool (like bootstrap or some js tool or widget) and use it for the future demo screen. To have a good screen render by using a new HTML/CSS/JS framework (like bootstrap), you must to define your global solution rendering and create GUI specifications that contain all visual cases. If we speak about create a bootstrap theme not for demo but for a good user experience, we'll have to create the GUI specifications first. Then we need a GUI developer group that define the guidance and validate new screen. In my opinion, changing colour of the actual demo GUI is a waste of time. But use new feature for new demo screen, that change the demo version into a patchwork but it's not a problem :) How the widgets are generated, the CSS class used, how js is used inside of that, etc. ? If we go this way (embed a HTML framework in OFBiz) I remember some proposed to use rather foundation, we would need to pick one and only one. Like wed did with jQuery as the main js lib that BTW we need to keep! I agree. We have to make the choice of a framework and use it. But we can keep in mind that maybe somebody want use another one so we can have detail documentation to explain how to change it. Another point, prefer to use heritage for the default css class. And with the next add-on management, it may be possible to have a specific add-on by css framework ;) Also some have proposed to get further and use something like Angular https://issues.apache.org/jira/browse/OFBIZ-5040?focusedCommentId=13887287 or Backbone https://issues.apache.org/jira/browse/OFBIZ-5522?focusedCommentId=13885989 you name it... https://cordova.apache.org/ (aka PhoneGap) is also worth considering see https://cwiki.apache.org/confluence/download/attachments/48792051/mobile_web.pdf?version=1modificationDate=1429534402000api=v2 PhoneGap is a very interesting project but I'm not sure that a phone app is a priority but it's only my opinion :D We need to make delicate choices and quickly, time is flying... So true... Julien. Jacques
Re: About the tutorial
Thanks Ashish :) This clarifies all, so please also forget my next message for Pranay (about a commit and Jira) Jacques Le 14/05/2015 11:41, Ashish Vijaywargiya a écrit : Hello Jacques, Please hold on for sometime. Pranay is on leave since last few days and I am sure he will post comment here as he is back to work. I hope you are not in hurry? Thanks! -- Kind Regards Ashish Vijaywargiya HotWax Systems - est. 1997 On Thu, May 14, 2015 at 3:04 PM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: It's a pity nobody cares about this tutorial. Wrong or not up to date documentation is worse than no documentation. Moreover this tutorial is/was a most important piece for newcomers discovery. Still hoping feedback... Jacques Le 09/05/2015 11:41, Jacques Le Roux a écrit : Hi All, Adrian, Adrian I have looked at your ApacheCon 15 presentation, good it has been advertised on the user ML! One point, I read: The Best Practice to follow is: “When a screen is split up into multiple templates or screens thedata preparation action should be associated only with the individualsmall screen that it prepares data for. This makes it easier to move templates and content pieces around and reuse them in many places. “ In other words, the data preparation logic should be contained within the screen widget that renders it –including forms, menus, and trees. But the tutorial found on the Wiki: https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Tutorial+-+A+Beginners+Development+Guide does not follow this best practice –the data preparation is done in the screen and not in the form that displays the data. Consequently, that form is not reusable –it will be empty (not contain any data) if it is used in any other screen. It seems that the Hotwax System contribution policy has changed and this is no longer maintained by them (was mostly Pranay). Pranay, HS team, could you please confirm this tutorial is no longer maintained by you and if we should rather link a page on HS blog? Of course I'm not thinking about only the point Adrian outlined, but in general. Thanks Jacques
Re: svn commit: r1675852 - in /ofbiz/trunk/applications/accounting/servicedef: secas.xml secas_invoice.xml
Hi Jacques, As mentioned by Ashish in another thread, Pranay is not actively working from last few days because his son was admitted to hospital. He will get back to you Jacques once he is back. Thanks -- Divesh Dutta. On Thu, May 14, 2015 at 3:46 PM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: Hi Pranay, I think you are ignoring me, not sure why though :/ Is it intrusive to ask? Thanks Jacques Le 06/05/2015 19:53, Jacques Le Roux a écrit : Hi Pranay, Any chances, or is it out of subject? Jacques Le 28/04/2015 09:16, Jacques Le Roux a écrit : Hi Pranay, That's cool, but is it not worth a Jira for releases logs? Thanks Jacques Le 24/04/2015 15:29, pran...@apache.org a écrit : Author: pranayp Date: Fri Apr 24 13:29:56 2015 New Revision: 1675852 URL: http://svn.apache.org/r1675852 Log: Fixed the order in which invoice and payment transactions are created. Payment transactions were being created prior to invoice transactions, It causes confusion for accountants in real world. It was a seca execution order which was causing the issue on setInvoiceStatus. Moved the trigger on setInvoiceStatus for checkInvoicePaymentApplications and capturePaymentsByInvoice from secas.xml to secas_invoice.xml, so that we do invoice transactions prior to payment. Modified: ofbiz/trunk/applications/accounting/servicedef/secas.xml ofbiz/trunk/applications/accounting/servicedef/secas_invoice.xml Modified: ofbiz/trunk/applications/accounting/servicedef/secas.xml URL: http://svn.apache.org/viewvc/ofbiz/trunk/applications/accounting/servicedef/secas.xml?rev=1675852r1=1675851r2=1675852view=diff == --- ofbiz/trunk/applications/accounting/servicedef/secas.xml (original) +++ ofbiz/trunk/applications/accounting/servicedef/secas.xml Fri Apr 24 13:29:56 2015 @@ -158,13 +158,4 @@ under the License. condition field-name=productTypeId operator=equals value=ASSET_USAGE/ action service=createFixedAssetAndLinkToProduct mode=sync/ /eca - -eca service=setInvoiceStatus event=commit -condition field-name=invoiceId operator=is-not-empty/ -condition field-name=statusId operator=equals value=INVOICE_READY/ -condition field-name=oldStatusId operator=not-equals value=INVOICE_READY/ -condition field-name=oldStatusId operator=not-equals value=INVOICE_PAID/ -action service=checkInvoicePaymentApplications mode=sync/ -action service=capturePaymentsByInvoice mode=sync/ -/eca /service-eca Modified: ofbiz/trunk/applications/accounting/servicedef/secas_invoice.xml URL: http://svn.apache.org/viewvc/ofbiz/trunk/applications/accounting/servicedef/secas_invoice.xml?rev=1675852r1=1675851r2=1675852view=diff == --- ofbiz/trunk/applications/accounting/servicedef/secas_invoice.xml (original) +++ ofbiz/trunk/applications/accounting/servicedef/secas_invoice.xml Fri Apr 24 13:29:56 2015 @@ -47,4 +47,12 @@ under the License. action service=createMatchingPaymentApplication mode=sync/ /eca +eca service=setInvoiceStatus event=commit +condition field-name=invoiceId operator=is-not-empty/ +condition field-name=statusId operator=equals value=INVOICE_READY/ +condition field-name=oldStatusId operator=not-equals value=INVOICE_READY/ +condition field-name=oldStatusId operator=not-equals value=INVOICE_PAID/ +action service=checkInvoicePaymentApplications mode=sync/ +action service=capturePaymentsByInvoice mode=sync/ +/eca /service-eca
Re: svn commit: r1675852 - in /ofbiz/trunk/applications/accounting/servicedef: secas.xml secas_invoice.xml
Pranay is not ignoring you. I posted comment on another thread which includes details about his unavailability. Kind Regards Ashish Vijaywargiya HotWax Systems - est. 1997 On Thu, May 14, 2015 at 3:46 PM, Jacques Le Roux jacques.le.r...@les7arts.com wrote: Hi Pranay, I think you are ignoring me, not sure why though :/ Is it intrusive to ask? Thanks Jacques Le 06/05/2015 19:53, Jacques Le Roux a écrit : Hi Pranay, Any chances, or is it out of subject? Jacques Le 28/04/2015 09:16, Jacques Le Roux a écrit : Hi Pranay, That's cool, but is it not worth a Jira for releases logs? Thanks Jacques Le 24/04/2015 15:29, pran...@apache.org a écrit : Author: pranayp Date: Fri Apr 24 13:29:56 2015 New Revision: 1675852 URL: http://svn.apache.org/r1675852 Log: Fixed the order in which invoice and payment transactions are created. Payment transactions were being created prior to invoice transactions, It causes confusion for accountants in real world. It was a seca execution order which was causing the issue on setInvoiceStatus. Moved the trigger on setInvoiceStatus for checkInvoicePaymentApplications and capturePaymentsByInvoice from secas.xml to secas_invoice.xml, so that we do invoice transactions prior to payment. Modified: ofbiz/trunk/applications/accounting/servicedef/secas.xml ofbiz/trunk/applications/accounting/servicedef/secas_invoice.xml Modified: ofbiz/trunk/applications/accounting/servicedef/secas.xml URL: http://svn.apache.org/viewvc/ofbiz/trunk/applications/accounting/servicedef/secas.xml?rev=1675852r1=1675851r2=1675852view=diff == --- ofbiz/trunk/applications/accounting/servicedef/secas.xml (original) +++ ofbiz/trunk/applications/accounting/servicedef/secas.xml Fri Apr 24 13:29:56 2015 @@ -158,13 +158,4 @@ under the License. condition field-name=productTypeId operator=equals value=ASSET_USAGE/ action service=createFixedAssetAndLinkToProduct mode=sync/ /eca - -eca service=setInvoiceStatus event=commit -condition field-name=invoiceId operator=is-not-empty/ -condition field-name=statusId operator=equals value=INVOICE_READY/ -condition field-name=oldStatusId operator=not-equals value=INVOICE_READY/ -condition field-name=oldStatusId operator=not-equals value=INVOICE_PAID/ -action service=checkInvoicePaymentApplications mode=sync/ -action service=capturePaymentsByInvoice mode=sync/ -/eca /service-eca Modified: ofbiz/trunk/applications/accounting/servicedef/secas_invoice.xml URL: http://svn.apache.org/viewvc/ofbiz/trunk/applications/accounting/servicedef/secas_invoice.xml?rev=1675852r1=1675851r2=1675852view=diff == --- ofbiz/trunk/applications/accounting/servicedef/secas_invoice.xml (original) +++ ofbiz/trunk/applications/accounting/servicedef/secas_invoice.xml Fri Apr 24 13:29:56 2015 @@ -47,4 +47,12 @@ under the License. action service=createMatchingPaymentApplication mode=sync/ /eca +eca service=setInvoiceStatus event=commit +condition field-name=invoiceId operator=is-not-empty/ +condition field-name=statusId operator=equals value=INVOICE_READY/ +condition field-name=oldStatusId operator=not-equals value=INVOICE_READY/ +condition field-name=oldStatusId operator=not-equals value=INVOICE_PAID/ +action service=checkInvoicePaymentApplications mode=sync/ +action service=capturePaymentsByInvoice mode=sync/ +/eca /service-eca
