August 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [ANN] Pharo Metacello Universes

by StÃ©phane Ducasse

On Aug 4, 2010, at 11:46 AM, Torsten Bergmann wrote: > Hi Miguel, > > hey, nice! If we follow this convention then it is easy to implement > a universe browser that selects the correct universe repo and > displays all loadable versions. Yes this was the idea behind metacelloRepositories we talk about with dale on the metacello ml. But you probably know that. > Loading stuff should just be > a few clicks away - I personally hate all this MC/Gofer typing ... expect if you work with multiple images and you have to always clicks clicks clicks.... > > Attached is a quick/simple implementation of such a browser: > > - file in the attached changeset (I tried in Pharo 1.2) > - open via World menu -> "Universe Browser" > - select the configuration you want and from the context menu choose > -- "Load configuration" -> only the config is loaded > -- "Load configuration and latest version" -> the config and lates version is loaded > > Have fun! I used Pharo 1.2 - should work in Pharo 1.0 and 1.1 too > (havent tested). Cool as soon as we fix the name I will integrate your browser in 1.2 Can you open an issue? Stef > > Bye > T. > -- > GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 > <Universe-UI.st>_______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 4, 2010

Re: [Pharo-project] [ANN] Pharo Metacello Universes

by StÃ©phane Ducasse

Yes! Good push now I understand what you meant with Universe. Now two important comments for me: The problem One is that we are creating another vocabulary - Why not sticking with MetacelloRepositoryForPharo10? Like that we will not have to explain an Universe is a metacello repository..... Second point: what I would like is to have that all the dependent packages and configurations are copied into the metacelloRepository. I do not want to have dependency to any external servers. This way we will self-contained distribution. Do you handle that? Else this is great. Stef On Aug 4, 2010, at 11:41 AM, Adrian Lienhard wrote: > Hi Miguel, > > Thanks! It's great to see progress on this front! > > Cheers, > Adrian > > On Aug 4, 2010, at 10:21 , Miguel Enrique CobÃ¡ MartÃnez wrote: > >> Hi all, >> >> I have created three new repositories on squeaksource: >> >> http://www.squeaksource.com/UniverseForPharo10 >> http://www.squeaksource.com/UniverseForPharo11 >> http://www.squeaksource.com/UniverseForPharo12 >> >> They are the repositories for the current versions of Pharo. The idea is >> that each new release add a new UniverseForXXX repository and populates >> it with the current UniverseForXXX packages of the stable release. >> >> Right now they are mostly empty, but should be populated by the >> community and the ConfigurationOfXXX maintainers. >> >> Most ConfigurationOfXXX packages in >> >> http://www.squeaksource.com/MetacelloRepository >> >> should be copied to UniverseForPharo10. Which versions? The last known >> version that is working correctly on Pharo 1.0. This will be the >> official universe for Pharo1.0. No ConfigurationOfXXX should be stored >> on UniverseForPharo10 if it is not working correctly on Pharo10. >> >> Then two things can follow: >> >> - If the package already has ConfigurationOfXXX package versions that >> work in Pharo 1.1, those versions should be copied to >> UniverseForPharo11. >> >> - If the ConfigurationOfXXX only works for Pharo1.0 and the maintainer >> want to create the configuration for Pharo 1.1, he/she must copy the >> last working configuration for the package from UniverseForPharo10 to >> UniverseForPharo11. There he/she can start modifying the package until >> it works correctly in Pharo1.1 (use the blessing: tags wisely to avoid >> marking a broken configuration as released) >> >> This will permit to populate the UniverseForPharo11 based on the last >> working package versions from UniverseForPharo10. From that point they >> will likely diverge because of maintenance releases to the packages in >> any UniverseForXXX repository. >> >> The same will must be done to migrate from UniverseForPharo11 to >> UniverseForPharo12. You get the idea. >> >> With time, MetacelloRepository should be deprecated in favor of this >> UniverseForXXX repositories. >> >> Anyone is free to copy a working version from a previous Universe to a >> new Universe. They have read/write permissions to all. >> >> This setup will avoid the problems we are having right now with the >> in-image changes that are rendering the ConfigurationOfXXX unusable in >> distinct releases of Pharo. >> >> What this means to the end user: >> >> - For released version of Pharo >> >> They will have to use gofer this way: >> >> Gofer new >> squeaksource: 'UniverseForPharo10'; "Or UniverseForPharo11" >> project: 'ConfigurationOfMagma'; >> load. >> ConfigurationOfMagma project latestVersion load. >> >> - For next releases of Pharo >> >> Gofer loadFromUniverse: 'Magma'. "Or with GoferProjectLoader" >> ConfigurationOfMagma project latestVersion load. >> >> All this depends on conventions to find the appropriate universe for >> each pharo release, and also in the support from tools (like gofer in >> this example or the GoferProjectLoader if it is part of the core image). >> The universe functionality of the tools right now rely on the >> SystemVersion current majorMinorVersion string for deciding which >> repository to connect to. This could be improved surely but for now it >> works. >> >> I'm loading a new version of Gofer to PharoInbox with this functionality >> added so if you want to load directly from the universes with gofer do: >> >> Gofer upgrade. >> Gofer loadFromUniverse: 'YourPackageAlreadyInAUniverse'. >> >> But wait to this change to be treated by Stephane or Lukas before >> attempt it. >> >> Right now there is only Magma in the three repositories, but it >> shouldn't be hard for the maintainers of the other Configurations to >> help populate the universes from Pharo1.0, Pharo1.1 and Pharo1.2. >> >> This will benefit us as a community because the universes for the >> released pharo versions will be mostly untouched (only maintenance >> releases) and people will have the freedom to modify the configuration >> in the unstable (currently UniverseForPharo12) universe without >> affecting the users of the stable versions. >> >> Also, this will avoid to have a lot of conditionals inside the >> ConfigurationOfXXX classes, because a given class will target a specific >> Pharo release (the version on the newest universes could even delete the >> methods for the old universe, because will likely won't work in the new >> universe, deleting unnecessary and legacy code from the configuration) >> >> Comments and improvements welcome >> >> -- >> Miguel CobÃ¡ >> http://miguel.leugim.com.mx >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 4, 2010

