Re: updatePostalAddress, updateTelecomNumber (contactMechs) missnamed ?

2018-02-26 Thread gil portenseigne 

Hello Deepak,

Nice Idea ! Thanks !

I think that we could have a new entity-auto invoke type, kind of 
"update-immutable" to manage the immutable case.


Then for the specific but existing need of PostalAddress fix (we met the 
need to fix a postalAddress without creating a new instance), we could 
use the basic invoce "update", with a serviceName (fixPostalAddress), 
with appropriate documentation for newcomers.


Regards,

Gil

On 24/02/2018 07:14, Deepak Dixit wrote:

Yes it may confuse but I think its correct, the basic rule is if you want
to update postal address (ContactMech) it will expire old one and create
new one with update. So Ideally PostalAddress is an immutable object where
you can;t do modification in it.

if you want to update you need to clone it and do update.

I think we can add this in entity auto engine so that it will be part of
entity auto framework.

Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com
www.hotwax.co

On Fri, Feb 23, 2018 at 8:11 PM, gil portenseigne <
gil.portensei...@nereide.fr> wrote:


Hello,

While working on a new contactMech type (no spoiler yet, that will come in
some days ;)), I wanted to develop the CRUD services , and stumbled upon
something that bother me.

Actually, when we update a contactMech in OFBiz, the service keep history
of it, to keep reference for related entity (like communicationEvent and
such). Thanks to that, old communication event/invoice/etc. refer to the
old contact mechanism.

That's fine with me, but what is bothering me is that updatePostalAddress
(and others) service is named like every auto-entity CRUD services within
OFBiz, that could be misleading for newcomers

I feel like we have to change the naming of these services. No good idea
yet about a new name... Am I the only one wondering about that ? Is that
fine to keep "udpate" in this context ?

WDYT ?

Gil


--
logoNrd 
 Gil PORTENSEIGNE
Intégrateur Apache-OFBiz, ERP en logiciel Libre
informat...@nereide.fr
8 rue des Déportés 37000 TOURS
02 47 50 30 54

| Réseau Libre Entreprise

Re: updatePostalAddress, updateTelecomNumber (contactMechs) missnamed ?

2018-02-23 Thread Rishi Solanki 
+1 Deepak!!

Rishi Solanki
Sr Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: +91-9893287847
http://www.hotwaxsystems.com
www.hotwax.co

On Sat, Feb 24, 2018 at 11:44 AM, Deepak Dixit <
deepak.di...@hotwaxsystems.com> wrote:

> Yes it may confuse but I think its correct, the basic rule is if you want
> to update postal address (ContactMech) it will expire old one and create
> new one with update. So Ideally PostalAddress is an immutable object where
> you can;t do modification in it.
>
> if you want to update you need to clone it and do update.
>
> I think we can add this in entity auto engine so that it will be part of
> entity auto framework.
>
> Thanks & Regards
> --
> Deepak Dixit
> www.hotwaxsystems.com
> www.hotwax.co
>
> On Fri, Feb 23, 2018 at 8:11 PM, gil portenseigne <
> gil.portensei...@nereide.fr> wrote:
>
> > Hello,
> >
> > While working on a new contactMech type (no spoiler yet, that will come
> in
> > some days ;)), I wanted to develop the CRUD services , and stumbled upon
> > something that bother me.
> >
> > Actually, when we update a contactMech in OFBiz, the service keep history
> > of it, to keep reference for related entity (like communicationEvent and
> > such). Thanks to that, old communication event/invoice/etc. refer to the
> > old contact mechanism.
> >
> > That's fine with me, but what is bothering me is that updatePostalAddress
> > (and others) service is named like every auto-entity CRUD services within
> > OFBiz, that could be misleading for newcomers
> >
> > I feel like we have to change the naming of these services. No good idea
> > yet about a new name... Am I the only one wondering about that ? Is that
> > fine to keep "udpate" in this context ?
> >
> > WDYT ?
> >
> > Gil
> >
> >
> > --
> > logoNrd 
> > Gil PORTENSEIGNE
> > Intégrateur Apache-OFBiz, ERP en logiciel Libre
> > informat...@nereide.fr
> > 8 rue des Déportés 37000 TOURS
> > 02 47 50 30 54
> >
> > | Réseau Libre Entreprise 
> >
> >
>

