[
https://issues.apache.org/cayenne/browse/CAY-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12936#action_12936
]
Kevin Menard commented on CAY-888:
----------------------------------
You're right. I've been dealing with Web apps too long. There it is customary
to bubble up an error message on a field. My only complaint about tooltips is
that for some messages they are simply too long. But, there likely isn't much
that can be done about that.
I've been unable to reproduce the root not being set. If I do, I'll let you
know.
I committed the second patch. The code quality was very good. I only had to
make minimal changes. Before I close the issue, however, can you please
investigate persisting the split pane sizes? It's definitely nice to be able
to change the pane sizes on the orderings and prefetches, but those values are
lost as soon as the Modeler is closed. If they could be saved in preferences
on a per project basis, that would be ideal.
> 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-2.txt, 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.
