Re: svn commit: r781689 - in /ofbiz/trunk/specialpurpose/googlecheckout: data/ entitydef/ servicedef/ src/org/ofbiz/googlecheckout/ widget/

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: svn commit: r781689 - in /ofbiz/trunk/specialpurpose/googlecheckout: data/ entitydef/ servicedef/ src/org/ofbiz/googlecheckout/ widget/

Vikas Mayur-3
Hi Ashish,

How about using a prefix Gc for Google Checkout (checkout being a  
single word) similar to what you described for General Ledger (Gl),  
though I do not see any problem with your changes :)

Vikas

On Jun 4, 2009, at 2:44 PM, [hidden email] wrote:

> Author: ashish
> Date: Thu Jun  4 09:14:51 2009
> New Revision: 781689
>
> URL: http://svn.apache.org/viewvc?rev=781689&view=rev
> Log:
> Changed the name of entities as it was exceeding the maximum length  
> i.e 30.
> Reported by Hans on Dev mailing list. Thanks Hans.
>
> There are two reason of choosing "Co" pattern for the entities.
>
> 1) I haven't seen any such pattern in OFBiz to define entity in  
> which you have three or more capital letter coming in b/w.
> Like for General Ledger, GlAccount is used OOTB.
>
> 2) In database it will split the table name to  
> Google_C_O_Shipping_Method if we keep the name GoogleCOShippingMethod.
> So it looks like you have some new word starting with "C" and  
> another new word starting with "O"
> But if we keep the name GoogleCoShippingMethod then it will split  
> the name into "Google_Co_Shipping_Method"
>
>
>


smime.p7s (3K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: svn commit: r781689 - in /ofbiz/trunk/specialpurpose/googlecheckout: data/ entitydef/ servicedef/ src/org/ofbiz/googlecheckout/ widget/

Ashish Vijaywargiya
-1.

GL is very commonly used term around the world for General Ledger.
IMO for now we are fine with the option GoogleCo as there might be some
other integration from google in future.
So think like Google as the common Prefix for all the integration with
Google and then add the Software name that has been integrated.

Suppose in future we have planned to do integration with two projects like
Android(http://developer.android.com/)  & OpenSocial(
http://code.google.com/apis/opensocial/).

So the name based on the existing pattern will be GoogleAndroid & GoogleOs
or GoogleOpenSocial as a prefix.

Now think about the idea that you have proposed:
The derived prefix will be Ga & Gos, which does not make any sense IMO.

Think about it and please let me know your thoughts on this.
Thanks Vikas for your comments :-)

--
Ashish

On Thu, Jun 4, 2009 at 3:32 PM, Vikas Mayur <[hidden email]>wrote:

> Hi Ashish,
>
> How about using a prefix Gc for Google Checkout (checkout being a single
> word) similar to what you described for General Ledger (Gl), though I do not
> see any problem with your changes :)
>
> Vikas
>
>>
>>
>>
>