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

Andrey Razumovsky commented on CAY-1077:
----------------------------------------

Seems that I rested too long :-) Cannot understand some of this issues:

1. You don't like that there are always more columns than selected values? If 
so, we can add new path component (new column) by double-click on the list 
entry.

2. Automatical selection of first component in the path can only occur when you 
have root selected, but no path. When you use sync button, both the root and 
path are selected. So I can see what can break behind the user here

3. I'd argue about that. Imagine a tree-like table A, which has to-one rel 
toParent and reverse childrenArray. Flattened toParent -> childrenArray can 
return siblings of the object. Other obvious example can be use of toParent -> 
toParent, which returns "grandfather" of the object

> ObjRelationship Mapping Dialog Improvements
> -------------------------------------------
>
>                 Key: CAY-1077
>                 URL: https://issues.apache.org/cayenne/browse/CAY-1077
>             Project: Cayenne
>          Issue Type: Improvement
>          Components: CayenneModeler GUI
>    Affects Versions: 3.0
>            Reporter: Andrus Adamchik
>            Assignee: Kevin Menard
>             Fix For: 3.0
>
>         Attachments: patch-CAY-1077.txt
>
>
> [This is a GSoC 2008 task]
> The biggest complaint about the ObjRelationship mapping dialog is that it is 
> often unclear how it operates, especially to the new users. I.e. empty list 
> of DbRelationships is displayed as a white area, not giving any hints on what 
> needs to be done to map a relationship. So that's confusing. Same thing when 
> you add 1 path component, there is no hint that you can chain more path 
> components for the flattened relationship.
> At the minimum we may just add some hint text ("Select next DbRelationship" 
> in grey over the next available dropdown), but ideally we should implement a 
> path browser, similar to how the SelectQuery prefetch and ordering browsers 
> operate (and similar to how OS X Finder does).

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

Reply via email to