- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Traits and PHP

by StÃ©phane Ducasse

check the ecoop paper of tom and also the google project Stef On Mar 18, 2010, at 2:35 PM, Lukas Renggli wrote: >> Some people are working at google to make traits part of Javascript. > > How do traits fit into a prototype model? Has anybody written about that? > > Lukas > > -- > Lukas Renggli > http://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

March 18, 2010

Re: [Pharo-project] Traits and PHP

by Lukas Renggli

> Some people are working at google to make traits part of Javascript. How do traits fit into a prototype model? Has anybody written about that? Lukas -- Lukas Renggli http://www.lukas-renggli.ch

March 18, 2010

Re: [Pharo-project] Traits and PHP

by Stefan Marr

On 18 Mar 2010, at 14:19, laurent laffont wrote: > Hi, > > it seems that the PHP people think about including Traits in the next PHP major release: http://marc.info/?l=php-internals&m=126875515019687&w=2 Indeed, we do ;) But there is still no agreement on the language design and the functionality... Best regards Stefan > > Laurent Laffont > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

March 18, 2010

Re: [Pharo-project] [ANN] Gofer Project Loader 1.0 (BETA)

by Miguel Enrique CobÃ¡ Martinez

El jue, 18-03-2010 a las 08:30 +0100, Adrian Lienhard escribiÃ³: > Here is yet another way how we could model universes. We just have multiple Metacello repositories: > > - MetacelloRepository is the one that everybody can commit to (testing universe) > - MetacelloRepositoryPharo1.0 is the stable universe for Pharo 1.0 > - MetacelloRepositoryPharo1.1 is the stable universe for Pharo 1.1 > - etc. > > A package always first gets into the testing universe and when it is known to work in a particular version it is copied into the appropriate repository. The Gofer Project Loader would just need to know the repository for the current Pharo version. Like in Debian, one can add the testing universe to get unstable versions if needed. > > This setup would not need any code changes in Metacello and it allows us to use access rights to assign people to manage the process and assert a certain level of quality. > > Cheers, > Adrian Yes, I liked this too. Specially the no metacello modifications part. +1 > > > On Mar 17, 2010, at 23:41 , Miguel Enrique CobÃ¡ Martinez wrote: > > > El miÃ©, 17-03-2010 a las 15:20 -0700, Dale Henrichs escribiÃ³: > >> ----- "Esteban Lorenzano" <estebanlm(a)gmail.com> wrote: > >> > >> | > - any idea about how we go to differentiate "stable" and "unstable" > >> | > >> | > universes for each Pharo version? How does the user know which version > >> | > is the one he needs for his version of Pharo? Sorry, this is not > >> | > directly related to the Gofer Project Loader but I think it is the next > >> | > important step towards a working package management system! > >> | > >> | No clue... maybe we need to add to Metacello a new "dependence > >> | dimension", like "minimum version of distribution"... but Dale can be > >> | much more helpful than me in this area. > >> > >> I imagine that code targetted for specific Pharo versions will be treated like we treat code targeted for different Smalltalk dialects. So you would write specs like the following: > >> > >> spec for: #common do: [...]. > >> spec for: #squeakCommon do: [...]. > >> spec for: #pharo do: [...]. > >> spec for: #'pharo1.0' do: [...]. > >> spec for: #'pharo1.1' do: [...]. > >> > >> or possibly like the following, if a finer version granularity is needed: > >> > >> spec for: #common do: [...]. > >> spec for: #squeakCommon do: [...]. > >> spec for: #pharo do: [...]. > >> spec for: #'pharo1.0' do: [...]. > >> spec for: #'pharo1.0-10508' do: [...]. > >> spec for: #'pharo1.0-10515' do: [...]. > >> spec for: #'pharo1.1' do: [...]. > >> spec for: #'pharo1.1-11508' do: [...]. > >> spec for: #'pharo1.1-11515' do: [...]. > >> > >> Dale > >> > > > > umm, no please! > > > > There would be a lot of combinations after a while. > > > > Why about having a new spec universes message that accept a list of > > symbols, each symbol representing a given "universe" of tested packages. > > This list will be the only thing to modify when grouping different > > versions of the same package in different repositories. > > > > For example, I start with ConfigurationOfMagma version 1.0r43. Two weeks > > later I release ConfigurationOfMagma with support for loading 1.0r44. > > Both this versions have been tested on Pharo 1.0. So the both are > > marked > > > > spec universes: #(#pharo10). > > > > A week later Pharo 1.1 is released, and I test the configuration on this > > new version of pharo. Both work ok. So I modify the line to: > > > > spec universes: #(#pharo10 #pharo11) > > > > and commit. > > > > The tools (GoferProjectLoader) then add functionality to scan this list > > and presents the users only the appropriated ones based on the image the > > users is querying the repository. > > > > Of course this is very simplistic because as the debian model shows, > > requires a maintainer of each configuration and the user to report if a > > given #pharo11 marked version actually doesn't work. If something don't > > work, or a new version is given that works, or the tag #pharo11 is > > removed from that version effectively removing it from that given > > universe until bugs are fixed or worked around. > > > > What do you think? > > > > Cheers > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > -- > > 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 -- Miguel CobÃ¡ http://miguel.leugim.com.mx

