Mariano, I noted your(??) comment about how some people will have significant work to build a new image. I somewhat fall into that category, and *really* fell into it as soon as I ported a few of my big packages to Pharo. Three things that I found missing were: (1) a way to identify work that I had failed to package; (2) a clean way to save large numbers of packages in one step; (3) a clean way to load a lot of code into a new image. By no means complete or perfect, I ended up with a "port" of a Dolphin goodie of mine I call Migrate. The intent is that users would sub-class it it to describe their packages. The recent move toward Gofer will probably have some impact on it, and a larger problem is that I need to clean up comments that contain things I do not want to make public. I mentioned this a while back and the response was underwhelming, but it is probably worth another mention, especially since there does not appear to be a magic solution to the problem. If there were, you would advising testers about how easy it will be for them to make a new image, right? :) The basic idea of Migrate is to iteratively extend your own #homeGrownPackageNames list until the suspect methods report is clean, or least understandable and ignorable. At that point, it is (in my experience) easy to save packages and make them available for a new image. Load Migrate and your subclass into the new image, and ask it to load packages. I would be happy to clean it up and make it available if there is any interest. A relevant class comment appears below. Bill CONFIGURE ========= Configure it using #homeGrownPackageNames and #me to tell it which packages are intended to hold your work, and how to identify you from the (misnomer!!!) #timeStamp aspects of the compiled methods you produce. SAVE YOUR WORK ============== Use #suspectMethodsReport to produce a listing of class>>selector names that might be in danger of being orphaned in your current image. Use #homeGrownPackgesSaveWithMessage: to save all of the identified home grown packages in the next version and with the common text message. BUILD A NEW IMAGE ================= Load Migrate into a new image. It wants underscore_madness.cs, and loads SIXX and other packages of interest to me; you can edit as needed to remove what you do not want to load. Put your packages in the cache directory for the new image. Yes, it is fussy about these things, but the idea is to find errors early rather than being stopped after a long wait. Likewise, if you do not like what #setPreferences does, edit it. ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Mariano Martinez Peck [marianopeck@gmail.com] Sent: Saturday, January 02, 2010 8:39 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Pharo testers.... WE NEED YOU!!! Cool....we are already 13 beta testers :) More than enought :) I updated http://code.google.com/p/pharo/w/list And we almost cover all the conbinations of OS, Browser and type of image :) Cheers Mariano On Sat, Jan 2, 2010 at 2:30 PM, Mariano Martinez Peck <marianopeck@gmail.com<mailto:marianopeck@gmail.com>> wrote: On Sat, Jan 2, 2010 at 1:50 AM, Hernán Morales Durand <hernan.morales@gmail.com<mailto:hernan.morales@gmail.com>> wrote: Hi Mariano, I don't use dev or web images. I've found the PharoCore more stable, for example now I'm fixing a dependency browser bug in the dev image #10502 (trying a dev after a long time), and clicking with the right button gives me : MessageNotUnderstood: OBTextSelection>>isMethodNode Yes, this is issue: http://code.google.com/p/pharo/issues/detail?id=1182 but isn't just that bug, I've never worked 30 minutes with the dev/web images without interaction bugs. I wonder what happens with Smalltalk and Pharo newcomers when these bugs appears, but there's no survey system for Pharo users so no one can't figure out anyway. Well, fortunately there are no too many public word of mouth recommendation systems yet :) Hernán: I agreee 100%. All of what you describe is what I said in the email with subject "We need to do something, seriously, ..." And that's exactly what I proposed to do this stuff about the beta testers. Cheers Mariano Cheers, Hernán 2010/1/1 Mariano Martinez Peck <marianopeck@gmail.com<mailto:marianopeck@gmail.com>>:
Sorry, I realize something. Maybe it would be cool also if you tell us if you use web or dev. I happens also several times that the seaside installation, or pier or whatever are not working very well. So...it would be cool to have both testers :)
If you have access to the wiki, just add your self on it. If you don't have access ask to Adrian and he will give you. Finally you can put it here and then I put it in the wiki.
Cheers!
Mariano
On Fri, Jan 1, 2010 at 10:56 PM, Mariano Martinez Peck <marianopeck@gmail.com<mailto:marianopeck@gmail.com>> wrote:
Ok.....I collect all the information here:
http://code.google.com/p/pharo/wiki/ListOfBetaTesters
Feel free to add something else.
The only thing we need now is Damien's answer...maybe he is in holidays, I don't know.
The last thing I would like to propose is that when we have a new image to test, not only we send the email to the mailing list but also cc to each of us. There is a lot of traffic (fortunately!!) in Pharo mailing list and not all the people here keeps truck for it every day. So, I think having them in cc is a good idea.
Cheers,
M
On Fri, Jan 1, 2010 at 12:41 AM, Miguel Cobá <miguel.coba@gmail.com<mailto:miguel.coba@gmail.com>> wrote:
So...here is the list, if you offer yourself, it would be cool to know: OS, VM version, Dev or Web, browser you usually work, 32 o 64 bits, I will then collect this and I will put it in the wiki.
- Mariano Martinez Peck. Mac OS, Squeak 4.2.2beta1U.app, Dev, OB, 32 bits - Stan Shepherd
WHO ELSE IS IN THE LIST ??
Me too.
- Miguel Cobá, Debian GNU/Linux Squeeze (testing), Pharo0.1 of 16 May 2008 [latest update: #10074], Web, OB, 32 bits
cheers and happy new year!!
Feliz año también Mariano.
Miguel Cobá http://miguel.leugim.com.mx
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project