<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Aw too bad then. I think some of the book resources out there are good enough. I remember when I was learning that I just didn't understand the scope of everything, and there wasn't a nicely illustrated graph of the api or anything. Of course, I picked seaside and smalltalk with very little programming experience to learn at the same time hehe.<br><br>RS<br><br>> Date: Mon, 23 Jan 2012 21:05:07 +0100<br>> Subject: Re: [Seaside] Live Ruby on rails tutorial sites<br>> From: philippe.marschall@gmail.com<br>> To: seaside@lists.squeakfoundation.org<br>> <br>> 2012/1/23 Robert Sirois <watchlala@hotmail.com>:<br>> > What about Amber?<br>> <br>> Amber doesn't run Seaside.<br>> <br>> > And then just limit the classes that are ever shown to the<br>> > user and delete them after the session times out or whatever?<br>> <br>> Ce n'est pas si facile que ça.<br>> <br>> (1 perform: ('cla', 'ss') asSymbol) environment at: ('Comp', 'iler') asSymbol<br>> <br>> And again, you give the web app user the full rights of the OS user<br>> that runs the image. Deleting the code that owned you after the<br>> session times out doesn't solve a thing once you've been owned. It<br>> also doesn't help if two users at the same time want to work on a<br>> class named 'Test' or 'MyClass' or 'Example'.<br>> <br>> Cheers<br>> Philippe<br>> _______________________________________________<br>> seaside mailing list<br>> seaside@lists.squeakfoundation.org<br>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside<br>                                            </div></body>
</html>