- Pharo-users - lists.pharo.org

Pharo on LinkedIn ...

by Geert Claes

We would like to invite those Pharoers who have a LinkedIn account to join our LinkedIn Pharo group. http://www.linkedin.com/e/hzbhb7-gkawp6l9-36/vgh/2558378/ -- View this message in context: http://forum.world.st/Pharo-on-LinkedIn-tp3312461p3312461.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 18, 2011

Re: [Pharo-users] [Pharo-project] Call for Pharo Support **important**

by StÃ©phane Ducasse

Thanks sven On Feb 18, 2011, at 9:15 AM, Sven Van Caekenberghe wrote: > > On 18 Feb 2011, at 08:51, Davorin Rusevljan wrote: > >> I am not expert in legalize, does signing of this letter imply some >> financial commitment on part of the signer, or it is just "Pharo is >> great and we would like to use it" kind of letter? >> >> Many thanks! >> >> Davorin Rusevljan >> http://www.cloud208.com/ > > I do not think of this letter as a contract, far from it. > > You just declare your support for the Pharo project and indicate that you would be interested in joining a future consortium, depending on the conditions of that membership of course. > > Anyway, I signed it. > > Sven > > >

Feb. 18, 2011

Re: [Pharo-users] [Pharo-project] Call for Pharo Support **important**

by Sven Van Caekenberghe

On 18 Feb 2011, at 08:51, Davorin Rusevljan wrote: > I am not expert in legalize, does signing of this letter imply some > financial commitment on part of the signer, or it is just "Pharo is > great and we would like to use it" kind of letter? > > Many thanks! > > Davorin Rusevljan > http://www.cloud208.com/ I do not think of this letter as a contract, far from it. You just declare your support for the Pharo project and indicate that you would be interested in joining a future consortium, depending on the conditions of that membership of course. Anyway, I signed it. Sven

Feb. 18, 2011

Re: [Pharo-users] [Pharo-project] Call for Pharo Support **important**

by StÃ©phane Ducasse

Hi davorin It says that you would consider paying a membership if this one is ok for you but that the membership would have to be clear. So this is just a letter of support. Your are not tying yourself. We will decide together the model because we should like that everybody can contribute. Now for us this is an important tool because we can seize the community to see if we could collect money to pay an engineer like igor full-time, half time.... Stef > I am not expert in legalize, does signing of this letter imply some > financial commitment on part of the signer, or it is just "Pharo is > great and we would like to use it" kind of letter? > > Many thanks! > > Davorin Rusevljan > http://www.cloud208.com/

Feb. 18, 2011

Re: [Pharo-users] [Pharo-project] Call for Pharo Support **important**

by Davorin Rusevljan

I am not expert in legalize, does signing of this letter imply some financial commitment on part of the signer, or it is just "Pharo is great and we would like to use it" kind of letter? Many thanks! Davorin Rusevljan http://www.cloud208.com/

Feb. 18, 2011

Re: [Pharo-users] [Pharo-project] Call for Pharo Support **important**

by StÃ©phane Ducasse

On Feb 16, 2011, at 11:28 PM, Tudor Girba wrote: > The reason I am asking is that in the text you say "if your company/research group would be interested", which tends to not invite individuals. > > Ok, so individuals should sign it, too? yes > > Cheers, > Doru > > > On 16 Feb 2011, at 23:01, StÃ©phane Ducasse wrote: > >> both >> this is a user and industrial consortium. >> may be I'm a dreamer but I would like something open to the community in general. >> >> >> Stef >> >> On Feb 16, 2011, at 10:11 PM, Tudor Girba wrote: >> >>> Just a question: are you interested only in companies/groups or also individuals? >>> >>> Cheers, >>> Doru >>> >>> >>> On 16 Feb 2011, at 16:38, StÃ©phane Ducasse wrote: >>> >>>> Dear Pharoers >>>> >>>> We are pursuing an effort to bring Pharo to the next level: we will set up a consortium of pharo users and industrial partners. Our goal is to build a legal infrastructure that will be able to sustain the development of Pharo and improve its future. As an example, we would like to be able to collect funds (ways as to be determined - we foresee a membership model or moral license) to pay engineering tasks to be performed such as improving the virtual machine, network libraries, better JIT support. To make it short we would like to give a chance to our community to grow and structure itself so that Pharo can get stronger and that risk (truck factor) gets minimized. >>>> >>>> We are contacting you to know if your company/research group would be interested to support such effort. Showing such interest is strategically important for us and INRIA which could also support such effort. Attached is the letter of support that we will collect once signed and scanned ( stephane.ducasse(a)inria.fr / faxed at: 00 33 (0)3 59 57 78 50) >>>> >>>> Thanks for your support >>>> >>>> The Pharo Board >>>> >>>> M. Denker, S. Ducasse, and A. Lienhard >>>> >>>> <Pharo-LetterOfSupport-EN-V2.doc> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Presenting is storytelling." >>> >>> >> >> > > -- > www.tudorgirba.com > > "Value is always contextual." > > > >

