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

Re: [Pharo-project] About Pharo working packages

by csrabak＠bol.com.br

Aug. 20, 2009

Re: [Pharo-project] About Pharo working packages

by csrabak＠bol.com.br

Aug. 20, 2009

Re: [Pharo-project] Pretty print doesn't work on Traits with OB Package Browser

by Alexandre Bergel

Well spotted. I think the Traits package should be updated. No need of class extension for this. Cheers, Alexandre On 19 Aug 2009, at 14:23, Mariano Martinez Peck wrote: > Hi! I opened this ticket: http://code.google.com/p/pharo/issues/detail?id=1076 > > This happens when using the OB Package Browser. I am using 10414. > To reproduce: > > 1) Browse any Trait, for example TBehaviorCategorization > 2) Select a method, right button, pretty print > 3) You will get a Trait DNU #formatterClass > > The fix is easy: > > Crate in Trait a instance side method: > > formatterClass > > ^self class formatterClass > > > The thing is that I don't know in which package should this be > commited. AST? > > Best, > > Mariano > > ps: the bug report and fix is thanks to Marcelo Cortez > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Aug. 20, 2009

Re: [Pharo-project] About Pharo working packages

by StÃ©phane Ducasse

could be a nice solution with gofer STef On Aug 20, 2009, at 7:52 PM, Damien Cassou wrote: > On Thu, Aug 20, 2009 at 10:32 AM, StÃ©phane > Ducasse<stephane.ducasse(a)inria.fr> wrote: >> About http://code.google.com/p/pharo/wiki/PackagesTestedInPharo >> I was wondering if it would not be better to use the Universe >> mechanism. >> We could create a Pharo Universe and people could describe that their >> packages load in Pharo1.0 >> This would be great and important to get a update to date catalog of >> what is working in Pharo1.0. >> What do you think? > > For a simple solution, I would propose to provide a class with Pharo > to contain a script per method, each script installing a package, > i.e., like we currently do in ScriptLoader but in another class. This > is similar to what Keith's Packages support already, but without the > Sake syntax and implementation that nobody looked at as of now. > > A method could look like: > > omnibrowser > self installer lukas > project: 'omnibrowser'; > install: 'OmniBrowser'; > install: 'OB-Standard'; > install: 'OB-Morphic'; > install: 'OB-SUnitIntegration'. > > The installer used could be either Installer or something else. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Lambdas are relegated to relative obscurity until Java makes them > popular by not having them." James Iry > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 20, 2009

Re: [Pharo-project] About Pharo working packages

by Damien Cassou

On Thu, Aug 20, 2009 at 10:32 AM, StÃ©phane Ducasse<stephane.ducasse(a)inria.fr> wrote: > About http://code.google.com/p/pharo/wiki/PackagesTestedInPharo > I was wondering if it would not be better to use the Universe mechanism. > We could create a Pharo Universe and people could describe that their > packages load in Pharo1.0 > This would be great and important to get a update to date catalog of > what is working in Pharo1.0. > What do you think? For a simple solution, I would propose to provide a class with Pharo to contain a script per method, each script installing a package, i.e., like we currently do in ScriptLoader but in another class. This is similar to what Keith's Packages support already, but without the Sake syntax and implementation that nobody looked at as of now. A method could look like: omnibrowser self installer lukas project: 'omnibrowser'; install: 'OmniBrowser'; install: 'OB-Standard'; install: 'OB-Morphic'; install: 'OB-SUnitIntegration'. The installer used could be either Installer or something else. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Aug. 20, 2009

Re: [Pharo-project] About Pharo working packages

by StÃ©phane Ducasse

On Aug 20, 2009, at 7:02 PM, Miguel CobÃ¡ wrote: > On Thu, Aug 20, 2009 at 3:32 AM, StÃ©phane > Ducasse<stephane.ducasse(a)inria.fr> wrote: >> Hi all >> >> About http://code.google.com/p/pharo/wiki/PackagesTestedInPharo >> I was wondering if it would not be better to use the Universe >> mechanism. >> We could create a Pharo Universe and people could describe that their >> packages load in Pharo1.0 >> This would be great and important to get a update to date catalog of >> what is working in Pharo1.0. >> What do you think? > > > I think that this will be discussed by the community at a large. What > will be the way to > install packages on Pharo. so far we only want MC packages :) > SqueakMap (PharoMap) > SqueakSouce (PharoSource) > Monticello repos on other site > Update stream (this will be for the core anyway) > MC1.5, MC1.6, MC2 > DeltaStreams > SARs > > A lot of options but we must not replicate the nightmare that squeak > has. > > I personally vote for Monticello and Monticello configuration for a > _well know official repo_. > > This repo will have just the official versions that work/worked with > pharo in a given time. > The other versions should be stored on personal separated repos, like > lukas repo or squeak repo. could be a solution Pharo10 with all the packages working. > But let discuss this. the problem is that for packages evolving you would have a lot of traffic > Also, I have something against universes, as they force to use just > the universe versions of a package and don't play > well with separated packages installed from monticello or other (but > maybe it is just me that haven't learned to use it > well, so if this is so, discard this last part) I do not know. I wanted to avoid squeakmap attitude where you could not know if a package would load or not. Stef