March 18, 2010

[Pharo-project] Traits and PHP

by laurent laffont

Hi, it seems that the PHP people think about including Traits in the next PHP major release: http://marc.info/?l=php-internals&m=126875515019687&w=2 Laurent Laffont

March 18, 2010

Re: [Pharo-project] A challenge for us

by StÃ©phane Ducasse

>> > We really should set up a backup repository with all the packages included in specs though. yes! yes yes! we discussed that with dale a while ago. > Older versions have already stopped working twice now due to package deletions, first FFI, and then RB. > > F.ex, doing (ConfigurationOfPharo project version: '1.0-rc2.10508') load in a 10508rc2 Core image will now fail. > > Cheers, > Henry > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 18, 2010

Re: [Pharo-project] A challenge for us

by Henrik Johansen

On Mar 18, 2010, at 11:15 18AM, Mariano Martinez Peck wrote: > > PS. The latest 1.0 release is PharoCore-1.0-10515rc3 (available from the gforge page), to get the equivalent of a Pharo (pharo-dev) rc image, load the ConfigurationOfPharo into that, and evaluate (ConfigurationOfPharo version: '1.0-rc.3-baseline') load. > > PPS. There will be an error when doing the load, since the AST-Tests package in squeaksource/rb has been renamed AST-Tests-Core, and the same for Refactoring-Tests, and the old packages removed... > Lukas, would you mind uploading them again? > For now, you can debug, and in the method that breaks, change the packageSpec's file to 'AST-Tests-Core-lr.8' and Refactoring-Tests-Core-lr.34 respectively. > This will happen twice, since the spec first loads ConfigurationOfRefactoringBrowser once as part of the defined packages, then again as a prereq when loading ConfigurationOfOmniBrowser. > > > It was fixed already some time ago. I have also updated all project to latests versions. I actually build a PharoDev image based on Pharo 1.0 RC3 and latests pharo dev tools and all seemed to work perfect. > > I will try to release such image by the end of the week/weekend. > > Cheers > > Mariano I guess the correct incantation was (ConfigurationOfPharo project version: '1.0-rc3.10515') load. :) We really should set up a backup repository with all the packages included in specs though. Older versions have already stopped working twice now due to package deletions, first FFI, and then RB. F.ex, doing (ConfigurationOfPharo project version: '1.0-rc2.10508') load in a 10508rc2 Core image will now fail. Cheers, Henry

March 18, 2010

Re: [Pharo-project] A challenge for us

by GermÃ¡n Arduino