Feb. 18, 2011

Re: [Pharo-users] Dependencies and Monticello

by Luc Fabresse

Hi Andrew, You forgot to declare 'PetitParser' and 'PetitTests' (not 'PetitTests-Core' ;-) ) Find attached a ConfigurationOfGrace. See class comment to load. Cheers, #Luc Le 17 fÃ©vr. 2011 Ã 17:31, Simon Denier a Ã©crit : > Hi Andrew > > If you don't want to spend the extra time to learn Metacello right now (although it's the very basic thing Metacello does, so I think it should be pretty easy for you to get started and just deal with the basics of Metacello), you can write a script to load packages in a specific order with Gofer. > > See http://www.lukas-renggli.ch/blog/gofer > > So something like > Gofer new > squeaksource: 'yourproject'; > package: 'packageX'; "get latest version of packageX" > version: 'packageY-yyyyy.188'; "get version 188 of packageY" > load > > and you can save the script in a method (to set up your environment) or even an external file which can be passed to and runned by the VM (not all VMs support this though) > > > > On 17 fÃ©vr. 2011, at 16:02, Andrew Black wrote: > >> Hi Stéf >> >> Thank you for the draft chapter, and also to Laurent for the video. The video, however, goes too fast for those who as yet do not understand. Using these resources, I have spent 2 or 3 hours learning about Metacello. It seems like a very powerful tool, but one that is overkill for my purposes. It looks like a lot of machinery is needed to do what is now the simplest thing for me, which is to load the bleeding edge version of my own code. However, the effort of learning all of this stuff has not been lost, because in 6 months or a year I may really need it. >> >> Still, I cannot figure out how to solve the motivating problem, which was described in my original mail: make my 'project' depend on someone else's package. >> >> So far I have this: >> >> baseline100: spec >> <version: '1.0-baseline'> >> >> spec for: #common do: [ >> spec blessing: #baseline. >> spec repository: 'http://www.SqueakSource/GraceParser'. >> spec >> package: 'Grace-Parser' with: [spec requires: 'PetitParser'; >> repository: 'http://source.lukas-renggli.ch/petit' ]; >> package: 'Grace-ParserTests' with: [spec requires: 'PetitTests-Core'; >> repository: 'http://source.lukas-renggli.ch/petit' ]. >> spec >> group: 'default' with: #('Core' 'Tests'); >> group: 'Core' with: #('Grace-Parser'); >> group: 'Tests' with: #('Grace-ParserTests'). ]. >> >> When I try to load: '1.0', I get a walkback with the message: 'Error: Name not found: PetitParser', so obviously I'm not describing the dependency correctly. >> >> What's the right way to define a dependency on a package in another repository? >> >> Andrew >> >> >> >> >> -----Original Message----- >> From: pharo-users-bounces(a)lists.gforge.inria.fr [mailto:pharo-users-bounces@lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse >> Sent: 15 February 2011 15:24 >> To: A friendly place where any question about pharo is welcome >> Subject: Re: [Pharo-users] Dependencies and Monticello >> >> Hi andrew >> >> Do not use dependencies. >> They do not work well. >> Use Metacello. Here is a draft I should finish on metacello. >> >> > > -- > Simon Denier > > > >

Feb. 17, 2011

Re: [Pharo-users] Dependencies and Monticello

by Simon Denier

Hi Andrew If you don't want to spend the extra time to learn Metacello right now (although it's the very basic thing Metacello does, so I think it should be pretty easy for you to get started and just deal with the basics of Metacello), you can write a script to load packages in a specific order with Gofer. See http://www.lukas-renggli.ch/blog/gofer So something like Gofer new squeaksource: 'yourproject'; package: 'packageX'; "get latest version of packageX" version: 'packageY-yyyyy.188'; "get version 188 of packageY" load and you can save the script in a method (to set up your environment) or even an external file which can be passed to and runned by the VM (not all VMs support this though) On 17 fÃ©vr. 2011, at 16:02, Andrew Black wrote: > Hi Stéf > > Thank you for the draft chapter, and also to Laurent for the video. The video, however, goes too fast for those who as yet do not understand. Using these resources, I have spent 2 or 3 hours learning about Metacello. It seems like a very powerful tool, but one that is overkill for my purposes. It looks like a lot of machinery is needed to do what is now the simplest thing for me, which is to load the bleeding edge version of my own code. However, the effort of learning all of this stuff has not been lost, because in 6 months or a year I may really need it. > > Still, I cannot figure out how to solve the motivating problem, which was described in my original mail: make my 'project' depend on someone else's package. > > So far I have this: > > baseline100: spec > <version: '1.0-baseline'> > > spec for: #common do: [ > spec blessing: #baseline. > spec repository: 'http://www.SqueakSource/GraceParser'. > spec > package: 'Grace-Parser' with: [spec requires: 'PetitParser'; > repository: 'http://source.lukas-renggli.ch/petit' ]; > package: 'Grace-ParserTests' with: [spec requires: 'PetitTests-Core'; > repository: 'http://source.lukas-renggli.ch/petit' ]. > spec > group: 'default' with: #('Core' 'Tests'); > group: 'Core' with: #('Grace-Parser'); > group: 'Tests' with: #('Grace-ParserTests'). ]. > > When I try to load: '1.0', I get a walkback with the message: 'Error: Name not found: PetitParser', so obviously I'm not describing the dependency correctly. > > What's the right way to define a dependency on a package in another repository? > > Andrew > > > > > -----Original Message----- > From: pharo-users-bounces(a)lists.gforge.inria.fr [mailto:pharo-users-bounces@lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse > Sent: 15 February 2011 15:24 > To: A friendly place where any question about pharo is welcome > Subject: Re: [Pharo-users] Dependencies and Monticello > > Hi andrew > > Do not use dependencies. > They do not work well. > Use Metacello. Here is a draft I should finish on metacello. > > -- Simon Denier

