- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Git written entirely in Smalltalk?

by Richard Sargent

Ben Coman wrote > Max, > > The other say I was contemplating having a git implementation written > entirely in Pharo, and today I bumped into something from your history > (~2011?) [1] indicating this might have been attempted. I'm curious > why this was abandoned in favour of libgit bindings. I have seen a lot of "not invented here" work in the Smalltalk world over the last 25 years. That in itself is enough reason to not reimplement everything in native Smalltalk. There are whole communities out there who specialize in one esoteric piece of technology. You can stand on their shoulders or you can copy their work. One of those appeals a lot more to me than the other. When we bind to someone else's work, their updates are almost free to us. Otherwise, we tie up a lot of our own resources replicating their work and not advancing our own. > [1] http://scg.unibe.ch/wiki/students/maxleske > > cheers -ben -- View this message in context: http://forum.world.st/Git-written-entirely-in-Smalltalk-tp4880274p4880430.h… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Feb. 24, 2016

[pharo-project/pharo-core] 4ade51: 50609

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 4ade51dbf2af66d85f356a52898d15c32b602ed1 https://github.com/pharo-project/pharo-core/commit/4ade51dbf2af66d85f356a52… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-02-24 (Wed, 24 Feb 2016) Changed paths: R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50608.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50609.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50608.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50609.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Slot.package/SlotClassBuilder.class/instance/initialize-release/build.st Log Message: ----------- 50609 17687 fix: changing class comments does not work https://pharo.fogbugz.com/f/cases/17687 http://files.pharo.org/image/50/50609.zip

Feb. 24, 2016

[pharo-project/pharo-core]

by GitHub

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

Feb. 24, 2016

GTSpotter displayed shortcut glitch

by stepharo

Hi doru and andrei I saw that you are displaying the shortcuts that can be used and this is good. Now may be I got it wrong but Cmd + M is not for implementors everywhere else it is Cmd + m Same for senders So I checked and Cmd + n is senders but displayed Cmd+N Cmd+N shows references and this is cool. Stef

Feb. 24, 2016

Re: [Pharo-dev] Help with PrStef with Fonts

by stepharo

