[jira] Created: (CAY-1077) ObjRelationship Mapping Dialog Improvements

[Cayenne - Dev mailing list]

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


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

[Cayenne - Dev mailing list]

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

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

Agreed. Actually I think this must be the same as 'Prefetches' browser, only using DbRels instead of ObjRels. I even think that 'Target' field in Inspector must be made read-only, because chain of relationships is determining it anyways. Auto-suggesting of relationships is cool, but not needed if we can choose them in a couple of clicks (and all rels would be seen at once, not in dropdown).
And Inspector must be able to be opened even if to Target was set, since it's a bit irritating to choose end destination and only then to complete all the path.

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

[Cayenne - Dev mailing list]

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

antidote edited comment on CAY-1077 at 7/1/08 12:17 PM:
-----------------------------------------------------------------

Agreed. Actually I think this must be the same as 'Prefetches' browser, only using DbRels instead of ObjRels. I even think that 'Target' field in Inspector must be made read-only, because chain of relationships is determining it anyways. Auto-suggesting of relationships is cool, but not needed if we can choose them in a couple of clicks (and all rels would be seen at once, not in dropdown).
And Inspector must be able to be opened even if no Target was set, since it's a bit irritating to choose end destination and only then to complete all the path.

      was (Author: antidote):
    Agreed. Actually I think this must be the same as 'Prefetches' browser, only using DbRels instead of ObjRels. I even think that 'Target' field in Inspector must be made read-only, because chain of relationships is determining it anyways. Auto-suggesting of relationships is cool, but not needed if we can choose them in a couple of clicks (and all rels would be seen at once, not in dropdown).
And Inspector must be able to be opened even if to Target was set, since it's a bit irritating to choose end destination and only then to complete all the path.
 

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

[Cayenne - Dev mailing list]

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

Andrus Adamchik commented on CAY-1077:
--------------------------------------

Looks like a plan. Let's do it this way.

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

[Cayenne - Dev mailing list]

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

Kevin Menard commented on CAY-1077:
-----------------------------------

It would also be nice if we could make many-to-many relationships easier to handle.  I think the proposed path will improve things quite a bit, but it may still be a little awkward dealing with the join tables.  I'll have to think about that one a bit more.

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

[Andrus Adamchik]

Hi Kevin,

Suggested procedure seems very straightforward regardless of whether  
the relationship is one step or multi-step. What are you concerns  
about many-to-many?

Andrus

On Jul 2, 2008, at 3:32 AM, Kevin Menard (JIRA) wrote:

> Kevin Menard commented on CAY-1077:
> -----------------------------------
>
> It would also be nice if we could make many-to-many relationships  
> easier to handle.  I think the proposed path will improve things  
> quite a bit, but it may still be a little awkward dealing with the  
> join tables.  I'll have to think about that one a bit more.

[Cayenne - Dev mailing list]

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

Andrey Razumovsky updated CAY-1077:
-----------------------------------

    Attachment: patch-CAY-1077.txt

You can now try the new dialog. In some way, the process of mapping a relation is now reverted. Before you had to choose target first, and then complete the path - now you in a short sequence of clicks select the path, and the target is completed automatically.
Still, there are few cases when you need to select the target:
1. When there are multiple ObjEntities mapped to one DbEntity, which is last in the path, and path browser chose the wrong one for you.
2. When you want to create new DbRelationship to another entity from ObjRelationship dialog.

If the targets in combo and path browser do not match (that can only happen when you set wrong target manually the target after selecting the path), path browser is valued higher.

-- EntityRelationshipsModel class is not used now, so if you think it is worthless (I do) please remove it and underlying JUnit test.

By the way, mapping of many-to-many relationship (with middle Join table) is two clicks now. I don't see how that can be improved any futher :)

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

[nirvdrum]

Thinking it over, the proposed path looks fine.  I was a little under the  
weather the last time I looked and wanted to make a note so I didn't  
forget about it later.  I see Andrey has already submitted a patch, so  
I'll poke around with it.

--
Kevin

On Wed, 02 Jul 2008 02:28:59 -0400, Andrus Adamchik  
<andrus@...> wrote:

> Hi Kevin,
>
> Suggested procedure seems very straightforward regardless of whether the  
> relationship is one step or multi-step. What are you concerns about  
> many-to-many?
>
> Andrus
>
> On Jul 2, 2008, at 3:32 AM, Kevin Menard (JIRA) wrote:
>
>> Kevin Menard commented on CAY-1077:
>> -----------------------------------
>>
>> It would also be nice if we could make many-to-many relationships  
>> easier to handle.  I think the proposed path will improve things quite  
>> a bit, but it may still be a little awkward dealing with the join  
>> tables.  I'll have to think about that one a bit more.
>

[Cayenne - Dev mailing list]

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

