Hi Chris,<br>I don't have a lot of time but I am definitely willing to help.<br>It would be great if we could discuss this portability layer together, also including anyone else that wishes to participate.<br>To what packages belong all the GUI / eToys related extensions? What are they used for?<br>
Cheers<br><br>r.<br><br><br><br><br><br><br><div class="gmail_quote">2009/8/10 Chris Muller <span dir="ltr"><<a href="mailto:ma.chris.m@gmail.com">ma.chris.m@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br>
<div class="im"><br>
> As I saw on the list there are people interested on a version of Magma<br>
> running on Pharo. Even more now that the first release of Pharo is<br>
> close. But how will this be handled.<br>
> - It will be a fork (I hope not) living in a different repository.<br>
> - Will the changes (like the code testing for each plataform to react<br>
> accordingly, e.g. extensions to BlockContext should be extensions to<br>
> BlockContext on Pharo and new Squeak) be merged in the official Magma.<br>
> - Will you bless this new code (after running the test suite on your own<br>
> hw/image/machine) or will be handled like the seasideHelper that never<br>
> went to official Magma, at least as a separate package ŕ la<br>
> Collections-BTree-lr or WriteBarrier that are included in the official<br>
> Magma.<br>
<br>
</div>A platform-adapter integrated into Magma could be used to delegate<br>
platform-specific operations.. The individual platform subclasses<br>
could even be their own separately-loadable package. This approach<br>
would allow a single code-base for all platforms, and would<br>
(hopefully) be useful for making it VW-compatible.. I'm available for<br>
support on the Magma side. Any volunteers to do the actual work?<br>
<div class="im"><br>
> etc) the integration of Magma with Seaside/Aida are very important for<br>
> me. Because Pharo is intended as a real, strong and minimal platform for<br>
> running Seaside apps, I think that Magma has a very big opportunity to<br>
> be a real foundations.<br>
<br>
</div>Can you tell me some ideas you may have for the kinds of things you'd<br>
like to see in a web-"integration" package for Magma?<br>
<div><div></div><div class="h5">_______________________________________________<br>
Magma mailing list<br>
<a href="mailto:Magma@lists.squeakfoundation.org">Magma@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/mailman/listinfo/magma" target="_blank">http://lists.squeakfoundation.org/mailman/listinfo/magma</a><br>
</div></div></blockquote></div><br>