this is what I started to suspect!!! Ok I saw that you already commit the code you were faster than me :) Stef Le 24/2/16 17:29, Nicolai Hess a Ã©crit : > > > Am 24.02.2016 5:26 nachm. schrieb "stepharo" <stepharo(a)free.fr > <mailto:stepharo@free.fr>>: > > > > > >>> > >>> may be > >>> > >>> showLesson: aLesson withTitle: aString > >>> self window setLabel: aString. > >>> self sourceTextModel setText: aLesson lesson. > >>> self isOpenInWindow ifFalse: [ self open ] > >>> > >>> > >>> but I do not know :( > >>> > >>> Stef > >>> > >> > >> Maybe both, > >> beForSmalltalkCode and beForSmalltalkScripting in > >> RubScrolledTextMorph should use > >> self textArea font: StandardFonts codeFont > >> > >> At the moment, only beForSmalltalkCode sets this font. > > > > > > Yes I did the same as you, I tried to add > > > > beForSmalltalkScripting > > self textArea beForSmalltalkScripting. > > > > self textArea font: StandardFonts codeFont > > > > But without success. I'm puzzled. > > Stef > > > > And you need to reset the tutorial, it reuses the existing lesson view. >

Feb. 24, 2016

Re: [Pharo-dev] Help with PrStef with Fonts

by stepharo

can you add a bug entry I will fix the other and publish it. Le 24/2/16 17:31, Nicolai Hess a Ã©crit : > > > Am 24.02.2016 5:29 nachm. schrieb "Nicolai Hess" > <nicolaihess(a)gmail.com <mailto:nicolaihess@gmail.com>>: > > > > > > Am 24.02.2016 5:26 nachm. schrieb "stepharo" <stepharo(a)free.fr > <mailto:stepharo@free.fr>>: > > > > > > > > >>> > > >>> may be > > >>> > > >>> showLesson: aLesson withTitle: aString > > >>> self window setLabel: aString. > > >>> self sourceTextModel setText: aLesson lesson. > > >>> self isOpenInWindow ifFalse: [ self open ] > > >>> > > >>> > > >>> but I do not know :( > > >>> > > >>> Stef > > >>> > > >> > > >> Maybe both, > > >> beForSmalltalkCode and beForSmalltalkScripting in > > >> RubScrolledTextMorph should use > > >> self textArea font: StandardFonts codeFont > > >> > > >> At the moment, only beForSmalltalkCode sets this font. > > > > > > > > > Yes I did the same as you, I tried to add > > > > > > beForSmalltalkScripting > > > self textArea beForSmalltalkScripting. > > > > > > self textArea font: StandardFonts codeFont > > > > > > But without success. I'm puzzled. > > > Stef > > > > > > > And you need to reset the tutorial, it reuses the existing lesson view. > > And maybe we should use beForSmalltalkScripting in the helpbrowser as > well, because right now, you can not use "printIt" >

Feb. 24, 2016

Re: [Pharo-dev] cannot use shortcut in text pane of MC

by stepharo

excellent! Le 24/2/16 08:57, Marcus Denker a Ã©crit : > fix in since 50597 > >> On 22 Feb 2016, at 08:41, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> https://pharo.fogbugz.com/f/cases/17570/Shortcuts-to-browse-code-are-not-av… >> >> There are *lots* of fixes in the queue to be integratedâ¦ progress is slow sometimes (e.g. this was done 12 days >> ago but we have just yesterday found someone to review to the fix). >> >> Marcus >> >>> On 21 Feb 2016, at 18:52, stepharo <stepharo(a)free.fr> wrote: >>> >>> Hi guillermo >>> >>> I do not know if this is the one you fixed but in >>> Pharo5.0 >>> Latest update: #50596 >>> >>> I cannot type the name of class and browse it in a MC textpane. >>> >>> Stef >>> <Screen Shot 2016-02-21 at 18.52.01.png> > >

Feb. 24, 2016

Re: [Pharo-dev] Starting to add class comment and test on BlElements

by stepharo

Oh excellent I think that I forgot to jump into a bloc world. So this means that I can now turn some examples into tests. Le 24/2/16 10:21, Glenn CavarlÃ© a Ã©crit : > Hi Stef, > > Yes, BlElement is the starting point, i think so. > All examples in BlElement run for me, do you have some errors ? > On my side, i'm starting to write examples using layouts. > > We can talk about the performances issue later (if asserts really have an > impact on) , when the first stable version will be released. > But for now, i think using asserts is a good choice to make things clear and > to help the understanding and the documentation (same for the <return> > pragma). Yes this is my feeling too. > > Glenn. > > > > ----- > Glenn CavarlÃ© > -- > View this message in context: http://forum.world.st/Starting-to-add-class-comment-and-test-on-BlElements-… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

Feb. 24, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] 9d9b04: 50606

by stepharo

Le 24/2/16 12:13, Marcus Denker a Ã©crit : >> On 24 Feb 2016, at 11:02, GitHub <noreply(a)github.com> wrote: >> >> >> >> Log Message: >> ----------- >> 50606 >> 16893 Update STON >> https://pharo.fogbugz.com/f/cases/16893 > > this includes: > > 17651 SettingsStonWriter>>#store should use #asciiOnly: option > https://pharo.fogbugz.com/f/cases/17651 > > > Cases closed last 7 days: 125. Not bad! No quite good! > Marcus > >

Feb. 24, 2016

Re: [Pharo-dev] Why implementors are getting all the text red?

by stepharo

Tx guille Stef Le 24/2/16 12:40, Guille Polito a Ã©crit : > I put a slice in the inbox with a patch that seems to solve this. I > duplicated some methods, so it should be reviewed/enhanced. But right > not I have a meeting and I cannot continue to work on this until tomorrow. > > On 02/24/2016 12:20 PM, Marcus Denker wrote: >> It is a bug. >> >> The alternative would be to continue to have the build failing on the CI often and the check of new submissions >> 8 out of 10 timesâ¦ honestly it was not possible to continue with a broken setup like that. >> >> https://pharo.fogbugz.com/f/cases/17684/highlighting-broken-in-message-list… >> >> We need to fix this next. >> >> Marcus >> >>> On 24 Feb 2016, at 12:12, stepharo<stepharo(a)free.fr> wrote: >>> >>> hi >>> >>> May be this is a well known bug but now all the implementors are showed in red. >>> So I cannot film that. >>> >>> Stef >>> >>> <edehdbdi..png> >

Feb. 24, 2016