Hi Bill, AFAIK monticello use to get the first part of the class category to define if code goes into a package or not. Why don't you make your code go into a category named differently than something named as an existent package? cheers, sebastian
> -----Mensaje original----- > De: [email protected] > [mailto:[email protected]] En > nombre de Schwab,Wilhelm K > Enviado el: Friday, May 29, 2009 03:56 > Para: [email protected] > Asunto: [Pharo-project] Finding code > > I am finding that OB, Moniticello, or just plain gremlins are > making life hard on me. I have code that I want to package; > more specifically, I need to repackage some of it. I thought > it might make sense to name something Seaside-ThisOrThat, but > that turns out to get burried in the Seaside 2 category, and > moving clases and methods to SeasideThisOrThat or another > package frequently locks up the image. > > I have all of the relevant code captured in a change set. Is > it safe to edit the categories in the chunks and file that > into a new image? I did that (hopefully correctly) to a copy > of the change set in the hopes tha a new image would see > things in the correct place from the bginning. > > If any of this sounds like typical newbie (re Monticello) > growing pains, please say so. > > Bill > > > _______________________________________________ > 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
