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

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

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

by Nicolai Hess

Am 24.02.2016 5:29 nachm. schrieb "Nicolai Hess" <nicolaihess(a)gmail.com>: > > > Am 24.02.2016 5:26 nachm. schrieb "stepharo" <stepharo(a)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] Help with PrStef with Fonts

by Nicolai Hess

Am 24.02.2016 5:26 nachm. schrieb "stepharo" <stepharo(a)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] [Moose-dev] Call for action for Roassal

by stepharo

Anne did you publish the code you did with guillaume on reimplementing graphViz? Stef Le 24/2/16 10:28, Anne Etien a Ã©crit : > Hi Alexandre, > > In a wonderful world, I would like: > - a real graph layout (like in graphviz) that can take into account around hundred nodes and several hundred of edges and place the nodes in order to see something. Currently, I have to use the circle layout and it looks strange. > - the possibility to place hangout of the edges on nodes (as box) more flexible. Indeed, I am reverse engineering a database containing around 80 tables and lot of foreign keys and the result is not readable since the edge are orthogonal starting from the top or the bottom of the box corresponding to the column name. I would like a real entity-relation diagram. > > For the remainder, I use only Telescope since I have just to specify my data and not to script the visualization taking into account the order of the instructionsâ¦ So donât change the interface of the existing API in order we can continue to use Telescope on top on Roassal. > > If you want, I can show you the current stage of the visu (once again done in Telescope on top of Roassal) in order that you see on real data how uggly it is. > > Cheers, > Anne > >> Le 24 fÃ©vr. 2016 Ã 09:51, Alexandre Bergel <alexandre.bergel(a)me.com> a Ã©crit : >> >> Dear community, >> >> As you may have seen, Roassal has entered a stabilization phase. The book AgileVisualization.com will soon be released. After its release, Roassal will go over a new development phase. In order to prepare it, I am asking this question: >> >> What are the 3 aspects you would like to see improved in Roassal? >> >> You can answer publicly or by sending private messages. >> >> Kind regards, >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)list.inf.unibe.ch >> https://www.list.inf.unibe.ch/listinfo/moose-dev > >

Feb. 24, 2016

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

by stepharo

> > 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

Feb. 24, 2016

Re: [Pharo-dev] [Bloc] MDLColor and new gradient

by stepharo

I do not know. May be. Le 23/2/16 10:30, Denis Kudriashov a Ã©crit : > Hi > > 2016-02-23 9:13 GMT+01:00 stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>>: > > May be we should have some Palette > > And we could have (brainstorming) > > (ColorBuilder from: MDLPalette) > -> aColorBuilder > aColorBuilder red > -> .... > > > What the difference between red colors from different palettes? And > why it is not just "MDLPalette red"?

Feb. 24, 2016

Re: [Pharo-dev] [Bloc] MDLColor and new gradient

by stepharo

tx for the pointer Le 24/2/16 10:34, Glenn CavarlÃ© a Ã©crit : > Hi, > In my memories, a first implementation of material colors was also made by > Alex in Brick packages. > This can be a inspiration source, too. > > > > ----- > Glenn CavarlÃ© > -- > View this message in context: http://forum.world.st/Bloc-MDLColor-and-new-gradient-tp4879795p4880198.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

Feb. 24, 2016