November 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Bringing external documentation internally , Deep Into Pharo , PBE

by ClÃ©ment Bera

How do you want to bring it ? With class comments, method with comment only ? I guess it is not a problem as long as it does not take too much memory (I mean as long as it is not a Mb). 2013/11/5 kilon alios <kilon.alios(a)gmail.com> > Is this a problem ? I want to bring external documentation inside the > Pharo image, and I was wondering if I need permission and such. I will be > editing also some documentation to make it easier to read and more current. > I am already working on Nativeboost documentation. >

Nov. 5, 2013

Re: [Pharo-dev] Bringing external documentation internally , Deep Into Pharo , PBE

by Alexandre Bergel

No permission at all. You just have to give credit to the authors, nothing more nothing less Cheers, Alexandre > On 5 Nov 2013, at 06:16, kilon alios <kilon.alios(a)gmail.com> wrote: > > Is this a problem ? I want to bring external documentation inside the Pharo image, and I was wondering if I need permission and such. I will be editing also some documentation to make it easier to read and more current. I am already working on Nativeboost documentation.

Nov. 5, 2013

Re: [Pharo-dev] [Seaside] Looking for camera(wo)man FOSDEM2014 Smalltalk devroom

by FranÃ§ois Stephany

Hi Stephan, If you still need someone, I can help ;) On Fri, Nov 1, 2013 at 11:01 AM, Stephan Eggermont <stephan(a)stack.nl> wrote: > Who is coming to FOSDEM2014 and is willing to help recording one or more > sessions > at the Smalltalk devroom? Instructions and equipment are provided. > > Thanks, > Stephan Eggermont_______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >

Nov. 5, 2013

[pharo-project/pharo-core]

by GitHub

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

Nov. 5, 2013

[pharo-project/pharo-core] 4d50f3: 30547

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 4d50f3e44e78355b74d43f8c80b7286222ca7b74 https://github.com/pharo-project/pharo-core/commit/4d50f3e44e78355b74d43f8c… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-11-05 (Tue, 05 Nov 2013) Changed paths: R Files.package/PharoFilesOpener.class/instance/open changes/tryToOpenChanges.st R Files.package/PharoFilesOpener.class/instance/open sources/tryToOpenSources.st A Files.package/PharoFilesOpener.class/instance/public/changesFileOrNil.st R Files.package/PharoFilesOpener.class/instance/public/checkAndOpenSourcesAndChanges.st A Files.package/PharoFilesOpener.class/instance/public/sourcesFileOrNil.st M Files.package/SourceFileArray.class/instance/file system/ensureOpen.st M Kernel.package/DateAndTime.class/instance/maintime/midnight.st M Kernel.package/DateAndTime.class/instance/offset/translateToUTC.st A Kernel.package/Timespan.class/instance/accessing/offset_.st M Kernel.package/Timespan.class/instance/conversion/translateToUTC.st M Kernel.package/Timespan.class/instance/conversion/translateTo_.st M KernelTests.package/DateTest.class/instance/helpers/epoch.st M KernelTests.package/DateTest.class/instance/tests/testNew.st A Manifest-Core.package/extension/RBShouldntRaiseErrorRule/class/uniqueIdentifierName.st A Manifest-Core.package/extension/RBShouldntRaiseErrorRule/instance/category.st A Manifest-Core.package/extension/RBShouldntRaiseErrorRule/instance/longDescription.st A Refactoring-Critics.package/RBShouldntRaiseErrorRule.class/README.md A Refactoring-Critics.package/RBShouldntRaiseErrorRule.class/definition.st A Refactoring-Critics.package/RBShouldntRaiseErrorRule.class/instance/accessing/group.st A Refactoring-Critics.package/RBShouldntRaiseErrorRule.class/instance/accessing/name.st A Refactoring-Critics.package/RBShouldntRaiseErrorRule.class/instance/accessing/rationale.st A Refactoring-Critics.package/RBShouldntRaiseErrorRule.class/instance/initialization/initialize.st R Refactoring-Tests-Core.package/RBTransformationRuleTest.class/class/as yet unclassified/cleanUp.st A Refactoring-Tests-Core.package/RBTransformationRuleTest.class/class/cleanup/cleanUp.st M Refactoring-Tests-Critics.package/RBSmalllintTest.class/instance/private/ruleFor_plusSelectors_.st A Refactoring-Tests-Critics.package/RBSmalllintTest.class/instance/tests/testShouldntRaiseError.st A Refactoring-Tests-Critics.package/RBSmalllintTestObject.class/instance/methods/ifTrueBlocks.st A Refactoring-Tests-Critics.package/RBSmalllintTestObject.class/instance/methods/shouldntRaiseError.st A Refactoring-Tests-Critics.package/RBSmalllintTestObject.class/instance/methods/shouldntRaiseException.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script202.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30547.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 30547 12070 Add lint rule for #shouldnt:raise: edge cases https://pharo.fogbugz.com/f/cases/12070 12068 DateTest >> #testNew is bogus with negative timezone offsets https://pharo.fogbugz.com/f/cases/12068 12069 In the SourceFiles global, only put objects that are polymorphic with SourceFileArray https://pharo.fogbugz.com/f/cases/12069 http://files.pharo.org/image/30/30547.zip

