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

Re: [Pharo-project] a process to maintain non core package

by Michael Roberts

do we have a list of candidate package management systems? cheers, Mike On Sun, Aug 9, 2009 at 1:52 PM, StÃ©phane Ducasse<stephane.ducasse(a)inria.fr> wrote: > > On Aug 9, 2009, at 2:26 PM, Adrian Lienhard wrote: > >> Hi, >> >> I really think we need a package management system and a process to >> maintain it. >> >> The goal is that loading and using non-core packages "just >> works" (unlike for instance SqueakMap, where loading more often fails >> than succeeds because there are a lot of obsolete packages and a >> dependency mechanism is missing). > > Yeap! > >> - There should be a responsible maintainer for each package >> - For each package there should be a known way to discuss and report >> problems >> - A gate keeper includes and removes packages from the set depending >> on their status >> >> This limits the set of included packages (at least initially) but >> would increase the quality and hence the user experience. >> >> Maybe there could be two sets, a stable and an unstable set. New >> packages would first go to the unstable set and then move up to the >> stable set after a while. > > Yes but if we take for example sound. When I integrate a fix from > Cuis I do not want to get > >> An automated build process could load packages into new builds and >> report the result of the tests. > > Yes! > >> The package management system does not need to be very sophisticated, >> but it should manage dependencies and have a simple GUI (to search for >> packages and see what is already loaded). > > Yes. > We should start incrementally fixing that. > I should look at Metacello and MC1.5 when I get more time. > > Stef > >> >> Cheers, >> Adrian >> >> On Aug 8, 2009, at 12:31 , StÃ©phane Ducasse wrote: >> >>> Hi >>> >>> in the future I would like to have a process like that to maintain >>> package like sound (or morphic extras) or any package that are not >>> core else we will not be able to maintain them or to apply package >>> wide changes. >>> >>> - we mark the packages that are not in the image but that we want to >>> maintain >>> - at integration step we >>> Â Â Â load all the external packages >>> - integrate >>> - publish in different repos >>> >>> Else I bet that we will not be able to maintain the non core >>> packages. >>> >>> Stef >>> >>> PS: I'm integrating >>> >>> Issue 1051: Cuis 0053-ensure-close.1.cs >>> and some changes touched sound so this is good experiment. >>> >>> _______________________________________________ >>> 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. 9, 2009

[Pharo-project] I will do an harvesting pause...

by StÃ©phane Ducasse

Aug. 9, 2009

Re: [Pharo-project] [ANN] 10412

by StÃ©phane Ducasse

On Aug 9, 2009, at 5:17 PM, Adrian Lienhard wrote: >> - Issue 1054: Cuis code author CUIS code author checking code >> SystemNavigation default contributorsNotSignatories >> SystemNavigation default allContributors >> SystemNavigation default contributionsOf: ... > > Stef, what is the difference to the Methodauthorships package that > we've use for the license cleaning [1]? I do not know. I forgot this package. > It seems that now we have a > duplicated and obsolete list of signatories in the image. Or did you > merge? No we should. What would be good is to fix all the initials to get the full name instead. What miguel did is nice for author we should get in a state where we get more uniform author information in the future. > > Cheers, > Adrian > > http://code.google.com/p/pharo/wiki/LicenseCleanEffort > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 9, 2009

Re: [Pharo-project] About v4 strike fonts

by StÃ©phane Ducasse

I get 0.0 and I use 4.1.1.beta2U which is the latest vm available on mac. Stef On Aug 9, 2009, at 4:35 PM, Juan Vuletich wrote: > StÃ©phane Ducasse wrote: >> When I move a window I get the following visual effect with strike >> font loaded >> >> >> ------------------------------------------------------------------------ >> > Print the following: > > | f1 f2 | > f1 := Form extent: 8@8 depth: 32. > f1 fillColor: (Color r: 1.0 g: 1.0 b: 0.7 alpha: 0.6). > f2 := Form extent: 8@8 depth: 32. > f2 fillColor: (Color r: 0.5 g: 1.0 b: 0.7 alpha: 0.7). > (BitBlt toForm: f1) sourceForm: f2; combinationRule: 20; copyBits. > (f1 colorAt: 2@2) alpha > > If you don't get 1.0 as the result, your VM is missing my April fix. > If you do get 1.0, please zip and upload your image somewhere so I > can take a look. > > Cheers, > Juan Vuletich

Aug. 9, 2009

Re: [Pharo-project] [ANN] 10413

by StÃ©phane Ducasse

http://www.jvuletich.org/Squeak/Misc/ take V4 Stef On Aug 9, 2009, at 3:35 PM, Hilaire Fernandes wrote: > 2009/8/9 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > >> Now it should be easier for people that want to test strike fonts >> (one >> file to load) > > Any pointer how to do it ? > > Hilaire > > -- > http://blog.ofset.org/hilaire > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 9, 2009

Re: [Pharo-project] [ANN] 10412

by Adrian Lienhard

> - Issue 1054: Cuis code author CUIS code author checking code > SystemNavigation default contributorsNotSignatories > SystemNavigation default allContributors > SystemNavigation default contributionsOf: ... Stef, what is the difference to the Methodauthorships package that we've use for the license cleaning [1]? It seems that now we have a duplicated and obsolete list of signatories in the image. Or did you merge? Cheers, Adrian http://code.google.com/p/pharo/wiki/LicenseCleanEffort

Aug. 9, 2009

Re: [Pharo-project] Missing characters when typing?

by Schwab,Wilhelm K

I use Shout; I do not use autocompletion. On the latter, if the system can keep up with me, it's quicker to just type of the stuff. -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Michael Rueger Sent: Sunday, August 09, 2009 1:57 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Missing characters when typing? Michael Rueger wrote: > as additional info: one more thing: is it happening to people who are *not* using shout or auto completion? Michael _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 9, 2009

[Pharo-project] About v4 strike fonts

by StÃ©phane Ducasse

When I move a window I get the following visual effect with strike font loaded

Aug. 9, 2009

Re: [Pharo-project] [ANN] 10413

by Hilaire Fernandes

2009/8/9 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > Now it should be easier for people that want to test strike fonts (one > file to load) Any pointer how to do it ? Hilaire -- http://blog.ofset.org/hilaire

Aug. 9, 2009

[Pharo-project] [ANN] 10413

by StÃ©phane Ducasse

- Issue 1055: Strike font preliminaries (with missing items base64Decoded base64Encoded) - Issue 836: Should integrate threadSafeTranscript - Issue 981: Changes Author initials and name to an unified fullName (thanks Miguel!) 39 items left :) (and a lot 1.0 items were added so we should continue). Now it should be easier for people that want to test strike fonts (one file to load)

Aug. 9, 2009