February 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Pharo-users] help needed for testing the order in spotter

by Tudor Girba

Hi, > On Feb 24, 2016, at 11:24 AM, Damien Cassou <damien.cassou(a)inria.fr> wrote: > > Tudor Girba <tudor(a)tudorgirba.com> writes: > >> Hi, >> >> We need a bit of help with testing the order in Spotter. We do not have a real solution yet, but the current one should improve the situation. >> >> We need a bit of feedback for this one: >> https://pharo.fogbugz.com/f/cases/17656/Spotter-should-sort-search-results >> >> Essentially, you would need to load the latest GT-Spotter and GT-SpotterExtensions-Core and let us know if it works better for spotting implementors or classes. > > I have the impression this is already in the image. It seems to be > working fine. Next time, it might help if you could just give us a Pharo > expression that loads the patch. Indeed, it is now in the image. Unfortunately, there was no feedback :(. I will do it better next time. I just thought that given the urgency with which issues were reported, people would have been more eager to test, so I hurried up :). Cheers, Doru > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." --Winston Churchill -- www.tudorgirba.com www.feenk.com "Quality cannot be an afterthought."

Feb. 24, 2016

Re: [Pharo-dev] GTSpotter displayed shortcut glitch

by Tudor Girba

Hi, > On Feb 24, 2016, at 6:00 PM, stepharo <stepharo(a)free.fr> wrote: > > 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. We used the same logic of displaying the keybindings as it is used in the menu. There if you have Shift, it appears explicitly. For example, for references, we have Shif+Cmd+N. I also think that we should have the letters in smallcaps, but at least now it is uniform. We can decide to change it everywhere, and I would be fine with that. Cheers, Doru > Stef > -- www.tudorgirba.com www.feenk.com "Every thing has its own flow."

Feb. 24, 2016

search query?

by stepharo

Hi in the debugger we get a search and I wonder what it is. I type true, each and nothing happens (well I do not get the methods list). I think that the ghost text is misleading since we should/can only type selectors.

Feb. 24, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] 4ade51: 50609

by stepharo

thanks this one is also important :) Le 24/2/16 18:02, GitHub a Ã©crit : > 50609 > 17687 fix: changing class comments does not work > https://pharo.fogbugz.com/f/cases/17687

Feb. 24, 2016

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