Re: Form Display Field improvement to manage multiple number format

[Pierre Smits]

Hi Charles,

See my comment in https://issues.apache.org/jira/browse/OFBIZ-7532.

Best regards,

Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Mon, Jul 11, 2016 at 3:43 PM, Charles STELTZLEN <
charles.steltz...@nereide.biz> wrote:

> 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-6711) Have configuration options regarding widgets

[Pierre Smits (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated OFBIZ-6711:

Assignee: (was: Pierre Smits)

> Have configuration options regarding widgets
> 
>
> Key: OFBIZ-6711
> URL: https://issues.apache.org/jira/browse/OFBIZ-6711
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: ALL APPLICATIONS, ALL COMPONENTS
>Reporter: Pierre Smits
> Attachments: OFBIZ-6711-widget.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OFBIZ-6211) Split configuration options in /framework/common .properties files

[Pierre Smits (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated OFBIZ-6211:

Assignee: (was: Pierre Smits)

> Split configuration options in /framework/common .properties files
> --
>
> Key: OFBIZ-6211
> URL: https://issues.apache.org/jira/browse/OFBIZ-6211
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: framework
>Reporter: Pierre Smits
>  Labels: common, configuration, multi-tenant
>
> The configuration file general.properties contains has configuration options 
> that are multi-tenant configurable (e.g. mail settings) and options that are 
> implementation specific (e.g. multitenant) and require a restart.
> The multi-tenant configurable options should move out of general.properties 
> into a separate .properties file.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [DISCUSSION] Proposed Task List for Moving Forward with Gradle and the Trunk

[Sharan-F]

Hi Everyone

Another update on the task list for moving forward with Gradle and the
Trunk. We would also like to get community feedback and comments on each of
the following 3 proposals:

Task 1 “Replace all the current jars in OFBiz with appropriate remote
libraries from a download repository
--
The work to replace the jars is ongoing and we have already removed 169 of
them. These libraries will now be automatically downloaded by Gradle. Work
will continue to remove the remaining files. As we are working through, we
are finding library migration issues with some of the specialpurpose
components so would like *to propose to deactivate all specialpurpose
components by default.*


Task 4. “ Move all java source files to\u2002$component/src/main/java and
introduce all unit tests in\u2002\u2002$component/src/test/java”
-
Another area we need to progress is the re-design and changing of the
directory structure so that we can separate the Java files between main and
test. This will help us simplify the implementation of a testing framework.
*The proposal for the directory structure is as follows:

   componentname/src/main/java
   componentname/src/test/java*


Task 10. “Propose the renaming specialpurpose to plugins or such an
appropriate name for clarity”
-
We would like * to propose changing the name of the specialpurpose folder to
'plugins'*

These are the 3 areas we would like to progress so please feel free to
respond with your feedback and comments.

Thanks
Sharan




--
View this message in context: 
http://ofbiz.135035.n4.nabble.com/DISCUSSION-Proposed-Task-List-for-Moving-Forward-with-Gradle-and-the-Trunk-tp4687808p4688257.html
Sent from the OFBiz - Dev mailing list archive at Nabble.com.

[jira] [Commented] (OFBIZ-7532) Form Display Field improvement to manage multiple number format

[Pierre Smits (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15371096#comment-15371096
 ] 

Pierre Smits commented on OFBIZ-7532:
-

I see nothing wrong with this issue. It is a sound improvement.

And the patch looks equally fine.

We don't need discuss a trivial aspect like the validation of choices. There 
are lots of best practices that can be found. It only needs one to start with. 
The rest can be covered through follow-up JIRA issues.

I don't believe we need contributors second-guessing their judgement after they 
have created their issues with the best of intentions, by doing a do-over of 
the issue in a mail thread in the dev mailing list.

The only thing I find missing in the patch is addressing the properties for 
multi-tenant usage, meaning an enhancement of the seed data set with respect to 
the SystemProperty value(s) desired. See OFBIZ-6164

> 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] [Updated] (OFBIZ-6189) Have configuration options for accounting

[Pierre Smits (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated OFBIZ-6189:

Assignee: (was: Pierre Smits)

> Have configuration options for accounting
> -
>
> Key: OFBIZ-6189
> URL: https://issues.apache.org/jira/browse/OFBIZ-6189
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: accounting
>Affects Versions: Trunk
>Reporter: Pierre Smits
>  Labels: configuration, multi-tenant
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OFBIZ-5522) Introduce websocket usage

[morten vermund (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-5522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15371231#comment-15371231
 ] 

morten vermund commented on OFBIZ-5522:
---

kreditkort i danmark http://www.kreditkort365.dk


Billigaste lån http://www.billigalaan.se/billigaste-lan


Låna pengar nu  http://www.billigalaan.se/lana-pengar-nu


lån penge i sverige http://www.laan-365.dk 

> Introduce websocket usage
> -
>
> Key: OFBIZ-5522
> URL: https://issues.apache.org/jira/browse/OFBIZ-5522
> Project: OFBiz
>  Issue Type: Task
>  Components: framework
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Minor
>
> After a discussion with Ean, was suggested (draft here):
> You need a service that lets you "subscribe" a widget to an entity and
> then propagate change events to the widget as the entity is modified.
> A generic mechanism like that could eventually expand to be a general
> purpose "data bound widgets" system that mostly looks like the existing
> system but magically reflects updates.
> Could be used with/for
> * The entity cache and webforms to automatically update views when data 
> changes. 
> * Replaces the current system notes
> * Create a dashboard type pages  (to be discussed futher)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (OFBIZ-7532) Form Display Field improvement to manage multiple number format

[Pierre Smits (JIRA)]

[ 
https://issues.apache.org/jira/browse/OFBIZ-7532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15371096#comment-15371096
 ] 

Pierre Smits edited comment on OFBIZ-7532 at 7/11/16 4:25 PM:
--

I see nothing wrong with this issue. It is a sound improvement.

And the patch looks equally fine.

We don't need to discuss a trivial aspect like the validation of choices. There 
are lots of best practices that can be found. It only needs one to start with. 
The rest can be covered through follow-up JIRA issues.

I don't believe we need contributors second-guessing their judgement after they 
have created their issues with the best of intentions, by doing a do-over of 
the issue in a mail thread in the dev mailing list.

The only thing I find missing in the patch is addressing the properties for 
multi-tenant usage, meaning an enhancement of the seed data set with respect to 
the SystemProperty value(s) desired. See OFBIZ-6164


was (Author: pfm.smits):
I see nothing wrong with this issue. It is a sound improvement.

And the patch looks equally fine.

We don't need discuss a trivial aspect like the validation of choices. There 
are lots of best practices that can be found. It only needs one to start with. 
The rest can be covered through follow-up JIRA issues.

I don't believe we need contributors second-guessing their judgement after they 
have created their issues with the best of intentions, by doing a do-over of 
the issue in a mail thread in the dev mailing list.

The only thing I find missing in the patch is addressing the properties for 
multi-tenant usage, meaning an enhancement of the seed data set with respect to 
the SystemProperty value(s) desired. See OFBIZ-6164

> 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] [Updated] (OFBIZ-6670) Have configuration options for Content.

[Pierre Smits (JIRA)]

 [ 
https://issues.apache.org/jira/browse/OFBIZ-6670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pierre Smits updated OFBIZ-6670:

Assignee: (was: Pierre Smits)

> Have configuration options for Content.
> ---
>
> Key: OFBIZ-6670
> URL: https://issues.apache.org/jira/browse/OFBIZ-6670
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: content
>Affects Versions: Trunk
>Reporter: Pierre Smits
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)