On 2006-12-22, at 03:35, Lukas Renggli wrote:
For
development purposes, I can live with manually flushing the
cache as needed.
It was like this in beginning of Magritte. It is just more
convenient not to have to worry about invalid caches. Maybe in you
case you want to disable it altogether, have a look at
MANamedBuilder and replace its references (should be only one) with
your own implementation that does not cache.
I was poking around the VW image today, and I've found a spot to hook
in flushing behavior fairly simply, if it's sufficient to flush just
the instance returned by MADescriptionBuilder class>>default.
Otherwise, I think a slightly more ambitious bit of coding will be
needed.
Otherwise, SeasidePlatformSupport looks like the place to add in some
hooks to register for change notification, since it already gets sent
#refactoringChange: when code is modified. What do you think, Michel?
--
============================================================
Thomas Koschate