Re: updatePostalAddress, updateTelecomNumber (contactMechs) missnamed ?

2018-02-23 Thread Deepak Dixit 
Yes it may confuse but I think its correct, the basic rule is if you want
to update postal address (ContactMech) it will expire old one and create
new one with update. So Ideally PostalAddress is an immutable object where
you can;t do modification in it.

if you want to update you need to clone it and do update.

I think we can add this in entity auto engine so that it will be part of
entity auto framework.

Thanks & Regards
--
Deepak Dixit
www.hotwaxsystems.com
www.hotwax.co

On Fri, Feb 23, 2018 at 8:11 PM, gil portenseigne <
gil.portensei...@nereide.fr> wrote:

> Hello,
>
> While working on a new contactMech type (no spoiler yet, that will come in
> some days ;)), I wanted to develop the CRUD services , and stumbled upon
> something that bother me.
>
> Actually, when we update a contactMech in OFBiz, the service keep history
> of it, to keep reference for related entity (like communicationEvent and
> such). Thanks to that, old communication event/invoice/etc. refer to the
> old contact mechanism.
>
> That's fine with me, but what is bothering me is that updatePostalAddress
> (and others) service is named like every auto-entity CRUD services within
> OFBiz, that could be misleading for newcomers
>
> I feel like we have to change the naming of these services. No good idea
> yet about a new name... Am I the only one wondering about that ? Is that
> fine to keep "udpate" in this context ?
>
> WDYT ?
>
> Gil
>
>
> --
> logoNrd 
> Gil PORTENSEIGNE
> Intégrateur Apache-OFBiz, ERP en logiciel Libre
> informat...@nereide.fr
> 8 rue des Déportés 37000 TOURS
> 02 47 50 30 54
>
> | Réseau Libre Entreprise 
>
>

Re: updatePostalAddress, updateTelecomNumber (contactMechs) missnamed ?

2018-02-23 Thread pierre.gaudin 

Hi Gil,

Personally, I understand your point of view, but renaming service could 
have major impact to existing code...

May be we could add a parameter to keep or leave history.

regards

Pierre
On 23/02/2018 15:56, Taher Alkhateeb wrote:

perhaps updatePostalAddressWithHistory

On Fri, Feb 23, 2018 at 5:41 PM, gil portenseigne
 wrote:

Hello,

While working on a new contactMech type (no spoiler yet, that will come in
some days ;)), I wanted to develop the CRUD services , and stumbled upon
something that bother me.

Actually, when we update a contactMech in OFBiz, the service keep history of
it, to keep reference for related entity (like communicationEvent and such).
Thanks to that, old communication event/invoice/etc. refer to the old
contact mechanism.

That's fine with me, but what is bothering me is that updatePostalAddress
(and others) service is named like every auto-entity CRUD services within
OFBiz, that could be misleading for newcomers

I feel like we have to change the naming of these services. No good idea yet
about a new name... Am I the only one wondering about that ? Is that fine to
keep "udpate" in this context ?

WDYT ?

Gil


--
logoNrd 
 Gil PORTENSEIGNE
Intégrateur Apache-OFBiz, ERP en logiciel Libre
informat...@nereide.fr
8 rue des Déportés 37000 TOURS
02 47 50 30 54

| Réseau Libre Entreprise

Re: updatePostalAddress, updateTelecomNumber (contactMechs) missnamed ?

2018-02-23 Thread Taher Alkhateeb 
perhaps updatePostalAddressWithHistory

On Fri, Feb 23, 2018 at 5:41 PM, gil portenseigne
 wrote:
