[Vm-dev] Nuking VM ImageSegment support (was Re: [squeak-dev] Daily Commit Log; System-bf.916)

H. Hirzel hannes.hirzel at gmail.com
Fri Sep 23 18:51:55 UTC 2016


Just for clarity:

Please note that saving a project (menu 'project' / 'save project') is
not yet working.

It breaks in

MorphicProject>>exportSegmentWithChangeSet: aChangeSetOrNil fileName: aFileName
directory: aDirectory withoutInteraction: noInteraction

world cleanUpReferences.

(world is a PasteUpMorph)


On 9/23/16, H. Hirzel <hannes.hirzel at gmail.com> wrote:
> Hello Jakob
>
> On 9/23/16, Jakob Reschke <jakob.reschke at student.hpi.de> wrote:
>> Hi Vaidotas,
>>
>> I cannot reproduce this. In my current trunk image where I
>> coincidentally try to get familiar with Environments to put them to
>> use, I can save morphs without a debugger appearing.
>
> This is indeed the case.
> A test case for Squeak6.0alpha-16755?
>
> 1. In a project activate the 'objects' flap.
> 2. Choose the 'Multimedia' category
> 3. Drag out a bookmorph
> 4. In the control bar click on the top-right icon to get 'more controls'
> 5. Add some morphs to the page
> 6. Add another page by clicking on 'plus' and add more morphs
> 7. Bring up the 'halo' menu
> 8. Choose submenu 'debug' and then 'save morph in file'.
> 9. Delete the morph
> 10. Choose menu 'tools' / 'File list'
> 11. Identify the file of the saved bookmorph and click on it.
> 12. Choose 'Load as morph'
>
> Result OK
>
> Questions:
> a) Since then is this working again?
> b) Which underlying mechanism is used to do this?
>
>
> --Hannes
>
>> Loading via drag
>> and drop works as well (though the option "load as morph" appears
>> twice in the dialog that prompts me for an action after the drop).
>>
>> Does Morph saving depend on ImageSegments anyway?
>>
>> Best regards,
>> Jakob
>>
>> 2016-09-23 16:10 GMT+02:00 Vaidotas Didžbalis <vaidasd at gmail.com>:
>>> Hello all,
>>> To save morph and restore it is a basic behavior which is broken since
>>> Squeak 4.5. This is a bug. Beginning from 4.5 new Squeak user will get a
>>> debugger window open in a few clicks. This bug happened as a side effect
>>> of
>>> pushing Environments package into the Squeak image beginning from Squeak
>>> 4.5. No one uses Environments; there are significant use for morph
>>> saving.
>>> Squeak needs this ability. Maybe it is easier to remove Environments
>>> from
>>> stock Image and to fix the bug introduced by that package.
>>> Introduction of new packages need not to break useful things...
>>> regards,
>>> Vaidotas
>>>
>>
>>
>


More information about the Squeak-dev mailing list