User:Barre/TODO - Revision history

Wjp: /* Draft5 */

2008-10-01T12:27:46Z

Draft5

2008-10-01T12:27:31Z

Draft5

2008-10-01T12:21:58Z

Draft5 (still working on this)

2008-09-30T21:55:33Z

Draft5

2008-09-30T20:46:00Z

Draft5

2008-09-30T20:40:42Z

Draft5

2008-09-30T20:38:22Z

Draft5

2008-09-30T20:37:36Z

Draft5

2008-09-30T20:35:09Z

Draft5

2008-09-30T17:58:39Z

Draft5

@@ Line 107: / Line 107: @@
 * [[image:CheckModified.png ]] Select scene and all modified data.
-plus option to choose destination for all selected, and individual dataset options as in current implementation.
+plus option to choose destination for all selected, and individual dataset options (as in current implementation).
 * if user deselects ALL, then selects the a scene file, logic shouldn't automatically re-check all modified data. We don't do this now either -- currently if a user tries to save the scene and unchecked modified data exists, we just pop up a message telling the user that the save requires them to go back and check unchecked stuff. We can keep this same behavior and adapt the Save button logic a little:

@@ Line 107: / Line 107: @@
 * [[image:CheckModified.png ]] Select scene and all modified data.
-plus option to choose destination option for all selected, and individual dataset options as in current implementation.
+plus option to choose destination for all selected, and individual dataset options as in current implementation.
 * if user deselects ALL, then selects the a scene file, logic shouldn't automatically re-check all modified data. We don't do this now either -- currently if a user tries to save the scene and unchecked modified data exists, we just pop up a message telling the user that the save requires them to go back and check unchecked stuff. We can keep this same behavior and adapt the Save button logic a little:

@@ Line 97: / Line 97: @@
 [[media:IconResources.zip | icon resources zip file ]]
-====Draft5 (still working on this)====
+====Draft5====
 A user selects File->Save

@@ Line 97: / Line 97: @@
 [[media:IconResources.zip | icon resources zip file ]]
-====Draft5====
+====Draft5 (still working on this)====
 A user selects File->Save

@@ Line 114: / Line 114: @@
 *** If yes, save.
 *** If not, pop up the message.
 '''Question:''' Is it confusing to have the scene bundled in with the data? (wjp) I think that it's reasonable to ask users to understand the concepts of datasets and scene descriptions at a high level, and reasonable also to treat them collectively as writable data. Unless it's important to clarify their difference to the user, it's simpler and more compact to treat their saving consistently. Anything I'm missing -- other opinions?

@@ Line 102: / Line 102: @@
 * widget raises with all modified data checked (as in current implementation).
 User has four convenient select options:
-* [[image:CheckAll.png]] User can select scene and all data for saving
+* [[image:CheckAll.png]] Select scene and all data for saving
-* [[image:UncheckAll.png]] User can deselect scene and all data
+* [[image:UncheckAll.png]] Deselect scene and all data
-* [[image:CheckModifiedData.png]] User can select all modified data (not scene file)
+* [[image:CheckModifiedData.png]] Select all modified data (not scene file)
-* [[image:CheckModified.png ]]User can select scene and all modified data.
+* [[image:CheckModified.png ]] Select scene and all modified data.
 plus option to choose destination option for all selected, and individual dataset options as in current implementation.
@@ Line 114: / Line 114: @@
 *** If yes, save.
 *** If not, pop up the message.
 '''Question:''' Is it confusing to have the scene bundled in with the data? (wjp) I think that it's reasonable to ask users to understand the concepts of datasets and scene descriptions at a high level, and reasonable also to treat them collectively as writable data. Unless it's important to clarify their difference to the user, it's simpler and more compact to treat their saving consistently. Anything I'm missing -- other opinions?

@@ Line 116: / Line 116: @@
 *** If not, pop up the message.
 '''Might be nice feature to support someday:''' should a user be able to save a scene description that contains only the selected subset of data in a scene? I can imagine this to be useful:
 My scene contains a volume V, transform T and model M, and two other "working" volumes. I want to save those three nodes only and a scene description that includes them but NOT my working volumes -- but I don't want to delete them yet.
@@ Line 124: / Line 130: @@
 ** If the scene.mrml file exists, popup message says ''"You have chosen to overwrite the scene file without saving all modified data. MRML file will not describe this data. Ok to proceed? OK/Cancel''
 ** If the scene.mrml file doesn't exist, popup message says ''"You have chosen to save the scene file without saving all modified data in the scene. MRML file will not describe this data. OK to proceed? OK/Cancel''
 ===Other===