Hi yuriy
A package manifest is the place where we keep package rules and meta data.
We should add documentation and others.
I think that all the packages should have a XXXManifest.
There we can define a method preUnload and after we can define a class
PackageUnloader (or put the logic in the PackageOrganiser way better :)).
So that we can say
PackageOrganiser current unload: 'XXX' and the preUnload is executed.
Stef
Le 27/8/16 à 16:23, Yuriy Tymchuk a écrit :
On 27 Aug 2016, at 11:00, stepharo <steph...@free.fr> wrote:
You see hernan doing positively is the best way to make that things happen
We can have a
preUnload hook
Now we should check how it fits with cleanForProduction and others.
But we should definitively have a way to express this.
So let us see how we can design it and then just implement it. I'm sure that GT
people are open to such hooks
and if you really want to get a better Pharo for you then talk to them and us.
https://pharo.fogbugz.com/f/cases/18997/Add-unload-to-package-manifest-in-QA
I like the idea, but how should it work? What is the package manifest? And how
the unload protocol looks like? Do I only add a method called #unload to
somewhere?
Uko
https://pharo.fogbugz.com/f/cases/18998/Add-unload-to-package-manifest-of-SpecDebugger
https://pharo.fogbugz.com/f/cases/18999/Add-unload-to-package-manifest-in-GT-Debugger
https://pharo.fogbugz.com/f/cases/19000/Add-unload-to-package-manifest-in-GT
Stef
