[jira] Closed: (OFBIZ-3937) preferred (most used) items in a mixed widget (combo-popup search)

["Jacques Le Roux (JIRA)" <ji...@apache.org>]

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

Jacques Le Roux closed OFBIZ-3937.
----------------------------------

      Assignee: Jacques Le Roux
    Resolution: Not A Problem

I just tried on a LookupGeo (with 1000+ entries) we have any performance issues with autocomplete (we retrieve by block of 10 by default). So I close...

> preferred (most used) items in a mixed widget (combo-popup search)
> ------------------------------------------------------------------
>
>                 Key: OFBIZ-3937
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-3937
>             Project: OFBiz
>          Issue Type: New Feature
>          Components: ALL COMPONENTS
>         Environment: noarch
>            Reporter: Corrado Campisano
>            Assignee: Jacques Le Roux
>            Priority: Minor
>   Original Estimate: 672h
>  Remaining Estimate: 672h
>
> Hi,
> was looking at the video "Framework Intro 4 Example App Overview" (http://vimeo.com/9606918).
> At minutes from 5:33 to 6:00, the presenter talks about the difference between combos and popup search for to provide FK (it's just foreign keys, right?) to entities being edited.
> I understand this point: I work for a global company and for some product orders management, I wait minutes with combos being populated with thousands of items...
> So I like OfBiz approach, but I'd like to go further...
> What about a mixed widget, displaying both a combo (populated with current users' most used items) and the button for the popup search?
> I understand this would imply some hard changes, and some overhead for looking for the 'most used', but would really help: having always to use the popoup search could be boring when you both have large items number but working usually with a smaller subset of them (think about any regionally organized, localized customer sales/management/support staff and tools).
> The linking table could be like this:
> mostUsedID - ID, autoinc
> userFK - current user id
> entityFK - entity db table to look for items
> itemFK - items ID in the entity db table
> count - number of time used
> Is that feasible?
> Best regards,
> Corrado

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.