Re: Bootstrap in framework folder

[Julien NICOLAS]

Le 02/06/2015 07:16, Taher Alkhateeb a écrit :

Hi Julien,

I remember in the earlier days of discussion on integrating bootstrap that you 
were the one who initially hesitated about putting bootstrap in the framework 
and you wanted the whole thing isolated outside in the theme
No, I was against to have menu and other html standard structure in the 
framework.



  (the description of OFBIZ-5840 shows that).

Are there any difficulties that you encountered which made you reconsider 
integrating at the framework level? Why not just apply classes to whatever you 
have in the framework (login screen etc) and then let CSS do its magic?
It could be interesting to have it in the framework to be able to add 
some tools. I just think about this kind of charts :
http://ironsummitmedia.github.io/startbootstrap-sb-admin-2/pages/index.html 
(area chart, bar chart and donut chart)


I plan to add each charts as a easy to use tool. And I think it could be 
logical to use a framework tool (bootstrap) and not a tool in an 
external theme for rendering...


Maybe I have to know what are the criteria to add something in the 
framework :)


Thanks for your help :)

Julien.


Taher Alkhateeb

- Original Message -

From: "Adrian Crum" 
To: dev@ofbiz.apache.org
Sent: Tuesday, 2 June, 2015 8:07:45 AM
Subject: Re: Bootstrap in framework folder

There is no need to put bootstrap in the framework folder. Any code that
needs it can use the one in the bootstrap theme.

Adrian Crum
Sandglass Software
www.sandglass-software.com

On 6/1/2015 12:45 PM, Julien NICOLAS wrote:

Hello,

I'm working on the bootstrap theme branch and I have a question that
seems to need a full topic.

I want to move the bootstrap framework from the theme folder to
ofbizroot/framework/image/webapp/image.

Why ?
Just because if we need any bootstrap rendering, it will be available in
the framework.
Even if it's for core tools.

I don't want to replace old theme but I want to be allow to use
bootstrap framework anywhere in the software :
- For the login page
- For charts widget
- For new theme

Want do you think ?

Thanks,

Julien.

Re: Bootstrap in framework folder

[Pierre Smits]

Having the theme behave as a self contained component gives you
configurability and flexibility. See
https://issues.apache.org/jira/browse/OFBIZ-6362. The Bootstrap theme can
be treated as such.

Best regards,

Pierre Smits

*ORRTIZ.COM *
Services & Solutions for Cloud-
Based Manufacturing, Professional
Services and Retail & Trade
http://www.orrtiz.com

On Tue, Jun 2, 2015 at 8:03 AM, Gavin Mabie  wrote:

> Hi Julien
>
> This idea was proposed before and it did not find favour with the community
> (including yourself). Anyway moving bootstrap theme resources to the
> framework container will not solve the login page issue. This is because
> the theme resources are linked to use preferences.  So when there is no
> logged in session Ofbiz uses the default theme which is defined in
> general.properties. try changing you default theme to bootstrap.
>
> Regards
>
> Gavin
> On 01 Jun 2015 9:46 PM, "Julien NICOLAS"  wrote:
> >
> > Hello,
> >
> > I'm working on the bootstrap theme branch and I have a question that
> seems to need a full topic.
> >
> > I want to move the bootstrap framework from the theme folder to
> ofbizroot/framework/image/webapp/image.
> >
> > Why ?
> > Just because if we need any bootstrap rendering, it will be available in
> the framework.
> > Even if it's for core tools.
> >
> > I don't want to replace old theme but I want to be allow to use bootstrap
> framework anywhere in the software :
> > - For the login page
> > - For charts widget
> > - For new theme
> >
> > Want do you think ?
> >
> > Thanks,
> >
> > Julien.
> >
> >
>

Re: Bootstrap in framework folder

[Gavin Mabie]

Hi Julien

This idea was proposed before and it did not find favour with the community
(including yourself). Anyway moving bootstrap theme resources to the
framework container will not solve the login page issue. This is because
the theme resources are linked to use preferences.  So when there is no
logged in session Ofbiz uses the default theme which is defined in
general.properties. try changing you default theme to bootstrap.

Regards

Gavin
On 01 Jun 2015 9:46 PM, "Julien NICOLAS"  wrote:
>
> Hello,
>
> I'm working on the bootstrap theme branch and I have a question that
seems to need a full topic.
>
> I want to move the bootstrap framework from the theme folder to
ofbizroot/framework/image/webapp/image.
>
> Why ?
> Just because if we need any bootstrap rendering, it will be available in
the framework.
> Even if it's for core tools.
>
> I don't want to replace old theme but I want to be allow to use bootstrap
framework anywhere in the software :
> - For the login page
> - For charts widget
> - For new theme
>
> Want do you think ?
>
> Thanks,
>
> Julien.
>
>

Re: Less stylesheet language (branch bootstrap)

[Taher Alkhateeb]

Hi Julien, 

Do you plan to use CSS preprocessors at runtime with a preprocessor engine or 
do you just plan to use them to spit out CSS and save it in the themes? If the 
case is the latter I see no reason to incorporate into the framework. 

Taher Alkhateeb 

- Original Message -

From: "Julien NICOLAS"  
To: "OFBiz Dev"  
Sent: Monday, 1 June, 2015 11:13:13 PM 
Subject: Less stylesheet language (branch bootstrap) 

Hello, 

I want to find a way to include the less stylesheet language. 
It's possible to use it by including less.js script but I'm not sure 
this is the most effective method. 

It could be possible to include the less compilator in ant. 

Is anybody already try to include less compilator in OFBiz ? 

Julien. 

Re: Font awesome in framework folder (branch bootstrap)

[Taher Alkhateeb]

Hi Julien, 

