david_costanzo

The message below is being cross-posted from LogoForum.

I have a question for FMSLogo and MSWLogo users.

Someone recently requested that selecting "File -> Open" from
FMSLogo's main menu should prompt the user if they want to replace the
current workspace with the new file, or merge the new file into the
current workspace. He said that his students end up with every

My students and I also have this problem, so I would like a solution
to it. But I would prefer not to add yet another dialog box (FMSLogo
has too many of them as it is and they seem to get in the way more
than they help). Does anyone like that File -> Open merges the new
file into the existing workspace? Would anyone be against having File
-> Open erase the current workspace before loading the new file? Is
there a compelling argument for having a dialog box that asks you
which sort of "File -> Open" you want?

Note that I still think that the LOAD command should merge into the
current workspace. I also think that if I ever implement drag&drop
for files, that should also merge (I'm not sure why, it just feels
like it should). The only behavior that I'm considering
changing is when you select File -> Open from the main menu.

Kindest Regards,

David Costanzo


LogoForum messages are archived at:
http://groups.yahoo.com/group/LogoForum

kohútek_petr

The message below is being cross-posted from LogoForum.

I think that better than dialog would be to make two menu commands:
File -> Open
File -> Load

this will be consistent with the command.
However it is also possible to name it "Open (merge)", or something
that will imply opening of a file.

Petr


-----Original Message-----
From: LogoForum@yahoogroups.com [mailto:LogoForum@yahoogroups.com] On
Behalf Of david_costanzo
Sent: Wednesday, May 31, 2006 8:12 AM
To: LogoForum@yahoogroups.com
Subject: [LogoForum] Does anyone like that FMSLogo File -> Open merges
into current workspace?

I have a question for FMSLogo and MSWLogo users.

Someone recently requested that selecting "File -> Open" from FMSLogo's
main menu should prompt the user if they want to replace the current
workspace with the new file, or merge the new file into the current
workspace. He said that his students end up with every procedure that


My students and I also have this problem, so I would like a solution to
it. But I would prefer not to add yet another dialog box (FMSLogo has
too many of them as it is and they seem to get in the way more than
they help). Does anyone like that File -> Open merges the new file
into the existing workspace? Would anyone be against having File
-> Open erase the current workspace before loading the new file? Is
there a compelling argument for having a dialog box that asks you which
sort of "File -> Open" you want?

Note that I still think that the LOAD command should merge into the
current workspace. I also think that if I ever implement drag&drop for
files, that should also merge (I'm not sure why, it just feels like it
should). The only behavior that I'm considering changing is when you
select File -> Open from the main menu.

Kindest Regards,

David Costanzo

LogoForum messages are archived at:
http://groups.yahoo.com/group/LogoForum

kohútek_petr

The message below is being cross-posted from LogoForum.

I think that better than dialog would be to make two menu commands:
File -> Open
File -> Load

this will be consistent with the command.
However it is also possible to name it "Open (merge)", or something
that will imply opening of a file.

Petr


-----Original Message-----
From: LogoForum@yahoogroups.com [mailto:LogoForum@yahoogroups.com] On
Behalf Of david_costanzo
Sent: Wednesday, May 31, 2006 8:12 AM
To: LogoForum@yahoogroups.com
Subject: [LogoForum] Does anyone like that FMSLogo File -> Open merges
into current workspace?

I have a question for FMSLogo and MSWLogo users.

Someone recently requested that selecting "File -> Open" from FMSLogo's
main menu should prompt the user if they want to replace the current
workspace with the new file, or merge the new file into the current
workspace. He said that his students end up with every procedure that


My students and I also have this problem, so I would like a solution to
it. But I would prefer not to add yet another dialog box (FMSLogo has
too many of them as it is and they seem to get in the way more than
they help). Does anyone like that File -> Open merges the new file
into the existing workspace? Would anyone be against having File
-> Open erase the current workspace before loading the new file? Is
there a compelling argument for having a dialog box that asks you which
sort of "File -> Open" you want?

