Hi, I did a fast test. I moved classes Object and Class to a new package named Core and then I saved the package Core and Kernel to a local repository. Then I closed the image without saving and tried to load new versions of Kernel and Core. Of course it failed. Then I tried to load to a fresh image Core and Kernel and it passed (as expected). So I tried to move this two classes to a system category named "tmp" and load Kernel and Core. It passed.
So this process is working well and may to save us a lot of troubles. It would be great to have it as a direct part of Monticello. Cheers, -- Pavel On Tue, Jun 22, 2010 at 6:00 PM, Stéphane Ducasse <[email protected]> wrote: > I do not know :) > did you try? > > Stef > > On Jun 22, 2010, at 12:37 PM, Pavel Krivanek wrote: > >> Hi Stef, >> >> I have a little idea about processing of package movements. What about >> to move classes that will belong in the next update to another package >> to the new temporary system category using the update script. That >> temporary category will not have any corresponding package. Then the >> update process will load new versions of the packages but because the >> moved classes will not be in any package, the loading order will be >> irrelevant and the right package will be assigned to the class during >> the mergin. The temporary category will be empty in the end and can be >> removed. The same way can be applicable for methods. >> >> Cheers >> -- Pavel >> >> On Mon, Jun 21, 2010 at 5:51 PM, Pavel Krivanek >> <[email protected]> wrote: >>> Hi Stef, >>> >>> 1) this UIManager patch >>> 2a) there is a small count of minor kernel changes that should be >>> harvested (SoundService and Browser dependency etc.) >>> 2b) http://code.google.com/p/pharo/issues/detail?id=2105, I will have >>> to check it again for the latest Pharo. >>> >>> In this stage it should be possible to shrink the image to about 3MB >>> (very unclean) >>> >>> 3) reorganize methods to clean the kernel packages, >>> 4) prepare network and monticello packages (quite easy) >>> 5) modify the rest of packages to be loadable >>> >>> None of this steps is hard or extremely time consuming. However it >>> requires at least two next eyes to audit the changes and a >>> selfmurderer to integrate it into the update stream ;-) >>> >>> -- Pavel >>> >>> >>> On Mon, Jun 21, 2010 at 3:57 PM, Stéphane Ducasse >>> <[email protected]> wrote: >>>> >>>> On Jun 21, 2010, at 12:03 PM, Pavel Krivanek wrote: >>>> >>>>> Hi Mariano, >>>>> >>>>> it is not so straightforward. You simply cannot switch from Morphic to >>>>> DummyUIManager (it requires several next steps and modifications). >>>>> This patch is only a small step to better Pharo UI Independency and >>>>> PharoKernel. >>>> >>>> It would be good to identify a roadmap of actions to step by step >>>> arrive to this point. >>>> Do you have a high level list? >>>> >>>> >>>>> When Pharo will be PharoKernel ready, we may start to >>>>> talk about benefits for the deployment. However you may add me as the >>>>> book user ;-) >>>>> >>>>> -- Pavel >>>>> >>>>> 2010/6/21 Mariano Martinez Peck <[email protected]>: >>>>>> Hi pavel. This is excellent :) >>>>>> >>>>>> Now, it would be cool to document how to use it. And even more, the >>>>>> scenarios where it can be useful. For example, suppose I deploy a >>>>>> headless >>>>>> PharoCore image with seaside, should I replace the UIManager with the >>>>>> Dummy >>>>>> ? what do I save? how can I do that? >>>>>> >>>>>> I think http://book.pharo-project.org/ is excellent for this. If you >>>>>> want >>>>>> to write something please let me know and I make you an user. >>>>>> >>>>>> Thanks again >>>>>> >>>>>> mariano >>>>>> >>>>>> On Thu, Jun 17, 2010 at 11:36 AM, Pavel Krivanek >>>>>> <[email protected]> >>>>>> wrote: >>>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I updated issue http://code.google.com/p/pharo/issues/detail?id=2069 >>>>>>> that adds DummyUIManager and makes Pharo more UIManager independent. >>>>>>> >>>>>>> Please review it, it is an important patch for better modularization. >>>>>>> >>>>>>> For the method fileInSilentlyAnnouncing: it only changes the category. >>>>>>> >>>>>>> Cheers, >>>>>>> -- Pavel >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Pharo-project mailing list >>>>>>> [email protected] >>>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Pharo-project mailing list >>>>>> [email protected] >>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>>> >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> [email protected] >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> [email protected] >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >> >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
