[
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-2.txt
As for #1, I actually had no plans to show any popups. I mean that tooltip text
for the textfield is set with error description (the one is visible when you
pause the mouse on the field). That's the way it is done in most IDEs. User
types something, then checking goes after some delay, if something's wrong text
usually goes curved underline (we've got a single textfield, so that's just red
background). When you move mouse to the malformed text, you see detailed
description. So i changed nothing in this part (if you have any suggestions -
please tell me).
The patch (it must be applied to rep code) cleans imports and fixes the bug
with incorrect scrolling (unexpected popup hiding). Now, the name in the tree
changes only after the focus is lost for the combo.
I still cannot reproduce the root not being set ("persisted"). If this
continues to occur, please tell me more about the consequence of actions and
enviroment it happened at.
> 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.