Font awesome is AWESOME! Good idea to incorporate, but again, why at the 
framework level and not the theme level just as in bootstrap? 

Regards, 

- Original Message -

From: "Julien NICOLAS"  
To: "OFBiz Dev"  
Sent: Monday, 1 June, 2015 10:50:34 PM 
Subject: Font awesome in framework folder (branch bootstrap) 

Hi, 

I'm using font awesome for my current projects. 
>From the official website : "Font Awesome gives you scalable vector 
icons that can instantly be customized — size, color, drop shadow, and 
anything that can be done with the power of CSS." 

So it's very useful for a good looking GUI :) 

Do you think it could be possible to push it in the 
OFBizRoot/framework/images/webapp/images folder ? 

Julien. 

Re: Bootstrap in framework folder

[Taher Alkhateeb]

Hi Julien, 

I remember in the earlier days of discussion on integrating bootstrap that you 
were the one who initially hesitated about putting bootstrap in the framework 
and you wanted the whole thing isolated outside in the theme (the description 
of OFBIZ-5840 shows that). 

Are there any difficulties that you encountered which made you reconsider 
integrating at the framework level? Why not just apply classes to whatever you 
have in the framework (login screen etc) and then let CSS do its magic? 

Taher Alkhateeb 

- Original Message -

From: "Adrian Crum"  
To: dev@ofbiz.apache.org 
Sent: Tuesday, 2 June, 2015 8:07:45 AM 
Subject: Re: Bootstrap in framework folder 

There is no need to put bootstrap in the framework folder. Any code that 
needs it can use the one in the bootstrap theme. 

Adrian Crum 
Sandglass Software 
www.sandglass-software.com 

On 6/1/2015 12:45 PM, Julien NICOLAS wrote: 
> Hello, 
> 
> I'm working on the bootstrap theme branch and I have a question that 
> seems to need a full topic. 
> 
> I want to move the bootstrap framework from the theme folder to 
> ofbizroot/framework/image/webapp/image. 
> 
> Why ? 
> Just because if we need any bootstrap rendering, it will be available in 
> the framework. 
> Even if it's for core tools. 
> 
> I don't want to replace old theme but I want to be allow to use 
> bootstrap framework anywhere in the software : 
> - For the login page 
> - For charts widget 
> - For new theme 
> 
> Want do you think ? 
> 
> Thanks, 
> 
> Julien. 
> 
> 

Re: Bootstrap in framework folder

[Adrian Crum]

There is no need to put bootstrap in the framework folder. Any code that 
needs it can use the one in the bootstrap theme.


Adrian Crum
Sandglass Software
www.sandglass-software.com

On 6/1/2015 12:45 PM, Julien NICOLAS wrote:

Hello,

I'm working on the bootstrap theme branch and I have a question that
seems to need a full topic.

I want to move the bootstrap framework from the theme folder to
ofbizroot/framework/image/webapp/image.

Why ?
Just because if we need any bootstrap rendering, it will be available in
the framework.
Even if it's for core tools.

I don't want to replace old theme but I want to be allow to use
bootstrap framework anywhere in the software :
 - For the login page
 - For charts widget
 - For new theme

Want do you think ?

Thanks,

Julien.

[jira] [Commented] (OFBIZ-6436) Different price Order vs. Invoice due rounding

[Scott Gray (JIRA)]

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

Scott Gray commented on OFBIZ-6436:
---

Order rounding and unit price rounding are not the same thing, please do not 
apply this patch.

Typically order amounts are rounded as late as possible in order to gain the 
most accurate order total possible.  I'm not sure why the invoice items are 
calculating to 2dp, they should be going to 3dp the same as order items and 
then being rounded for the invoice total only.  This strategy increases the 
accuracy of invoice amounts when an order is broken into multiple invoices.

> Different price Order vs. Invoice due rounding
> --
>
> Key: OFBIZ-6436
> URL: https://issues.apache.org/jira/browse/OFBIZ-6436
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk
>Reporter: Ingo Wolfmayr
>Assignee: Michael Brohl
> Attachments: priceservices.patch
>
>
> When creating an order with the following data, invoice and order calculates 
> different prices due to different rounding strategies:
> Example:
> Net price: 8,70
> Price Rule: 2 %
> Calc price: 8,526
> Order quantity: 2
> Rounding order: 2 dec
> Rounding invoice: 2 dec
> Both: ROUND_HALF_UP
> Calculation for order price:
> 8,526 * 2 = 17,052 --> Rouning = 17,05 (rounding takes place after multipying 
> with the order quantity )
> Calculation for invoice price:
> 8,53 * 2 = 17,06 (rounding takes place before multipying with the order  
> quantity)
> Rounding takes place on different places and leads to (from my understanding) 
> misscalculation.
> I create a patch that applies rounding on PriceCalculation level. Therefore:
> 1) get singe unit price and do all calculations on it (Price rules ...)
> 2) before forwarding the price, apply rounding (ORDER SETTINGS) on single 
> unit price
> As the invoice calculation uses the unit price (if invoice is associate with 
> order) from ORDER_ITEM it will calculate with the already rounded value.
> Result: Order Price = Invoice Price
> I would appreciate any thought on it.



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

Less stylesheet language (branch bootstrap)

[Julien NICOLAS]

Hello,

I want to find a way to include the less stylesheet language.
It's possible to use it by including less.js script but I'm not sure 
this is the most effective method.


It could be possible to include the less compilator in ant.

Is anybody already try to include less compilator in OFBiz ?

Julien.

Font awesome in framework folder (branch bootstrap)

[Julien NICOLAS]

Hi,

I'm using font awesome for my current projects.
From the official website : "Font Awesome gives you scalable vector 
icons that can instantly be customized — size, color, drop shadow, and 
anything that can be done with the power of CSS."


