[Vtigercrm-developers] list view context menu

Doug sailsfast at gmail.com
Wed Mar 13 21:06:30 UTC 2013


Ah, thanks
On Mar 13, 2013 4:35 PM, "Adam Heinz" <amh at metricwise.net> wrote:

> Heh, no. It's simply a translation string replacement for "Add Sales
> Order"; it's the terminology that client is used to.
>
>
> On Wed, Mar 13, 2013 at 4:16 PM, Doug <sailsfast at gmail.com> wrote:
>
>> SO I am curious...  Does record contract have something to do with
>> service contracts?
>>
>> On Wed, Mar 13, 2013 at 3:19 PM, Adam Heinz <amh at metricwise.net> wrote:
>>
>>> I finished my prototype a couple days ago and finally remembered to take
>>> some screenshots of it.  You can see how I've replaced the links of the
>>> list view Action column with a single icon that opens up my context menu
>>> (jquery-ui dialog).  Comparing that to the detail view, you can see that
>>> the options are nearly identical; the view appointment link is omitted from
>>> detail view for obvious reasons).  The View History link was added by stock
>>> ModTracker and it works from the ListView without any changes!  So far my
>>> handler function is pretty straightforward:
>>>
>>> /**
>>>  * @param Vtiger_LinkData $linkData
>>>  * @return bool
>>>  */
>>> public static function isLinkPermitted($linkData) {
>>> $link = $linkData->getLink();
>>>  $url = $link->linkurl;
>>> $parts = parse_url($url);
>>> if ('javascript' == $parts['scheme']) {
>>>  return self::isJavascriptPermitted($linkData, $parts);
>>> }
>>> $query = $parts['query'];
>>>  $parms = array();
>>> parse_str($query, $parms);
>>> $action = $parms['action'];
>>>  $record = $linkData->getInputParameter('record');
>>> if ($parms['module'] != '$MODULE$') {
>>>  $module = $parms['module'];
>>> $record = self::getRelated($module, $record);
>>> } else {
>>>  $module = $linkData->getModule();
>>> }
>>> if (isPermitted($module, $action, $record) != 'yes') {
>>>  return false;
>>> }
>>> return true;
>>>  }
>>>
>>>
>>>
>>> On Fri, Feb 8, 2013 at 2:11 PM, Sreenivas Kanumuru <svk at vtiger.com>wrote:
>>>
>>>> Adam,
>>>>
>>>> We can certainly tweak vtiger6 UI if it helps. We'll await your
>>>> screenshots to get a better idea of the proposed change.
>>>>
>>>> thanks,
>>>> Sreenivas
>>>>
>>>>
>>>>
>>>> --
>>>> Sreenivas Kanumuru
>>>> vtiger Team
>>>>
>>>> Direct: +91 96323-55656
>>>> Skype: skanumuru
>>>>
>>>> *Connect with us on: *Twitter <http://twitter.com/#%21/vtigercrm> *I*
>>>> Facebook <http://www.facebook.com/pages/vtiger/226866697333578?sk=wall>
>>>>  *I* Blog <http://blog.vtiger.com/>* I* Wiki<http://wiki.vtiger.com/index.php/Main_Page>
>>>>  *I *Forums  <http://forums.vtiger.com/>*I* Website<http://vtiger.com/>
>>>>
>>>>
>>>> On Fri, Feb 8, 2013 at 3:18 AM, Adam Heinz <amh at metricwise.net> wrote:
>>>>
>>>>> I am working on a prototype replacement for the list view action
>>>>> column. We have never found it very useful as our users prefer the detail
>>>>> view ajax edit for the bulk of their changes and generally don't have
>>>>> delete permissions; which are the only two actions ever listed [1].  I've
>>>>> reviewed vt6 and the mouse over behavior is no better; we're stuck with the
>>>>> same basic actions for every record.
>>>>>
>>>>> The Vtiger_Link class has enabled us to remove custom code and replace
>>>>> it with data, bringing our fork more in line with stock vtigercrm.  One
>>>>> thing that I've started to notice is that our context menu entries often
>>>>> overlap our detail view actions, the main difference being that our context
>>>>> menus are custom code, whereas the detail view actions are Vtiger_Links.
>>>>>  The obvious next step is to generate context menus from Vtiger_Links!  The
>>>>> handler parameter gives me a ton of control over which links are shown when
>>>>> I generate the context menu, which I am doing via a simple
>>>>> action=ModuleAjax&file=ContextMenu request.  This lazy evaluation prevents
>>>>> list view load times from being unwieldy, without sacrificing flexibility.
>>>>>
>>>>> Anyway, I'll have a patch up before too long (and maybe some
>>>>> screenshots), but I really wanted to throw this out before the mouse over
>>>>> behavior in vt6 is set in stone.  We're finally starting to deploy 5.4.0 to
>>>>> our users, so I am only now beginning to look at vt6.  Though I generally
>>>>> like the crisp new look, it takes several steps backwards in terms of user
>>>>> interface.  I'll start a new thread tomorrow enumerating my usability
>>>>> concerns.
>>>>>
>>>>> [1]
>>>>> http://trac.vtiger.com/cgi-bin/trac.cgi/browser/vtigercrm/branches/5.4.0/include/utils/ListViewUtils.php#L970
>>>>>
>>>>> _______________________________________________
>>>>> http://www.vtiger.com/
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> http://www.vtiger.com/
>>>>
>>>
>>>
>>> _______________________________________________
>>> http://www.vtiger.com/
>>>
>>
>>
>> _______________________________________________
>> http://www.vtiger.com/
>>
>
>
> _______________________________________________
> http://www.vtiger.com/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.vtigercrm.com/pipermail/vtigercrm-developers/attachments/20130313/781bd6fc/attachment.html 


More information about the vtigercrm-developers mailing list