[Vtigercrm-developers] Picklist handling [Was: Re: Coding Guidelines for vtiger CRM extensions]

[Uma S]

Hi,

After discussion with team-members, had updated trac ticket about
conclusion.

Could you peoples look into this and share your thoughts?

On Mon, Nov 24, 2014 at 3:46 PM, Uma S <uma.s at vtiger.com> wrote:

> Hi,
>
> We had reported this has an enhancement in trac
> <http://trac.vtiger.com/cgi-bin/trac.cgi/ticket/8353#ticket>. Will get
> back with this.
>
> On Fri, Nov 21, 2014 at 3:18 PM, Stacey Johnson <
> stacey.johnson110 at gmail.com> wrote:
>
>> developer numeric code instead of prefix. I guess 4 digits is enough?
>>
>> Stacey
>>
>> On Fri, Nov 21, 2014 at 3:13 PM, Alan Lord <alanslists at gmail.com> wrote:
>>
>>> On 20/11/14 13:17, IT-Solutions4You wrote:
>>>
>>>> Hi to all developers ;-)
>>>>
>>>> I see huge activity last days, we are happy with it. But I have a
>>>> please, can we keep the basic Coding Guidelines defined by vtiger team
>>>> to avoid compatibility problems in the future.
>>>>
>>>
>>> +1.
>>>
>>> This is even more important now we have the extension store and multiple
>>> providers of similar modules.
>>>
>>> On this subject is something I've been meaning to discuss for a while
>>> now...
>>>
>>> Could vtiger/us also look at the way picklist tables are generated for
>>> some future release please?
>>>
>>> Right now, if I used vtlib to create a new UIType 15 or 16 field - let's
>>> call it "type", it creates a table called vtiger_type to hold the picklist
>>> values...
>>>
>>> Now my module's basetable may well be called libertus_lsmymodule.
>>>
>>> Right now I have to prefix my field name with not only "ls" to signify
>>> it's one of ours, but also, when we are talking about a common field name
>>> for picklists such as "status" or "type", an indication of the module name
>>> it is for - if it is exclusive.
>>>
>>> So my field ends up being called something like 'lsmymod_type' which
>>> vtiger then ends up creating a table called vtiger_lsmymod_type.
>>>
>>> In a few cases where we have had more descriptive field names I have run
>>> into problems with the length of the table name - which is limited in the
>>> vtiger code IIRC.
>>>
>>> I think it would be helpful if the picklist tables could be prefixed
>>> with the same prefix as the original module so our picklists would
>>> typically start with libertus_ rather than vtiger_...
>>>
>>> Or maybe someone can up with a better solution for picklists?
>>>
>>> Cheers
>>>
>>> Al
>>>
>>>
>>> _______________________________________________
>>> http://www.vtiger.com/
>>>
>>
>>
>> _______________________________________________
>> http://www.vtiger.com/
>>
>
>
>
> --
> With
> Best Regards
> Uma.S
> Vtiger Team
>



-- 
With
Best Regards
Uma.S
Vtiger Team
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20141126/25e10019/attachment.html>