> Hello,
>
> While working on a new contactMech type (no spoiler yet, that will come in
> some days ;)), I wanted to develop the CRUD services , and stumbled upon
> something that bother me.
>
> Actually, when we update a contactMech in OFBiz, the service keep history of
> it, to keep reference for related entity (like communicationEvent and such).
> Thanks to that, old communication event/invoice/etc. refer to the old
> contact mechanism.
>
> That's fine with me, but what is bothering me is that updatePostalAddress
> (and others) service is named like every auto-entity CRUD services within
> OFBiz, that could be misleading for newcomers
>
> I feel like we have to change the naming of these services. No good idea yet
> about a new name... Am I the only one wondering about that ? Is that fine to
> keep "udpate" in this context ?
>
> WDYT ?
>
> Gil
>
>
> --
> logoNrd 
> Gil PORTENSEIGNE
> Intégrateur Apache-OFBiz, ERP en logiciel Libre
> informat...@nereide.fr
> 8 rue des Déportés 37000 TOURS
> 02 47 50 30 54
>
> | Réseau Libre Entreprise 
>

updatePostalAddress, updateTelecomNumber (contactMechs) missnamed ?

2018-02-23 Thread gil portenseigne 

Hello,

While working on a new contactMech type (no spoiler yet, that will come 
in some days ;)), I wanted to develop the CRUD services , and stumbled 
upon something that bother me.


Actually, when we update a contactMech in OFBiz, the service keep 
history of it, to keep reference for related entity (like 
communicationEvent and such). Thanks to that, old communication 
event/invoice/etc. refer to the old contact mechanism.


That's fine with me, but what is bothering me is that 
updatePostalAddress (and others) service is named like every auto-entity 
CRUD services within OFBiz, that could be misleading for newcomers


I feel like we have to change the naming of these services. No good idea 
yet about a new name... Am I the only one wondering about that ? Is that 
fine to keep "udpate" in this context ?


WDYT ?

Gil


--
logoNrd 
Gil PORTENSEIGNE
Intégrateur Apache-OFBiz, ERP en logiciel Libre
informat...@nereide.fr
8 rue des Déportés 37000 TOURS
02 47 50 30 54

| Réseau Libre Entreprise

[jira] [Commented] (OFBIZ-6856) ContactMechs Label

2016-01-28 Thread Julien NICOLAS (JIRA) 

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

Julien NICOLAS commented on OFBIZ-6856:
---

Yes, Nicolas ask me that it's better to apply it to 14 and 15 release :)

I'm not sure that it is an improvement, because the label ContactMech is not a 
normal sentence. So for me, it must be fixed.
Then, Contact Mech is not a good translation, and if I change it in the menu, I 
have to change it in the creation button.

And even it is an improvement, it's label improvement, not a big deal ;)

> ContactMechs Label
> --
>
> Key: OFBIZ-6856
> URL: https://issues.apache.org/jira/browse/OFBIZ-6856
> Project: OFBiz
>  Issue Type: Bug
>  Components: product
>Affects Versions: Trunk, 13.07.02
>Reporter: Julien NICOLAS
>Assignee: Julien NICOLAS
>Priority: Minor
> Fix For: 13.07.03, Upcoming Branch
>
> Attachments: JIRA6856-1307.patch, JIRA6856-1412.patch, 
> JIRA6856-1512.patch, JIRA6856.patch
>
>
> Is it normal that in facility, the label for contact information is named 
> "ContactMechs".
> I think it could be a mistake but I'm French and maybe I miss something.
> Anyway, I think this label must be "Contact Mechs" and if we want to 
> standardize the contact mech label, it must be "Contact Information"
> In the same way, if you select "ContactMechs", you can find the "New Contact 
> Mech" button that can be rename as "New contact information".
> What is your opinion ?



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

[jira] [Updated] (OFBIZ-6856) ContactMechs Label

2016-01-28 Thread Julien NICOLAS (JIRA) 

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

Julien NICOLAS updated OFBIZ-6856:
--
Attachment: JIRA6856-1412.patch

