- Pharo-dev - lists.pharo.org

Re: [Pharo-project] access to pharoextras repository

by Ben Coman

stephane ducasse wrote: >> That is why, either we explicitly put the 'Tests' group in the 'default' group, >> > > - I would go for this behavior because I do not like implicit behavior when this is about configuration > and I will start to write comments in all the configurations > > "default is used when nothing is specified by default it will load everything but better specify what everything is" > > > So once we agree I will start editing configurations like a mad. > > Stef > > In you book chapter about Configurations you might hint "why" it is preferred to include Tests in default. For me... * people fresh to the package get some examples. * encourages new tests to be added. Having to find & load a 'Tests' group at a later time would be an impediment to this. You might also consider a convention for an 'Examples' group.

March 10, 2013

Re: [Pharo-project] Pharo consultants

by Mariano Martinez Peck

Thanks Stef for the nice words :) Maybe a first step which could be quite easy is to add a page of "Pharo associated consultants" or something like that in the Pharo website. Like the one we have now for contributors: http://www.pharo-project.org/community/contributors but for consultants. And each consultant can write a few keywords or small paragraph about their expertise. Best, On Sat, Mar 9, 2013 at 7:11 PM, Sebastian Sastre < sebastian(a)flowingconcept.com> wrote: > Ah I get it, that's right. > > Probably what I mean is a better site of that goal which is answering *who > is who in terms of what he/she did* > > thinking in https://angel.co/ as a benchmark > > sebastian <https://about.me/sebastianconcept> > > o/ > > > > > > On Mar 9, 2013, at 5:39 PM, stephane ducasse wrote: > > > That would be awesome. > > Glad to hear about an initiative to make things sustainable. > > A catalog of people who works using it would be great. > > > We have the association just for that! In the next version we will add > blogging facilities. > > No need to be a social network site, just a catalog for people to navigate > who's working with it. Plus a subscribe/login for everyone manage its own > profile so consultants can set a photo some bio and its portfolio > > > Did you check the association web site :) > > Everybody could endorse skills or write reviews > > > We cannot do that but you can link to linkedIn. > > I know I know... Linked In already kind of does that, but that's not the > point > > > so we are already linking into linkedIn :) > > > The point is that we have our little proprietary thing focused on Pharo > and endorsed by Pharo itself > > > We have the association and it points to linkedIn > > > If I would have available time I would make flowing itself to sponsor with > developing such a site/extension to current pharo site > > > Sorry but I do not understand what you mean. > > > > sebastian <https://about.me/sebastianconcept> > > o/ > > > > > > On Mar 8, 2013, at 6:05 PM, StÃ©phane Ducasse wrote: > > Hi guys > > I just got a nice chat with a cool Pharo expert (Mariano) that is doing > consulting and development around Pharo and this is a cool feeling to know > that smart guys in our community can find nice jobs that keeps them busy in > Pharo. > I think that we should market the community much more, because I think > that this is important for other companies > to know that they can find help with really talented people in our > community. > May be we should make more noise around: > Pharo: a community with smart developers for cool business > > Stef > > > > > > > > > -- Mariano http://marianopeck.wordpress.com

March 10, 2013

Re: [Pharo-project] FMSound bass1 play

by phil＠highoctane.be

Never got that working on iOS. Obvious since: - (void) ioBeep { #ifdef BUILD_FOR_OSX NSBeep(); #endif } On OSX >From docs: http://cocoadev.com/wiki/NSBeep NSBeep() plays the system beep that the users have defined in the Sound Panel of the System Preferences. If sound effects aren't activated in there, no beep. On a 2.0 image the Beeper primitiveBeep works perfectly with a VM build from sources on 15/02/2013. Phil 2013/3/9 stephane ducasse <stephane.ducasse(a)free.fr>: > but > > Beeper primitiveBeep > > still does not work > > Stef > > On Mar 9, 2013, at 11:05 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > >> The problem was that I had my headset plugged in and not on my ears => just one hour to find that is the indication that I should better go to sleep. >> >> Stef >> >> On Mar 9, 2013, at 10:21 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: >> >>> Hi guys >>> >>> I'm migrating the package Sound and MorphicSound to Pharo2.0 and SmalltalkHub. >>> But I cannot make >>> >>> FMSound bass1 play >>> produce a sound. >>> >>> Phil if i remember correctly you worked on that a couple of months ago. >>> Can you summarize your findings? >>> >>> Stef >> > >

March 9, 2013

Re: [Pharo-project] fogbugz entries

by Benjamin

Most probably because during the migration, more specific status has been lost. What you should do is list the open active cases (I have something like First 50 open cases that are active which more or less is want I was used to have in Google Issue Tracker). I will try to have a look at that and fix them by hand, but not now (pair programming on Amber with Nico) ^^ Ben On Mar 9, 2013, at 8:55 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > I wanted to have a look at the new fogbugz entries. > But when I list all active entries, I have quite a lot of entries with "Closed (Active)", any clue what that means?

March 9, 2013

Re: [Pharo-project] FMSound bass1 play

by phil＠highoctane.be

Will have a look at my notes. Phil 2013/3/9 stephane ducasse <stephane.ducasse(a)free.fr>: > The problem was that I had my headset plugged in and not on my ears => just one hour to find that is the indication that I should better go to sleep. > > Stef > > On Mar 9, 2013, at 10:21 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > >> Hi guys >> >> I'm migrating the package Sound and MorphicSound to Pharo2.0 and SmalltalkHub. >> But I cannot make >> >> FMSound bass1 play >> produce a sound. >> >> Phil if i remember correctly you worked on that a couple of months ago. >> Can you summarize your findings? >> >> Stef > >

March 9, 2013

Re: [Pharo-project] Pharo consultants

by Sebastian Sastre

Ah I get it, that's right. Probably what I mean is a better site of that goal which is answering who is who in terms of what he/she did thinking in https://angel.co/ as a benchmark sebastian o/ On Mar 9, 2013, at 5:39 PM, stephane ducasse wrote: > >> That would be awesome. >> >> Glad to hear about an initiative to make things sustainable. >> >> A catalog of people who works using it would be great. > > We have the association just for that! In the next version we will add blogging facilities. > >> No need to be a social network site, just a catalog for people to navigate who's working with it. Plus a subscribe/login for everyone manage its own profile so consultants can set a photo some bio and its portfolio > > Did you check the association web site :) > >> Everybody could endorse skills or write reviews > > We cannot do that but you can link to linkedIn. > >> I know I know... Linked In already kind of does that, but that's not the point > > so we are already linking into linkedIn :) >> >> The point is that we have our little proprietary thing focused on Pharo and endorsed by Pharo itself > > We have the association and it points to linkedIn > > >> If I would have available time I would make flowing itself to sponsor with developing such a site/extension to current pharo site > > Sorry but I do not understand what you mean. > > >> >> sebastian >> >> o/ >> >> >> >> >> >> On Mar 8, 2013, at 6:05 PM, StÃ©phane Ducasse wrote: >> >>> Hi guys >>> >>> I just got a nice chat with a cool Pharo expert (Mariano) that is doing consulting and development around Pharo and this is a cool feeling to know that smart guys in our community can find nice jobs that keeps them busy in Pharo. >>> I think that we should market the community much more, because I think that this is important for other companies >>> to know that they can find help with really talented people in our community. >>> May be we should make more noise around: >>> Pharo: a community with smart developers for cool business >>> >>> Stef >>> >>> >>> >>> >>> >> >

