- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] No more dirty packages in Pharo

by StÃ©phane Ducasse

excellent! On Sep 1, 2013, at 9:41 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Ok, great. I loaded ConfigurationOfMagritte3 #development, and Grease loaded clean. Thank you! > > The only remaining problem was asMorph in Magritte-Morph, but I fixed it now, so Magritte loads clean in Pharo 2.0. > > Cheers, > Doru > > > > On Sun, Sep 1, 2013 at 7:29 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Great. > > What version? > > Doru > > > On Fri, Aug 30, 2013 at 12:59 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > Hi, > > I've fixed Magritte and Grease configurations so that loading these projects do not dirty any pharo package anymore. > > Best > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without losing enthusiasm." > Winston Churchill > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Sept. 1, 2013

Re: [Pharo-dev] where is hosted Grease?

by Esteban Lorenzano

On Sep 1, 2013, at 9:11 AM, Johan Brichau <johan(a)inceptive.be> wrote: > > On 31 Aug 2013, at 17:45, Tobias Pape <Das.Linux(a)gmx.de> wrote: > >>> That is like saying everyone have to be in the Seaside team to upload just a fix in Grease? >> >> >> Then make a grease team. >> Grease was invented for Seaside by the seaside team, doesn't >> that make the Seaside team the official maintainer? >> Then yes, everyone who wants his fix in the official Grease >> repo has to be on that team or ask someone there to merge/integrate/upload. > > > Does it really matter if you need to be on the Seaside team for contributing to only a specific sub project? not really. you could be a contributor of a project (not a team), and not part of the team... you could be part of Grease project without having anything to do with the rest of Seaside. > For example, Damien recently contributed fixes to the configurations and therefore I added him to the Seaside team. > > Easy. done. > > Apart from that, it makes sense to move Grease to its own project. > I'm not an author of Grease, but I did the move of Seaside to Smalltalkhub and raised the issue about Grease not having its proper project on the Seaside-dev mailinglist while doing this back in July. > If I remember correctly, there was no opposition to moving it to its separate space if this helped development. The reason it did not happen yet is that I previously thought we needed to merge the two Grease versions from the two Seaside repositories to a single one. But now I realise that we should only move the most recent one (the one from Seaside31). > > ESUG is coming up. If we did not do it by then, talk to us. > > Cheers > Johan

Sept. 1, 2013

Re: [Pharo-dev] No more dirty packages in Pharo

by Tudor Girba

Ok, great. I loaded ConfigurationOfMagritte3 #development, and Grease loaded clean. Thank you! The only remaining problem was asMorph in Magritte-Morph, but I fixed it now, so Magritte loads clean in Pharo 2.0. Cheers, Doru On Sun, Sep 1, 2013 at 7:29 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Great. > > What version? > > Doru > > > On Fri, Aug 30, 2013 at 12:59 PM, Damien Cassou <damien.cassou(a)gmail.com>wrote: > >> Hi, >> >> I've fixed Magritte and Grease configurations so that loading these >> projects do not dirty any pharo package anymore. >> >> Best >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Success is the ability to go from one failure to another without losing >> enthusiasm." >> Winston Churchill >> >> _______________________________________________ >> Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > -- www.tudorgirba.com "Every thing has its own flow"

Sept. 1, 2013

talkFFI tutorial

by StÃ©phane Ducasse

http://rochiamaya.wordpress.com/2013/07/30/create-bindings-with-talkffi/ http://rochiamaya.wordpress.com/2013/08/06/how-to-use-the-generated-binding…

Sept. 1, 2013

Re: [Pharo-dev] where is hosted Grease?

by StÃ©phane Ducasse