So it's very useful for a good looking GUI :)

Do you think it could be possible to push it in the 
OFBizRoot/framework/images/webapp/images folder ?


Julien.

Bootstrap in framework folder

[Julien NICOLAS]

Hello,

I'm working on the bootstrap theme branch and I have a question that 
seems to need a full topic.


I want to move the bootstrap framework from the theme folder to 
ofbizroot/framework/image/webapp/image.


Why ?
Just because if we need any bootstrap rendering, it will be available in 
the framework.

Even if it's for core tools.

I don't want to replace old theme but I want to be allow to use 
bootstrap framework anywhere in the software :

- For the login page
- For charts widget
- For new theme

Want do you think ?

Thanks,

Julien.

[jira] [Commented] (OFBIZ-6427) Implement FindService record grouping/summarization functionality

[Christian Carlow (JIRA)]

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

Christian Carlow commented on OFBIZ-6427:
-

Another part of this that needs to be handled, perhaps by a separate issue 
dependent on this one, is the ability to hide detail records and show only the 
group summaries.

> Implement FindService record grouping/summarization functionality
> -
>
> Key: OFBIZ-6427
> URL: https://issues.apache.org/jira/browse/OFBIZ-6427
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Christian Carlow
> Attachments: OFBIZ-6427_poc.patch, screen1.png, screen2.png
>
>
> Just as sortSeq and sortDir will be added to find fields like ignoreCase is 
> available, groupBy check box would also enhance user query capabilities.  
> FindService would have to be extended to process the list and create 
> group/summary records.
> For example, if a grid/form lists customer orders and the user wants to 
> determine the total quantity and price of products ordered between a date 
> range, then check marking the groupBy for productId would insert a grouping 
> record before the details containing totals.
> This issue is primarily meant to handle reports for which pagination isn't 
> used because all records are displayed.  For these reports queries, group 
> totals can simply be calculated by looping each detail record.  But if 
> pagination is used, the method of calculating totals for grouping records 
> becomes more complicated because if detail records exist outside of the 
> current page but are part of a group being summarized then they will be 
> excluded from the group total unless implemented some other way.



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

Framework Architecture

[Ron Wheeler]

If there is an interest in redoing the framework or upgrading it or 
changing the base technology and the application interface, perhaps this 
is something that should be investigated to see if it simplifies the 
process and adds an optimization layer that we don't have to write.


Ron


 Forwarded Message 
From:   - Mon Jun 01 11:37:38 2015
X-Account-Key:  account4
X-UIDL: 0010f909471c11b5
X-Mozilla-Status:   0001
X-Mozilla-Status2:  
X-Mozilla-Keys: 
Return-Path: 


X-Original-To:  rwhee...@artifact-software.com
Delivered-To:   rwhee...@artifact-software.com
Received: 	from localhost (localhost.localdomain [127.0.0.1]) by 
smtp.artifact-software.com (Postfix) with ESMTP id 1D40F6A657F for 
; Mon, 1 Jun 2015 11:34:50 -0400 (EDT)

X-Virus-Scanned:amavisd-new at artifact-software.com
Received: 	from smtp.artifact-software.com ([127.0.0.1]) by localhost 
(smtp.artifact-software.com [127.0.0.1]) (amavisd-new, port 10024) with 
ESMTP id HyInAOj1ZKaX for ; Mon, 1 Jun 
2015 11:34:48 -0400 (EDT)
Received: 	from mail.apache.org (hermes.apache.org [140.211.11.3]) by 
smtp.artifact-software.com (Postfix) with SMTP id D7AFA6A657E for 
; Mon, 1 Jun 2015 11:34:47 -0400 (EDT)

Received:   (qmail 36279 invoked by uid 500); 1 Jun 2015 15:34:37 -
Mailing-List:   contact announce-h...@apache.org; run by ezmlm
Precedence: bulk
List-Help:  
List-Unsubscribe:   
List-Post:  
List-Id:
Delivered-To:   mailing list annou...@apache.org
Delivered-To:   moderator for annou...@apache.org
Received:   (qmail 39773 invoked by uid 99); 1 Jun 2015 06:47:06 -
MIME-Version:   1.0
X-Received: 	by 10.202.218.132 with SMTP id 
r126mr15814831oig.69.1433141224794; Sun, 31 May 2015 23:47:04 -0700 (PDT)

Date:   Sun, 31 May 2015 23:47:04 -0700
Message-ID: 


Subject:[ANNOUNCE] Apache Calcite 1.3.0 (incubating) released
From:   Julian Hyde 
To: annou...@apache.org
Cc: d...@calcite.incubator.apache.org
Content-Type:   multipart/alternative; boundary=001a113d5dfa9df0c805176f3127



The Apache Calcite team is pleased to announce the release ofApache 
Calcite 1.3.0 (incubating).
Calcite is a dynamic data management framework. Its cost-basedoptimizer 
converts queries, represented in relational algebra,into executable 
plans. Calcite supports many front-end languagesand back-end data 
engines, and includes an SQL parser and theAvatica JDBC driver.

The release is available here:
http://www.apache.org/dyn/closer.cgi/incubator/calcite/apache-calcite-1.3.0-incubating/
and the release notes here:
http://calcite.incubator.apache.org/docs/history.html#v1-3-0
We welcome your help and feedback. For more information on how toreport 
problems, and to get involved, visit the project website at

http://calcite.incubator.apache.org
(We just revised the website. Hope you like the new look!)
Julian Hyde, on behalf of the Apache Calcite Team