Nov. 5, 2013

Bringing external documentation internally , Deep Into Pharo , PBE

by kilon alios

Is this a problem ? I want to bring external documentation inside the Pharo image, and I was wondering if I need permission and such. I will be editing also some documentation to make it easier to read and more current. I am already working on Nativeboost documentation.

Nov. 5, 2013

Re: [Pharo-dev] WhatsUp from: 2013-11-04 until: 2013-11-17

by Sven Van Caekenberghe

On 05 Nov 2013, at 06:04, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > I am glad you are considering other types of fonts :). Still, I think that Open Sans does not work well with Source Code. First, there is not enough distinction between them, and second, their rhythms do not match (both in terms of height and width). > > Choosing a consistent family of fonts mitigates these problems. Source is a family of fonts that also comes with a Source Sans variation. That is why my settings look like: Change my fonts, I will, and Walk this path, try to, Master âDoruâ Yoda ;-) > #('SourceCodeProRegular' 'SourceCodeProBold' 'SourceSansProRegular' 'SourceSansProBold') do: [ :each | > Smalltalk globals > at: each asSymbol > ifAbsent: [ > Gofer new > smalltalkhubUser: 'girba' project: 'FreeFonts'; > package: each; > load ]. > (Smalltalk at: each asSymbol) new install ]. > FreeTypeSystemSettings loadFt2Library: true. > FreeTypeFontProvider current updateFromSystem > StandardFonts > setAllStandardFontsTo: (LogicalFont familyName: 'Source Sans Pro' pointSize: 10); > haloFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 10); > windowTitleFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 14); > balloonFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 10); > codeFont: (LogicalFont familyName: 'Source Code Pro' pointSize: 10) > > > Here is a screenshot: > https://www.dropbox.com/s/i39f7phfy9v1bqh/pharo-with-only-source-fonts.png > > Notice how I also load the bold versions of both fonts so that we can use them both in code and in lists. > > Cheers, > Doru > > > > On Mon, Nov 4, 2013 at 5:31 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hey Doru, > > On 04 Nov 2013, at 17:01, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> - Continue on the topic of "Pharo IDE of the Futureâ > > Great, looking forward to it ! > > FWIW, I have come around about the fonts ;-) > > I have been using Open Sans & Source Code Pro for a while now, and I like them. > > These are my font selections for my MacBook Air 13ââ (1440x900): > > <Screen Shot 2013-11-04 at 17.25.38.png> > Light and modern, like Pharo itself ! > > Apart from the bolding of the window title font, this code sets those fonts: > > SourceCodeProRegular new install. > OpenSansRegular new install. > FreeTypeFontProvider current updateFromSystem. > > #( > #(#defaultFont: 'Open Sans' 12) > #(#listFont: 'Open Sans' 12) > #(#menuFont: 'Open Sans' 12) > #(#windowTitleFont: 'Open Sans' 12) > #(#balloonFont: 'Open Sans' 10) > #(#codeFont: 'Source Code Pro' 11) > #(#buttonFont: 'Open Sans' 12) > #(#haloFont: 'Open Sans' 10)) do: [ :spec | > | font | > font := LogicalFont familyName: spec second pointSize: spec third. > StandardFonts perform: spec first with: font ] > > Thanks again for taking care ! > > Sven > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Nov. 5, 2013

Re: [Pharo-dev] Latest Xcode to Compile VM

by Camillo Bruni

On 2013-11-05, at 05:07, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > What's the latest Xcode version successfully used to compile the Pharo VM? I > don't want to upgrade past the maintainers... I think everybody upgraded to 10.9 but did not have time yet to compile the VM :P. The Mac slave is using a rather old OS and an even older Xcode...

Nov. 5, 2013

Re: [Pharo-dev] Feature request poll

by Tudor Girba