> ContactMechs Label
> --
>
> Key: OFBIZ-6856
> URL: https://issues.apache.org/jira/browse/OFBIZ-6856
> Project: OFBiz
>  Issue Type: Bug
>  Components: product
>Affects Versions: Trunk, 13.07.02
>Reporter: Julien NICOLAS
>Assignee: Julien NICOLAS
>Priority: Minor
> Fix For: 13.07.03, Upcoming Branch
>
> Attachments: JIRA6856-1307.patch, JIRA6856-1412.patch, JIRA6856.patch
>
>
> Is it normal that in facility, the label for contact information is named 
> "ContactMechs".
> I think it could be a mistake but I'm French and maybe I miss something.
> Anyway, I think this label must be "Contact Mechs" and if we want to 
> standardize the contact mech label, it must be "Contact Information"
> In the same way, if you select "ContactMechs", you can find the "New Contact 
> Mech" button that can be rename as "New contact information".
> What is your opinion ?



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

[jira] [Commented] (OFBIZ-6856) ContactMechs Label

2016-01-28 Thread Pierre Smits (JIRA) 

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

Pierre Smits commented on OFBIZ-6856:
-

When you consider this a bug and apply it to (soon unsupported) branch 13.07, 
you should also backport it to branches 14.12 and 15.12. 

But frankly this is an improvement.

> ContactMechs Label
> --
>
> Key: OFBIZ-6856
> URL: https://issues.apache.org/jira/browse/OFBIZ-6856
> Project: OFBiz
>  Issue Type: Bug
>  Components: product
>Affects Versions: Trunk, 13.07.02
>Reporter: Julien NICOLAS
>Assignee: Julien NICOLAS
>Priority: Minor
> Fix For: 13.07.03, Upcoming Branch
>
> Attachments: JIRA6856-1307.patch, JIRA6856-1412.patch, JIRA6856.patch
>
>
> Is it normal that in facility, the label for contact information is named 
> "ContactMechs".
> I think it could be a mistake but I'm French and maybe I miss something.
> Anyway, I think this label must be "Contact Mechs" and if we want to 
> standardize the contact mech label, it must be "Contact Information"
> In the same way, if you select "ContactMechs", you can find the "New Contact 
> Mech" button that can be rename as "New contact information".
> What is your opinion ?



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

[jira] [Updated] (OFBIZ-6856) ContactMechs Label

2016-01-28 Thread Julien NICOLAS (JIRA) 

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

Julien NICOLAS updated OFBIZ-6856:
--
Attachment: JIRA6856-1512.patch

> ContactMechs Label
> --
>
> Key: OFBIZ-6856
> URL: https://issues.apache.org/jira/browse/OFBIZ-6856
> Project: OFBiz
>  Issue Type: Bug
>  Components: product
>Affects Versions: Trunk, 13.07.02
>Reporter: Julien NICOLAS
>Assignee: Julien NICOLAS
>Priority: Minor
> Fix For: 13.07.03, Upcoming Branch
>
> Attachments: JIRA6856-1307.patch, JIRA6856-1412.patch, 
> JIRA6856-1512.patch, JIRA6856.patch
>
>
> Is it normal that in facility, the label for contact information is named 
> "ContactMechs".
> I think it could be a mistake but I'm French and maybe I miss something.
> Anyway, I think this label must be "Contact Mechs" and if we want to 
> standardize the contact mech label, it must be "Contact Information"
> In the same way, if you select "ContactMechs", you can find the "New Contact 
> Mech" button that can be rename as "New contact information".
> What is your opinion ?



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

[jira] [Comment Edited] (OFBIZ-6856) ContactMechs Label

2016-01-28 Thread Julien NICOLAS (JIRA) 

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

Julien NICOLAS edited comment on OFBIZ-6856 at 1/28/16 8:35 AM:


Issue fixed in release :
Trunk 1727207
13.07 1727212
14.12 1727261
15.12 1727273


was (Author: julien.nicolas):
Issue fixed in release :
Trunk 1727207
13.07 1727212

> ContactMechs Label
> --
>
> Key: OFBIZ-6856
> URL: https://issues.apache.org/jira/browse/OFBIZ-6856
> Project: OFBiz
>  Issue Type: Bug
>  Components: product
>Affects Versions: Trunk, 13.07.02
>Reporter: Julien NICOLAS
>Assignee: Julien NICOLAS
>Priority: Minor
> Fix For: 13.07.03, Upcoming Branch
>
> Attachments: JIRA6856-1307.patch, JIRA6856-1412.patch, 
> JIRA6856-1512.patch, JIRA6856.patch
>
>
> Is it normal that in facility, the label for contact information is named 
> "ContactMechs".
> I think it could be a mistake but I'm French and maybe I miss something.
> Anyway, I think this label must be "Contact Mechs" and if we want to 
> standardize the contact mech label, it must be "Contact Information"
> In the same way, if you select "ContactMechs", you can find the "New Contact 
> Mech" button that can be rename as "New contact information".
> What is your opinion ?



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

