April 2016 - Pharo-users - lists.pharo.org

Re: [Pharo-users] GTPlayground/Inspector stacked vertically

by Johan Fabry

> On Apr 29, 2016, at 09:03, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > On Fri, Apr 29, 2016 at 1:49 PM, Johan Fabry <jfabry(a)dcc.uchile.cl <mailto:jfabry@dcc.uchile.cl>> wrote: > > For this specific case you may want to use the SpecEasel which is an example of the of the Roassal2Spec package. You can change the layout of the boxes there by changing the defaultSpec method at class side (but some minimal Spec knowledge is required). > > Well I certainly have enough knowledge to change a layout, but the lacking code support (mainly syntax highlighting) is a real pain (certainly worse than having a large window). > But at least I can add it to my todo and see if it can be improvedâ¦ Ah well, the SpecEasel was a quick example not meant to be used intensively, which is why there is no syntax highlighting. If you change the text widget for a Rubric one and you configure it to be for Smalltalk (there is a setting for that) you should get syntax highlighting and all other bells and whistles for free. ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile

April 29, 2016

Re: [Pharo-users] GTPlayground/Inspector stacked vertically

by Peter UhnÃ¡k

On Fri, Apr 29, 2016 at 1:49 PM, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > > For this specific case you may want to use the SpecEasel which is an > example of the of the Roassal2Spec package. You can change the layout of > the boxes there by changing the defaultSpec method at class side (but some > minimal Spec knowledge is required). > Well I certainly have enough knowledge to change a layout, but the lacking code support (mainly syntax highlighting) is a real pain (certainly worse than having a large window). But at least I can add it to my todo and see if it can be improved... Thanks, Peter

April 29, 2016

Re: [Pharo-users] GTPlayground/Inspector stacked vertically

by Johan Fabry

For this specific case you may want to use the SpecEasel which is an example of the of the Roassal2Spec package. You can change the layout of the boxes there by changing the defaultSpec method at class side (but some minimal Spec knowledge is required). > On Apr 29, 2016, at 04:48, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Hi, > > how technically complex it would be to stack the panes in the Playground on top of each other, instead of side by side? > > Right now I waste half of my screen just for one line just so I can get a reasonably sized visualization. > > <side-by-side.png> > â > Instead I would like to have something like this, even if it was limited to just two panes. > > <on-top.png> > â > > (Or the other way around, code at the bottom, visu at the top, doesn't matter.) > > Of course it would probably have to be resizable (I wouldn't want to have the same problem, just vertically. > > And yes, I can just inspect the results, but that's quite annoying as it opens yet another window which I have to close all the time. > > Peter ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile

April 29, 2016

Re: [Pharo-users] restoring a deleted method

by Siemen Baader

On Mon, Apr 25, 2016 at 4:50 PM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > This should work in Pharo 5.0 > Thanks. I'll look forward to that then :) -- Siemen

April 29, 2016

Re: [Pharo-users] VTermOutPutDriver

by Valentin Ryckewaert

Hi everyone, i'm working on it and I don't know what to do about colors... I can have methods like : - backgroundBlue & writingBlue - blueBackground & blueWriting (My choice) - blue & backgroundBlue - No methods like that and only backgroundColor: & writingColor: What do you prefer? 2016-04-27 13:08 GMT+02:00 Valentin Ryckewaert < valentin.ryckewaert(a)gmail.com>: > I found the problem, it's just that the dictionnary which make correspond > bold to the code needed didn't have the bold (and other stuffs I suppose) > I'm trying to fix this. > > 2016-04-27 12:20 GMT+02:00 phil(a)highoctane.be <phil(a)highoctane.be>: > >> Some code I have around: >> >> >> Tools class>>#inform: aString color: aSymbol >> | out | >> out := VTermOutputDriver stdout. >> >> out perform: aSymbol. >> >> DateAndTime now printHMSOn: out. >> >> out >> nextPutAll: ' : '; >> nextPutAll: aString. >> >> out lf. >> >> Usage: >> >> Tools inform: 'Blah' color: #red. >> >> FYI VTermOutputDriver and friends come from another project of Camillo >> Bruni (now gone from the list, do not ask) which contained the full support >> for termcap. >> >> I've the source somewhere and it should definitely be revived. >> >> Phil >> >> >> >> On Wed, Apr 27, 2016 at 10:41 AM, Blondeau Vincent < >> vincent.blondeau(a)worldline.com> wrote: >> > >> > Hi, >> > >> > >> > >> > Termcap methods seems not implemented and used by the output driver >> (see initialize).. Maybe you should implement them before anything ? >> > >> > >> > >> > Vincent >> > >> > >> > >> > De : Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] De la >> part de Valentin Ryckewaert >> > EnvoyÃ© : mercredi 27 avril 2016 10:35 >> > Ã : Any question about pharo is welcome >> > Objet : [Pharo-users] VTermOutPutDriver >> > >> > >> > >> > Hi everyone, >> > >> > >> > >> > i'm reading VTermOutPutDriver and I tried to use the example of the >> documentation: >> > >> > >> > >> > | out | >> > >> > out := VTermOutputDriver stdout. >> > >> > out << 'normal text'. >> > >> > out lf. >> > >> > 'red text' do: [ :c | out color256: Color red. out << c ]. >> > >> > out lf. >> > >> > 'bold text' do: [ :c | out bold. out << c ]. >> > >> > out clear. >> > >> > out lf. >> > >> > >> > >> > As I understood it >> > >> > 'bold text' do: [ :c | out bold. out << c ]. >> > >> > is the problem, the termcap 'md' looks like not existing but it exists >> : http://man7.org/linux/man-pages/man5/termcap.5.html >> > >> > >> > >> > Should I send an issue for not working method or wrong doc ? >> > >> > >> > >> !!!************************************************************************************* >> > "Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã >> l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par >> le secret professionnel. Si vous recevez ce message par erreur, merci d'en >> avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du >> message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de >> Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien >> que les meilleurs efforts soient faits pour maintenir cette transmission >> exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et >> sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant >> d'un virus transmis. >> > >> > This e-mail and the documents attached are confidential and intended >> solely for the addressee; it may also be privileged. If you receive this >> e-mail in error, please notify the sender immediately and destroy it. As >> its integrity cannot be secured on the Internet, the Worldline liability >> cannot be triggered for the message content. Although the sender endeavours >> to maintain a computer virus-free network, the sender does not warrant that >> this transmission is virus-free and will not be liable for any damages >> resulting from any virus transmitted.!!!" >> > >

