[jira] Updated: (CAY-888) CM Usability: Object Select Query Improvements

["Andrey Razumovsky (JIRA)" <de...@cayenne.apache.org>]

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

Andrey Razumovsky updated CAY-888:
----------------------------------

    Attachment: patch-CAY-888.txt

#1. Done.  works this way: some time after end of user's input (currently 1,5 sec) qualifier text field is verified and set red if something's wrong (and tooltip shows the error message).
Advanced checking include standard syntax checking, and, as mentioned before, checking that all paths can be resolved for query root. If root is not selected, this is skipped.
If you have any ideas of what else to check, please tell me.

#2. Done
#3 Done.


> CM Usability: Object Select Query Improvements
> ----------------------------------------------
>
>                 Key: CAY-888
>                 URL: https://issues.apache.org/cayenne/browse/CAY-888
>             Project: Cayenne
>          Issue Type: New Feature
>          Components: CayenneModeler GUI
>            Reporter: Thomas Bernhard
>            Assignee: Kevin Menard
>         Attachments: patch-CAY-888.txt
>
>
> Object Select Query UI should be smarter and more usable:
> #1 Qualifier field shouldn't be just a dummy text filed. It should be smarter, with validations, or even some sort of completion
> or live checking so that the user quickly can do what he wants and be sure that it's OK. Because this dummy field is very error prone, many CM users avoid "Named Queries". I must admint - even myself - I always type something wrong there.
> #2 When selecting a QueryRoot -> e.g to Person, than the Query Name should be changed too to "PersonQuery", but only in the case the user hasn't manually changed that field to something else than the default generated by CM at dialog open. This is very user friendly (many IDEs offer such "variable suggestion").
> #3 Orderings and Prefetches tab panes should use a JSplitPane to separte the upper and the lower zones. For entities with many fields, the users always have to scroll because one can't simply drag a split pane to adapt the size.

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