December 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Scale in 3.0 (kind of ANN)

by Norbert Hartl

> Am 02.12.2014 um 13:31 schrieb Ben Coman <btc(a)openinworld.com>: > > phil(a)highoctane.be wrote: >> I've put Guille's Scale thing (http://guillep.github.io/blog/2014/01/23/replacing-bash-with-pharo/) into Pharo 3.0 >> Details on how to use here: >> http://smalltalkhub.com/#!/~philippeback/Scale >> Enjoy, >> Phil > > > > We named the command we needed scale, because scales are in shells, > > it sounded nice. > > Nice lateral thinking, but it seems like a stretch :) > > For making a shell, why not something simple in the tradition of sh, bash, csh, ksh, psh? e.g. pharosh or phsh? > +1 Norbert

Dec. 2, 2014

Re: [Pharo-dev] default fonts changed in Pharo 4.0

by Sven Van Caekenberghe

Esteban, Did you look/read what Juraj Kubelka did ? Like this issue, but there are others too: https://pharo.fogbugz.com/f/cases/13967 I vaguely remember he found something wrt initialization, maybe Marcus remembers. Sven > On 02 Dec 2014, at 13:10, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > â¦ and I lost fonts again :( > I made an integration and fonts got lostâ¦ Iâm reviving issue, and working on it :( > > Esteban > >> On 02 Dec 2014, at 12:47, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >>> >>> On 02 Dec 2014, at 12:12, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>>> >>>> On 02 Dec 2014, at 12:02, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>> >>>> >>>>> On 02 Dec 2014, at 11:46, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>>> >>>>> There is no Source Code Sans :). There is only "Source Sans Pro" or "Source Code Pro". >>>> >>>> Yes, right now in the latest 4.0. >>>> >>>> But there used to be a different one, that is the one I am using, see screenshot (http://www.google.com/fonts/specimen/Open+Sans) I don't remember where I got it from (Igor is the author), but I have been using it for months. >>> >>> no, it was me the authorâ¦ and it was a mistake I made first time thatâs why I removed it (but I can package it and put it somewhere anywayâ¦ I was even thinking on create a âFont Repositoryâ where put different fonts, until I found this: http://smalltalkhub.com/#!/~girba/FreeFonts which is a cool repo, but does not works completely along our versionâ¦ we will need to merge :P) >> >> Maybe it would be even better if there was code in the image to make these embedded fonts yourself (or a comment). >> >>>> My question was, why choose one above the other ? >>> >>> I replaced it with the Source Sans Pro because same family fonts works better together (Source * Pro) >> >> OK. It seems to have a smaller width, we'll see. >> >>> cheers, >>> Esteban >>> >>>> >>>> <Screen Shot 2014-12-02 at 11.57.13.png> >>>> >>>>> >>>>> Doru >>>>> >>>>> On Tue, Dec 2, 2014 at 11:35 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>>> What is the difference between 'Open Sans' and 'Source Code Sans' ? >>>>> >>>>> I am using the former in my 3.0 image, and I like it a bit more, it seems a bit wider. >>>>> >>>>>> On 02 Dec 2014, at 11:27, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>>>> >>>>>> Great! >>>>>> >>>>>> Doru >>>>>> >>>>>> p.s. Finally :) >>>>>> >>>>>> >>>>>> On Tue, Dec 2, 2014 at 9:48 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>>>> Hi, >>>>>> >>>>>> We changed the default fonts in Pharo for the ones that are used normally in Moose. >>>>>> They are: Source Sans Pro and Source Code Pro. >>>>>> We needed to do it for several reasons: >>>>>> >>>>>> 1) TxText (the new text model) is cairo based, and cairo just can work with real fonts, so we need them as default (now we will be able to integrate TxText and start the replace of old editors) >>>>>> 2) Current fonts takes too much space and do not scales fine (at least that Iâve been told) >>>>>> >>>>>> So, well, thatâ¦ you will see âsomething differentâ when you download latest image version :) >>>>>> >>>>>> cheers, >>>>>> Esteban >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> www.tudorgirba.com >>>>>> >>>>>> "Every thing has its own flow" >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> www.tudorgirba.com >>>>> >>>>> "Every thing has its own flow" >

Dec. 2, 2014

Re: [Pharo-dev] Scale in 3.0 (kind of ANN)

by Ben Coman

phil(a)highoctane.be wrote: > I've put Guille's Scale thing > (http://guillep.github.io/blog/2014/01/23/replacing-bash-with-pharo/) > into Pharo 3.0 > > Details on how to use here: > > http://smalltalkhub.com/#!/~philippeback/Scale > > Enjoy, > Phil > > > > We named the command we needed scale, because scales are in shells, > it sounded nice. Nice lateral thinking, but it seems like a stretch :) For making a shell, why not something simple in the tradition of sh, bash, csh, ksh, psh? e.g. pharosh or phsh?

Dec. 2, 2014

Re: [Pharo-dev] default fonts changed in Pharo 4.0

by Tudor Girba

Thanks, Esteban. This kind of work is too under appreciated. Cheers, Doru On Tue, Dec 2, 2014 at 1:10 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > â¦ and I lost fonts again :( > I made an integration and fonts got lostâ¦ Iâm reviving issue, and working > on it :( > > Esteban > > On 02 Dec 2014, at 12:47, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > On 02 Dec 2014, at 12:12, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > On 02 Dec 2014, at 12:02, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > On 02 Dec 2014, at 11:46, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > There is no Source Code Sans :). There is only "Source Sans Pro" or > "Source Code Pro". > > > Yes, right now in the latest 4.0. > > But there used to be a different one, that is the one I am using, see > screenshot (http://www.google.com/fonts/specimen/Open+Sans) I don't > remember where I got it from (Igor is the author), but I have been using it > for months. > > > no, it was me the authorâ¦ and it was a mistake I made first time thatâs > why I removed it (but I can package it and put it somewhere anywayâ¦ I was > even thinking on create a âFont Repositoryâ where put different fonts, > until I found this: http://smalltalkhub.com/#!/~girba/FreeFonts which is > a cool repo, but does not works completely along our versionâ¦ we will need > to merge :P) > > > Maybe it would be even better if there was code in the image to make these > embedded fonts yourself (or a comment). > > My question was, why choose one above the other ? > > > I replaced it with the Source Sans Pro because same family fonts works > better together (Source * Pro) > > > OK. It seems to have a smaller width, we'll see. > > cheers, > Esteban > > > <Screen Shot 2014-12-02 at 11.57.13.png> > > > Doru > > On Tue, Dec 2, 2014 at 11:35 AM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > What is the difference between 'Open Sans' and 'Source Code Sans' ? > > I am using the former in my 3.0 image, and I like it a bit more, it seems > a bit wider. > > On 02 Dec 2014, at 11:27, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Great! > > Doru > > p.s. Finally :) > > > On Tue, Dec 2, 2014 at 9:48 AM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > Hi, > > We changed the default fonts in Pharo for the ones that are used normally > in Moose. > They are: Source Sans Pro and Source Code Pro. > We needed to do it for several reasons: > > 1) TxText (the new text model) is cairo based, and cairo just can work > with real fonts, so we need them as default (now we will be able to > integrate TxText and start the replace of old editors) > 2) Current fonts takes too much space and do not scales fine (at least > that Iâve been told) > > So, well, thatâ¦ you will see âsomething differentâ when you download > latest image version :) > > cheers, > Esteban > > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 2, 2014

Re: [Pharo-dev] default fonts changed in Pharo 4.0

by Esteban Lorenzano

â¦ and I lost fonts again :( I made an integration and fonts got lostâ¦ Iâm reviving issue, and working on it :( Esteban > On 02 Dec 2014, at 12:47, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> >> On 02 Dec 2014, at 12:12, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >>> >>> On 02 Dec 2014, at 12:02, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>> >>>> On 02 Dec 2014, at 11:46, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>> >>>> There is no Source Code Sans :). There is only "Source Sans Pro" or "Source Code Pro". >>> >>> Yes, right now in the latest 4.0. >>> >>> But there used to be a different one, that is the one I am using, see screenshot (http://www.google.com/fonts/specimen/Open+Sans) I don't remember where I got it from (Igor is the author), but I have been using it for months. >> >> no, it was me the authorâ¦ and it was a mistake I made first time thatâs why I removed it (but I can package it and put it somewhere anywayâ¦ I was even thinking on create a âFont Repositoryâ where put different fonts, until I found this: http://smalltalkhub.com/#!/~girba/FreeFonts which is a cool repo, but does not works completely along our versionâ¦ we will need to merge :P) > > Maybe it would be even better if there was code in the image to make these embedded fonts yourself (or a comment). > >>> My question was, why choose one above the other ? >> >> I replaced it with the Source Sans Pro because same family fonts works better together (Source * Pro) > > OK. It seems to have a smaller width, we'll see. > >> cheers, >> Esteban >> >>> >>> <Screen Shot 2014-12-02 at 11.57.13.png> >>> >>>> >>>> Doru >>>> >>>> On Tue, Dec 2, 2014 at 11:35 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>> What is the difference between 'Open Sans' and 'Source Code Sans' ? >>>> >>>> I am using the former in my 3.0 image, and I like it a bit more, it seems a bit wider. >>>> >>>>> On 02 Dec 2014, at 11:27, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>>> >>>>> Great! >>>>> >>>>> Doru >>>>> >>>>> p.s. Finally :) >>>>> >>>>> >>>>> On Tue, Dec 2, 2014 at 9:48 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>>> Hi, >>>>> >>>>> We changed the default fonts in Pharo for the ones that are used normally in Moose. >>>>> They are: Source Sans Pro and Source Code Pro. >>>>> We needed to do it for several reasons: >>>>> >>>>> 1) TxText (the new text model) is cairo based, and cairo just can work with real fonts, so we need them as default (now we will be able to integrate TxText and start the replace of old editors) >>>>> 2) Current fonts takes too much space and do not scales fine (at least that Iâve been told) >>>>> >>>>> So, well, thatâ¦ you will see âsomething differentâ when you download latest image version :) >>>>> >>>>> cheers, >>>>> Esteban >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> www.tudorgirba.com >>>>> >>>>> "Every thing has its own flow" >>>> >>>> >>>> >>>> >>>> >>>> -- >>>> www.tudorgirba.com >>>> >>>> "Every thing has its own flow"

Dec. 2, 2014

Re: [Pharo-dev] default fonts changed in Pharo 4.0

by Sven Van Caekenberghe

> On 02 Dec 2014, at 12:12, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> >> On 02 Dec 2014, at 12:02, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> >>> On 02 Dec 2014, at 11:46, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> >>> There is no Source Code Sans :). There is only "Source Sans Pro" or "Source Code Pro". >> >> Yes, right now in the latest 4.0. >> >> But there used to be a different one, that is the one I am using, see screenshot (http://www.google.com/fonts/specimen/Open+Sans) I don't remember where I got it from (Igor is the author), but I have been using it for months. > > no, it was me the authorâ¦ and it was a mistake I made first time thatâs why I removed it (but I can package it and put it somewhere anywayâ¦ I was even thinking on create a âFont Repositoryâ where put different fonts, until I found this: http://smalltalkhub.com/#!/~girba/FreeFonts which is a cool repo, but does not works completely along our versionâ¦ we will need to merge :P) Maybe it would be even better if there was code in the image to make these embedded fonts yourself (or a comment). >> My question was, why choose one above the other ? > > I replaced it with the Source Sans Pro because same family fonts works better together (Source * Pro) OK. It seems to have a smaller width, we'll see. > cheers, > Esteban > >> >> <Screen Shot 2014-12-02 at 11.57.13.png> >> >>> >>> Doru >>> >>> On Tue, Dec 2, 2014 at 11:35 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> What is the difference between 'Open Sans' and 'Source Code Sans' ? >>> >>> I am using the former in my 3.0 image, and I like it a bit more, it seems a bit wider. >>> >>> > On 02 Dec 2014, at 11:27, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> > >>> > Great! >>> > >>> > Doru >>> > >>> > p.s. Finally :) >>> > >>> > >>> > On Tue, Dec 2, 2014 at 9:48 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> > Hi, >>> > >>> > We changed the default fonts in Pharo for the ones that are used normally in Moose. >>> > They are: Source Sans Pro and Source Code Pro. >>> > We needed to do it for several reasons: >>> > >>> > 1) TxText (the new text model) is cairo based, and cairo just can work with real fonts, so we need them as default (now we will be able to integrate TxText and start the replace of old editors) >>> > 2) Current fonts takes too much space and do not scales fine (at least that Iâve been told) >>> > >>> > So, well, thatâ¦ you will see âsomething differentâ when you download latest image version :) >>> > >>> > cheers, >>> > Esteban >>> > >>> > >>> > >>> > >>> > >>> > -- >>> > www.tudorgirba.com >>> > >>> > "Every thing has its own flow" >>> >>> >>> >>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Every thing has its own flow"

Dec. 2, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40394 Home: https://github.com/pharo-project/pharo-core

Dec. 2, 2014

[pharo-project/pharo-core] e3c61d: 40394

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: e3c61d5e96987e907d531dafe966378d863112aa https://github.com/pharo-project/pharo-core/commit/e3c61d5e96987e907d531daf… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-12-02 (Tue, 02 Dec 2014) Changed paths: M AST-Core.package/ManifestASTCore.class/definition.st M Fuel.package/ManifestFuel.class/definition.st M Manifest-Core.package/ManifestManifestCore.class/definition.st A Manifest-Core.package/PackageManifest.class/README.md A Manifest-Core.package/PackageManifest.class/class/testing/isManifest.st A Manifest-Core.package/PackageManifest.class/definition.st A Manifest-Core.package/PackageManifest.class/instance/code-critics/rejectClasses.st A Manifest-Core.package/PackageManifest.class/instance/code-critics/rejectRules.st A Manifest-Core.package/PackageManifest.class/instance/comparing/=.st A Manifest-Core.package/PackageManifest.class/instance/comparing/hash.st M Manifest-Core.package/SmalllintManifestChecker.class/instance/manifest/isFalsePositive_forRuleId_versionId_.st M Manifest-Core.package/TheManifestBuilder.class/class/instance creation/of_.st M Manifest-Core.package/TheManifestBuilder.class/class/utils/allManifestClasses.st M Manifest-Core.package/TheManifestBuilder.class/class/utils/manifestClassComment.st M Manifest-Core.package/TheManifestBuilder.class/definition.st M Manifest-Core.package/TheManifestBuilder.class/instance/accessing/manifest.st M Manifest-Core.package/TheManifestBuilder.class/instance/adding%2Fremoving/addRejectClass_.st M Manifest-Core.package/TheManifestBuilder.class/instance/adding%2Fremoving/addRejectRule_.st M Manifest-Core.package/TheManifestBuilder.class/instance/adding%2Fremoving/cleanUp.st M Manifest-Core.package/TheManifestBuilder.class/instance/adding%2Fremoving/removeRejectClass_.st M Manifest-Core.package/TheManifestBuilder.class/instance/adding%2Fremoving/removeRejectRule_.st M Manifest-Core.package/TheManifestBuilder.class/instance/comparing/=.st M Manifest-Core.package/TheManifestBuilder.class/instance/manifest/createManifestNamed_.st M Manifest-Core.package/TheManifestBuilder.class/instance/manifest/falsePositiveOf_version_.st M Manifest-Core.package/TheManifestBuilder.class/instance/manifest/hasFalsePositiveOf_version_.st M Manifest-Core.package/TheManifestBuilder.class/instance/manifest/hasToDoOf_version_.st M Manifest-Core.package/TheManifestBuilder.class/instance/manifest/hasTruePositiveOf_version_.st M Manifest-Core.package/TheManifestBuilder.class/instance/manifest/rejectClasses.st M Manifest-Core.package/TheManifestBuilder.class/instance/manifest/rejectRules.st M Manifest-Core.package/TheManifestBuilder.class/instance/manifest/toDoOf_version_.st M Manifest-Core.package/TheManifestBuilder.class/instance/manifest/truePositiveOf_version_.st M Manifest-Core.package/TheManifestBuilder.class/instance/private/addAllItem_selector_.st M Manifest-Core.package/TheManifestBuilder.class/instance/private/compileSelector_returnValue_.st M Manifest-Core.package/TheManifestBuilder.class/instance/private/dateOf_forSelector_.st M Manifest-Core.package/TheManifestBuilder.class/instance/private/isObsoleteManifest.st M Manifest-Core.package/TheManifestBuilder.class/instance/private/removeAllItem_selector_.st M Manifest-Core.package/TheManifestBuilder.class/instance/private/removeObsoleteFalsePositiveOf_.st A Manifest-Core.package/extension/RPackage/instance/packageManifest.st M Manifest-Core.package/extension/TBehavior/instance/isManifest.st M Manifest-CriticBrowser.package/ManifestManifestCriticBrowser.class/definition.st R Manifest-Tests.package/ManifestManifestTests.class/class/meta data/rejectClasses.st R Manifest-Tests.package/ManifestManifestTests.class/class/meta data/rejectRules.st M Manifest-Tests.package/ManifestManifestTests.class/definition.st M NautilusRefactoring.package/NautilusRefactoring.class/instance/private-class/privateGenerateSubclassFor_.st M NautilusRefactoring.package/NautilusRefactoring.class/instance/private-class/privateGenerateSuperClassFor_.st M NautilusRefactoring.package/NautilusRefactoring.class/instance/private-class/privateInsertSubclassFor_.st M NautilusRefactoring.package/NautilusRefactoring.class/instance/private-class/privateInsertSuperclassFor_.st M OpalCompiler-Core.package/ManifestOpalCompilerCore.class/definition.st A Refactoring-Core.package/RBRemoveMethodRefactoring.class/instance/preconditions/checkBrowseAllOccurences_.st A Refactoring-Core.package/RBRemoveMethodRefactoring.class/instance/preconditions/checkBrowseOccurrenceOf_in_.st A Refactoring-Core.package/RBRemoveMethodRefactoring.class/instance/preconditions/checkBrowseOccurrences_.st M Refactoring-Core.package/RBRemoveMethodRefactoring.class/instance/preconditions/checkReferencesToAnyOf_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script394.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40394.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M StartupPreferences.package/StartupPreferencesLoader.class/instance/accessing/add_.st M UserManager-Tests.package/ManifestKeyChainTest.class/definition.st Log Message: ----------- 40394 14556 Error: Instances of UndefinedObject are not indexable https://pharo.fogbugz.com/f/cases/14556 14505 Better integration of Package Manifest https://pharo.fogbugz.com/f/cases/14505 10719 Problem removing methods with more than one implementor using suggestions https://pharo.fogbugz.com/f/cases/10719 12594 #runOnce: of StartupAction not working https://pharo.fogbugz.com/f/cases/12594 http://files.pharo.org/image/40/40394.zip

Dec. 2, 2014

Re: [Pharo-dev] ubuntu vm build

by Norbert Hartl

Hi, > Am 01.12.2014 um 21:02 schrieb Markus Fritsche <mfritsche(a)reauktion.de>: > > Hello Norbert, > > I tried using the copy feature - can you check if it worked? > it worked for me. I tested the image a little while and it looks good. Thanks I didn't see the copy thing yesterday. Norbert > Kind regards > Markus > > On 01.12.2014 19:36, Norbert Hartl wrote: >> Hi, >> >> I forgot who is maintaining the ubuntu launchpad ppa vm build. But whoever you are ( :) ) would it be possible to include a vm build for the actual ubuntu release utopic unicorn? >> >> thanks, >> >> Norbert >> >> > >

Dec. 2, 2014

Re: [Pharo-dev] default fonts changed in Pharo 4.0

by kilon alios

https://www.youtube.com/watch?v=_J6-3l3hCm0

Dec. 2, 2014