[jira] [Closed] (OFBIZ-10031) Convert CategoryServices.xml mini lang to groovy
[ https://issues.apache.org/jira/browse/OFBIZ-10031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Le Roux closed OFBIZ-10031. --- Thanks Nicolas and Dennis, This was committed in trunk at r1822912, closing > Convert CategoryServices.xml mini lang to groovy > > > Key: OFBIZ-10031 > URL: https://issues.apache.org/jira/browse/OFBIZ-10031 > Project: OFBiz > Issue Type: Sub-task > Components: framework >Affects Versions: Trunk >Reporter: Dennis Balkir >Assignee: Nicolas Malin >Priority: Minor > Attachments: > OFBIZ-10031_org.apache.ofbiz.product.category.CategoryServices_convert.patch, > OFBIZ-10031_org.apache.ofbiz.product.category.CategoryServices_convert.patch > > > Migration of the CategoryServices.xml to Groovy -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10186) Configure official document templates for an organizational party
[ https://issues.apache.org/jira/browse/OFBIZ-10186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16351547#comment-16351547 ] Nicolas Malin commented on OFBIZ-10186: --- I push a new patch with the only the entity : * CustomScreen entity to manage different configurable screen * PartyPrefDocTypeTpl entity to link an organization party to a custom screen for a document type * A screen ListPartyPrefDocTypeTpl to manage that If no objection, I will commit on trunk. At this time a want just support invoice, order and quote but we can grow this solution on other document type. > Configure official document templates for an organizational party > - > > Key: OFBIZ-10186 > URL: https://issues.apache.org/jira/browse/OFBIZ-10186 > Project: OFBiz > Issue Type: New Feature > Components: accounting >Reporter: Nicolas Malin >Assignee: Nicolas Malin >Priority: Major > Labels: invoice, organization, template > Attachments: OFBIZ-10186.patch, OFBIZ-10186.patch, Sélection_134.png, > Sélection_135.png > > > For an organizational party, add possibility to give the specific template to > use for official document like invoice and order. > The first step is adding mechanism to indicate what template to use for a > party, for that : > * add CustomScreen entity (like CustomMethod) to prepare and organize your > screen by theme > * add PartyPrefDocTypeTpl as association entity between an organizational > party, a document type and a custom screen > For use case, I create a new invoice template for oriented on EU format (in > process) with VAT directly display on invoice item. > Related mailing list thread : > https://lists.apache.org/thread.html/4a5244e6d022564414e4f4a5676f72288d4000913ec2afa7e4af5e1a@%3Cdev.ofbiz.apache.org%3E > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OFBIZ-10186) Configure official document templates for an organizational party
[ https://issues.apache.org/jira/browse/OFBIZ-10186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Malin updated OFBIZ-10186: -- Attachment: OFBIZ-10186.patch > Configure official document templates for an organizational party > - > > Key: OFBIZ-10186 > URL: https://issues.apache.org/jira/browse/OFBIZ-10186 > Project: OFBiz > Issue Type: New Feature > Components: accounting >Reporter: Nicolas Malin >Assignee: Nicolas Malin >Priority: Major > Labels: invoice, organization, template > Attachments: OFBIZ-10186.patch, OFBIZ-10186.patch, Sélection_134.png, > Sélection_135.png > > > For an organizational party, add possibility to give the specific template to > use for official document like invoice and order. > The first step is adding mechanism to indicate what template to use for a > party, for that : > * add CustomScreen entity (like CustomMethod) to prepare and organize your > screen by theme > * add PartyPrefDocTypeTpl as association entity between an organizational > party, a document type and a custom screen > For use case, I create a new invoice template for oriented on EU format (in > process) with VAT directly display on invoice item. > Related mailing list thread : > https://lists.apache.org/thread.html/4a5244e6d022564414e4f4a5676f72288d4000913ec2afa7e4af5e1a@%3Cdev.ofbiz.apache.org%3E > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10196) Set security object on groovy context
[
https://issues.apache.org/jira/browse/OFBIZ-10196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16351403#comment-16351403
]
Nicolas Malin commented on OFBIZ-10196:
---
Ok finally it's easy, I added this for eclipse and intellij at revision
1823028. And on the same time, complete junit test
> Set security object on groovy context
> -
>
> Key: OFBIZ-10196
> URL: https://issues.apache.org/jira/browse/OFBIZ-10196
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
>Affects Versions: Trunk
>Reporter: Nicolas Malin
>Assignee: Nicolas Malin
>Priority: Minor
> Attachments: 10196.patch
>
>
> In a groovy service to call the security object you need to do :
> {code}Security security = dispatcher.dispatchContext.security{code}
> For simplification, I set the security object in groovy context like
> dispatcher and delegator
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OFBIZ-10164) Splitter Widget
[ https://issues.apache.org/jira/browse/OFBIZ-10164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16351340#comment-16351340 ] Taher Alkhateeb commented on OFBIZ-10164: - It's up to you, but you can perhaps update this Jira instead of creating a new one? And if you can do the entire thing in a theme, then i think common-theme might be the best candidate for that. > Splitter Widget > --- > > Key: OFBIZ-10164 > URL: https://issues.apache.org/jira/browse/OFBIZ-10164 > Project: OFBiz > Issue Type: New Feature > Components: framework >Affects Versions: Trunk >Reporter: James Yong >Assignee: James Yong >Priority: Minor > Fix For: Trunk > > Attachments: OFBIZ-10164.patch, OFBIZ-10164.patch, OFBIZ-10164.patch, > horizontal.png, vertical.png > > > A new splitter widget that will use a tag named 'splitter'. > This splitter tag has the following attributes: > a. sizes = [25, 75] where the containers within will be splitted with a ratio > of 25% and 75% > b. parentId which is the ID of the parent container > c. direction = vertical or horizonal (default) > The splitter tag can only contains container(s) as immediate child. > Using the library from http://nathancahill.github.io/Split.js/ which is > licensed under MIT license. > Update on 20180128: > 1) The patch comes with an example where you can view the splitter at > https://localhost:8443/catalog/control/main > 2) No need to add square brackets when defining sizes. > 3) parentId attribute is removed, -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OFBIZ-10196) Set security object on groovy context
[
https://issues.apache.org/jira/browse/OFBIZ-10196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16351309#comment-16351309
]
Nicolas Malin commented on OFBIZ-10196:
---
I don't use eclipse so it's will difficult to valid your proposal but sure +1 ;)
> Set security object on groovy context
> -
>
> Key: OFBIZ-10196
> URL: https://issues.apache.org/jira/browse/OFBIZ-10196
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
>Affects Versions: Trunk
>Reporter: Nicolas Malin
>Assignee: Nicolas Malin
>Priority: Minor
> Attachments: 10196.patch
>
>
> In a groovy service to call the security object you need to do :
> {code}Security security = dispatcher.dispatchContext.security{code}
> For simplification, I set the security object in groovy context like
> dispatcher and delegator
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