[jira] [Commented] (OFBIZ-6856) ContactMechs Label

2016-01-28 Thread Jacques Le Roux (JIRA) 

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

Jacques Le Roux commented on OFBIZ-6856:


And there is a lazy consensus about backporting labels anyway

> ContactMechs Label
> --
>
> Key: OFBIZ-6856
> URL: https://issues.apache.org/jira/browse/OFBIZ-6856
> Project: OFBiz
>  Issue Type: Bug
>  Components: product
>Affects Versions: Trunk, 13.07.02
>Reporter: Julien NICOLAS
>Assignee: Julien NICOLAS
>Priority: Minor
> Fix For: 13.07.03, Upcoming Branch
>
> Attachments: JIRA6856-1307.patch, JIRA6856-1412.patch, 
> JIRA6856-1512.patch, JIRA6856.patch
>
>
> Is it normal that in facility, the label for contact information is named 
> "ContactMechs".
> I think it could be a mistake but I'm French and maybe I miss something.
> Anyway, I think this label must be "Contact Mechs" and if we want to 
> standardize the contact mech label, it must be "Contact Information"
> In the same way, if you select "ContactMechs", you can find the "New Contact 
> Mech" button that can be rename as "New contact information".
> What is your opinion ?



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

[jira] [Commented] (OFBIZ-6856) ContactMechs Label

2016-01-27 Thread Julien NICOLAS (JIRA) 

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

Julien NICOLAS commented on OFBIZ-6856:
---

Issue fixed in release :
Trunk 1727207
13.07 1727212

> ContactMechs Label
> --
>
> Key: OFBIZ-6856
> URL: https://issues.apache.org/jira/browse/OFBIZ-6856
> Project: OFBiz
>  Issue Type: Bug
>  Components: product
>Affects Versions: Trunk, 13.07.02
>Reporter: Julien NICOLAS
>Assignee: Julien NICOLAS
>Priority: Minor
> Fix For: 13.07.03, Upcoming Branch
>
> Attachments: JIRA6856-1307.patch, JIRA6856.patch
>
>
> Is it normal that in facility, the label for contact information is named 
> "ContactMechs".
> I think it could be a mistake but I'm French and maybe I miss something.
> Anyway, I think this label must be "Contact Mechs" and if we want to 
> standardize the contact mech label, it must be "Contact Information"
> In the same way, if you select "ContactMechs", you can find the "New Contact 
> Mech" button that can be rename as "New contact information".
> What is your opinion ?



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

[jira] [Updated] (OFBIZ-6856) ContactMechs Label

2016-01-27 Thread Julien NICOLAS (JIRA) 

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

Julien NICOLAS updated OFBIZ-6856:
--
Attachment: JIRA6856.patch

Fix translation issue for contact Mech as Party contact Mech translation for 
trunk

> ContactMechs Label
> --
>
> Key: OFBIZ-6856
> URL: https://issues.apache.org/jira/browse/OFBIZ-6856
> Project: OFBiz
>  Issue Type: Bug
>  Components: product
>Affects Versions: Trunk, 13.07.02
>Reporter: Julien NICOLAS
>Assignee: Julien NICOLAS
>Priority: Minor
> Attachments: JIRA6856.patch
>
>
> Is it normal that in facility, the label for contact information is named 
> "ContactMechs".
> I think it could be a mistake but I'm French and maybe I miss something.
> Anyway, I think this label must be "Contact Mechs" and if we want to 
> standardize the contact mech label, it must be "Contact Information"
> In the same way, if you select "ContactMechs", you can find the "New Contact 
> Mech" button that can be rename as "New contact information".
> What is your opinion ?



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

[jira] [Closed] (OFBIZ-6856) ContactMechs Label

