[jira] [Commented] (OFBIZ-7618) Add "changeByUserLoginId" field for ShipmentStatus
[ https://issues.apache.org/jira/browse/OFBIZ-7618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15371696#comment-15371696 ] Charles STELTZLEN commented on OFBIZ-7618: -- Done. > Add "changeByUserLoginId" field for ShipmentStatus > -- > > Key: OFBIZ-7618 > URL: https://issues.apache.org/jira/browse/OFBIZ-7618 > Project: OFBiz > Issue Type: Sub-task > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Nameet Jain >Assignee: Nicolas Malin > Attachments: OFBIZ-7618.patch, ofbiz-7618-ShipmentStatus.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7618) Add "changeByUserLoginId" field for ShipmentStatus
[ https://issues.apache.org/jira/browse/OFBIZ-7618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles STELTZLEN updated OFBIZ-7618: - Attachment: (was: ofbiz-7618-ShipmentStatus.patch) > Add "changeByUserLoginId" field for ShipmentStatus > -- > > Key: OFBIZ-7618 > URL: https://issues.apache.org/jira/browse/OFBIZ-7618 > Project: OFBiz > Issue Type: Sub-task > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Nameet Jain >Assignee: Nicolas Malin > Attachments: OFBIZ-7618.patch, ofbiz-7618-ShipmentStatus.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7618) Add "changeByUserLoginId" field for ShipmentStatus
[ https://issues.apache.org/jira/browse/OFBIZ-7618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles STELTZLEN updated OFBIZ-7618: - Attachment: ofbiz-7618-ShipmentStatus.patch > Add "changeByUserLoginId" field for ShipmentStatus > -- > > Key: OFBIZ-7618 > URL: https://issues.apache.org/jira/browse/OFBIZ-7618 > Project: OFBiz > Issue Type: Sub-task > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Nameet Jain >Assignee: Nicolas Malin > Attachments: OFBIZ-7618.patch, ofbiz-7618-ShipmentStatus.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7618) Add "changeByUserLoginId" field for ShipmentStatus
[ https://issues.apache.org/jira/browse/OFBIZ-7618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles STELTZLEN updated OFBIZ-7618: - Attachment: ofbiz-7618-ShipmentStatus.patch > Add "changeByUserLoginId" field for ShipmentStatus > -- > > Key: OFBIZ-7618 > URL: https://issues.apache.org/jira/browse/OFBIZ-7618 > Project: OFBiz > Issue Type: Sub-task > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Nameet Jain >Assignee: Nicolas Malin > Attachments: OFBIZ-7618.patch, ofbiz-7618-ShipmentStatus.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7618) Add "changeByUserLoginId" field for ShipmentStatus
[ https://issues.apache.org/jira/browse/OFBIZ-7618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15371500#comment-15371500 ] Charles STELTZLEN commented on OFBIZ-7618: -- I took it. Charles > Add "changeByUserLoginId" field for ShipmentStatus > -- > > Key: OFBIZ-7618 > URL: https://issues.apache.org/jira/browse/OFBIZ-7618 > Project: OFBiz > Issue Type: Sub-task > Components: ALL COMPONENTS >Affects Versions: Trunk >Reporter: Nameet Jain >Assignee: Nicolas Malin > Attachments: OFBIZ-7618.patch > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Form Display Field improvement to manage multiple number format
Hi, On display field used in Forms, there is a "type" "accounting-number" which is used to format number like 'accounting-number.format' property configuration (arithmetic.properties) : #,##0.;(#,##0.). The proposal is to extend this idea by using a "type" "number" and an additional attribute called "format-pattern". This field will be used by form renderer to get the good property. It use FlexibleString to manage variable in this field and so allow to have different format for the same column according to some conditions. example: format-pattern="accounting"/> The "format-pattern" will be stored in the arithmetic.properties. example: # the default number format default.number.format = ##0.00 accounting.number.format = #,##0.;(#,##0.) quantity.number.format = ##0.00 integer-quantity.number.format = #0 percentage.number.format = ##.##% export.number.format = #.00 In ModelFormField.java, the system gets property using EntityUtilProperties.getPropertyValue to be able to quickly add a new format. A JIRA exists on this proposition (opened to soon as Jacques mentionned ) :https://issues.apache.org/jira/browse/OFBIZ-7532 Do think that this proposal is a good one ? Best regards, Charles
[jira] [Updated] (OFBIZ-7532) Form Display Field improvement to manage multiple number format
[ https://issues.apache.org/jira/browse/OFBIZ-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles STELTZLEN updated OFBIZ-7532: - Attachment: OFBIZ-7532.patch > Form Display Field improvement to manage multiple number format > --- > > Key: OFBIZ-7532 > URL: https://issues.apache.org/jira/browse/OFBIZ-7532 > Project: OFBiz > Issue Type: Improvement > Components: ALL COMPONENTS >Affects Versions: Trunk > Reporter: Charles STELTZLEN >Priority: Minor > Attachments: OFBIZ-7532.patch > > > On display field used in forms, there is a "type" "accounting-number" which > is used to format number like property configuration : > #,##0.;(#,##0.). > This JIRA propose to extend this idea by using a "type" "number" and an > additional attribute called "format-pattern". This field will be used by form > renderer to get the good property. It use FlexibleString to manage variable > in this field and so allow to have different format for the same column > according to some conditions. > example: format-pattern="accounting"/> > The "format-pattern" will be stored in arithmetic.properties. > example: > # the default number format > default.number.format = ##0.00 > accounting.number.format = #,##0.;(#,##0.) > quantity.number.format = ##0.00 > integer-quantity.number.format = #0 > percentage.number.format = ##.##% > export.number.format = #.00 > In ModelFormField.java, the system gets property using > EntityUtilProperties.getPropertyValue to ba able to quickly add a new format. > I think that it will require a discussion on Dev mailing-list to validate the > choices. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7532) Form Display Field improvement to manage multiple number format
Charles STELTZLEN created OFBIZ-7532: Summary: Form Display Field improvement to manage multiple number format Key: OFBIZ-7532 URL: https://issues.apache.org/jira/browse/OFBIZ-7532 Project: OFBiz Issue Type: Improvement Components: ALL COMPONENTS Affects Versions: Trunk Reporter: Charles STELTZLEN Priority: Minor On display field used in forms, there is a "type" "accounting-number" which is used to format number like property configuration : #,##0.;(#,##0.). This JIRA propose to extend this idea by using a "type" "number" and an additional attribute called "format-pattern". This field will be used by form renderer to get the good property. It use FlexibleString to manage variable in this field and so allow to have different format for the same column according to some conditions. example: The "format-pattern" will be stored in arithmetic.properties. example: # the default number format default.number.format = ##0.00 accounting.number.format = #,##0.;(#,##0.) quantity.number.format = ##0.00 integer-quantity.number.format = #0 percentage.number.format = ##.##% export.number.format = #.00 In ModelFormField.java, the system gets property using EntityUtilProperties.getPropertyValue to ba able to quickly add a new format. I think that it will require a discussion on Dev mailing-list to validate the choices. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7350) Manage filters in lookup auto completion
[ https://issues.apache.org/jira/browse/OFBIZ-7350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15335943#comment-15335943 ] Charles STELTZLEN commented on OFBIZ-7350: -- Yes, this is exactly the goal of this feature. > Manage filters in lookup auto completion > > > Key: OFBIZ-7350 > URL: https://issues.apache.org/jira/browse/OFBIZ-7350 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Release Branch 12.04, Release Branch 13.07, Release > Branch 14.12, Trunk, Release Branch 15.12 > Reporter: Charles STELTZLEN >Assignee: Deepak Dixit >Priority: Minor > Attachments: OFBIZ-7350.13.07.patch, OFBIZ-7350.patch > > > On form lookup, we can specify target parameters to pass them to the lookup > screen and do filtered searches with these parameters. It works fine when you > click on lookup button. But when you start to write something in lookup > input, these parameters are not passed to the ajax auto-complete system. So, > the results are not filtered. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7350) Manage filters in lookup auto completion
[ https://issues.apache.org/jira/browse/OFBIZ-7350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles STELTZLEN updated OFBIZ-7350: - Attachment: OFBIZ-7350.patch OFBIZ-7350.13.07.patch > Manage filters in lookup auto completion > > > Key: OFBIZ-7350 > URL: https://issues.apache.org/jira/browse/OFBIZ-7350 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Release Branch 12.04, Release Branch 13.07, Release > Branch 14.12, Trunk, Release Branch 15.12 > Reporter: Charles STELTZLEN >Priority: Minor > Attachments: OFBIZ-7350.13.07.patch, OFBIZ-7350.patch > > > On form lookup, we can specify target parameters to pass them to the lookup > screen and do filtered searches with these parameters. It works fine when you > click on lookup button. But when you start to write something in lookup > input, these parameters are not passed to the ajax auto-complete system. So, > the results are not filtered. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7350) Manage filters in lookup auto completion
[ https://issues.apache.org/jira/browse/OFBIZ-7350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles STELTZLEN updated OFBIZ-7350: - Attachment: (was: lookup-improvement_13.07.patch) > Manage filters in lookup auto completion > > > Key: OFBIZ-7350 > URL: https://issues.apache.org/jira/browse/OFBIZ-7350 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Release Branch 12.04, Release Branch 13.07, Release > Branch 14.12, Trunk, Release Branch 15.12 > Reporter: Charles STELTZLEN >Priority: Minor > Attachments: OFBIZ-7350.13.07.patch, OFBIZ-7350.patch > > > On form lookup, we can specify target parameters to pass them to the lookup > screen and do filtered searches with these parameters. It works fine when you > click on lookup button. But when you start to write something in lookup > input, these parameters are not passed to the ajax auto-complete system. So, > the results are not filtered. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OFBIZ-7350) Manage filters in lookup auto completion
[ https://issues.apache.org/jira/browse/OFBIZ-7350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15331498#comment-15331498 ] Charles STELTZLEN commented on OFBIZ-7350: -- Thanks Jacques. I'm working on it ;). I have some issues with git and svn patches. I will propose both patches. > Manage filters in lookup auto completion > > > Key: OFBIZ-7350 > URL: https://issues.apache.org/jira/browse/OFBIZ-7350 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Release Branch 12.04, Release Branch 13.07, Release > Branch 14.12, Trunk, Release Branch 15.12 > Reporter: Charles STELTZLEN >Priority: Minor > Attachments: lookup-improvement_13.07.patch > > > On form lookup, we can specify target parameters to pass them to the lookup > screen and do filtered searches with these parameters. It works fine when you > click on lookup button. But when you start to write something in lookup > input, these parameters are not passed to the ajax auto-complete system. So, > the results are not filtered. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OFBIZ-7350) Manage filters in lookup auto completion
[ https://issues.apache.org/jira/browse/OFBIZ-7350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles STELTZLEN updated OFBIZ-7350: - Attachment: lookup-improvement_13.07.patch Patch for branch 13.07 > Manage filters in lookup auto completion > > > Key: OFBIZ-7350 > URL: https://issues.apache.org/jira/browse/OFBIZ-7350 > Project: OFBiz > Issue Type: Improvement > Components: framework >Affects Versions: Release Branch 12.04, Release Branch 13.07, Release > Branch 14.12, Trunk, Release Branch 15.12 > Reporter: Charles STELTZLEN >Priority: Minor > Attachments: lookup-improvement_13.07.patch > > > On form lookup, we can specify target parameters to pass them to the lookup > screen and do filtered searches with these parameters. It works fine when you > click on lookup button. But when you start to write something in lookup > input, these parameters are not passed to the ajax auto-complete system. So, > the results are not filtered. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-7350) Manage filters in lookup auto completion
Charles STELTZLEN created OFBIZ-7350: Summary: Manage filters in lookup auto completion Key: OFBIZ-7350 URL: https://issues.apache.org/jira/browse/OFBIZ-7350 Project: OFBiz Issue Type: Improvement Components: framework Affects Versions: Release Branch 15.12, Trunk, Release Branch 14.12, Release Branch 13.07, Release Branch 12.04 Reporter: Charles STELTZLEN Priority: Minor On form lookup, we can specify target parameters to pass them to the lookup screen and do filtered searches with these parameters. It works fine when you click on lookup button. But when you start to write something in lookup input, these parameters are not passed to the ajax auto-complete system. So, the results are not filtered. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (OFBIZ-4442) French translation missing in portal pages management
French translation missing in portal pages management - Key: OFBIZ-4442 URL: https://issues.apache.org/jira/browse/OFBIZ-4442 Project: OFBiz Issue Type: Improvement Components: framework Reporter: Charles STELTZLEN Priority: Trivial Somes labels are not translated in Portal Pages management. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OFBIZ-4442) French translation missing in portal pages management
[ https://issues.apache.org/jira/browse/OFBIZ-4442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Charles STELTZLEN updated OFBIZ-4442: - Attachment: CommonUiLabels.xml.patch Patch adding missing translations French translation missing in portal pages management - Key: OFBIZ-4442 URL: https://issues.apache.org/jira/browse/OFBIZ-4442 Project: OFBiz Issue Type: Improvement Components: framework Reporter: Charles STELTZLEN Priority: Trivial Labels: patch Attachments: CommonUiLabels.xml.patch Original Estimate: 0.5h Remaining Estimate: 0.5h Somes labels are not translated in Portal Pages management. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (OFBIZ-4151) Text fields in Portlet forms not editable
Text fields in Portlet forms not editable - Key: OFBIZ-4151 URL: https://issues.apache.org/jira/browse/OFBIZ-4151 Project: OFBiz Issue Type: Bug Components: ALL APPLICATIONS Environment: ofbiz r1062528 Reporter: Charles STELTZLEN Apply given patch on framework or just add an include-form with text field on one of the ExemplePortalPage. https://localhost:8443/example/control/showPortalPage?portalPageId=10020parentPortalPageId=EXAMPLE On Firefox browser, the form fileds are not editable, I cannot write anything in the field, moreover, I cannot put the mouse cursor in. It works on Chromium browser. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (OFBIZ-1978) createShipment parameters : add a shipmentId in IN parameters
createShipment parameters : add a shipmentId in IN parameters - Key: OFBIZ-1978 URL: https://issues.apache.org/jira/browse/OFBIZ-1978 Project: OFBiz Issue Type: Improvement Components: product Reporter: Charles STELTZLEN Priority: Minor In Shipment services, the service of creation, called *createShipment*, don't accept our own *shipmentId*. It can be a problem in some business, and I think it won't be difficult to add a IN parameter shipmentId. So, I propose to change the service and use a shipmentId given by default, and if there is no shipmentId in parameters, it will get the next sequenced id (as it already done in the createShipment service). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