Disclaimer: Apache Calcite is an effort undergoing incubation at 
TheApache Software Foundation (ASF), sponsored by Apache 
Incubator.Incubation is required of all newly accepted projects until a 
furtherreview indicates that the infrastructure, communications, and 
decisionmaking process have stabilized in a manner consistent with 
othersuccessful ASF projects. While incubation status is not necessarily 
areflection of the completeness or stability of the code, it 
doesindicate that the project has yet to be fully endorsed by the ASF.

Framework Architecture

[Ron Wheeler]

If there is an interest in redoing the framework or upgrading it or 
changing the base technology and the application interface, perhaps this 
is something that should be investigated to see if it simplifies the 
process and adds an optimization layer that we don't have to write.


Ron


 Forwarded Message 

The Apache Calcite team is pleased to announce the release ofApache 
Calcite 1.3.0 (incubating).
Calcite is a dynamic data management framework. Its cost-basedoptimizer 
converts queries, represented in relational algebra,into executable 
plans. Calcite supports many front-end languagesand back-end data 
engines, and includes an SQL parser and theAvatica JDBC driver.

The release is available here:
http://www.apache.org/dyn/closer.cgi/incubator/calcite/apache-calcite-1.3.0-incubating/
and the release notes here:
http://calcite.incubator.apache.org/docs/history.html#v1-3-0
We welcome your help and feedback. For more information on how toreport 
problems, and to get involved, visit the project website at

http://calcite.incubator.apache.org
(We just revised the website. Hope you like the new look!)
Julian Hyde, on behalf of the Apache Calcite Team

Disclaimer: Apache Calcite is an effort undergoing incubation at 
TheApache Software Foundation (ASF), sponsored by Apache 
Incubator.Incubation is required of all newly accepted projects until a 
furtherreview indicates that the infrastructure, communications, and 
decisionmaking process have stabilized in a manner consistent with 
othersuccessful ASF projects. While incubation status is not necessarily 
areflection of the completeness or stability of the code, it 
doesindicate that the project has yet to be fully endorsed by the ASF.

[jira] [Created] (OFBIZ-6438) PartyGeoLocation shows menus when accessed

[Pierre Smits (JIRA)]

Pierre Smits created OFBIZ-6438:
---

 Summary: PartyGeoLocation shows menus when accessed
 Key: OFBIZ-6438
 URL: https://issues.apache.org/jira/browse/OFBIZ-6438
 Project: OFBiz
  Issue Type: Bug
  Components: party
Affects Versions: Trunk
Reporter: Pierre Smits


When viewing the PartyGeoLocation of a party profile, the screen shows the 
standard set of screens (menus, etc) in stead of just the geo map.



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

[jira] [Comment Edited] (OFBIZ-6427) Implement FindService record grouping/summarization functionality

[Christian Carlow (JIRA)]

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

Christian Carlow edited comment on OFBIZ-6427 at 6/1/15 4:05 PM:
-

Attached are some screenshots of the POC patch.

Multi-sort capability was provided with sort sequence dropdown where lowest 
number indicates first sort.  A sort direction dropdown was also provided with 
the sort sequence which is ascending by default.  If a sort sequence isn't 
chosen then the field is ignored.

If a sort sequence is chosen then it activates the group checking 
functionality.  Fields are set to be grouped with the group style dropdown and 
"group-row" is the only 1 available so far.  

Group functions are listed as table rows at the end of each find field row and 
have sequence dropdowns that activate the group function and specify the order 
in which they should appear in the group's summary field.  Function expression 
text boxes are provided for each group function sequence dropdowns so that 
end-users can control what appears for each specific grouping function.  The 
expression text by default is set to:
{code}
" ${functionValue}". 
{code}. The functionValue expression is replaced with whatever is calculated 
during the find service.

Right now the grouping functionality is integrated into 
FindServices.performFindList but may be provided as a separate function.


was (Author: ofbizzer):
Attached are some screenshots of the POC patch.

Multi-sort capability was provided with sort sequence dropdown where lowest 
number indicates first sort.  A sort direction dropdown was also provided with 
the sort sequence which is ascending by default.  If a sort sequence isn't 
chosen then the field is ignored.

If a sort sequence is chosen then it activates the group checking 
functionality.  Fields are set to be grouped with the group style dropdown and 
"group-row" is the only 1 available so far.  

Group functions are listed as table rows at the end of each find field row and 
have sequence dropdowns that activate the group function and specify the order 
in which they should appear in the group's summary field.  Function expression 
text boxes are provided for each group function sequence dropdowns so that 
end-users can control what appears for each specific grouping function.  The 
expression text by default is set to:
{code}
" ${functionValue}".  ${functionValue} 
{code}. The functionValue expression is replaced with whatever is calculated 
during the find service.

Right now the grouping functionality is integrated into 
FindServices.performFindList but may be provided as a separate function.

> Implement FindService record grouping/summarization functionality
> -
>
> Key: OFBIZ-6427
> URL: https://issues.apache.org/jira/browse/OFBIZ-6427
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Christian Carlow
> Attachments: OFBIZ-6427_poc.patch, screen1.png, screen2.png
>
>
> Just as sortSeq and sortDir will be added to find fields like ignoreCase is 
> available, groupBy check box would also enhance user query capabilities.  
> FindService would have to be extended to process the list and create 
> group/summary records.
> For example, if a grid/form lists customer orders and the user wants to 
> determine the total quantity and price of products ordered between a date 
> range, then check marking the groupBy for productId would insert a grouping 
> record before the details containing totals.
> This issue is primarily meant to handle reports for which pagination isn't 
> used because all records are displayed.  For these reports queries, group 
> totals can simply be calculated by looping each detail record.  But if 
> pagination is used, the method of calculating totals for grouping records 
> becomes more complicated because if detail records exist outside of the 
> current page but are part of a group being summarized then they will be 
> excluded from the group total unless implemented some other way.



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