Note that I still think that the LOAD command should merge into the
current workspace. I also think that if I ever implement drag&drop for
files, that should also merge (I'm not sure why, it just feels like it
should). The only behavior that I'm considering changing is when you
select File -> Open from the main menu.

Kindest Regards,

David Costanzo

LogoForum messages are archived at:
http://groups.yahoo.com/group/LogoForum

sirgimp

The message below is being cross-posted from LogoForum.

I think its a "real bad" idea to erase anything a user has created
without warning. I think some kind of prompt is the way to go. A "Merge
or Erase Workspace?" kind of thing. The Load command does merge and so
that is a kind of default. If you want Open to erase the workspace, you
must give the user a choice.
*
-----------------------------------------
Come play with Sir Gimp at the GimpBlog:
http://elgimpo.blogspot.com

Pray for Peace,
Jason and Donna Gervich


----- Original Message ----
From: david_costanzo <david_costanzo@yahoo.com>
To: LogoForum@yahoogroups.com
Sent: Tuesday, May 30, 2006 11:12:20 PM
Subject: [LogoForum] Does anyone like that FMSLogo File -> Open merges
into current workspace?

I have a question for FMSLogo and MSWLogo users.

Someone recently requested that selecting "File -> Open" from
FMSLogo's main menu should prompt the user if they want to replace the
current workspace with the new file, or merge the new file into the
current workspace.**He said that his students end up with every

My students and I also have this problem, so I would like a solution
to it.**But I would prefer not to add yet another dialog box (FMSLogo
has too many of them as it is and they seem to get in the way more
than they help).**Does anyone like that File -> Open merges the new
file into the existing workspace?**Would anyone be against having File
-> Open erase the current workspace before loading the new file?**Is
there a compelling argument for having a dialog box that asks you
which sort of "File -> Open" you want?

Note that I still think that the LOAD command should merge into the
current workspace.**I also think that if I ever implement drag&drop
for files, that should also merge**(I'm not sure why, it just feels
like it should).**The only behavior that I'm considering
changing is when you select File -> Open from the main menu.

Kindest Regards,

David Costanzo


LogoForum messages are archived at:
http://groups.yahoo.com/group/LogoForum

david_costanzo

The message below is being cross-posted from LogoForum.


I didn't ask the question properly. I agree that the user shouldn't
lose data without warning. Even the current behavior of merging into
the current workspace can lose data, so it requires a prompt if there
are unsaved changes. This is a separate problem and has a clear,
correct solution.

To rephrase my question:

If there are no unsaved changes (for example, if you just loaded the
wrong workspace or if you just saved your workspace), does File ->
Open just replace your workspace with the one in the file, or does it
prompt you if you want to either replace your workspace, or merge the
new file into your workspace.
The behavior of File -> Open when you have unsaved changes will always
give you a chance to cancel the operation.

To rephrase my question again:
Have you ever been glad that "File -> Open" merges the new file into
the current workspace as opposed to replacing it?

If the answer is "yes" then the GUI will support both options. For
me, the answer has *never* been "yes" and it has often been "no and
that behavior just caused me a problem". If the answer has never been
"yes" for anyone, then the merging behavior will be eliminated from
the GUI.

-David Costanzo


LogoForum messages are archived at:
http://groups.yahoo.com/group/LogoForum

david_costanzo

LogoForum@yahoogroups.com

Thank you to everyone who replied to my question, you all provided
excellent feedback.

I have decided that there is enough opposition to what I had proposed
that I will NOT make any changes to the way File -> Open behaves. I
may explore some other (more drastic) ways to solve the problem of


unburied procedures in the workspace, similar to what "File ->
Edit..." shows. This would serve as a visual reminder that you have
to do "File -> New" to clear your workspace. It might also make it
easier to bury/erase procedures selectivly (assuming that I add a
context menu).

-David Costanzo