<p dir="ltr">Yes, it just takes moving the extension to a platform - specific package. I know how to do that for Pharo, but I'm clueless what to do for Gemstone.</p>
<div class="gmail_quote">On Jun 16, 2014 4:48 PM, <<a href="mailto:seaside@googlecode.com">seaside@googlecode.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Comment #1 on issue 797 by <a href="mailto:jo...@yesplan.be" target="_blank">jo...@yesplan.be</a>: Seaside-JSON-Core extends BlockClosure but BlockClosure is not a portable class<br>
<a href="http://code.google.com/p/seaside/issues/detail?id=797" target="_blank">http://code.google.com/p/<u></u>seaside/issues/detail?id=797</a><br>
<br>
I guess this is a straightforward request and change. We just need to mind updating the Gemstone JSON package. There is a testcase covering this method, so it will pop up as broken when porting.<br>
<br>
-- <br>
You received this message because this project is configured to send all issue notifications to this address.<br>
You may adjust your notification preferences at:<br>
<a href="https://code.google.com/hosting/settings" target="_blank">https://code.google.com/<u></u>hosting/settings</a><br>
<br>
______________________________<u></u>_________________<br>
issues mailing list<br>
To unsubscribe, email <a href="mailto:issues-leave@lists.seaside.st" target="_blank">issues-leave@lists.seaside.st</a><br>
<a href="http://lists.seaside.st/listinfo/issues" target="_blank">http://lists.seaside.st/<u></u>listinfo/issues</a><br>
</blockquote></div>