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

From: Kevin Menard (JIRA) ("Kevin)
Date: Wed Jun 04 2008 - 20:43:52 EDT

  • Next message: Kevin Menard (JIRA): "[jira] Commented: (CAY-888) CM Usability: Object Select Query Improvements"

        [ https://issues.apache.org/cayenne/browse/CAY-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12913#action_12913 ]

    Kevin Menard commented on CAY-888:
    ----------------------------------

    I can verify that #2 & #3 work as advertised. I cannot get #1 to work, however. The field turns red, but I never see a tooltip. The error message does get printed to the console, however.

    Also, there seemed to be a lot of unnecessary import statements leftover. They're simple enough to clean-up, but if you need to generate another patch, please remove them.

    > 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.
    



    This archive was generated by hypermail 2.0.0 : Wed Jun 04 2008 - 20:44:14 EDT