March 9, 2013

Re: [Pharo-project] FMSound bass1 play

by stephane ducasse

but Beeper primitiveBeep still does not work Stef On Mar 9, 2013, at 11:05 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > The problem was that I had my headset plugged in and not on my ears => just one hour to find that is the indication that I should better go to sleep. > > Stef > > On Mar 9, 2013, at 10:21 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > >> Hi guys >> >> I'm migrating the package Sound and MorphicSound to Pharo2.0 and SmalltalkHub. >> But I cannot make >> >> FMSound bass1 play >> produce a sound. >> >> Phil if i remember correctly you worked on that a couple of months ago. >> Can you summarize your findings? >> >> Stef >

March 9, 2013

Re: [Pharo-project] FMSound bass1 play

by stephane ducasse

The problem was that I had my headset plugged in and not on my ears => just one hour to find that is the indication that I should better go to sleep. Stef On Mar 9, 2013, at 10:21 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > Hi guys > > I'm migrating the package Sound and MorphicSound to Pharo2.0 and SmalltalkHub. > But I cannot make > > FMSound bass1 play > produce a sound. > > Phil if i remember correctly you worked on that a couple of months ago. > Can you summarize your findings? > > Stef

March 9, 2013

Re: [Pharo-project] access to pharoextras repository

by stephane ducasse

> That is not what I said :). ok I see :) > > We often get at least two groups in a configuration: > - Core - the real code > - Tests - the associated tests Yes I tried to get consistent. > The question is what should be loaded by 'default' (this is what gets loaded when you do not specify anything in the dependency). Ok I forgot that one. > By saying > spec group: 'default' with: #('Core') > we say that by default we do not load tests. Yes and by default I would prefer to get the tests too :) > If we do not specify any 'default', it will take by default everything, hence it will be equivalent in our case with > spec group: 'default' with: #('Core' 'Tests'); Does it really load everything? So default is ALL by default --- I forgot again. > I would want to favor the loading of tests by default. Me too. > That is why, either we explicitly put the 'Tests' group in the 'default' group, - I would go for this behavior because I do not like implicit behavior when this is about configuration and I will start to write comments in all the configurations "default is used when nothing is specified by default it will load everything but better specify what everything is" So once we agree I will start editing configurations like a mad. Stef > or we do not specify a 'default' at all in trivial configurations like the ConfigurationOfXMLParser. > > Cheers, > Doru > > >>> Hi, >>> >>> Could anyone provide me with access to the PharoExtras team on STHub? >>> >>> I would need to modify a bit the ConfigurationOfXMLParser to load both Core and Tests by default. >>> >>> Cheers, >>> Doru >>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "If you can't say why something is relevant, >>> it probably isn't." >>> >>> >> >> > > -- > www.tudorgirba.com > > "Speaking louder won't make the point worthier." > >

March 9, 2013

Re: [Pharo-project] customizing the CommandLineHandler to run Moose tests

by stephane ducasse

thanks! Stef On Mar 9, 2013, at 10:41 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > I wanted to investigate it a bit more before announcing the problem. You can reproduce it on Mac, quite consistently: just run the attached script (you need to have wget installed), or do it manually: > > 1. download and unzip the latest Moose 4.8: > https://ci.inria.fr/moose/job/Moose-latest-dev-4.8/lastSuccessfulBuild/arti… > 2. download and unzip the latest Pharo VM: > http://pharo.gforge.inria.fr/ci/vm/pharo/mac/pharo-mac-latest.zip > 3. execute: > ./Pharo.app/Contents/MacOS/Pharo ./Moose-latest-dev-4.8.image moosetest > > > The VM crashes, but there is no trace of the error. > > Cheers, > Doru > > > On Mar 9, 2013, at 1:35 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > >> Hi doru >> >> can you report precisely because now we cannot take any action? >> >> Stef >> >>> >>> p.s. The VM still crashes when running the tests though (at least on Mac) >> > > -- > www.tudorgirba.com > > "What is more important: To be happy, or to make happy?" > >

March 9, 2013