2016-01-27 Thread Julien NICOLAS (JIRA) 

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

Julien NICOLAS closed OFBIZ-6856.
-

> ContactMechs Label
> --
>
> Key: OFBIZ-6856
> URL: https://issues.apache.org/jira/browse/OFBIZ-6856
> Project: OFBiz
>  Issue Type: Bug
>  Components: product
>Affects Versions: Trunk, 13.07.02
>Reporter: Julien NICOLAS
>Assignee: Julien NICOLAS
>Priority: Minor
> Fix For: 13.07.03, Upcoming Branch
>
> Attachments: JIRA6856-1307.patch, JIRA6856.patch
>
>
> Is it normal that in facility, the label for contact information is named 
> "ContactMechs".
> I think it could be a mistake but I'm French and maybe I miss something.
> Anyway, I think this label must be "Contact Mechs" and if we want to 
> standardize the contact mech label, it must be "Contact Information"
> In the same way, if you select "ContactMechs", you can find the "New Contact 
> Mech" button that can be rename as "New contact information".
> What is your opinion ?



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

[jira] [Updated] (OFBIZ-6856) ContactMechs Label

2016-01-27 Thread Julien NICOLAS (JIRA) 

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

Julien NICOLAS updated OFBIZ-6856:
--
Attachment: JIRA6856-1307.patch

Patch for 13.07

> ContactMechs Label
> --
>
> Key: OFBIZ-6856
> URL: https://issues.apache.org/jira/browse/OFBIZ-6856
> Project: OFBiz
>  Issue Type: Bug
>  Components: product
>Affects Versions: Trunk, 13.07.02
>Reporter: Julien NICOLAS
>Assignee: Julien NICOLAS
>Priority: Minor
> Attachments: JIRA6856-1307.patch, JIRA6856.patch
>
>
> Is it normal that in facility, the label for contact information is named 
> "ContactMechs".
> I think it could be a mistake but I'm French and maybe I miss something.
> Anyway, I think this label must be "Contact Mechs" and if we want to 
> standardize the contact mech label, it must be "Contact Information"
> In the same way, if you select "ContactMechs", you can find the "New Contact 
> Mech" button that can be rename as "New contact information".
> What is your opinion ?



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

[jira] [Commented] (OFBIZ-6856) ContactMechs Label

2016-01-26 Thread Jacques Le Roux (JIRA) 

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

Jacques Le Roux commented on OFBIZ-6856:


>I must post it in dev mailing list before but I was thinking to solve it asap 
>and think "If I create Jira, it will be visible in the ML Dev"..

Yes but some, like me, filter Jira issues in different email client folders, so 
it's easier to follow and discuss when well separating things (at least for me 
:))

> ContactMechs Label
> --
>
> Key: OFBIZ-6856
> URL: https://issues.apache.org/jira/browse/OFBIZ-6856
> Project: OFBiz
>  Issue Type: Bug
>  Components: product
>Affects Versions: Trunk, 13.07.02
>Reporter: Julien NICOLAS
>Assignee: Julien NICOLAS
>Priority: Minor
>
> Is it normal that in facility, the label for contact information is named 
> "ContactMechs".
> I think it could be a mistake but I'm French and maybe I miss something.
> Anyway, I think this label must be "Contact Mechs" and if we want to 
> standardize the contact mech label, it must be "Contact Information"
> In the same way, if you select "ContactMechs", you can find the "New Contact 
> Mech" button that can be rename as "New contact information".
> What is your opinion ?



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

ContactMechs

2016-01-26 Thread Julien NICOLAS 
Is it normal that in facility, the label for contact information is 
named "ContactMechs".

I think it could be a mistake but I'm French and maybe I miss something.

Anyway, I think this label must be "Contact Mechs" and if we want to 
standardize the contact mech label, it must be "Contact Information" 
(like in party)


In the same way, if you select "ContactMechs", you can find the "New 
Contact Mech" button that can be rename as "New contact information".


What is your opinion ?


https://issues.apache.org/jira/browse/OFBIZ-6856

Julien.

[jira] [Commented] (OFBIZ-6856) ContactMechs Label