Aug. 20, 2009

Re: [Pharo-project] About Pharo working packages

by Miguel CobÃ¡

On Thu, Aug 20, 2009 at 3:32 AM, StÃ©phane Ducasse<stephane.ducasse(a)inria.fr> wrote: > Hi all > > About http://code.google.com/p/pharo/wiki/PackagesTestedInPharo > I was wondering if it would not be better to use the Universe mechanism. > We could create a Pharo Universe and people could describe that their > packages load in Pharo1.0 > This would be great and important to get a update to date catalog of > what is working in Pharo1.0. > What do you think? I think that this will be discussed by the community at a large. What will be the way to install packages on Pharo. SqueakMap (PharoMap) SqueakSouce (PharoSource) Monticello repos on other site Update stream (this will be for the core anyway) MC1.5, MC1.6, MC2 DeltaStreams SARs A lot of options but we must not replicate the nightmare that squeak has. I personally vote for Monticello and Monticello configuration for a _well know official repo_. This repo will have just the official versions that work/worked with pharo in a given time. The other versions should be stored on personal separated repos, like lukas repo or squeak repo. But let discuss this. Also, I have something against universes, as they force to use just the universe versions of a package and don't play well with separated packages installed from monticello or other (but maybe it is just me that haven't learned to use it well, so if this is so, discard this last part) Miguel CobÃ¡ http://miguel.leugim.com.mx

Aug. 20, 2009

Re: [Pharo-project] 10394, pharo beeps on every SystemWindow open/close

by Alexandre Bergel

Easy to remove the beeping attitude. The class DummySoundSystem define the method beep. Empty its body and enjoy the silence Alexandre On 20 Aug 2009, at 10:19, Mariano Martinez Peck wrote: > Hi folks: This but is still happening to me. In only happens in > Linux and with the core image. In this situation, I cannot use this > image because every SystemWIndows I open or close, do a beep. > However, the Pharo dev image works ok for me. > > The solution is very simple: Disable the preference: "soundsEnabled" > The thing is that this is really annoying and there is a lot of > people that it isn't aware of that. In addition, in Pharo, it is > already disable by default. > > Can this be change? I am sorry I don't know how to really fix it. > > Best, > > Mariano > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Aug. 20, 2009

Re: [Pharo-project] 10394, pharo beeps on every SystemWindow open/close

by Mariano Martinez Peck

On Thu, Aug 20, 2009 at 11:49 AM, Damien Cassou <damien.cassou(a)gmail.com>wrote: > 2009/8/20 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > Hi folks: This but is still happening to me. In only happens in Linux and > > with the core image. In this situation, I cannot use this image because > > every SystemWIndows I open or close, do a beep. > > However, the Pharo dev image works ok for me. > > > > The solution is very simple: Disable the preference: "soundsEnabled" > > The thing is that this is really annoying and there is a lot of people > that > > it isn't aware of that. In addition, in Pharo, it is already disable by > > default. > > > > Can this be change? I am sorry I don't know how to really fix it. > > Please open a bug report with status 'Fixed' and tag Milestone-1.0. ok, done http://code.google.com/p/pharo/issues/detail?id=1080 > > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Lambdas are relegated to relative obscurity until Java makes them > popular by not having them." James Iry > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 20, 2009

Re: [Pharo-project] Getting Javascript in Moose and/or Pharo

by Alexandre Bergel

True! Alexandre On 20 Aug 2009, at 03:40, Michael Roberts wrote: > Have you looked at OMeta? there is a package for squeak I think. > > Mike > > On Monday, August 17, 2009, Alexandre Bergel <alexandre(a)bergel.eu> > wrote: >> Dear List >> >> Making Pharo interacting with Javascript has been the cup of tea of >> the Seaside community. >> I am wondering whether there has been an attempt to produce a parser >> for Javascript within Pharo. >> >> We are interested in getting Javascript models within Moose. >> >> For now, it is likely what we will use the parser of Mozilla to >> produce MSE files. >> >> Cheers, >> Alexandre >> >> NB: Sorry for the cross-posting >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> _______________________________________________ >> 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 > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Aug. 20, 2009