Hi Keith,<br>Indeed, I remember from trying it probably more than a year ago, that your Seaside Magma integration was brilliant, and it covered all the important issues for a web application, such as session sharing / pooling and general configuration integrated to Seaside.<br>
I hope it is not to difficult to make it run again. I eagerly wait for the 81 version of Jetsam :).<br>Magma seems to be running very well and I would really love to see that stack running together again.<br>Cheers<br><br>
r.<br><br><br><div class="gmail_quote">On Mon, Aug 10, 2009 at 7:07 PM, Keith Hodges <span dir="ltr"><<a href="mailto:keith_hodges@yahoo.co.uk">keith_hodges@yahoo.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="h5">Chris Muller wrote:<br>
> Hi,<br>
><br>
><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>
><br>
> 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>
><br>
><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>
><br>
> 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>
><br>
><br>
</div></div>Honestly Magma-seasideHelper probably contains everything and the<br>
kitchen sink.<br>
<br>
There is also a Magma control panel.<br>
<br>
It also contains a mechainism for multiple applications to merge onto a<br>
single db. So for example a user logins component, can be running<br>
alongside a store-products component.<br>
<br>
best regards<br>
<font color="#888888"><br>
Keith<br>
</font><div><div></div><div class="h5"><br>
_______________________________________________<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>