Re: [Pharo-project] [update 1.2] #12080

by Henrik Johansen

It's referenced directly by f.ex. VMMaker, so I wouldn't do that. Cheers, Henry On Aug 4, 2010, at 11:40 49AM, StÃ©phane Ducasse wrote: > Yes there is a substituteClass which delegate to Multi.... > May be we should remove CrLFFileStream > > On Aug 3, 2010, at 11:28 PM, Levente Uzonyi wrote: > >> On Tue, 3 Aug 2010, StÃ©phane Ducasse wrote: >> >>> 12080 >>> ----- >>> >>> - Issue 1298: CrLfFileStream not properly initialized on Mac OS. Thanks Andrew Black and Carlo Teixeira. >> >> CrLFFileStream? That shouldn't be used anywhere. It was superseded by MultiByteFileStream. In Squeak [CrLfFileStream new] will return a MultiByteFileStream. >> >> >> Levente >> >>> >>> Lot of conflicts on this one.... >>> >>> Stef >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 4, 2010

[Pharo-project] [ANN] Pharo Metacello Universes

by Torsten Bergmann

Hi Miguel, hey, nice! If we follow this convention then it is easy to implement a universe browser that selects the correct universe repo and displays all loadable versions. Loading stuff should just be a few clicks away - I personally hate all this MC/Gofer typing ... Attached is a quick/simple implementation of such a browser: - file in the attached changeset (I tried in Pharo 1.2) - open via World menu -> "Universe Browser" - select the configuration you want and from the context menu choose -- "Load configuration" -> only the config is loaded -- "Load configuration and latest version" -> the config and lates version is loaded Have fun! I used Pharo 1.2 - should work in Pharo 1.0 and 1.1 too (havent tested). Bye T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

Aug. 4, 2010

Re: [Pharo-project] Gofer support for Universes

by Serge Stinckwich

