January 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Hudson now Jenkins

by StÃ©phane Ducasse

>> > Hudson/Jenkins release once a week, pretty amazing. Well I'm sure that it makes sense but this is their problem. For Pharo1.3 we want to be able to release after any green build. We want to make sure that all the process is fluid so that we do not have any stress about releasing. Now we will release 2 or 3 times a year maximum. Stef

Jan. 31, 2011

[Pharo-project] how to use dejavu bitmap fonts

by Tudor Girba

Hi, I am trying to use the DejaVuBitmapFonts, but I do not know how to install them. I tried the following: Gofer it squeaksource: 'DejaVu'; package: 'DejaVuBitmapFonts'; load. DejaVuHolder installFull. However, this creates a problem in using TextConstants. Can anyone help? Cheers, Doru -- www.tudorgirba.com "One cannot do more than one can do."

Jan. 31, 2011

Re: [Pharo-project] Issue 3472 in pharo: Text selection problem in Pharo-dev 1.2

by pharo＠googlecode.com

Comment #9 on issue 3472 by stephane...(a)gmail.com: Text selection problem in Pharo-dev 1.2 http://code.google.com/p/pharo/issues/detail?id=3472 Thanks a lot alain. This is because there are people like you that this communaute is great. Stef

Jan. 31, 2011

Re: [Pharo-project] would be nice if configuration comment always contain how to load them :(

by StÃ©phane Ducasse

On Jan 31, 2011, at 9:39 PM, laurent laffont wrote: > On Mon, Jan 31, 2011 at 8:56 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Why not put this comment by default in all the configurationOfXXX > > I spent 10 min to find how to load Profstef to check a bug and I wrote the chapter on metacello with > mariano so there is something wrong. > > So, what would you put in comment for ConfigurationOfProfStef ? > > ConfigurationOfXXX project latestVersion load normally works ..... just that. I tried several commands and I do not remember all these magic invocation. In my project I put a comment so that I can forget and come back in 10 years and I will not have to guess because I guess badly. Stef > > Laurent > > > > Stef > > > > Don't forget that the aim is to have all the configurations updated to > > the new symbolic version capabilities of the Metacello. > > > > Given that, then the standard (official) way to load (either by hand or > > by tools like the browser) *any* configuration will be something similar > > to: > > > > Gofer it "or new" > > squeaksource: "MetacelloRepository"; > > project: "XXX"; > > load. > > > > ((Smalltalk globals at: #ConfigurationOfXXX) project version: #stable) > > load > > > > This of course will be hidden from users by the existence of the > > user-tools and will install the stable version tested for the image > > version metacello it is running on. > > > > Of course it will be way to load a specific version (either because a > > bug fix hunting or simply by personal preference) of a given > > configuration. Something like: > > > > ((Smalltalk globals at: #ConfigurationOfXXX) project version: > > '1.4-something') load > > > > But this will be only for specific users and for specific reasons. Most > > users only want the stable version for its platform and metacello's > > symbolic versions give them that. > > > > Cheers. > > > > > > El lun, 31-01-2011 a las 17:23 +0100, Luc Fabresse escribiÃ³: > >> +1 > >> > >> > >> #Luc > >> > >> > >> 2011/1/31 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > >> > >> > >> > >> > > > > -- > > Miguel CobÃ¡ > > http://twitter.com/MiguelCobaMtz > > http://miguel.leugim.com.mx > > > > > > > > > > >

Jan. 31, 2011

Re: [Pharo-project] Issue 3472 in pharo: Text selection problem in Pharo-dev 1.2

by pharo＠googlecode.com

Updates: Status: Fixed Labels: Milestone-1.3 Comment #8 on issue 3472 by aplan...(a)gmail.com: Text selection problem in Pharo-dev 1.2 http://code.google.com/p/pharo/issues/detail?id=3472 in inbox, SLICE-Issue-3472-smalltalkEditor-evaluateSelection-fix should be ok for 1.2 and 1.3

Jan. 31, 2011

Re: [Pharo-project] would be nice if configuration comment always contain how to load them :(

by laurent laffont

On Mon, Jan 31, 2011 at 8:56 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Why not put this comment by default in all the configurationOfXXX > > I spent 10 min to find how to load Profstef to check a bug and I wrote the > chapter on metacello with > mariano so there is something wrong. > So, what would you put in comment for ConfigurationOfProfStef ? ConfigurationOfXXX project latestVersion load normally works ..... Laurent > > Stef > > > > Don't forget that the aim is to have all the configurations updated to > > the new symbolic version capabilities of the Metacello. > > > > Given that, then the standard (official) way to load (either by hand or > > by tools like the browser) *any* configuration will be something similar > > to: > > > > Gofer it "or new" > > squeaksource: "MetacelloRepository"; > > project: "XXX"; > > load. > > > > ((Smalltalk globals at: #ConfigurationOfXXX) project version: #stable) > > load > > > > This of course will be hidden from users by the existence of the > > user-tools and will install the stable version tested for the image > > version metacello it is running on. > > > > Of course it will be way to load a specific version (either because a > > bug fix hunting or simply by personal preference) of a given > > configuration. Something like: > > > > ((Smalltalk globals at: #ConfigurationOfXXX) project version: > > '1.4-something') load > > > > But this will be only for specific users and for specific reasons. Most > > users only want the stable version for its platform and metacello's > > symbolic versions give them that. > > > > Cheers. > > > > > > El lun, 31-01-2011 a las 17:23 +0100, Luc Fabresse escribiÃ³: > >> +1 > >> > >> > >> #Luc > >> > >> > >> 2011/1/31 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > >> > >> > >> > >> > > > > -- > > Miguel CobÃ¡ > > http://twitter.com/MiguelCobaMtz > > http://miguel.leugim.com.mx > > > > > > > > > > >

Jan. 31, 2011

Re: [Pharo-project] would be nice if configuration comment always contain how to load them :(

by StÃ©phane Ducasse

Thanks Dale. Stef On Jan 31, 2011, at 9:27 PM, Dale Henrichs wrote: > Stef, > > I will make changes to the default config comment to include a template (metacello Issue 106)... the current (as of 1.0-beta.28) comment in the template is: > > Copy me to create a new configuration or edit and evaluate the following doits. > > "Create configuration class and initial baseline method" > > MetacelloToolBox > createBaseline: '1.0-baseline' > for: 'MyProject' > repository: 'http://www.example.com/MyProjectRepository' > requiredProjects: #('Gofer') > packages: #('MyProject-Core' 'MyProject-Tests') > dependencies: > {('MyProject-Core' -> #('Gofer')). > ('MyProject-Tests' -> #('MyProject-Core'))} > groups: > {('default' -> #('Core')). > ('Core' -> #('MyProject-Core')). > ('Tests' -> #('MyProject-Tests'))}. > > "create initial development method from the baseline" > > MetacelloToolBox > createDevelopment: '1.0' > for: 'MyProject' > importFromBaseline: '1.0-baseline' > description: 'initial version'. > > But this would a be a good place to include information about how to load the configuration as well... > > Dale > > On 01/31/2011 11:56 AM, StÃ©phane Ducasse wrote: >> Why not put this comment by default in all the configurationOfXXX >> >> I spent 10 min to find how to load Profstef to check a bug and I wrote the chapter on metacello with >> mariano so there is something wrong. >> >> Stef >> >> >>> Don't forget that the aim is to have all the configurations updated to >>> the new symbolic version capabilities of the Metacello. >>> >>> Given that, then the standard (official) way to load (either by hand or >>> by tools like the browser) *any* configuration will be something similar >>> to: >>> >>> Gofer it "or new" >>> squeaksource: "MetacelloRepository"; >>> project: "XXX"; >>> load. >>> >>> ((Smalltalk globals at: #ConfigurationOfXXX) project version: #stable) >>> load >>> >>> This of course will be hidden from users by the existence of the >>> user-tools and will install the stable version tested for the image >>> version metacello it is running on. >>> >>> Of course it will be way to load a specific version (either because a >>> bug fix hunting or simply by personal preference) of a given >>> configuration. Something like: >>> >>> ((Smalltalk globals at: #ConfigurationOfXXX) project version: >>> '1.4-something') load >>> >>> But this will be only for specific users and for specific reasons. Most >>> users only want the stable version for its platform and metacello's >>> symbolic versions give them that. >>> >>> Cheers. >>> >>> >>> El lun, 31-01-2011 a las 17:23 +0100, Luc Fabresse escribiÃ³: >>>> +1 >>>> >>>> >>>> #Luc >>>> >>>> >>>> 2011/1/31 StÃ©phane Ducasse<stephane.ducasse(a)inria.fr> >>>> >>>> >>>> >>>> >>> >>> -- >>> Miguel CobÃ¡ >>> http://twitter.com/MiguelCobaMtz >>> http://miguel.leugim.com.mx >>> >>> >>> >>> >> >> >

Jan. 31, 2011

Re: [Pharo-project] pharo.st should be a permanent domain, I think

by Adrian Lienhard

-1 ...because in my opinion there should be exactly one main domain name. The additional names should just redirect to this one. Of course we could discuss whether pharo.st should be that main domain. But (already quite long time ago) we decided to go for pharo-project.org. I still think that is the better name, in particular for people who don't know what the meaning of .st is. I think they are less likely to klick on www.pharo.st in a search engine than on www.pharo-project.org. Cheers, Adrian On Jan 31, 2011, at 21:15 , Diogenes Moreira wrote: > Always ready. as a boy scout.. only send me de ssh conxion... > > > On Mon, Jan 31, 2011 at 5:08 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > >> Hi, >> I tried pharo.st to reach pharo. I liked. It's small, concise, beautiful >> (and it has a .st!) >> One problem is that as soon as you type pharo.st, you loose the url. I >> would like to stay in the url I entered to pharo-project. I think this is >> easily doable with an apache configuration. >> I'm not an apache guy, but I'm sure if there are some problem with this, >> and all of you agree this is desirable, someone from the list (cough, cough, >> DiÃ³genes, cough, cough) can do the job :) >> >> Cheers, >> Esteban >>

Jan. 31, 2011

Re: [Pharo-project] what do we do for OmniBrowser?

by StÃ©phane Ducasse

I know. I'm doing a lot too. I believe that a good infrastructure will help us. This is why I believe that we need metacellorepositories. Stef On Jan 31, 2011, at 9:16 PM, Esteban Lorenzano wrote: > I think we need to move OB outside lukas domain. Sadly, lukas now does not have time to do all that wonderful work we are used :( > That means we (the community) need some guys to step into, and maintain the packages ourselves. I'm not jumping my self because right now I have more tasks than I can handle, but maybe some one can do it. > > Lukas, can you provide a list of tasks you see we need to do for getting OB working with 1.2? (I dunno if they are on the tracker, if that's the case, I'm sorry :) ) > > best, > Esteban > > El 31/01/2011, a las 5:03p.m., StÃ©phane Ducasse escribiÃ³: > >> Hi guys >> >> Lukas will not maintain OB for Pharo 1.2 and personnally I will not do it because I do not have the knowledge and the time. >> So now this is time to know what do we do for OmniBrowser. I have all my ears open. >> >> >> The first step I would do >> - host OB for 1.1 in a repository where we have write access. >> - create a configurationOf for OB and save it there >> >> >> Stef >

Jan. 31, 2011

Re: [Pharo-project] would be nice if configuration comment always contain how to load them :(

by Dale Henrichs

Stef, I will make changes to the default config comment to include a template (metacello Issue 106)... the current (as of 1.0-beta.28) comment in the template is: Copy me to create a new configuration or edit and evaluate the following doits. "Create configuration class and initial baseline method" MetacelloToolBox createBaseline: '1.0-baseline' for: 'MyProject' repository: 'http://www.example.com/MyProjectRepository' requiredProjects: #('Gofer') packages: #('MyProject-Core' 'MyProject-Tests') dependencies: {('MyProject-Core' -> #('Gofer')). ('MyProject-Tests' -> #('MyProject-Core'))} groups: {('default' -> #('Core')). ('Core' -> #('MyProject-Core')). ('Tests' -> #('MyProject-Tests'))}. "create initial development method from the baseline" MetacelloToolBox createDevelopment: '1.0' for: 'MyProject' importFromBaseline: '1.0-baseline' description: 'initial version'. But this would a be a good place to include information about how to load the configuration as well... Dale On 01/31/2011 11:56 AM, StÃ©phane Ducasse wrote: > Why not put this comment by default in all the configurationOfXXX > > I spent 10 min to find how to load Profstef to check a bug and I wrote the chapter on metacello with > mariano so there is something wrong. > > Stef > > >> Don't forget that the aim is to have all the configurations updated to >> the new symbolic version capabilities of the Metacello. >> >> Given that, then the standard (official) way to load (either by hand or >> by tools like the browser) *any* configuration will be something similar >> to: >> >> Gofer it "or new" >> squeaksource: "MetacelloRepository"; >> project: "XXX"; >> load. >> >> ((Smalltalk globals at: #ConfigurationOfXXX) project version: #stable) >> load >> >> This of course will be hidden from users by the existence of the >> user-tools and will install the stable version tested for the image >> version metacello it is running on. >> >> Of course it will be way to load a specific version (either because a >> bug fix hunting or simply by personal preference) of a given >> configuration. Something like: >> >> ((Smalltalk globals at: #ConfigurationOfXXX) project version: >> '1.4-something') load >> >> But this will be only for specific users and for specific reasons. Most >> users only want the stable version for its platform and metacello's >> symbolic versions give them that. >> >> Cheers. >> >> >> El lun, 31-01-2011 a las 17:23 +0100, Luc Fabresse escribiÃ³: >>> +1 >>> >>> >>> #Luc >>> >>> >>> 2011/1/31 StÃ©phane Ducasse<stephane.ducasse(a)inria.fr> >>> >>> >>> >>> >> >> -- >> Miguel CobÃ¡ >> http://twitter.com/MiguelCobaMtz >> http://miguel.leugim.com.mx >> >> >> >> > >

Jan. 31, 2011