[jira] [Comment Edited] (OFBIZ-6427) Implement FindService record grouping/summarization functionality

[Christian Carlow (JIRA)]

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

Christian Carlow edited comment on OFBIZ-6427 at 6/1/15 4:05 PM:
-

Attached are some screenshots of the POC patch.

Multi-sort capability was provided with sort sequence dropdown where lowest 
number indicates first sort.  A sort direction dropdown was also provided with 
the sort sequence which is ascending by default.  If a sort sequence isn't 
chosen then the field is ignored.

If a sort sequence is chosen then it activates the group checking 
functionality.  Fields are set to be grouped with the group style dropdown and 
"group-row" is the only 1 available so far.  

Group functions are listed as table rows at the end of each find field row and 
have sequence dropdowns that activate the group function and specify the order 
in which they should appear in the group's summary field.  Function expression 
text boxes are provided for each group function sequence dropdowns so that 
end-users can control what appears for each specific grouping function.  The 
expression text by default is set to:
{code}
" ${functionValue}".  ${functionValue} 
{code}. The functionValue expression is replaced with whatever is calculated 
during the find service.

Right now the grouping functionality is integrated into 
FindServices.performFindList but may be provided as a separate function.


was (Author: ofbizzer):
Attached are some screenshots of the POC patch.

Multi-sort capability was provided with sort sequence dropdown where lowest 
number indicates first sort.  A sort direction dropdown was also provided with 
the sort sequence which is ascending by default.  If a sort sequence isn't 
chosen then the field is ignored.

If a sort sequence is chosen then it activates the group checking 
functionality.  Fields are set to be grouped with the group style dropdown and 
"group-row" is the only 1 available so far.  

Group functions are listed as table rows at the end of each find field row and 
have sequence dropdowns that activate the group function and specify the order 
in which they should appear in the group's summary field.  Function expression 
text boxes are provided for each group function sequence dropdowns so that 
end-users can control what appears for each specific grouping function.  By the 
expression text is 
{code}
" ${functionValue}".  ${functionValue} 
{code} is replaced with whatever is calculated during the find service.

Right now the grouping functionality is integrated into 
FindServices.performFindList but may be provided as a separate function.

> Implement FindService record grouping/summarization functionality
> -
>
> Key: OFBIZ-6427
> URL: https://issues.apache.org/jira/browse/OFBIZ-6427
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Christian Carlow
> Attachments: OFBIZ-6427_poc.patch, screen1.png, screen2.png
>
>
> Just as sortSeq and sortDir will be added to find fields like ignoreCase is 
> available, groupBy check box would also enhance user query capabilities.  
> FindService would have to be extended to process the list and create 
> group/summary records.
> For example, if a grid/form lists customer orders and the user wants to 
> determine the total quantity and price of products ordered between a date 
> range, then check marking the groupBy for productId would insert a grouping 
> record before the details containing totals.
> This issue is primarily meant to handle reports for which pagination isn't 
> used because all records are displayed.  For these reports queries, group 
> totals can simply be calculated by looping each detail record.  But if 
> pagination is used, the method of calculating totals for grouping records 
> becomes more complicated because if detail records exist outside of the 
> current page but are part of a group being summarized then they will be 
> excluded from the group total unless implemented some other way.



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

[jira] [Comment Edited] (OFBIZ-6427) Implement FindService record grouping/summarization functionality

[Christian Carlow (JIRA)]

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

Christian Carlow edited comment on OFBIZ-6427 at 6/1/15 4:03 PM:
-

Attached are some screenshots of the POC patch.

Multi-sort capability was provided with sort sequence dropdown where lowest 
number indicates first sort.  A sort direction dropdown was also provided with 
the sort sequence which is ascending by default.  If a sort sequence isn't 
chosen then the field is ignored.

If a sort sequence is chosen then it activates the group checking 
functionality.  Fields are set to be grouped with the group style dropdown and 
"group-row" is the only 1 available so far.  

Group functions are listed as table rows at the end of each find field row and 
have sequence dropdowns that activate the group function and specify the order 
in which they should appear in the group's summary field.  Function expression 
text boxes are provided for each group function sequence dropdowns so that 
end-users can control what appears for each specific grouping function.  By the 
expression text is 
{code}
" ${functionValue}".  ${functionValue} 
{code} is replaced with whatever is calculated during the find service.

Right now the grouping functionality is integrated into 
FindServices.performFindList but may be provided as a separate function.


was (Author: ofbizzer):
Attached are some screenshots of the POC patch.

Multi-sort capability was provided with sort sequence dropdown where lowest 
number indicates first sort.  A sort direction dropdown was also provided with 
the sort sequence which is ascending by default.  If a sort sequence isn't 
chosen then the field is ignored.

If a sort sequence is chosen then it activates the group checking 
functionality.  Fields are set to be grouped with the group style dropdown and 
"group-row" is the only 1 available so far.  

Group functions are listed as table rows at the end of each find field row and 
have sequence dropdowns that activate the group function and specify the order 
in which they should appear in the group's summary field.  Function expression 
text boxes are provided for each group function sequence dropdowns so that 
end-users can control what appears for each specific grouping function.  By the 
expression text is " ${functionValue}".  ${functionValue} is 
replaced with whatever is calculated during the find service.

Right now the grouping functionality is integrated into 
FindServices.performFindList but may be provided as a separate function.

