[Pharo-project] [Seaside] Re: [Metacello] What is the plan with Pharo changes?

Mariano Martinez Peck marianopeck at gmail.com
Sat Aug 4 12:14:12 UTC 2012

On Sat, Aug 4, 2012 at 2:01 PM, Stéphane Ducasse
<stephane.ducasse at inria.fr>wrote:

> On Aug 4, 2012, at 11:21 AM, Mariano Martinez Peck wrote:
> > Hi all. I am answering to all together:
> >
> > 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).
> >
> > 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:
> >
> > 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 :)
> > 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.
> I do not understand why metacello is concerned about
> systemChangeNotification.
Just to make certain things silent in the tests.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20120804/b22900a4/attachment.htm

More information about the seaside mailing list