I think you miss the point of Miguel. This is not the previous "Universe" but just repositories of ConfigurationOfXXX for Pharo 1.0&1.1. Maybe the name is misleading. Regards, On Wed, Aug 4, 2010 at 4:26 PM, Lukas Renggli <renggli(a)gmail.com> wrote: > I'll have a look when I am back from holidays. > > Two questions arise: > > - Is Universe still relevant and maintained by anybody these days? > Looks like all current code is managed with Metacello nowadays. > > - Gofer was designed to make Monticello scriptable. How do actions > like commit and merge map to Gofer? > > Lukas > > On Wednesday, August 4, 2010, Miguel Enrique CobÃ¡ MartÃnez > <miguel.coba(a)gmail.com> wrote: >> StÃ©phane, Lukas, >> >> I have uploaded >> >> Gofer-Core-MiguelCoba.124 >> Gofer-Tests-MiguelCoba.117 >> >> to PharoInbox repository on squeaksource. >> >> They are based on the versions of gofer in Pharo 1.0 >> Gofer-Core-MarkusDenker.117 >> Gofer-Tests-MarkusDenker.116 >> >> and add universes support to gofer. >> >> What do you think, are they worth integrating to mainstream gofer? >> Does this functionality belongs to Gofer? I know of GoferProjectLoader, >> but it isn't part of PharoCore, so that discards it right now. >> >> What is the procedure to merge it to trunk gofer, if so decided, so that >> a >> >> Gofer upgrade >> >> in any Pharo image gets this new version? >> >> Cheers >> -- >> Miguel CobÃ¡ >> http://miguel.leugim.com.mx >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

Aug. 4, 2010

Re: [Pharo-project] How detect a primitve?

by StÃ©phane Ducasse

Indeed isPrimitive is better On Aug 4, 2010, at 3:37 AM, James Ladd wrote: > > See CompiledMethod >> #primitive. > > > > > > Levente > > Thank you. > > Funny how you can't see things right in front of you sometimes. > I was thinking isPrimitive. > > Rgs, James. > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 4, 2010

Re: [Pharo-project] [ANN] Pharo Metacello Universes

by Adrian Lienhard

Hi Miguel, Thanks! It's great to see progress on this front! Cheers, Adrian On Aug 4, 2010, at 10:21 , Miguel Enrique CobÃ¡ MartÃnez wrote: > Hi all, > > I have created three new repositories on squeaksource: > > http://www.squeaksource.com/UniverseForPharo10 > http://www.squeaksource.com/UniverseForPharo11 > http://www.squeaksource.com/UniverseForPharo12 > > They are the repositories for the current versions of Pharo. The idea is > that each new release add a new UniverseForXXX repository and populates > it with the current UniverseForXXX packages of the stable release. > > Right now they are mostly empty, but should be populated by the > community and the ConfigurationOfXXX maintainers. > > Most ConfigurationOfXXX packages in > > http://www.squeaksource.com/MetacelloRepository > > should be copied to UniverseForPharo10. Which versions? The last known > version that is working correctly on Pharo 1.0. This will be the > official universe for Pharo1.0. No ConfigurationOfXXX should be stored > on UniverseForPharo10 if it is not working correctly on Pharo10. > > Then two things can follow: > > - If the package already has ConfigurationOfXXX package versions that > work in Pharo 1.1, those versions should be copied to > UniverseForPharo11. > > - If the ConfigurationOfXXX only works for Pharo1.0 and the maintainer > want to create the configuration for Pharo 1.1, he/she must copy the > last working configuration for the package from UniverseForPharo10 to > UniverseForPharo11. There he/she can start modifying the package until > it works correctly in Pharo1.1 (use the blessing: tags wisely to avoid > marking a broken configuration as released) > > This will permit to populate the UniverseForPharo11 based on the last > working package versions from UniverseForPharo10. From that point they > will likely diverge because of maintenance releases to the packages in > any UniverseForXXX repository. > > The same will must be done to migrate from UniverseForPharo11 to > UniverseForPharo12. You get the idea. > > With time, MetacelloRepository should be deprecated in favor of this > UniverseForXXX repositories. > > Anyone is free to copy a working version from a previous Universe to a > new Universe. They have read/write permissions to all. > > This setup will avoid the problems we are having right now with the > in-image changes that are rendering the ConfigurationOfXXX unusable in > distinct releases of Pharo. > > What this means to the end user: > > - For released version of Pharo > > They will have to use gofer this way: > > Gofer new > squeaksource: 'UniverseForPharo10'; "Or UniverseForPharo11" > project: 'ConfigurationOfMagma'; > load. > ConfigurationOfMagma project latestVersion load. > > - For next releases of Pharo > > Gofer loadFromUniverse: 'Magma'. "Or with GoferProjectLoader" > ConfigurationOfMagma project latestVersion load. > > All this depends on conventions to find the appropriate universe for > each pharo release, and also in the support from tools (like gofer in > this example or the GoferProjectLoader if it is part of the core image). > The universe functionality of the tools right now rely on the > SystemVersion current majorMinorVersion string for deciding which > repository to connect to. This could be improved surely but for now it > works. > > I'm loading a new version of Gofer to PharoInbox with this functionality > added so if you want to load directly from the universes with gofer do: > > Gofer upgrade. > Gofer loadFromUniverse: 'YourPackageAlreadyInAUniverse'. > > But wait to this change to be treated by Stephane or Lukas before > attempt it. > > Right now there is only Magma in the three repositories, but it > shouldn't be hard for the maintainers of the other Configurations to > help populate the universes from Pharo1.0, Pharo1.1 and Pharo1.2. > > This will benefit us as a community because the universes for the > released pharo versions will be mostly untouched (only maintenance > releases) and people will have the freedom to modify the configuration > in the unstable (currently UniverseForPharo12) universe without > affecting the users of the stable versions. > > Also, this will avoid to have a lot of conditionals inside the > ConfigurationOfXXX classes, because a given class will target a specific > Pharo release (the version on the newest universes could even delete the > methods for the old universe, because will likely won't work in the new > universe, deleting unnecessary and legacy code from the configuration) > > Comments and improvements welcome > > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 4, 2010

