<br><br><div class="gmail_quote">On Wed, May 25, 2011 at 5:14 PM, Yanni Chiu <span dir="ltr"><<a href="mailto:yanni@rogers.com">yanni@rogers.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 24/05/11 4:39 PM, Martin Dias wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
We really appreciate all kind of feedback and comments. If you want to<br>
try it, check in the website how to do it. It is extremely easy.<br>
</blockquote>
<br></div>
I had a brief look and will look some more. I may try to use it to serialize a Pier kernel.<br>
<br></blockquote><div> </div><div>heheheheh. We would LOVE that. In fact, I told martin few months ago to do EXACTLY that. <br>If you could give it a try or need help, please let us know.<br><br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
In another use case, I'd like to serialize from one image, and deserialize in another image - under end user control. The issue here is that "nasty" code could be introduced: e.g. capture the Fuel output, deserialize, add nasty code, re-serialize, then send onward for import to image. Would it be possible to have some sort of "virus" filter? Maybe something like the Star Trek transporter that can filter out nasty stuff before re-materializing. :) For a start, maybe an inclusion list and/or an exclusion list of classes and globals would be useful.<div>
<div></div><div class="h5"><br></div></div></blockquote><div><br>I guess this should be easy to do. For the moment:<br><br>- globals objects are hardcoded in #globalNames<br>- globals behaviors (classes and traits) are managed (by default) in kind of "light" serialization. Where we only serialize the global name which means that the class has to be present in Smalltalk globals in the image that you want to materialize.<br>
<br>You can change the default behavior and be able to completely serialize a class/trait. But this is much more complicated and it is still work on process (ClassBuilder is not your best friend).<br><br>Cheers<br clear="all">
<br></div></div><br>-- <br>Mariano<br><a href="http://marianopeck.wordpress.com" target="_blank">http://marianopeck.wordpress.com</a><br><br>