Kevin Menard commented on CAY-1077:
-----------------------------------

The new dialog is a definite improvement.  A couple of comments on usability, however.  It looks like these are comments about the prefetch chooser as well, which is understandable as they're designed to be similar.

1) The difference between toOne and toMany is blurred to the point of being potentially confusing.  At least two columns of values are used all the time, which can be confusing for toOnes, which should only use a single column.

2) The toMany is selected automatically, which is nice, but can also cause the user to generate syntactically correct, but logically wrong maps.  This may not be a huge issue, but the case I'm thinking of us is someone inadvertently messing up a relationship that the modeler created via the sync button.

3) I can't envision a case where cyclical mappings would be what the user intended.  Perhaps if each path had a qualifier attached to it, but that's not possible currently.  So, I would suggest removing components already in the path from being candidates.  I think this would go a long way to addressing the usability issue raised in #1.

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

[Cayenne - Dev mailing list]

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

[Cayenne - Dev mailing list]

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

Kevin Menard commented on CAY-1077:
-----------------------------------

I've been away from the issue a bit myself and needed a refresher.

1. I guess you could boil it down to that.  I think it's more of an issue of there always being multiple columns, even for what should be a toOne relationship.  I think a double-click could work, but we'd want to make sure that's somehow intuitive.  I'm not sure it is with a columnar selector, unfortunately.

2. Indeed, the sync button does work well.  My issue was more with the ease at which a user can break a sync'd connection.  Maybe I'm trying to be too protective, but being able to convert a toOne to a toMany is simplistic to the point of being hazardous, IMHO.

3. I should have clarified a bit more.  Of course toMany could have interesting relationships and detecting a static cycle in that case would be impossible.  But, for toOnes with bi-directional relationships, we can detect cycles fairly easily.  We should not allow such to be mapped.

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

[Andrey Razumovsky]

1. I can suggest adding new column by double-click *OR* single click on
right arrow. That's probably more intiitive.

2. You might be right, but I can't see what can be done about it - ?

3. So this comes to not allowing sequenced reverse one-to-one relationships?
(A->B->A). I'll do it that way

2008/7/23, Kevin Menard (JIRA) <dev@...>:

>
>
>     [
> https://issues.apache.org/cayenne/browse/CAY-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13013#action_13013]
>
>
> Kevin Menard commented on CAY-1077:
> -----------------------------------
>
>
> I've been away from the issue a bit myself and needed a refresher.
>
> 1. I guess you could boil it down to that.  I think it's more of an issue
> of there always being multiple columns, even for what should be a toOne
> relationship.  I think a double-click could work, but we'd want to make sure
> that's somehow intuitive.  I'm not sure it is with a columnar selector,
> unfortunately.
>
> 2. Indeed, the sync button does work well.  My issue was more with the ease
> at which a user can break a sync'd connection.  Maybe I'm trying to be too
> protective, but being able to convert a toOne to a toMany is simplistic to
> the point of being hazardous, IMHO.
>
> 3. I should have clarified a bit more.  Of course toMany could have
> interesting relationships and detecting a static cycle in that case would be
> impossible.  But, for toOnes with bi-directional relationships, we can
> detect cycles fairly easily.  We should not allow such to be mapped.
>
>
> > 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.
>
>

[Cayenne - Dev mailing list]

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

Andrey Razumovsky updated CAY-1077:
-----------------------------------

    Attachment: patch-CAY-1077-2.txt

Changes in new patch:
-New column is not automatically added when a list row is selected. You need to double-click. I added a tooltip to the browser. Hope this helps.
- A->B->A to-One chains are now forbidden

> 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-2.txt, 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.

[Cayenne - Dev mailing list]

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

Kevin Menard commented on CAY-1077:
-----------------------------------

I've committed the changes.  Generally, I like what I see.  But, the behavior of the column selector should be the same for the relationship dialog and the prefetch dialog.  I'm going to push out a snapshot and let people decide which one they like better.  After that, we'll revisit the issue.

> 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-2.txt, 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.

[Andrus Adamchik]

I tested it this morning, and I couldn't force the second level of  
relationships to open to the right of the first. Is this just  
something in my env or is there a bug / unfinished implementation?

Thanks,
Andrus

On Aug 1, 2008, at 2:43 PM, Kevin Menard (JIRA) wrote:

>
>    [ https://issues.apache.org/cayenne/browse/CAY-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13027 
> #action_13027 ]
>
> Kevin Menard commented on CAY-1077:
> -----------------------------------
>
> I've committed the changes.  Generally, I like what I see.  But, the  
> behavior of the column selector should be the same for the  
> relationship dialog and the prefetch dialog.  I'm going to push out  
> a snapshot and let people decide which one they like better.  After  
> that, we'll revisit the issue.
>
>> 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-2.txt, 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.
>
>