Hi Henrik: Thanks you very much by the detailed explanation! I will start playing with 1.1 and try these things probably on the weekend (A rainy weekend is expected here). Cheers. GermÃ¡n. 2010/3/17 Henrik Sperre Johansen <henrik.s.johansen(a)veloxit.no>: > On 18.03.2010 01:09, GermÃ¡n Arduino wrote: > > I would like to help also, even when I'm with very little free time. > > To start I would like to understand how is the Pharo development > process, being that (until now) I've mostly used RC2/3. > > The main doubts I've are: > > 1. The UNSTABLE version (the 1.1 right?) comes with no dev tools > installed (OB, Shout, etc). Exist some metacello configuration to > install all these tools? (I thinked that could be > ConfigurationOfPharo, but seems that fail to install). > > Not all dev tools can be expected to be updated and work on a > work-in-progress core image, thus we (well, at least I) make due with the > good ol' system browser. > Important packages will be updated and configurations working in 1.1 made > available after API changes have been prohibited. > That said, the O2Browser was updated a short time ago to work in 1.1 IIRC, > your best bet for a more advanced browser would probably be to try and load > a configuration of that. > > 2. On the gforge page (http://gforge.inria.fr/frs/?group_id=1299) > what is Pharo (pharo-dev) ? Is 1.0 RC2 with some tools? > > Pharo-dev is older versions of the core image, with tools equivalent to what > is found in the RC-releases preloaded. (In fact, the latest release in that > category is Pharo1.0-10508-rc2dev10.01.2.zip ) > > 3. On the gforge page (http://gforge.inria.fr/frs/?group_id=1299) > what is Pharo1.1-64bit-Core? I mean, with which vm is supposed to be > used? > > It's an image that has been run through the SystemTracer which converts it > to 64bit format. > You will be able to run it on the 64-64 version of the 5.0 Mac OSX VM's, not > sure about the other platforms. > Please note many of the vm-plugins are not 64bit clean, thus are likely to > fail or crash your VM if used. > > 4. Some days ago I asked (with no response) about the Package Browser > on RC2. I've found several mails talking about some problems between > OB and O2, but I've not clear how to install it (I would like to have > on 1.1 also). > > AFAIK, Alexandre and David spent some time a while ago to completely > separate the model of O2 from that used by OB, thus resolving clashes caused > by O2 overrides, now both should be able to be loaded at the same time in > 1.0. > (load with ConfigurationOfO2 in MetacelloRepository) > > Well, this is all for now, I will try also to read on the web page > about repos and other things related with the Pharo development > process. > > Thanks. > GermÃ¡n. > > There's only two repo's you really need: > MetacelloRepository, for loading the tools you find useful (Really nice for > checking issues with different tools in 1.1 as well) > Inbox - Where you commit slices for inclusion in the next version. > > Cheers, > Henry > > PS. The latest 1.0 release is PharoCore-1.0-10515rc3 (available from the > gforge page), to get the equivalent of a Pharo (pharo-dev) rc image, load > the ConfigurationOfPharo into that, and evaluate (ConfigurationOfPharo > version: '1.0-rc.3-baseline') load. > > PPS. There will be an error when doing the load, since the AST-Tests package > in squeaksource/rb has been renamed AST-Tests-Core, and the same for > Refactoring-Tests, and the old packages removed... > Lukas, would you mind uploading them again? > For now, you can debug, and in the method that breaks, change the > packageSpec's file to 'AST-Tests-Core-lr.8' and Refactoring-Tests-Core-lr.34 > respectively. > This will happen twice, since the spec first loads > ConfigurationOfRefactoringBrowser once as part of the defined packages, then > again as a prereq when loading ConfigurationOfOmniBrowser. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 18, 2010

Re: [Pharo-project] A challenge for us

by Mariano Martinez Peck

> PS. The latest 1.0 release is PharoCore-1.0-10515rc3 (available from the > gforge page), to get the equivalent of a Pharo (pharo-dev) rc image, load > the ConfigurationOfPharo into that, and evaluate (ConfigurationOfPharo > version: '1.0-rc.3-baseline') load. > > PPS. There will be an error when doing the load, since the AST-Tests > package in squeaksource/rb has been renamed AST-Tests-Core, and the same for > Refactoring-Tests, and the old packages removed... > Lukas, would you mind uploading them again? > For now, you can debug, and in the method that breaks, change the > packageSpec's file to 'AST-Tests-Core-lr.8' and Refactoring-Tests-Core-lr.34 > respectively. > This will happen twice, since the spec first loads > ConfigurationOfRefactoringBrowser once as part of the defined packages, then > again as a prereq when loading ConfigurationOfOmniBrowser. > It was fixed already some time ago. I have also updated all project to latests versions. I actually build a PharoDev image based on Pharo 1.0 RC3 and latests pharo dev tools and all seemed to work perfect. I will try to release such image by the end of the week/weekend. 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 18, 2010

Re: [Pharo-project] new pavel mini image :)

by Mariano Martinez Peck

Pavel: where can I get all the scripts that you used for this new PharoKernel ? Thanks Mariano On Fri, Feb 26, 2010 at 8:42 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Hi guys > > I do not know if you noticed by Pavel uploaded a new minimal image > http://gforge.inria.fr/frs/shownotes.php?release_id=4921 > > This is really exciting. > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 18, 2010