>> I can understand. >> We wanted for long time a Grease version that does not dirty our moose packages. > > Does that mean that: > - if Moose does not load Grease, that Moose implements (a part of) Grease? no ;) > - if Moose loads Grease, that Moose overwrites (a part of) Grease? no :) > > In either case, does it not make sense to use Grease and contribute the changes there, rather than fork a specific version of Grease? Yes but for that there needs to have a place to publish changes And a maintained Configuration. In our case, the situation is much simpler. Pharo added trimBoth in String (because "THERE IS NO POINT TO KEEP COOL CODE OF CORE SYSTEM CLASSES IN EXTERNAL PACKAGES" - remember that this is the motto of Pharo - systematically get a better infrastructure) - I know that you know but other readers of this email may not be (yet) brainwashed :). So since the configuration (which is the tool to say for Pharo1.4 load version 123, for Pharo2.0 load version (without trimboth)â¦. was not updated we got redefinition in grease on String methods. With have the right tool to manage complexity we should just use them instead of a packages list and a gofer script. Stef

Sept. 1, 2013

Re: [Pharo-dev] where is hosted Grease?

by Johan Brichau

On 31 Aug 2013, at 17:45, Tobias Pape <Das.Linux(a)gmx.de> wrote: >> That is like saying everyone have to be in the Seaside team to upload just a fix in Grease? > > > Then make a grease team. > Grease was invented for Seaside by the seaside team, doesn't > that make the Seaside team the official maintainer? > Then yes, everyone who wants his fix in the official Grease > repo has to be on that team or ask someone there to merge/integrate/upload. Does it really matter if you need to be on the Seaside team for contributing to only a specific sub project? For example, Damien recently contributed fixes to the configurations and therefore I added him to the Seaside team. Easy. done. Apart from that, it makes sense to move Grease to its own project. I'm not an author of Grease, but I did the move of Seaside to Smalltalkhub and raised the issue about Grease not having its proper project on the Seaside-dev mailinglist while doing this back in July. If I remember correctly, there was no opposition to moving it to its separate space if this helped development. The reason it did not happen yet is that I previously thought we needed to merge the two Grease versions from the two Seaside repositories to a single one. But now I realise that we should only move the most recent one (the one from Seaside31). ESUG is coming up. If we did not do it by then, talk to us. Cheers Johan

Sept. 1, 2013

Re: [Pharo-dev] where is hosted Grease?

by Johan Brichau

On 31 Aug 2013, at 23:00, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> Ok, but please keep the code updated because I have to fix Grease to work in Pharo 2.0 > > I can understand. > We wanted for long time a Grease version that does not dirty our moose packages. Does that mean that: - if Moose does not load Grease, that Moose implements (a part of) Grease? - if Moose loads Grease, that Moose overwrites (a part of) Grease? In either case, does it not make sense to use Grease and contribute the changes there, rather than fork a specific version of Grease? Johan

Sept. 1, 2013

Re: [Pharo-dev] where is hosted Grease?

by StÃ©phane Ducasse

Soon smalltalkhub project will have inbox. Right now this is annoying :) Nicolas is aware of that. >>> I did a separate repository, let me know if you want to be added as contributor >>> >>> http://smalltalkhub.com/#!/~hernan/Grease >> >> We should not "hijack" such projects into "private" STHub users like Hernan's private URL. >> SmalltalkHub already has team functionality and the according teams are already setup. > > Ok, but please keep the code updated because I have to fix Grease to work in Pharo 2.0 I can understand. We wanted for long time a Grease version that does not dirty our moose packages. >> Grease belongs to Seaside since it was developed by the seaside team. Therefore >> it should be a "Seaside team" project also on STHub as before. >> >> There are already team projects for the Seaside team. See http://smalltalkhub.com/#!/~Seaside >> with already migrated code. >> >> So for Grease we/or the seaside team should use: >> >> http://smalltalkhub.com/#!/~Seaside/Grease >> >> We should align with the seaside team/developers, otherwise we would add more confusion >> regarding the code move and the configuration. >> > > That is like saying everyone have to be in the Seaside team to upload just a fix in Grease? > > Cheers, > > HernÃ¡n > >> Thanks >> T. >> >> > >

Aug. 31, 2013

Where is hosted Grease?

by Torsten Bergmann

Looks like http://smalltalkhub.com/#!/~Seaside/Seaside31/ and http://smalltalkhub.com/#!/~Seaside/Seaside30 already contain Grease. So it is already migrated to STHub. In it's current state it's directly bound to Seaside. There is now also a Jenkins Job [1] and it looks like version 1.0.8/baseline 1.0.8 of ConfigurationOfGrease refer to http://www.smalltalkhub.com/mc/Seaside/Seaside30/main So I dont know if http://smalltalkhub.com/#!/~Seaside/Grease or http://smalltalkhub.com/#!/~hernan/Grease are really necessary. I've limited net access these days - maybe someone can clearify about a future Grease repo on the "seaside-dev" mailinglist. Since the Seaside community invented/implemented Grease I agree with Tobias that it is (by default) the official maintainer and should decide to avoid many forks/teams. Thx T. [1] http://lists.squeakfoundation.org/pipermail/seaside-dev/2013-August/005341.…

Aug. 31, 2013

Re: [Pharo-dev] [3.0] Down to 5 failing tests!

by Camillo Bruni

cool! I am on to it for the NativeBoost Manifest. On 2013-08-31, at 17:55, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Nearly green! > > -> Mac is green > > -> Linux: 2 failing tests > > > NBFFIExternalStructTests > testReturnStruct1Byte > NBFFIExternalUnionTests > testReturnUnion1Byte > > -> Windows: 3 failing tests > > ZnServerTests > testEntityTooLarge > testHeaderLineTooLong > testRequestLineTooLong > > > https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/ >

Aug. 31, 2013