<div dir="ltr">Okay, I've put it in the inbox as System-bf.916.<div><br></div><div>Are we sure about removing the ability to store? I just noticed that Eliot claimed to have fixed ImageSegments in System-eem.758. OTOH if nobody intends to use them it's better to get rid of the dead code.<br><div><br></div><div>- Bert -</div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 14, 2016 at 5:48 AM, H. Hirzel <span dir="ltr"><<a href="mailto:hannes.hirzel@gmail.com" target="_blank">hannes.hirzel@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">+1<br>
<div class="gmail-HOEnZb"><div class="gmail-h5"><br>
On 9/13/16, Tobias Pape <<a href="mailto:Das.Linux@gmx.de">Das.Linux@gmx.de</a>> wrote:<br>
> +1<br>
> On 13.09.2016, at 22:09, Bert Freudenberg <<a href="mailto:bert@freudenbergs.de">bert@freudenbergs.de</a>> wrote:<br>
><br>
>> Hi all,<br>
>><br>
>> I think there is no current usage of image segments. Project storing has<br>
>> been broken for a while and that's the only current use I am aware of.<br>
>><br>
>> What about this idea:<br>
>><br>
>> We keep ImageSegment but remove all support for writing. It would only be<br>
>> used for importing old projects. It would not use the VM primitives<br>
>> (because they are incompatible anyways).<br>
>><br>
>> The number of methods in ImageSegment would shrink from more than 80 to<br>
>> 15. My SegmentLoader has 25 methods, it replaces the VM primitive. Cog<br>
>> appears to be fast enough to not cause a significant slowdown in loading.<br>
>><br>
>> With this, old projects can still be imported, but writing projects would<br>
>> have to use some other serialization mechanism (which we discussed<br>
>> before). It would remove quite a bit of unused code, making the remaining<br>
>> code more easily understandable.<br>
>><br>
>> Sounds good?<br>
>><br>
>> - Bert -<br>
>><br>
><br>
><br>
><br>
<br>
</div></div></blockquote></div><br></div></div></div>