Pharo is Pharo. And we should promote it like that. http://www.tudorgirba.com/blog/pharo-is-pharo Doru On Mon, Nov 4, 2013 at 11:19 PM, kilon alios <kilon.alios(a)gmail.com> wrote: > I think now Pharo as Pharo. It stands on its own get inspired by the past, > inventing the future ;) > > how that sounds ? > > > On Mon, Nov 4, 2013 at 11:21 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com>wrote: > >> >> On 04 Nov 2013, at 22:13, Esteban A. Maringolo <emaringolo(a)gmail.com> >> wrote: >> >> >> 2013/11/4 Alexandre Bergel <alexandre.bergel(a)me.com> >> >>> Why do you mention Smalltalk at all actually? In my classes, I simply >>> say that Pharo is inspired by Smalltalk, if I ever mention it >>> It is easier to be convinced by the future than by the past. >>> >>> >> To me trying to dissociate Smalltalk from Pharo is like trying to >> dissociate Smalltalk from VisualWorks (aka "Cincom Smalltalk"). >> Or worst... ANSI C from C++. >> >> I still mention Smalltalk, and I promote Pharo as "an active Smalltalk >> dialect". >> >> Maybe it will be better to promote it plainly as Pharoâ¦ >> >> I just say that Pharo is what had to happen with Smalltalk in last 30 >> years. We can think about Pharo in Smalltalk like Scala in Java. But Java >> had versions, and Smalltalk is treated just as only 80th year frozen >> snapshot. Iâd say that Pharo is a Smalltalk of 2013 year. Oh, yes, but in >> public itâs better to say that Pharo is completely different ;) >> >> >> >> >> >> >> >> Esteban A. Maringolo >> >> >> > -- www.tudorgirba.com "Every thing has its own flow"

Nov. 5, 2013

Re: [Pharo-dev] WhatsUp from: 2013-11-04 until: 2013-11-17

by Tudor Girba

Hi, I am glad you are considering other types of fonts :). Still, I think that Open Sans does not work well with Source Code. First, there is not enough distinction between them, and second, their rhythms do not match (both in terms of height and width). Choosing a consistent family of fonts mitigates these problems. Source is a family of fonts that also comes with a Source Sans variation. That is why my settings look like: #('SourceCodeProRegular' 'SourceCodeProBold' 'SourceSansProRegular' 'SourceSansProBold') do: [ :each | Smalltalk globals at: each asSymbol ifAbsent: [ Gofer new smalltalkhubUser: 'girba' project: 'FreeFonts'; package: each; load ]. (Smalltalk at: each asSymbol) new install ]. FreeTypeSystemSettings loadFt2Library: true. FreeTypeFontProvider current updateFromSystem StandardFonts setAllStandardFontsTo: (LogicalFont familyName: 'Source Sans Pro' pointSize: 10); haloFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 10); windowTitleFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 14); balloonFont: (LogicalFont familyName: 'Source Sans Pro' pointSize: 10); codeFont: (LogicalFont familyName: 'Source Code Pro' pointSize: 10) Here is a screenshot: https://www.dropbox.com/s/i39f7phfy9v1bqh/pharo-with-only-source-fonts.png Notice how I also load the bold versions of both fonts so that we can use them both in code and in lists. Cheers, Doru On Mon, Nov 4, 2013 at 5:31 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hey Doru, > > On 04 Nov 2013, at 17:01, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > - Continue on the topic of "Pharo IDE of the Futureâ > > > Great, looking forward to it ! > > FWIW, I have come around about the fonts ;-) > > I have been using Open Sans & Source Code Pro for a while now, and I like > them. > > These are my font selections for my MacBook Air 13ââ (1440x900): > > Light and modern, like Pharo itself ! > > Apart from the bolding of the window title font, this code sets those > fonts: > > SourceCodeProRegular new install. > OpenSansRegular new install. > FreeTypeFontProvider current updateFromSystem. > > #( > #(#defaultFont: 'Open Sans' 12) > #(#listFont: 'Open Sans' 12) > #(#menuFont: 'Open Sans' 12) > #(#windowTitleFont: 'Open Sans' 12) > #(#balloonFont: 'Open Sans' 10) > #(#codeFont: 'Source Code Pro' 11) > #(#buttonFont: 'Open Sans' 12) > #(#haloFont: 'Open Sans' 10)) do: [ :spec | > | font | > font := LogicalFont familyName: spec second pointSize: spec third. > StandardFonts perform: spec first with: font ] > > Thanks again for taking care ! > > Sven > -- www.tudorgirba.com "Every thing has its own flow"

Nov. 5, 2013