2016-01-26 Thread Julien NICOLAS (JIRA) 

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

Julien NICOLAS commented on OFBIZ-6856:
---

Yes, you're true !
I must post it in dev mailing list before but I was thinking to solve it asap 
and think "If I create Jira, it will be visible in the ML Dev"... 
Anyway, I'll do it.

And... Thank you to remember me this old topic, I was laughing the first time 
and laugh today again ! :D :D :D

I miss Adrian for that too !


> ContactMechs Label
> --
>
> Key: OFBIZ-6856
> URL: https://issues.apache.org/jira/browse/OFBIZ-6856
> Project: OFBiz
>  Issue Type: Bug
>  Components: product
>Affects Versions: Trunk, 13.07.02
>Reporter: Julien NICOLAS
>Assignee: Julien NICOLAS
>Priority: Minor
>
> Is it normal that in facility, the label for contact information is named 
> "ContactMechs".
> I think it could be a mistake but I'm French and maybe I miss something.
> Anyway, I think this label must be "Contact Mechs" and if we want to 
> standardize the contact mech label, it must be "Contact Information"
> In the same way, if you select "ContactMechs", you can find the "New Contact 
> Mech" button that can be rename as "New contact information".
> What is your opinion ?



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

Re: ContactMechs

2016-01-26 Thread Sharan-F 
Hi Julien

I think the ContactMech name is historic and is probably a bit of OFBiz
jargon :-)

It could be translated as 'Contact Details' or 'Contact Information'. If we
are already using 'Contact Information' as a description somewhere then I
think it makes sense to standardise it to be the same across the
applications where possible.

Thanks
Sharan



--
View this message in context: 
http://ofbiz.135035.n4.nabble.com/ContactMechs-tp4676462p4676473.html
Sent from the OFBiz - Dev mailing list archive at Nabble.com.

[jira] [Created] (OFBIZ-6856) ContactMechs Label

2016-01-25 Thread Julien NICOLAS (JIRA) 
Julien NICOLAS created OFBIZ-6856:
-

 Summary: ContactMechs Label
 Key: OFBIZ-6856
 URL: https://issues.apache.org/jira/browse/OFBIZ-6856
 Project: OFBiz
  Issue Type: Bug
  Components: product
Affects Versions: 13.07.02, Trunk
Reporter: Julien NICOLAS
Assignee: Julien NICOLAS
Priority: Minor


Is it normal that in facility, the label for contact information is named 
"ContactMechs".
I think it could be a mistake but I'm French and maybe I miss something.

Anyway, I think this label must be "Contact Mechs" and if we want to 
standardize the contact mech label, it must be "Contact Information"

In the same way, if you select "ContactMechs", you can find the "New Contact 
Mech" button that can be rename as "New contact information".

What is your opinion ?



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

[jira] [Commented] (OFBIZ-6856) ContactMechs Label

2016-01-25 Thread Jacques Le Roux (JIRA) 

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

Jacques Le Roux commented on OFBIZ-6856:


Hi Julien,

I think it was hastily done long ago and nobody never noticed. The French 
translation is good, for that I used "Coordonnées" this would be Contact 
details" in English.

It's better to ask such quesitons on dev ML. If you are interested by such 
discussions you may have some fun reading 
http://markmail.org/message/gccxgunjggmwqsei

Thanks!


> ContactMechs Label
> --
>
> Key: OFBIZ-6856
> URL: https://issues.apache.org/jira/browse/OFBIZ-6856
> Project: OFBiz
>  Issue Type: Bug
>  Components: product
>Affects Versions: Trunk, 13.07.02
>Reporter: Julien NICOLAS
>Assignee: Julien NICOLAS
>Priority: Minor
>
> Is it normal that in facility, the label for contact information is named 
> "ContactMechs".
> I think it could be a mistake but I'm French and maybe I miss something.
> Anyway, I think this label must be "Contact Mechs" and if we want to 
> standardize the contact mech label, it must be "Contact Information"
> In the same way, if you select "ContactMechs", you can find the "New Contact 
> Mech" button that can be rename as "New contact information".
> What is your opinion ?



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