March 2010 - Pharo-users - lists.pharo.org

Re: [Pharo-users] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1

by Mariano Martinez Peck

2010/3/21 Miguel Enrique CobÃ¡ Martinez <miguel.coba(a)gmail.com> > El sÃ¡b, 20-03-2010 a las 20:40 +0100, Mariano Martinez Peck escribiÃ³: > > Hi folks. We are proud to announce the (hopefully) last RC3 for Pharo > > 1.0. > > - What happened to the background image? > I said several times I don't have a screen to test. And I ask several times for help. I won't do everything. I don't know how to do it neither how to test it. So, or someone do it and test it, or it won't be again. I only remember this link, but there were more opportunities: http://n4.nabble.com/Latest-Polymorph-td1468728.html#a1468728 > - The text on: DEVImageWorkspaces openExternalProjectWorkspace at the > end says: > > "If you want an object database, you can install Magma > (http://wiki.squeak.org/squeak/2665) > For the installation instuctions check the method: ConfigurationOfMagma > >> workspace " > > Can we change this to: > > "Magma is an object oriented database for Smalltalk. It supports > replication, high-availability fault-tolerance and multiuser > capabilities (http://wiki.squeak.org/squeak/2665) You can install it > with: > > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfMagma'; > load. > > ((Smalltalk at: #ConfigurationOfMagma) project latestVersion) load > > "You can also review the method ConfigurationOfMagma>>workspace for > alternative installation methods for Magma. > Sure, no problem. I will do. > > - Also, in the same workspace: > Gofer new > squeaksource: 'Moose'; > package: 'ConfigurationOfMoose'; > load. > > (Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault. > > Should be: > Gofer new > squeaksource: 'Moose'; > package: 'ConfigurationOfMoose'; > load. > > (Smalltalk at: #ConfigurationOfMoose) loadDefault > > As the other examples use the methods directly and not the perform > indirection. > > Yes, true. But the problem is that as loadDefualt doesn't exist in the image, with the Shout Workpsace you see that word in red...is not nice. What do you think ? Thanks for the feedback. Mariano > > Cheers > > > > > > _______________________________________________ > > Pharo-users mailing list > > Pharo-users(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > >

March 21, 2010

Re: [Pharo-users] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1

by Mariano Martinez Peck

