On 20 janv. 2010, at 14:02, Henrik Johansen wrote: > > On Jan 20, 2010, at 1:25 09PM, Simon Denier wrote: > >> >> On 20 janv. 2010, at 11:29, Mariano Martinez Peck wrote: >> >>> Hi: I found that several times, we need to run some piece of code after a >>> slide. The only way I see doing this is to write it in a txt , and, >>> hopefully (many times, the commiter or the integrator forget about it), >>> remember to put that in the email or issue, when I let you know the fix is >>> ready. Is there a better way ? >>> >>> What about having a method in ScriptLoader where we can commit that >>> together with the slice? Then when someone integrates that, it will see >>> that, and will move that piece of code, from there, to the update or script >>> methods. >>> >>> I don't know. What do you think ? >> >> >> If I understood correctly, Monticello already has this feature for package >> so I guess it should work for slices. >> >> Click on a package in MC browser, then click on the 'Scripts' button in the >> toolbar, you get menu to edit the preamble, postscript, as well as >> preambleOfRemoval and postscriptOfRemoval > > Preamble/Postscripts don't work anymore in Pharo though, following the > procedure you outlined I get a DNU when selecting the script I want to edit. > Not sure when they were removed, but probably it was part of some PackageInfo > cleaning.
Ah, actually I have never used the feature, but I thought some people used it for some packages (typically requiring to clean stuff in globals). Maybe someone else can help? -- Simon
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
