Hi all. I am answering to all together:<div><br></div><div>Stef: Yes, I imported and loaded the Pier of DBX website in Pharo 2.0 with seaside and magritte. With 5 minutes of opening debuggers and change things I was able to correctly make it work (at least, my app, I didn't run all tests to see).</div>
<div><br></div><div>Dale: We don't want to just help you with "hacks", that why I send this email and several others, to see what others think so that can find better and non-hacky solutions. So, let's try to find good solutions:</div>
<div><br></div><div>1) does it help if we put back FildeDirectory and we remove it later ? so that you have time to update Metacello and that we can still use Metacello :)</div><div>2) for the SystemChangeNotifier does it make sense to delegate to the closures? [ xx ] valueWithoutSystemNotifications. Or we add a #doSilently: and we add a MetacelloPharo20Platform that overrides the behavior. </div>
<div>3) as Janko said, what about improving/using Grease/Sport for this purpose? do they provide something for this? could this be added?</div><div>4) Should we integrate Metacello in the image with our changes until you have time and find a good solution that works everywhere? Maybe if we do 1) it is not very necessary.</div>
<div><br></div><div>Thanks for considering this a friendly and positive thread. <br><br><div class="gmail_quote">On Sat, Aug 4, 2012 at 9:16 AM, Janko Mivšek <span dir="ltr"><<a href="mailto:janko.mivsek@eranova.si" target="_blank">janko.mivsek@eranova.si</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Dale,<br>
<br>
Dne <a href="tel:04.%2008.%202012%2007" value="+33408201207">04. 08. 2012 07</a>:31, piše Dale Henrichs:<br>
<div class="im"><br>
> The bigger problem is that I have to have a code base that runs on multiple platforms while being maintainable, so a "port" to Pharo-2.0 is only a starting point. In the case of FileTree, which is the real bottleneck there's a lot code that is written against the FileDirectory API, so there will need to be significant work to find a way to keep a common code base .... a much tougher problem, than "just getting it working", it can be solved with time, but I didn't budget time for an emergency rewrite of FileTree ... today.<br>
<br>
</div>Just FYI, there is a Sport portability library and by using Sport's<br>
SpFilename you have an instantly portable file support over quite a<br>
dozen Smalltalks. So, if someone adapt Sport to a new Pharo 2.0<br>
filesystem first ..<br>
<br>
Best regards<br>
<span class="HOEnZb"><font color="#888888">Janko<br>
<br>
<br>
--<br>
Janko Mivšek<br>
Aida/Web<br>
Smalltalk Web Application Server<br>
<a href="http://www.aidaweb.si" target="_blank">http://www.aidaweb.si</a><br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
seaside mailing list<br>
<a href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Mariano<br><a href="http://marianopeck.wordpress.com" target="_blank">http://marianopeck.wordpress.com</a><br><br>
</div>