Re: [Pharo-project] [update 1.2] #12080

by StÃ©phane Ducasse

Yes there is a substituteClass which delegate to Multi.... May be we should remove CrLFFileStream On Aug 3, 2010, at 11:28 PM, Levente Uzonyi wrote: > On Tue, 3 Aug 2010, StÃ©phane Ducasse wrote: > >> 12080 >> ----- >> >> - Issue 1298: CrLfFileStream not properly initialized on Mac OS. Thanks Andrew Black and Carlo Teixeira. > > CrLFFileStream? That shouldn't be used anywhere. It was superseded by MultiByteFileStream. In Squeak [CrLfFileStream new] will return a MultiByteFileStream. > > > Levente > >> >> Lot of conflicts on this one.... >> >> Stef >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 4, 2010

Re: [Pharo-project] Strange Smalltalk vmVersion

by StÃ©phane Ducasse

which one is useful? I had the impression that the 1006 clearly identify the vm Stef On Aug 4, 2010, at 12:15 AM, John M McIntosh wrote: > http://isqueak.org/getAttributeIntoLength > > where > indexNumber = 1004, return CFBundleShortVersionString and interpreterVersion > > Maybe you want 1006 > indexNumber = 1006, return build string, which is say 'Mac Carbon 3.8.18b3 10-Apr-08 >DC0EAF5D-C46C-479D-B2A3-DBD4A2DF95A8<' > > Or what are you looking for? > > On 2010-08-03, at 12:49 PM, StÃ©phane Ducasse wrote: > >> I will add a method comment! >> >> Stef >> >> On Aug 3, 2010, at 9:28 PM, Adrian Lienhard wrote: >> >>> That's the version of the image with which the interpreter was generated. >>> >>> Adrian >>> >>> On Aug 3, 2010, at 18:50 , StÃ©phane Ducasse wrote: >>> >>>> Hi john >>>> >>>> Smalltalk getSystemAttribute: 1004 >>>> returns >>>> 'Squeak3.8.1 of ''28 Aug 2006'' [latest update: #6747] Squeak VM 4.2.4b1' >>>> >>>> do you know how we can fix that? >>>> >>>> Stef >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > =========================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 > Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com > =========================================================================== > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 4, 2010

Re: [Pharo-project] Gofer support for Universes

by StÃ©phane Ducasse

Miguel Who is maintaining Universe? What is the state of the software managed by Universes? We want to have "certified" loadable, self contained robust distributions. It will take time but we will get there. So I would not pollute gofer with Universe. Stef > StÃ©phane, Lukas, > > I have uploaded > > Gofer-Core-MiguelCoba.124 > Gofer-Tests-MiguelCoba.117 > > to PharoInbox repository on squeaksource. > > They are based on the versions of gofer in Pharo 1.0 > Gofer-Core-MarkusDenker.117 > Gofer-Tests-MarkusDenker.116 > > and add universes support to gofer. > > What do you think, are they worth integrating to mainstream gofer? > Does this functionality belongs to Gofer? I know of GoferProjectLoader, > but it isn't part of PharoCore, so that discards it right now. > > What is the procedure to merge it to trunk gofer, if so decided, so that > a > > Gofer upgrade > > in any Pharo image gets this new version? > > Cheers > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 4, 2010