Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle object reference form inputs. #9

Open
milko opened this issue Aug 13, 2014 · 0 comments
Open

Handle object reference form inputs. #9

milko opened this issue Aug 13, 2014 · 0 comments
Assignees

Comments

@milko
Copy link
Owner

milko commented Aug 13, 2014

Object references are tricky to handle in forms, since they contain the native identifier of an object as value, but need to present a user friendly interface. In the current system we have one object reference type, kTYPE_REF_UNIT, which is relevant to users and needs to be handled in a user friendly way.

Tags of this type should feature the kTAG_DOMAIN property which indicates what kind of unit the field references, tags that do not have this property may reference any kind of unit.

The idea is to provide an input field that will be used with a full-text search operation that will return a list of possible choices, the user then must select one of these choices.

The choice selection could be presented in the same way as the default table view, with the addition of the relevance indicator (will be subject of another issue), giving the user an idea of how relevant his/her choices are.

The other possibility is to have tags feature another property which contains a list of tags that can be used to search the required referenceusing a set of its properties.

The idea is to first implement the first case, then explore the possibility to implement the second case.

@milko milko self-assigned this Aug 18, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant