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

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

by Alexandre Bergel

I agree with Adrian Alexandre Le 31 janv. 2011 Ã 15:31, Adrian Lienhard <adi(a)netstyle.ch> a Ã©crit : > -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] pharo.st should be a permanent domain, I think

by Adrian Lienhard

Hi Esteban, >> ...because in my opinion there should be exactly one main domain name. The additional names should just redirect to this one. > > why? For instance to make sure that there are not the same pages listed in search engine results with different domain names. Then, (according to SEO guys) you get better indexed if you have just one domain name, redirecting to it and making all external links point to that name. In general, I like consistency and I don't like redundancy :). Imagine in the mailing list one guy linking to pharo.st/news the next to www.pharo-project.org/news the next to www.pharo.st/news etc... Cheers, Adrian

Jan. 31, 2011

[Pharo-project] Issue 3639 in pharo: ServerDirectory contains a lot of old and unused code

by pharo＠googlecode.com

Status: Accepted Owner: stephane...(a)gmail.com New issue 3639 by stephane...(a)gmail.com: ServerDirectory contains a lot of old and unused code http://code.google.com/p/pharo/issues/detail?id=3639 We should do another pass and remove some of the unused behavior related to multiple updates distributions.

Jan. 31, 2011

[Pharo-project] Issue 3638 in pharo: look for sender of etoyCleaningLeftToDo

by pharo＠googlecode.com

Status: Accepted Owner: stephane...(a)gmail.com New issue 3638 by stephane...(a)gmail.com: look for sender of etoyCleaningLeftToDo http://code.google.com/p/pharo/issues/detail?id=3638 there are still code to clean

Jan. 31, 2011

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

by pharo＠googlecode.com

Updates: Status: Closed Comment #11 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 in 13034

Jan. 31, 2011

[Pharo-project] [update 1.2] #12329

by StÃ©phane Ducasse

12329 ----- - Issue 3472: Text selection problem in Pharo-dev 1.2. Thanks alain Plantec. Stef

Jan. 31, 2011

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

by Esteban Lorenzano

El 31/01/2011, a las 5:31p.m., Adrian Lienhard escribiÃ³: > ...because in my opinion there should be exactly one main domain name. The additional names should just redirect to this one. why?

Jan. 31, 2011

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

by pharo＠googlecode.com

Comment #10 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 in 12329

Jan. 31, 2011

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

by Esteban Lorenzano

I would like to propose the integration of Gofer Project Loader to Gofer. Then you just write: Gofer project load: 'Blah'. A lot easier than remember all the other stuff. best, Esteban El 31/01/2011, a las 5:49p.m., StÃ©phane Ducasse escribiÃ³: > > 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] how to use dejavu bitmap fonts

by StÃ©phane Ducasse

The package should be updated to 1.2. It should declare fonts probably in one of the classVar of the TextConstant SharedPool. Probably TextSharedInformation have a look. In 1.2 we cleaned the last global poolvar = textConstant which was used as a pool but also as a repository to plug anything inside instead of specific classVariable in adequate classes. It was a good plate of spaghettis code. I know that benjamin wants to take some times to do another pass and move the left over to the class they belongs to but it will take some time. Stef On Jan 31, 2011, at 9:52 PM, Tudor Girba wrote: > 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