> > I see that the installScript uses ConfigurationOfMetacello from > gemsource metacello repository instead of Metacello repository. Given > that this will be the final release of 1.0, shouldn't we copy > ConfigurationOfMetacello to squeaksource/MetacelloRepository so that the > package registered in monticello is this instead of the gemstone one. > This repo for ConfigurationOfMetacello overrides the one of PharoCore > that points to squeaksource. > > Dale, can you put this version in squeaksource. The release is very > close and anyway it will be shipped in Pharo dev 1.0, so will reach a > lot of people, even if not on squeaksource > > Yes. This is because I added the ImageForDevelopers in the group. With that, when running headless I have the problem with the progress Bar. Then, i needed to use the silntly method, which is in Metacello beta.25 which is not released yet. That's why I have to put the other one. Don't worry that beta.25 will be then correctly uploaded and released. After that, the installScript will be even simpler as I won't need to install Metacello manually, but with the ensureMetacello ;) Cheers Mariano > Cheers > > > > Mariano > > > > _______________________________________________ > > Pharo-users mailing list > > Pharo-users(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > >

March 21, 2010

Re: [Pharo-users] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1

by Miguel Enrique CobÃ¡ Martinez

El sÃ¡b, 20-03-2010 a las 20:40 +0100, Mariano Martinez Peck escribiÃ³: > Hi folks. We are proud to announce the (hopefully) last RC3 for Pharo > 1.0. - What happened to the background image? - The text on: DEVImageWorkspaces openExternalProjectWorkspace at the end says: "If you want an object database, you can install Magma (http://wiki.squeak.org/squeak/2665) For the installation instuctions check the method: ConfigurationOfMagma >> workspace " Can we change this to: "Magma is an object oriented database for Smalltalk. It supports replication, high-availability fault-tolerance and multiuser capabilities (http://wiki.squeak.org/squeak/2665) You can install it with: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfMagma'; load. ((Smalltalk at: #ConfigurationOfMagma) project latestVersion) load "You can also review the method ConfigurationOfMagma>>workspace for alternative installation methods for Magma. - Also, in the same workspace: Gofer new squeaksource: 'Moose'; package: 'ConfigurationOfMoose'; load. (Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault. Should be: Gofer new squeaksource: 'Moose'; package: 'ConfigurationOfMoose'; load. (Smalltalk at: #ConfigurationOfMoose) loadDefault As the other examples use the methods directly and not the perform indirection. Cheers > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users -- Miguel CobÃ¡ http://miguel.leugim.com.mx

March 21, 2010

Re: [Pharo-users] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1

by Miguel Enrique CobÃ¡ Martinez

El sÃ¡b, 20-03-2010 a las 20:40 +0100, Mariano Martinez Peck escribiÃ³: > Hi folks. We are proud to announce the (hopefully) last RC3 for Pharo > 1.0. > > This image is based in PharoCore-1.0-10515rc3. The image also contain > lot of fixes and improvements of external packages: > > These, are the fixed issues of the external tools: > > OB: Issues 1891, 1748, 1670, 1667, 1705, 1667 > > O2: issues 1887, 1312, 1429, 1886, 2073 > > New Inspector: issues 1783, 1499 > > Refactoring Browser: issue 2108 > > The link is: > https://gforge.inria.fr/frs/download.php/26680/Pharo-1.0-10515-rc3dev10.03.… > > Cheers I see that the installScript uses ConfigurationOfMetacello from gemsource metacello repository instead of Metacello repository. Given that this will be the final release of 1.0, shouldn't we copy ConfigurationOfMetacello to squeaksource/MetacelloRepository so that the package registered in monticello is this instead of the gemstone one. This repo for ConfigurationOfMetacello overrides the one of PharoCore that points to squeaksource. Dale, can you put this version in squeaksource. The release is very close and anyway it will be shipped in Pharo dev 1.0, so will reach a lot of people, even if not on squeaksource Cheers > > Mariano > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users -- Miguel CobÃ¡ http://miguel.leugim.com.mx

March 21, 2010

GSoC next steps

by Mariano Martinez Peck

Hi folks. We received several mails asking questions for the next step. So I think it is a good idea to clarify it a bit. Mentors and students, will have to register in Google GSoC website, but first we want them to be registered in our ESUG GSoC website. Why? Several reasons: 1. We are trying to approach this year GSoC on a more organized way, 2. that's why we are building that special Smalltalk GSoc website, 3. to support you, the students and the projects as best as possible. We are developing this registration in our website and it was almost finish. We will call for mentors first. We created a mailing list for all the mentors. If you are mentor, you should be there. If you are not, please contact us. We had already sent an email to mentors mailing list to invite them to register as mentors in our ESUG GSoC website. If we discover bugs during that period, they will be fixed. Once after all mentors have been successfully registered and the registration process is working correctly, then we will invite students to register also. After that, students and mentors will be registered in our website, each of them will have each other's contact information, each will have their own page for the project, etc. Once all of this is done, then mentors and students will register in the Google GSoC webpage. Finally, mentors will vote and choose the projects to be selected. Even more, if there is more than one student for the same project, the mentor will have to choose. Cheers GSoC admin team esug.gsoc.adm2010(a)gmail.com http://gsoc2010.esug.org/

March 21, 2010

Re: [Pharo-users] [Pharo-project] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1

by StÃ©phane Ducasse

thanks a lot mariano. this is cool to have somebody like you helping and pushing pharo that way. Stef On Mar 20, 2010, at 8:40 PM, Mariano Martinez Peck wrote: > Hi folks. We are proud to announce the (hopefully) last RC3 for Pharo 1.0. > > This image is based in PharoCore-1.0-10515rc3. The image also contain lot of fixes and improvements of external packages: > > These, are the fixed issues of the external tools: > > OB: Issues 1891, 1748, 1670, 1667, 1705, 1667 > > O2: issues 1887, 1312, 1429, 1886, 2073 > > New Inspector: issues 1783, 1499 > > Refactoring Browser: issue 2108 > > The link is: https://gforge.inria.fr/frs/download.php/26680/Pharo-1.0-10515-rc3dev10.03.… > > Cheers > > Mariano > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 20, 2010

Re: [Pharo-users] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1

by Johan Fabry

Excellent news! I am looking forward to trying it out! (probably will be next month though ...) On 20 Mar 2010, at 16:40, Mariano Martinez Peck wrote: > Hi folks. We are proud to announce the (hopefully) last RC3 for Pharo 1.0. > > This image is based in PharoCore-1.0-10515rc3. The image also contain lot of fixes and improvements of external packages: > > These, are the fixed issues of the external tools: > > OB: Issues 1891, 1748, 1670, 1667, 1705, 1667 > > O2: issues 1887, 1312, 1429, 1886, 2073 > > New Inspector: issues 1783, 1499 > > Refactoring Browser: issue 2108 > > The link is: https://gforge.inria.fr/frs/download.php/26680/Pharo-1.0-10515-rc3dev10.03.… > > Cheers > > Mariano > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users -- Johan Fabry jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile

March 20, 2010

Re: [Pharo-users] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1

by Mariano Martinez Peck

Sorry, the link is actually this one: https://gforge.inria.fr/frs/download.php/26681/Pharo-1.0-10515-rc3dev10.03.… On Sat, Mar 20, 2010 at 8:40 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > Hi folks. We are proud to announce the (hopefully) last RC3 for Pharo 1.0. > > This image is based in PharoCore-1.0-10515rc3. The image also contain lot > of fixes and improvements of external packages: > > These, are the fixed issues of the external tools: > > OB: Issues 1891, 1748, 1670, 1667, 1705, 1667 > > O2: issues 1887, 1312, 1429, 1886, 2073 > > New Inspector: issues 1783, 1499 > > Refactoring Browser: issue 2108 > > The link is: > https://gforge.inria.fr/frs/download.php/26680/Pharo-1.0-10515-rc3dev10.03.… > > Cheers > > Mariano > >

March 20, 2010

[BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1

by Mariano Martinez Peck

Hi folks. We are proud to announce the (hopefully) last RC3 for Pharo 1.0. This image is based in PharoCore-1.0-10515rc3. The image also contain lot of fixes and improvements of external packages: These, are the fixed issues of the external tools: OB: Issues 1891, 1748, 1670, 1667, 1705, 1667 O2: issues 1887, 1312, 1429, 1886, 2073 New Inspector: issues 1783, 1499 Refactoring Browser: issue 2108 The link is: https://gforge.inria.fr/frs/download.php/26680/Pharo-1.0-10515-rc3dev10.03.… Cheers Mariano

March 20, 2010

Re: [Pharo-users] Does vm shipped with Squeak 4.0 support closures? [cross posted]

by Mariano Martinez Peck

Hi Tom. Squeak V4.0 as far as I understood (I may be wrong) doesn't support closures as it is the same as Squeak 3.10.2 but with changes in the license. Squeak trunk (not 4.0) do support closures, the same as Pharo. For the Pharo side, it is easy. From http://www.pharo-project.org/pharo-download you can download the image and the VM and it will work. Seaside one click images are based on Pharo, so the same applies for Seaside. A closure enable VM should work also with non-closure images (like squeak v4.0) as I understand (again, I may be wrong). I saw a mail from Chris in squeak-dev saying he has a problem with the SqueakVM...so I am not sure if the VM shipped supports closures or not. Hope this helps. Mariano On Thu, Mar 18, 2010 at 10:25 PM, <Tom.X.Porter(a)gmail.com> wrote: > I know that Pharo (or at least Pharo with seaside) requires a VM with > closure support, and the Pharo download page gives access to a vm 4.2.2b1 > that supports them. > > Squeak V4.0 has a vm 4.2.3.b1u, but I am unclear if it was build with > support for closures. I just thought I would check on the pharo list and > with the mouse folks as well, as I run both on my mac. I guess I might need > both VM's. > > Thanks to both for all the hard work! > > Tom P. > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > >

March 19, 2010