> Implement FindService record grouping/summarization functionality
> -
>
> Key: OFBIZ-6427
> URL: https://issues.apache.org/jira/browse/OFBIZ-6427
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Christian Carlow
> Attachments: OFBIZ-6427_poc.patch, screen1.png, screen2.png
>
>
> Just as sortSeq and sortDir will be added to find fields like ignoreCase is 
> available, groupBy check box would also enhance user query capabilities.  
> FindService would have to be extended to process the list and create 
> group/summary records.
> For example, if a grid/form lists customer orders and the user wants to 
> determine the total quantity and price of products ordered between a date 
> range, then check marking the groupBy for productId would insert a grouping 
> record before the details containing totals.
> This issue is primarily meant to handle reports for which pagination isn't 
> used because all records are displayed.  For these reports queries, group 
> totals can simply be calculated by looping each detail record.  But if 
> pagination is used, the method of calculating totals for grouping records 
> becomes more complicated because if detail records exist outside of the 
> current page but are part of a group being summarized then they will be 
> excluded from the group total unless implemented some other way.



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

[jira] [Updated] (OFBIZ-6427) Implement FindService record grouping/summarization functionality

[Christian Carlow (JIRA)]

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

Christian Carlow updated OFBIZ-6427:

Attachment: OFBIZ-6427_poc.patch

Resubmitting patch because it was missing the theme and widget enhancements.  
Hopefully I'm not too out-of-sync with the trunk that the patch can't be easily 
applied and tested.

Again, this is a starting point and still needs a decent amount of work.  I'm 
not sure it its worthy of a separate branch while being developed.

Any feedback is appreciated.

> Implement FindService record grouping/summarization functionality
> -
>
> Key: OFBIZ-6427
> URL: https://issues.apache.org/jira/browse/OFBIZ-6427
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Christian Carlow
> Attachments: OFBIZ-6427_poc.patch, screen1.png, screen2.png
>
>
> Just as sortSeq and sortDir will be added to find fields like ignoreCase is 
> available, groupBy check box would also enhance user query capabilities.  
> FindService would have to be extended to process the list and create 
> group/summary records.
> For example, if a grid/form lists customer orders and the user wants to 
> determine the total quantity and price of products ordered between a date 
> range, then check marking the groupBy for productId would insert a grouping 
> record before the details containing totals.
> This issue is primarily meant to handle reports for which pagination isn't 
> used because all records are displayed.  For these reports queries, group 
> totals can simply be calculated by looping each detail record.  But if 
> pagination is used, the method of calculating totals for grouping records 
> becomes more complicated because if detail records exist outside of the 
> current page but are part of a group being summarized then they will be 
> excluded from the group total unless implemented some other way.



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

[jira] [Updated] (OFBIZ-6427) Implement FindService record grouping/summarization functionality

[Christian Carlow (JIRA)]

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

Christian Carlow updated OFBIZ-6427:

Attachment: (was: OFBIZ-6427_poc.patch)

> Implement FindService record grouping/summarization functionality
> -
>
> Key: OFBIZ-6427
> URL: https://issues.apache.org/jira/browse/OFBIZ-6427
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Christian Carlow
> Attachments: screen1.png, screen2.png
>
>
> Just as sortSeq and sortDir will be added to find fields like ignoreCase is 
> available, groupBy check box would also enhance user query capabilities.  
> FindService would have to be extended to process the list and create 
> group/summary records.
> For example, if a grid/form lists customer orders and the user wants to 
> determine the total quantity and price of products ordered between a date 
> range, then check marking the groupBy for productId would insert a grouping 
> record before the details containing totals.
> This issue is primarily meant to handle reports for which pagination isn't 
> used because all records are displayed.  For these reports queries, group 
> totals can simply be calculated by looping each detail record.  But if 
> pagination is used, the method of calculating totals for grouping records 
> becomes more complicated because if detail records exist outside of the 
> current page but are part of a group being summarized then they will be 
> excluded from the group total unless implemented some other way.



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

[jira] [Updated] (OFBIZ-6427) Implement FindService record grouping/summarization functionality

[Christian Carlow (JIRA)]

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

Christian Carlow updated OFBIZ-6427:

Attachment: screen2.png
screen1.png

Attached are some screenshots of the POC patch.

Multi-sort capability was provided with sort sequence dropdown where lowest 
number indicates first sort.  A sort direction dropdown was also provided with 
the sort sequence which is ascending by default.  If a sort sequence isn't 
chosen then the field is ignored.

If a sort sequence is chosen then it activates the group checking 
functionality.  Fields are set to be grouped with the group style dropdown and 
"group-row" is the only 1 available so far.  

Group functions are listed as table rows at the end of each find field row and 
have sequence dropdowns that activate the group function and specify the order 
in which they should appear in the group's summary field.  Function expression 
text boxes are provided for each group function sequence dropdowns so that 
end-users can control what appears for each specific grouping function.  By the 
expression text is " ${functionValue}".  ${functionValue} is 
replaced with whatever is calculated during the find service.

Right now the grouping functionality is integrated into 
FindServices.performFindList but may be provided as a separate function.

> Implement FindService record grouping/summarization functionality
> -
>
> Key: OFBIZ-6427
> URL: https://issues.apache.org/jira/browse/OFBIZ-6427
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Christian Carlow
> Attachments: OFBIZ-6427_poc.patch, screen1.png, screen2.png
>
>
> Just as sortSeq and sortDir will be added to find fields like ignoreCase is 
> available, groupBy check box would also enhance user query capabilities.  
> FindService would have to be extended to process the list and create 
> group/summary records.
> For example, if a grid/form lists customer orders and the user wants to 
> determine the total quantity and price of products ordered between a date 
> range, then check marking the groupBy for productId would insert a grouping 
> record before the details containing totals.
> This issue is primarily meant to handle reports for which pagination isn't 
> used because all records are displayed.  For these reports queries, group 
> totals can simply be calculated by looping each detail record.  But if 
> pagination is used, the method of calculating totals for grouping records 
> becomes more complicated because if detail records exist outside of the 
> current page but are part of a group being summarized then they will be 
> excluded from the group total unless implemented some other way.



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

