Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

User experience issue : adding connector to a crosscut #897

Closed
phreed opened this issue Mar 18, 2016 · 7 comments
Closed

User experience issue : adding connector to a crosscut #897

phreed opened this issue Mar 18, 2016 · 7 comments

Comments

@phreed
Copy link

phreed commented Mar 18, 2016

It is difficult to know if preexisting connectors exists between objects.
The main purpose of crosscut views is to establish a context in which
connectors can be managed.

The current implementation is great for adding new connectors.
If there are two objects A and B and there is no connector between them;
then adding a connector is trivial.
If there are more than one type of A-B connector that can be created;
a list of the different connector types is presented.

Assume there is already a A-B connector in another crosscut.
It may be that the A-B connector is relevant to the current crosscut.
Presently, the A-B connector can be copied from the tree into the crosscut.
The difficulty is in identifying that the connection exists and which one it may be.
The means for identifying the other A-B connectors is an unpleasant experience.
The problem only manifests itself by examination of the "conpoisition" view
which, in some cases, will automatically include the new connectors.

Suggestion:
Enhance the list of connector types presented during creation
to include all existing A-B connections in addition to the creation options.

@pmeijer
Copy link
Contributor

pmeijer commented Mar 22, 2016

Do you use connector and connection interchangeably here?

@pmeijer
Copy link
Contributor

pmeijer commented Mar 22, 2016

goto

Fred is this sufficient. Clicking on the GoTo item will open up the existing connection. From there you can locate the node in the tree-browser. (Currently only the path is display since the connection may or may not be loaded at the time of the menu creation.)

@pmeijer
Copy link
Contributor

pmeijer commented Mar 22, 2016

Currently if there is only one type of connection it is created automatically. With this change I would assume that the menu should at least pop up if there are existing connections. However would you like it to pop up even though there aren't any (and it that case display the only option 'Create connection...'?).

@pmeijer
Copy link
Contributor

pmeijer commented Mar 22, 2016

One more thing, do you have a better phrase than 'GoTo'? 'Open'?

@pmeijer pmeijer added this to the v1.7.0 milestone Mar 22, 2016
@pmeijer pmeijer self-assigned this Mar 22, 2016
@phreed
Copy link
Author

phreed commented Mar 23, 2016

If there are no existing connections and there is only one valid rule then automatically selecting the only choice is appropriate.
'Go To' sounds odd to my ear 'Open' or 'Use' would be fine.
Yes, sorry, when I wrote 'connector' I meant 'connection'.

kecso added a commit that referenced this issue Mar 23, 2016
@pmeijer pmeijer closed this as completed Mar 24, 2016
@pmeijer
Copy link
Contributor

pmeijer commented Mar 24, 2016

Closed by #906

@pmeijer
Copy link
Contributor

pmeijer commented Apr 22, 2016

Can you file a separate issue for that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants