View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0002400Slicer4Core: MRMLpublic2012-08-14 12:242018-03-02 11:06
Reporterlassoan Assigned Toalexy  
PrioritynormalSeveritytextReproducibilityalways
Status closedResolutionfixed 
Product Version 
Target VersionSlicer 4.5.0-1Fixed in VersionSlicer 4.5.0-1 
Summary0002400: Rename the "Create and rename new Node" command to "Create new Node as..."
Description

In node selectors on the module UI the following options are available for output nodes ("Node" can be Volume, Transform, etc.):

  • Rename current Node
  • Create new Node
  • Create and rename new Node
  • Delete current Node

The name of the recently added "Create and rename new Node" is quite bad due to several reasons: it's too long (5 words!), it contains two verbs (a command very rarely contains more verbs, because it's confusing), and it does not follow the usual naming convention of other software (in any Windows program this option would be called "Create new Node as..." - similarly to "Save" -> "Save as...").

"Create new Node as..." (Create new Volume as..., Create new Transform as...) seem to be a much better option:

  • Rename current Node
  • Create new Node
  • Create new Node as...
  • Delete current Node
TagsNo tags attached.

Relationships

related to 0002466 closedinorton CLIs that use DVW nodes crash in MRMLIDImageIO 

Activities

alexy

alexy

2013-08-06 10:16

developer   ~0009410

Moving to 4.4 due to a documentation change effect.
pieper

pieper

2014-03-07 06:45

administrator   ~0011338

Would require fixing all the documentation and corresponding screen captures.
pieper

pieper

2014-03-07 06:48

administrator   ~0011339

At the bug review session it wasn't clear that the suggested wording is actually better. Including 'rename' is very specific where 'as' is not specific.
lassoan

lassoan

2014-03-07 07:06

developer   ~0011341

Rename is specific, but actually no rename is performed (a new object is created with the requested name), so it is wrong.

But the main problem is that we introduce a new wording for a very widely used concept. Open any software application (really, any) and you'll see that when you create an object with a new name the "[verb] as" pattern is used (e.g., "Save as...").
If you find any software where the "[verb] and rename]" pattern is used for anything then you can close this ticket as "no fix" and I won't complain.
pieper

pieper

2014-03-07 08:37

administrator   ~0011345

"Create and name..." would seem to be the correct wording then.
lassoan

lassoan

2014-03-07 09:16

developer   ~0011354

For me "Create and name Node" and "Create and rename Node" are quite similar. Name is 2 letters shorter, so that's an improvement, but still sounds very unfamiliar. Have you seen "[verb] and name..." used in other software?

We should involve more people in the discussion.
alexy

alexy

2014-04-11 08:16

developer   ~0011574

Since there is no consensus and it may need more discussions, re-targeting to 4.5

jcfr

jcfr

2015-06-19 14:44

administrator   ~0013142

This has been fixed in r24350

See http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=24350

Issue History

Date Modified Username Field Change
2012-08-14 12:24 lassoan New Issue
2012-08-14 12:24 lassoan Status new => assigned
2012-08-14 12:24 lassoan Assigned To => alexy
2012-08-22 05:56 jcfr Target Version => Slicer 4.3.0
2013-08-06 10:16 alexy Note Added: 0009410
2013-08-06 10:16 alexy Target Version Slicer 4.3.0 => Slicer 4.4.0
2014-03-07 06:45 pieper Note Added: 0011338
2014-03-07 06:47 pieper Relationship added related to 0002466
2014-03-07 06:48 pieper Note Added: 0011339
2014-03-07 07:06 lassoan Note Added: 0011341
2014-03-07 08:37 pieper Note Added: 0011345
2014-03-07 09:16 lassoan Note Added: 0011354
2014-04-11 08:16 alexy Note Added: 0011574
2014-04-11 08:16 alexy Target Version Slicer 4.4.0 => Slicer 4.5.0-1
2015-06-19 14:44 jcfr Note Added: 0013142
2015-06-19 14:44 jcfr Status assigned => resolved
2015-06-19 14:44 jcfr Fixed in Version => Slicer 4.4.1
2015-06-19 14:44 jcfr Resolution open => fixed
2015-09-09 08:29 jcfr Fixed in Version Slicer 4.4.1 => Slicer 4.5.0-1
2018-03-02 11:06 jcfr Status resolved => closed