[jira] [Updated] (OFBIZ-6427) Implement FindService record grouping/summarization functionality

[Christian Carlow (JIRA)]

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

Christian Carlow updated OFBIZ-6427:

Attachment: OFBIZ-6427_poc.patch

This patch is still a work in process and provided as a proof of concept.  As 
of right now the grouping functionality is only supported for TextFindFields 
and needs to be extended to the other find fields including drop downs which 
are the only find type field that may not be used as find so the xsd should 
probably be extended to indicate when a dropdown should be used as a find field 
or not.

The patch adds the multi sort functionality of OFBIZ-6428 upon which the 
grouping is dependent.  OFBIZ-6428 may be patched separately and extracted from 
this patch.

> Implement FindService record grouping/summarization functionality
> -
>
> Key: OFBIZ-6427
> URL: https://issues.apache.org/jira/browse/OFBIZ-6427
> Project: OFBiz
>  Issue Type: Improvement
>  Components: framework
>Affects Versions: Trunk
>Reporter: Christian Carlow
> Attachments: OFBIZ-6427_poc.patch
>
>
> Just as sortSeq and sortDir will be added to find fields like ignoreCase is 
> available, groupBy check box would also enhance user query capabilities.  
> FindService would have to be extended to process the list and create 
> group/summary records.
> For example, if a grid/form lists customer orders and the user wants to 
> determine the total quantity and price of products ordered between a date 
> range, then check marking the groupBy for productId would insert a grouping 
> record before the details containing totals.
> This issue is primarily meant to handle reports for which pagination isn't 
> used because all records are displayed.  For these reports queries, group 
> totals can simply be calculated by looping each detail record.  But if 
> pagination is used, the method of calculating totals for grouping records 
> becomes more complicated because if detail records exist outside of the 
> current page but are part of a group being summarized then they will be 
> excluded from the group total unless implemented some other way.



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

[jira] [Commented] (OFBIZ-6436) Different price Order vs. Invoice due rounding

[Ingo Wolfmayr (JIRA)]

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

Ingo Wolfmayr commented on OFBIZ-6436:
--

Hi Jacques, sorry I deleted it. BR Ingo



> Different price Order vs. Invoice due rounding
> --
>
> Key: OFBIZ-6436
> URL: https://issues.apache.org/jira/browse/OFBIZ-6436
> Project: OFBiz
>  Issue Type: Improvement
>Affects Versions: Release Branch 13.07, Release Branch 14.12, Trunk
>Reporter: Ingo Wolfmayr
>Assignee: Michael Brohl
> Attachments: priceservices.patch
>
>
> When creating an order with the following data, invoice and order calculates 
> different prices due to different rounding strategies:
> Example:
> Net price: 8,70
> Price Rule: 2 %
> Calc price: 8,526
> Order quantity: 2
> Rounding order: 2 dec
> Rounding invoice: 2 dec
> Both: ROUND_HALF_UP
> Calculation for order price:
> 8,526 * 2 = 17,052 --> Rouning = 17,05 (rounding takes place after multipying 
> with the order quantity )
> Calculation for invoice price:
> 8,53 * 2 = 17,06 (rounding takes place before multipying with the order  
> quantity)
> Rounding takes place on different places and leads to (from my understanding) 
> misscalculation.
> I create a patch that applies rounding on PriceCalculation level. Therefore:
> 1) get singe unit price and do all calculations on it (Price rules ...)
> 2) before forwarding the price, apply rounding (ORDER SETTINGS) on single 
> unit price
> As the invoice calculation uses the unit price (if invoice is associate with 
> order) from ORDER_ITEM it will calculate with the already rounded value.
> Result: Order Price = Invoice Price
> I would appreciate any thought on it.



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

[jira] [Updated] (OFBIZ-1599) Issues with tax adjustment precision (3 decimals) and AcctgTransEntry.amount field (2 decimal)

[Ingo Wolfmayr (JIRA)]

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

Ingo Wolfmayr updated OFBIZ-1599:
-
Attachment: (was: PriceService.patch)

> Issues with tax adjustment precision (3 decimals) and AcctgTransEntry.amount 
> field (2 decimal)
> --
>
> Key: OFBIZ-1599
> URL: https://issues.apache.org/jira/browse/OFBIZ-1599
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: accounting
>Reporter: Jacopo Cappellato
>Assignee: Jacques Le Roux
> Fix For: Trunk
>
> Attachments: Issue_1599.patch, Issue_1599.patch, Issue_1599.patch, 
> Issue_1599.patch, Issue_1599.patch
>
>
> On Jan 7, 2008, at 10:17 PM, Scott Gray wrote:
> > Perhaps we need to do 2 things:
> > 1. Summarize AcctgTransEntries so that you have one entry per TaxAuthority
> > rather than for each tax adjustment
> > 2. During order/invoice processing, calc and final should be applied on a
> > per TaxAuthority basis, so that we are only ever collecting final rounded
> > amounts for each tax authority.
> >
> > So for example if we have invoice with the following adjustments:
> > (I just made these numbers up, they don't relate to any percentages)
> > UT_TAXMAN - $4.311
> > UT_TAXMAN - $7.397
> > UT_UTAH_TAXMAN - $5.643
> > UT_UTAH_TAXMAN - $16.828
> >
> > Tax final would be calculated like this:
> > UT_TAXMAN - $4.311 + $7.399 = $11.71 (2dp)
> > UT_UTAH_TAXMAN - $5.643 + $16.828 = $22.47 (2dp)
> > Tax Total = $11.71 + $22.47 = $34.18
> >
> > Then the AcctgTransEntries would be:
> > UT_TAXMAN = $11.71
> > UT_UTAH_TAXMAN = $22.47
> >
> > Regards
> > Scott
> >
> >
> > On 08/01/2008, David E Jones  wrote:
> >>
> >>
> >> On Jan 7, 2008, at 11:04 AM, Scott Gray wrote:
> >>
> >>> Hi Jacopo
> >>>
> >>> My understanding of calc and final:
> >>> calc - adjustment level rounding
> >>> final - the sum of all tax adjustments (tax total) is rounded to this
> >>> precision
> >>>
> >>> Perhaps AcctgTransEntry.amount needs to store to a higher precision
> >>> as well?
> >>
> >> What Scott says above is correct as I understand it, but I'm not sure
> >> this last part is a good idea.
> >>
> >> Accounting/GL transactions are meant to be final and to avoid problems
> >> they are structured in a way where reporting just involves adding
> >> things up and using straight totals with no rounding, etc to avoid any
> >> biasing (with the exception of certain averages and such, but that is
> >> different as precision on those is used in a different way).
> >>
> >> It seems to me that posting anything to an accounting with more than 2
> >> decimals of precision seems like a bad idea to me, except perhaps the
> >> infamous "rounding remainder" accounts. We should probably consult
> >> with an accounting before doing much of that sort of thing, but of
> >> course if we do change the AcctgTransEntry.amount to be higher
> >> precision we can always configure/code around it.
> >>
> >> -David
> >>
> >>
> >>> On 08/01/2008, Jacopo Cappellato  wrote:
> 
>  While testing the GL accounting transactions I've found something
>  that
>  could be an issue in the procedure that computes the sales tax
>  adjustment for the invoice.
>  I've noticed that the InvoiceItem.amount for sales tax contains
>  sometimes a number with 3 decimals, even if the arithmetic.properties
>  file we have:
> 
>  salestax.calc.decimals = 3
>  salestax.final.decimals = 2
>  salestax.rounding = ROUND_HALF_UP
> 
>  You can recreate this by creating and invoicing a sales order for 3
>  units of GZ-1000.
> 
>  For example, look at this invoice:
> 
> 
> 
> >> https://demo.hotwaxmedia.com/accounting/control/invoiceOverview?invoiceId=CI1
> 
>  Having 3 decimals is an issue for the gl auto posting service for
>  sales
>  invoices because the sales tax item generates an AcctgTransEntry, but
>  the AcctgTransEntry.amount field can only store 2 decimals.
> 
>  I'd appreciate suggestions/hints.
> 
>  Cheers,
> 
>  Jacopo
> 
> >>
> >>
> >>



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

[jira] [Commented] (OFBIZ-5840) Create bootstrap theme

[Jacques Le Roux (JIRA)]

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

Jacques Le Roux commented on OFBIZ-5840:


+1

> Create bootstrap theme
> --
>
> Key: OFBIZ-5840
> URL: https://issues.apache.org/jira/browse/OFBIZ-5840
> Project: OFBiz
>  Issue Type: New Feature
>  Components: framework, themes
>Affects Versions: Bootstrap theme
>Reporter: Julien NICOLAS
>  Labels: bootstrap, theme
> Attachments: Facility.PNG, FindAgreement..png, Footer.jpg, 
> GlobalDecorator.patch, ImprovedFooter.patch, MacroMenuRenderer.patch, 
> OFBIZ-5840-Menufactory.patch, OFBIZ-5840-Menufactory.patch, 
> appbar_menu_ftl.patch, bootified.js, bootified_js_screentrans.patch, 
> bootstrap-theme.zip, bootstrap.zip, calendar.PNG, catalog.png, 
> htmlMenuMacroLibrary.patch, pagination_htmlFormMacroLibrary.patch, 
> panelCollapse_htmlSreenMacroLibrary.patch, party menu tab bar.PNG, 
> preferences.png, styling_issue_1.png, styling_issue_2.png, 
> styling_issue_3.png, styling_issue_4.png, styling_issue_5.png, 
> styling_issue_6.png, styling_issue_7.png, styling_issue_8.png, 
> styling_issue_9.png, tab-bar.png, workeffort.PNG
>
>
> 1- create a sub-directory called bootstrap under the image webapp to put
> the resources over there (js, css and fonts) as indicated earlier by Gavin.
> (Julien : not sure about location)
> 2- check to make sure that the current version of jQuery is compatible with
> the installed version or upgrade it accordingly
> 3- Create a new theme based on one of the existing themes as suggested by
> Julien and Gavin
> 4- Test the theme by switching to it and handle major bugs / issues.
> 5- Start to make a few test screens utilizing Bootstrap



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

[jira] [Commented] (OFBIZ-6326) Pagination doesn't render well in Bootstrap Basic

[Julien NICOLAS (JIRA)]

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

Julien NICOLAS commented on OFBIZ-6326:
---

Jacques & Pierre,

Good, it's difficult to find an Apple computer but easier to find Windows one :)
I'll check it asap.

Thanks 

> Pagination doesn't render well in Bootstrap Basic
> -
>
> Key: OFBIZ-6326
> URL: https://issues.apache.org/jira/browse/OFBIZ-6326
> Project: OFBiz
>  Issue Type: Sub-task
>  Components: themes
>Affects Versions: Bootstrap theme
>Reporter: Pierre Smits
>Assignee: Julien NICOLAS
>  Labels: pagination
> Fix For: Bootstrap theme
>
> Attachments: Image 068.png, Screen Shot 2015-05-30 at 14.52.17.png
>
>
> When accessing an overview page (e.g. /catalog/control/FindProduct) with more 
> than the default number of records to be shown, the pagination comes out 
> garbled.



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