April 29, 2016

GTPlayground/Inspector stacked vertically

by Peter UhnÃ¡k

Hi, how technically complex it would be to stack the panes in the Playground on top of each other, instead of side by side? Right now I waste half of my screen just for one line just so I can get a reasonably sized visualization. â Instead I would like to have something like this, even if it was limited to just two panes. â (Or the other way around, code at the bottom, visu at the top, doesn't matter.) Of course it would probably have to be resizable (I wouldn't want to have the same problem, just vertically. And yes, I can just inspect the results, but that's quite annoying as it opens yet another window which I have to close all the time. Peter

April 29, 2016

Re: [Pharo-users] Playgound inspecting

by Tudor Girba

Hi, I added bindings in a new version of GTInspector and it seems to work without setting the classOrMetaClass: https://pharo.fogbugz.com/f/cases/17948/Bindings-in-the-evaluator-pane-in-I… Could you test? Cheers, Doru > On Apr 28, 2016, at 10:05 AM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > > > 2016-04-28 9:51 GMT+02:00 Nicolai Hess <nicolaihess(a)gmail.com>: > > > 2016-04-28 7:20 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > Hi Nicolai, > > > On Apr 27, 2016, at 11:12 PM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > > > > > > 2016-04-27 23:07 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > > Le 27/04/2016 22:55, Esteban Lorenzano a Ã©crit : > > > > On 27 Apr 2016, at 22:52, Thierry Goubier <thierry.goubier(a)gmail.com > > <mailto:thierry.goubier@gmail.com>> wrote: > > > > Hi Doru, > > > > Le 27/04/2016 22:38, Tudor Girba a Ã©crit : > > Hi, > > > > On Apr 27, 2016, at 10:17 PM, Thierry Goubier > > <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com>> wrote: > > > > Le 27/04/2016 21:26, Hilaire a Ã©crit : > > Now I remember I already asked several months ago, and it does not > > work. > > > > Editing on the value does not work for me. > > > > http://forum.world.st/GL-inspector-editing-attribute-td4837704.html > > > > The same mis fortune is encountered with Pharo5 > > > > I don't imagine how it can be like that and I fell unproductive now > > with > > Playground and GTInspector, althought I acknowledge there are nice > > ideas > > in these new tools but it can't be at the price of productivity. > > > > Hopefully you can switch to Workspace and EyeInspector. > > > > With the help of Nicolai Hess, we worked a bit on improving syntax > > colouring for the EyeInspector and this has been integrated. Maybe > > someone can look into doing the same with GT (to correctly set > > #doItReceiver, #doItContext and a few other things related to syntax > > highlighting). > > > > What exactly is the problem in GT regarding syntax highlighting? > > > > If you inspect a morph (say GTInspector inspect: Morph new), when you > > type bounds (one of Morph instance variables) in the text pane below, > > you get a red == erroneous / undefined var. > > > > but thatâs not a syntax highlighting problem: is a bindings problem :P > > > > both > > > > binding, because glamours smalltalk code mode automatically creates bindings (when OCASTSemantic analyzer tries to > > lookup a variable) (see glamours workspacebinding strategy) > > > > and styling > > because for a "raw"-tab inspector pane, glamour does not set the classOrMetaClass attribute of the styler. > > I am looking at this issue right now: > https://pharo.fogbugz.com/f/cases/17948/Bindings-in-the-evaluator-pane-in-I… > > Could you explain why setting the classOrMetaClass is important in this context if we add the bindings to the instance variables? > > That depends on how you want to add bindints for instance variables. > > For evaluating expressions with instance variables, OCASTSemantic analyzer already knows how to lookup the > variable binding from the OCInstanceScope (it does not work at the moment, because inspect (the requestor) is asked first, and > it creates a binding on the fly). > > For syntax highlighting, the styler needs to know if a classOrMetaClass attribute is set, otherwise it does not create a compilation > context that can lookup up with the correct instance scope. (see SHRBTextStyler>>#privateStyle: ) > > If you omit to create bindings on the fly for instance variables, you need to set the classOrMetaClass attribute > but if you include the instance variable bindings and the GT inspector (the requestor in #lookupVar: ) is responsible for finding the correct > var, it may work without setting the classOrMetaClass attribute - I don't know for sure. > > I think I tried that one when looking at the styler workspace style issue and it didn't work. Some of the comments about styling and bindings seems out of date, and the RB based styler behaves differently. > > Thierry > > > > > > Cheers, > Doru > > > > > > > I can let you try to solve it by playing with the bindings ;) > > > > Thierry > > > > Esteban > > > > > > In the latest 5.0, in EyeInspector, it will correctly highlight bounds > > as a defined variable. > > > > Moreover, and the source of the first complaint, in GTInspector, > > inspecting bounds will give a nil answer instead of the morph bounds. > > Whereas EyeInspector will properly answer (0@0) corner: (50@40). > > > > Thierry > > > > Cheers, > > Doru > > > > > > By the way, would someone know how to force the styler to re-style a > > text? When selecting another element in for example a > > EyeTreeInspector, this changes the reference class for syntax > > highlighting (and the styler correctly picks that) but the existing > > text isn't re-colored. > > > > Thierry > > > > > > Hilaire > > > > > > Le 27/04/2016 15:51, Sean P. DeNigris a Ã©crit : > > HilaireFernandes wrote > > instance variables evaluate to nil in the bottom area of the > > integrated > > inspector. > > There is no direct inst var access from the playground. I was > > initially > > shocked by this as well and have had to resort to #instVarNamed: > > on several > > occasions. On the bright side, you can edit the values in place in the > > 'Value' column above. > > > > > > > > > > -- > > www.tudorgirba.com <http://www.tudorgirba.com> > > www.feenk.com > > > > "Value is always contextual." > > -- > www.tudorgirba.com > www.feenk.com > > "Problem solving efficiency grows with the abstractness level of problem understanding." -- www.tudorgirba.com www.feenk.com "When people care, great things can happen."

April 28, 2016

Re: [Pharo-users] Moose-Algos-Graph Library in Pharo 5

by Tudor Girba

Metacello new configuration: 'MooseAlgos'; smalltalkhubUser: 'Moose' project: 'MooseAlgos'; version: #development; load: 'Moose-Tests-Algos-Graphâ > On Apr 28, 2016, at 10:21 AM, Christophe Demarey <christophe.demarey(a)inria.fr> wrote: > > Metacello new > configuration: 'MooseAlgos'; > smalltalkhubUser: 'Moose' project: 'MooseAlgos'; > version: #bleedingEdge; > load: 'Moose-Tests-Algos-Graph' > >> Le 25 avr. 2016 Ã 18:52, Volkert <volkert(a)komponentenwerkstatt.de> a Ã©crit : >> >> Christophe, Alexandre, i will give it a try .... How can i load "Moose-Tests-Algos-Graph" into Pharo 5.0? >> >> Thanks, Volkert >> >> On 25.04.2016 10:23, Christophe Demarey wrote: >>> Hi, >>> >>> Moose-Algos-Graph contains very classical algorithmes applying on graphes (Breadth-first search, dijkstra, tarjan, topological sorting, etc). >>> It is now in Pharo 5 because it is used by the dependency analyser. >>> As Alexandre said, there are almost no documentation and it is not so easy to combine algorithms (run an algo on the output of another algo). >>> You can look at Moose-Tests-Algos-Graph package (to be loaded) and DADependencyChecker>>#shortestPathToPackageIntroducingDependency:startingFrom: for some examples. >>> >>> Christophe >>> >>> >>>> Le 24 avr. 2016 Ã 20:55, Alexandre Bergel <alexandre.bergel(a)me.com> a Ã©crit : >>>> >>>> Hi Volkert! >>>> >>>> This package contains some classical graph algorithms we use in software analysis (e.g., clustering, strong component). >>>> Unfortunately, there is no much documentation about it. If you are using these algorithms, then it would be great to write some documentation. >>>> >>>> In addition to this package, and as you know, Roassal offers many layout algorithms. >>>> >>>> Regarding, >>>> Alexandre >>>> >>>>> On Apr 24, 2016, at 6:39 AM, Volkert <volkert(a)komponentenwerkstatt.de> wrote: >>>>> >>>>> Dear all, >>>>> >>>>> if have found the "Moose-Algos-Graph" package in Pharo 5. What is the idea behind this package? Is this "the" official Pharo Graph Library? >>>>> Do we have some examples how to use it? >>>>> >>>>> LG, >>>>> Volkert >>>>> >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel http://www.bergel.eu >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>> >>>> >>>> >>>> >>> >> >> > > -- www.tudorgirba.com www.feenk.com "Not knowing how to do something is not an argument for how it cannot be done."

April 28, 2016

Re: [Pharo-users] Moose-Algos-Graph Library in Pharo 5

by Christophe Demarey

Metacello new configuration: 'MooseAlgos'; smalltalkhubUser: 'Moose' project: 'MooseAlgos'; version: #bleedingEdge; load: 'Moose-Tests-Algos-Graph' > Le 25 avr. 2016 Ã 18:52, Volkert <volkert(a)komponentenwerkstatt.de> a Ã©crit : > > Christophe, Alexandre, i will give it a try .... How can i load "Moose-Tests-Algos-Graph" into Pharo 5.0? > > Thanks, Volkert > > On 25.04.2016 10:23, Christophe Demarey wrote: >> Hi, >> >> Moose-Algos-Graph contains very classical algorithmes applying on graphes (Breadth-first search, dijkstra, tarjan, topological sorting, etc). >> It is now in Pharo 5 because it is used by the dependency analyser. >> As Alexandre said, there are almost no documentation and it is not so easy to combine algorithms (run an algo on the output of another algo). >> You can look at Moose-Tests-Algos-Graph package (to be loaded) and DADependencyChecker>>#shortestPathToPackageIntroducingDependency:startingFrom: for some examples. >> >> Christophe >> >> >>> Le 24 avr. 2016 Ã 20:55, Alexandre Bergel <alexandre.bergel(a)me.com> a Ã©crit : >>> >>> Hi Volkert! >>> >>> This package contains some classical graph algorithms we use in software analysis (e.g., clustering, strong component). >>> Unfortunately, there is no much documentation about it. If you are using these algorithms, then it would be great to write some documentation. >>> >>> In addition to this package, and as you know, Roassal offers many layout algorithms. >>> >>> Regarding, >>> Alexandre >>> >>>> On Apr 24, 2016, at 6:39 AM, Volkert <volkert(a)komponentenwerkstatt.de> wrote: >>>> >>>> Dear all, >>>> >>>> if have found the "Moose-Algos-Graph" package in Pharo 5. What is the idea behind this package? Is this "the" official Pharo Graph Library? >>>> Do we have some examples how to use it? >>>> >>>> LG, >>>> Volkert >>>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >> > >

April 28, 2016

Re: [Pharo-users] Playgound inspecting

by Thierry Goubier

2016-04-28 9:51 GMT+02:00 Nicolai Hess <nicolaihess(a)gmail.com>: > > > 2016-04-28 7:20 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > >> Hi Nicolai, >> >> > On Apr 27, 2016, at 11:12 PM, Nicolai Hess <nicolaihess(a)gmail.com> >> wrote: >> > >> > >> > >> > 2016-04-27 23:07 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com>: >> > Le 27/04/2016 22:55, Esteban Lorenzano a Ã©crit : >> > >> > On 27 Apr 2016, at 22:52, Thierry Goubier <thierry.goubier(a)gmail.com >> > <mailto:thierry.goubier@gmail.com>> wrote: >> > >> > Hi Doru, >> > >> > Le 27/04/2016 22:38, Tudor Girba a Ã©crit : >> > Hi, >> > >> > On Apr 27, 2016, at 10:17 PM, Thierry Goubier >> > <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com>> wrote: >> > >> > Le 27/04/2016 21:26, Hilaire a Ã©crit : >> > Now I remember I already asked several months ago, and it does not >> > work. >> > >> > Editing on the value does not work for me. >> > >> > http://forum.world.st/GL-inspector-editing-attribute-td4837704.html >> > >> > The same mis fortune is encountered with Pharo5 >> > >> > I don't imagine how it can be like that and I fell unproductive now >> > with >> > Playground and GTInspector, althought I acknowledge there are nice >> > ideas >> > in these new tools but it can't be at the price of productivity. >> > >> > Hopefully you can switch to Workspace and EyeInspector. >> > >> > With the help of Nicolai Hess, we worked a bit on improving syntax >> > colouring for the EyeInspector and this has been integrated. Maybe >> > someone can look into doing the same with GT (to correctly set >> > #doItReceiver, #doItContext and a few other things related to syntax >> > highlighting). >> > >> > What exactly is the problem in GT regarding syntax highlighting? >> > >> > If you inspect a morph (say GTInspector inspect: Morph new), when you >> > type bounds (one of Morph instance variables) in the text pane below, >> > you get a red == erroneous / undefined var. >> > >> > but thatâs not a syntax highlighting problem: is a bindings problem :P >> > >> > both >> > >> > binding, because glamours smalltalk code mode automatically creates >> bindings (when OCASTSemantic analyzer tries to >> > lookup a variable) (see glamours workspacebinding strategy) >> > >> > and styling >> > because for a "raw"-tab inspector pane, glamour does not set the >> classOrMetaClass attribute of the styler. >> >> I am looking at this issue right now: >> >> https://pharo.fogbugz.com/f/cases/17948/Bindings-in-the-evaluator-pane-in-I… >> >> Could you explain why setting the classOrMetaClass is important in this >> context if we add the bindings to the instance variables? >> > > That depends on how you want to add bindints for instance variables. > > For evaluating expressions with instance variables, OCASTSemantic analyzer > already knows how to lookup the > variable binding from the OCInstanceScope (it does not work at the moment, > because inspect (the requestor) is asked first, and > it creates a binding on the fly). > > For syntax highlighting, the styler needs to know if a classOrMetaClass > attribute is set, otherwise it does not create a compilation > context that can lookup up with the correct instance scope. (see > SHRBTextStyler>>#privateStyle: ) > > If you omit to create bindings on the fly for instance variables, you need > to set the classOrMetaClass attribute > but if you include the instance variable bindings and the GT inspector > (the requestor in #lookupVar: ) is responsible for finding the correct > var, it may work without setting the classOrMetaClass attribute - I don't > know for sure. > I think I tried that one when looking at the styler workspace style issue and it didn't work. Some of the comments about styling and bindings seems out of date, and the RB based styler behaves differently. Thierry > > > > >> >> Cheers, >> Doru >> >> >> >> > >> > I can let you try to solve it by playing with the bindings ;) >> > >> > Thierry >> > >> > Esteban >> > >> > >> > In the latest 5.0, in EyeInspector, it will correctly highlight bounds >> > as a defined variable. >> > >> > Moreover, and the source of the first complaint, in GTInspector, >> > inspecting bounds will give a nil answer instead of the morph bounds. >> > Whereas EyeInspector will properly answer (0@0) corner: (50@40). >> > >> > Thierry >> > >> > Cheers, >> > Doru >> > >> > >> > By the way, would someone know how to force the styler to re-style a >> > text? When selecting another element in for example a >> > EyeTreeInspector, this changes the reference class for syntax >> > highlighting (and the styler correctly picks that) but the existing >> > text isn't re-colored. >> > >> > Thierry >> > >> > >> > Hilaire >> > >> > >> > Le 27/04/2016 15:51, Sean P. DeNigris a Ã©crit : >> > HilaireFernandes wrote >> > instance variables evaluate to nil in the bottom area of the >> > integrated >> > inspector. >> > There is no direct inst var access from the playground. I was >> > initially >> > shocked by this as well and have had to resort to #instVarNamed: >> > on several >> > occasions. On the bright side, you can edit the values in place in the >> > 'Value' column above. >> > >> > >> > >> > >> > -- >> > www.tudorgirba.com <http://www.tudorgirba.com> >> > www.feenk.com >> > >> > "Value is always contextual." >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "Problem solving efficiency grows with the abstractness level of problem >> understanding." >> >> >> >> >> >> >

April 28, 2016