My last experience with my mvc only image was not successful. Maybe
this is related to lack of "graceful exception handling". However if those
serialization methods are not needed for core magma functionalities, how
about exclude them from core packages?
Anyway I'll try to install them. :-)
----- Original Message -----
From: Keith Hodges <keith_hodges(a)yahoo.co.uk>
To: "S.J.Chun" <chunsj(a)embian.com>, Magma(a)lists.squeakfoundation.org
Sent: 08-04-14 09:21:29
Subject: Re: [Q] Unneeded overhead?
S.J.Chun wrote:
> As you can see from MagmaCompatibilityLayer-pk.2.mcz in KernelImage
> repository, there're many unneeded GUI - mostly morph related - related
> classes on which magma is dependent.
>
> Should magma use thses classes? Are there any package or plan for
> removing these classes? I've once made changeset to remove these classes
> but when I want to update these classes are big hurdle. This is my reason
> of avoiding magma.
>
> Thanks in advance.
Magma is not depending upon these classes at all. It simply provides
some methods for serializing these classes.
If you have not got those classes in the image then you dont need the
methods for serializing them. If those classes are not present, simply
load magma anyway, ignoring the warnings. It is rather silly for the
Kernel Image Compatability Layer to provide these classes as dummies,
but I seem to remember that the KernelImage doesnt have any facilities
for handling exceptions gracefully
Keith