Feb. 17, 2011

Re: [Pharo-users] Dependencies and Monticello

by Andrew Black

Hi Stéf Thank you for the draft chapter, and also to Laurent for the video. The video, however, goes too fast for those who as yet do not understand. Using these resources, I have spent 2 or 3 hours learning about Metacello. It seems like a very powerful tool, but one that is overkill for my purposes. It looks like a lot of machinery is needed to do what is now the simplest thing for me, which is to load the bleeding edge version of my own code. However, the effort of learning all of this stuff has not been lost, because in 6 months or a year I may really need it. Still, I cannot figure out how to solve the motivating problem, which was described in my original mail: make my 'project' depend on someone else's package. So far I have this: baseline100: spec <version: '1.0-baseline'> spec for: #common do: [ spec blessing: #baseline. spec repository: 'http://www.SqueakSource/GraceParser'. spec package: 'Grace-Parser' with: [spec requires: 'PetitParser'; repository: 'http://source.lukas-renggli.ch/petit' ]; package: 'Grace-ParserTests' with: [spec requires: 'PetitTests-Core'; repository: 'http://source.lukas-renggli.ch/petit' ]. spec group: 'default' with: #('Core' 'Tests'); group: 'Core' with: #('Grace-Parser'); group: 'Tests' with: #('Grace-ParserTests'). ]. When I try to load: '1.0', I get a walkback with the message: 'Error: Name not found: PetitParser', so obviously I'm not describing the dependency correctly. What's the right way to define a dependency on a package in another repository? Andrew -----Original Message----- From: pharo-users-bounces(a)lists.gforge.inria.fr [mailto:pharo-users-bounces@lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse Sent: 15 February 2011 15:24 To: A friendly place where any question about pharo is welcome Subject: Re: [Pharo-users] Dependencies and Monticello Hi andrew Do not use dependencies. They do not work well. Use Metacello. Here is a draft I should finish on metacello.

Feb. 17, 2011

Re: [Pharo-users] [Pharo-project] Call for Pharo Support **important**

by Tudor Girba

The reason I am asking is that in the text you say "if your company/research group would be interested", which tends to not invite individuals. Ok, so individuals should sign it, too? Cheers, Doru On 16 Feb 2011, at 23:01, StÃ©phane Ducasse wrote: > both > this is a user and industrial consortium. > may be I'm a dreamer but I would like something open to the community in general. > > > Stef > > On Feb 16, 2011, at 10:11 PM, Tudor Girba wrote: > >> Just a question: are you interested only in companies/groups or also individuals? >> >> Cheers, >> Doru >> >> >> On 16 Feb 2011, at 16:38, StÃ©phane Ducasse wrote: >> >>> Dear Pharoers >>> >>> We are pursuing an effort to bring Pharo to the next level: we will set up a consortium of pharo users and industrial partners. Our goal is to build a legal infrastructure that will be able to sustain the development of Pharo and improve its future. As an example, we would like to be able to collect funds (ways as to be determined - we foresee a membership model or moral license) to pay engineering tasks to be performed such as improving the virtual machine, network libraries, better JIT support. To make it short we would like to give a chance to our community to grow and structure itself so that Pharo can get stronger and that risk (truck factor) gets minimized. >>> >>> We are contacting you to know if your company/research group would be interested to support such effort. Showing such interest is strategically important for us and INRIA which could also support such effort. Attached is the letter of support that we will collect once signed and scanned ( stephane.ducasse(a)inria.fr / faxed at: 00 33 (0)3 59 57 78 50) >>> >>> Thanks for your support >>> >>> The Pharo Board >>> >>> M. Denker, S. Ducasse, and A. Lienhard >>> >>> <Pharo-LetterOfSupport-EN-V2.doc> >> >> -- >> www.tudorgirba.com >> >> "Presenting is storytelling." >> >> > > -- www.tudorgirba.com "Value is always contextual."

Feb. 16, 2011