> Well in the Workspace menubar menu I'm seeing I'm seeing save contents to file..., but no open. It doesn't make sense to have to go somewhere else to do that.

I never saw that before, but the problem with it is it just "dumps"
the text and doesn't assume FileList (model) behavior, where the
workspace is now associated with that file so that, when I press
Command+s, it will save to the file again.  To get that behavior we'd
have to "become" the Workspace to a FileList which is too complicated.

Now that I've seen "save contents to file..." I'd actually like to
remove it; it is totally inconsistent.

A Workspace is supposed to be transient, that's why it does not have
FileList capabilities.

 - Chris



>
> The issues are discussed in the mantis report.
>
> I would like a convenient way to programmatically save all my Workspaces to text files, then reload them for migration into a new image.
>
> Ken
>
>>Incidentally, we do already have a way to open files into a workspace.
>>
>>  World Menu | open... | file...
>>
>>But I agree it would be nice to be able to spawn independent windows
>>from the FileList..
>>
>>  - Chris
>>
>>On Tue, Dec 7, 2010 at 4:05 PM, Ken G. Brown <kbrown at mac.com> wrote:
>>> I'd like to suggest that
>>> M5669-Workspace-openFile.2.cs
>>>
>> > from http://bugs.squeak.org/bug_view_advanced_page.php?bug_id=5669 get pulled into Squeak 4.2.
>>>
>>> It has changes for Kernel-Models, ST80-Controllers, and Tools-Base.
>>> What are the steps necessary to get this changeset applied?
>>>
>>> Ken G. Brown
>>>
>>>
>
>
>