August 2018 - Pharo-users - lists.pharo.org

Re: [Pharo-users] [Moose-dev] feenk log
by Tudor Girba Aug. 17, 2018

Aug. 17, 2018

Hi, Bindings is an issue indeed. They are at the same level as theming and we are not at that level yet. At present time we are focused on showing the breadth of what we can achieve with the new infrastructure. We are currently using only the Bloc keybinding mechanism (equivalent to Keymapping). We did explore the use of Commander, but it was not a match for our initial work. This does not mean that itâs not a good library. Just that we are still exploring and still need to learn what we need. Our focus is on an infrastructure for actions that is as close as possible to Bloc, and to figure out which parts need to go at which level of abstraction. Cheers, Doru > On Aug 17, 2018, at 5:14 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > Hi Doru > > this is great. We are brainstorming to see if and how Commander should be tuned to offer a smoother extensibility. > Julien was developing commands for all his spec tools and guille used commander for Iceberg. > We plan to have a meeting brainstorming about commands and context when guille is back from vacation (before > ESUG). On your side what did you use for the key binding? > > I would like to able to have pluggable binding so that we can have emacs like ctrl a / ctrle â¦ > > Stef > >> On 17 Aug 2018, at 06:47, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> Hi, >> >> We again got carried away and forgot to update the world about what is up in our corner. Here is a summary: >> >> -- >> Bloc & Brick >> -- >> >> - Text editor stability has been significantly improved >> - Improved support for selection in the text editor >> - Support for typical editing keybindings (copy, cut, paste) >> - Text editor debuggability: >> https://twitter.com/feenkcom/status/1024680215379959808 >> https://twitter.com/feenkcom/status/1020768298017992704 >> - The text editor can handle emojis: >> https://twitter.com/feenkcom/status/1021872214151507968 >> >> -- >> GT >> -- >> >> - Inspector >> We now have an initial version of a working inspector with resizable panes: >> https://twitter.com/feenkcom/status/1030091849795612672 >> https://twitter.com/feenkcom/status/1030314856736538624 >> It shows a display string for the current object: >> https://twitter.com/feenkcom/status/1024564065870512129 >> It can handle errors in the definition of views gracefully: >> https://twitter.com/feenkcom/status/1009174937217720320 >> We now have multiple extensions expressed in the new Inspector: >> https://twitter.com/feenkcom/status/1024321868566814720 >> https://twitter.com/feenkcom/status/1022393383850008576 >> >> - Documenter saw multiple enhancements. >> We can now resize various previews live: >> https://twitter.com/feenkcom/status/1002851190475026432 >> https://twitter.com/feenkcom/status/1001407762285375490 >> https://twitter.com/feenkcom/status/1001152789874167808 >> It now relies on the annotation mechanism from Pillar: >> https://twitter.com/feenkcom/status/1006508725409079298 >> We can now link classes and expand their definition: >> https://twitter.com/feenkcom/status/1014609460520775681 >> https://twitter.com/feenkcom/status/1029085603948843008 >> The preview of examples can handle errors gracefully: >> https://twitter.com/feenkcom/status/1022123808524836864 >> We can run examples in place, enabling a smoother tutorial experience: >> https://twitter.com/feenkcom/status/1028390957023223809 >> We have new documentation expressed in it: >> https://twitter.com/feenkcom/status/1007008814204444672 >> >> >> >> Have fun, >> The feenk team >> >> -- >> www.feenk.com >> >> "Presenting is storytelling." >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)list.inf.unibe.ch >> https://www.list.inf.unibe.ch/listinfo/moose-dev > > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr > http://www.synectique.eu / http://www.pharo.org > 03 59 35 87 52 > Assistant: Julie Jonas > FAX 03 59 57 78 50 > TEL 03 59 35 86 16 > S. Ducasse - Inria > 40, avenue Halley, > Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza > Villeneuve d'Ascq 59650 > France > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.feenk.com "Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."

1 0

feenk log
by Tudor Girba Aug. 17, 2018

Aug. 17, 2018

Hi, We again got carried away and forgot to update the world about what is up in our corner. Here is a summary: -- Bloc & Brick -- - Text editor stability has been significantly improved - Improved support for selection in the text editor - Support for typical editing keybindings (copy, cut, paste) - Text editor debuggability: https://twitter.com/feenkcom/status/1024680215379959808 https://twitter.com/feenkcom/status/1020768298017992704 - The text editor can handle emojis: https://twitter.com/feenkcom/status/1021872214151507968 -- GT -- - Inspector We now have an initial version of a working inspector with resizable panes: https://twitter.com/feenkcom/status/1030091849795612672 https://twitter.com/feenkcom/status/1030314856736538624 It shows a display string for the current object: https://twitter.com/feenkcom/status/1024564065870512129 It can handle errors in the definition of views gracefully: https://twitter.com/feenkcom/status/1009174937217720320 We now have multiple extensions expressed in the new Inspector: https://twitter.com/feenkcom/status/1024321868566814720 https://twitter.com/feenkcom/status/1022393383850008576 - Documenter saw multiple enhancements. We can now resize various previews live: https://twitter.com/feenkcom/status/1002851190475026432 https://twitter.com/feenkcom/status/1001407762285375490 https://twitter.com/feenkcom/status/1001152789874167808 It now relies on the annotation mechanism from Pillar: https://twitter.com/feenkcom/status/1006508725409079298 We can now link classes and expand their definition: https://twitter.com/feenkcom/status/1014609460520775681 https://twitter.com/feenkcom/status/1029085603948843008 The preview of examples can handle errors gracefully: https://twitter.com/feenkcom/status/1022123808524836864 We can run examples in place, enabling a smoother tutorial experience: https://twitter.com/feenkcom/status/1028390957023223809 We have new documentation expressed in it: https://twitter.com/feenkcom/status/1007008814204444672 Have fun, The feenk team -- www.feenk.com "Presenting is storytelling."

3 2

Trait method override
by Vitor Medina Cruz Aug. 17, 2018

Aug. 17, 2018

Hello, In a class that uses a Trait, how can I override one of it's method by appending behavior to the method implemented by the Trait? In a typical override, this is done by calling super: method super method "extended behavior" ... Is there a way to change "super" to a reference the Trait? Regards, Vitor

3 6

Is the debugger known to be unstable on recent Pharo 7?
by Tim Mackinnon Aug. 17, 2018

Aug. 17, 2018

Hi, Iâm doing some travelling and had a stretch on a plane with Pharo 7 - 64bit b166, and was trying out some changes to Calypso to plug in some potential keyboard extensions. Anyway, in figuring stuff out I noticed the debugger had a number of issues - which I can try to investigate more but wanted to say something before ploughing on. When I hit a method invoked from the keyboard which has self halt (not a soft breakpoint, as I was changing code and didnât want to keep losing the breakpoint) - when I made a change and hit save I get an extra empty predebug window ? The older debug window also has a my single method but no stack and is not debuggable. The upshot is that I have to start debugging all over again? I also noticed that when I hit an error and got a debugger and then fixed the error, resumed but then hit another - the title of the window was still the old error msg and not the new one (so quite confusing). Has there been recent work done in the debugger that might explain these? Tim Sent from my iPhone

1 1

separate native window of same Pharo image
by Peter UhnÃ¡k Aug. 17, 2018

Aug. 17, 2018

Hi, did anyone play around with launching a separate native window for Pharo? E.g. I have normal window in which Pharo is, and then I open a separate native window that shows just e.g. Transcript. I know that there are some projects like OSWindow-SDL and OSWindows-UI (using WinAPI), but both of them are aimed at opening windows with non-pharo content, which is not what I want. Any pointers? Thanks, Peter

4 7

Re: [Pharo-users] Zinc loading problems (as project dep) - versions mess
by Sven Van Caekenberghe Aug. 16, 2018

Aug. 16, 2018

Yes, those .TheIntegrator versions are not real, can't explain that further. If you want to go to the very latest version, you also have to load the latest version of ConfigurationOfZincHTTPComponents first, else you get an older latest version (yes this is a bit confusing, but it makes perfect sense when you think of it). All this is normally done by the Metacello mechanism. Here is how you can do that in direct scripting: Metacello new configuration: 'ZincHTTPComponents'; repository: 'http://mc.stfx.eu/ZincHTTPComponents'; version: #stable; load: #('Core' 'WebSocket' ). (Untested though). > On 16 Aug 2018, at 19:45, Petr Fischer via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > > From: Petr Fischer <petr.fischer(a)me.com> > Subject: Re: [Pharo-users] Zinc loading problems (as project dep) - versions mess > Date: 16 August 2018 at 19:45:41 GMT+2 > To: pharo-users(a)lists.pharo.org > > > I can't understand a mess in Zinc packages versions. I downloaded fresh 6.1 (32bit) image from pharo.org, opened Monticelo Browser and searced for 'Zinc-HTTP' package. > There is version Zinc-HTTP (TheIntegrator.461). Repository info points to "http://mc.stfx.eu/ZincHTTPComponents" by default, so I opened the repository and there is no packages with "TheIntegrator". Even version numbers are different - version SvenVanCaekenberghe.461 is different if I diff it. It looks like the version TheIntegrator.461 is close to SvenVanCaekenberghe.453. > > Next test: when I run this code in fresh image: > > ConfigurationOfZincHTTPComponents project load: #stable > > there is Zinc-HTTP (SvenVanCaekenberghe.453) after load. Why not 475 (it's stable or not)? > > And now, I'm totally confused. > > pf > > >> Hi Petr, >> >> I also have >> >> project: 'ZincHTTPComponents' with: [ >> spec >> className: 'ConfigurationOfZincHTTPComponents'; >> repository: 'http://mc.stfx.eu/ZincHTTPComponents'; >> loads: #('Core' 'Tests' 'REST' 'AWS'); >> versionString: #stable ]; >> >> in my main project, which has not changed in years and always works, AFAIK. >> >> I also use(d) the load expression >> >> ConfigurationOfZincHTTPComponents project load: #stable >> >> a lot and it normally works. >> >> Metacello sometimes acts weird when you already have code/projects loaded. >> >> I am afraid I don't know what could be wrong. >> >> Sven >> >>> On 16 Aug 2018, at 17:09, Petr Fischer via Pharo-users <pharo-users(a)lists.pharo.org> wrote: >>> >>> >>> From: Petr Fischer <petr.fischer(a)me.com> >>> Subject: Zinc loading problems (as project dep) >>> Date: 16 August 2018 at 17:09:41 GMT+2 >>> To: pharo-users(a)lists.pharo.org >>> >>> >>> Hello, >>> >>> I am trying to load stable Zinc as dependency in my project, like this: >>> >>> ... >>> project: 'ZincHTTPComponents' with: [ >>> spec >>> className: #ConfigurationOfZincHTTPComponents; >>> versionString: #'stable'; >>> loads: #('Core' 'WebSocket' ); >>> repository: 'http://mc.stfx.eu/ZincHTTPComponents/' ]. >>> ... >>> >>> I need WebSocket package, whiuch is not loaded by default and updated Core package (there is new method ZnClient defaultEncoder: - I need this). >>> >>> Actual stable version of ZincHTTPComponents is 2.9.4 (for Pharo 6.x) and in this 2.9.4 stable version, there is Zinc-HTTP package with version Zinc-HTTP-SvenVanCaekenberghe.475. >>> >>> Default version in Pharo 6.1 image is Zinc-HTTP-TheIntegrator.461. >>> >>> After my project configuration load, there is no updated Zinc in my image. >>> >>> When I try to load manually by: >>> >>> ConfigurationOfZincHTTPComponents project load: #stable. >>> >>> error dialog occurs complaining about Zinc-HTTP have unsaved changes in the image (load/merge/cancel) - so, maybe, automatic load of Zinc as project depenedency is ignored due to this reason. >>> >>> How to solve this situation? Can I force dependency to load (in my project ConfigurationOf)? >>> >>> Thanks! Petr Fischer >>> >>> >>> >>> >>> >> > > >

2 1

Re: [Pharo-users] Zinc loading problems (as project dep)
by Sven Van Caekenberghe Aug. 16, 2018

Aug. 16, 2018

Hi Petr, I also have project: 'ZincHTTPComponents' with: [ spec className: 'ConfigurationOfZincHTTPComponents'; repository: 'http://mc.stfx.eu/ZincHTTPComponents'; loads: #('Core' 'Tests' 'REST' 'AWS'); versionString: #stable ]; in my main project, which has not changed in years and always works, AFAIK. I also use(d) the load expression ConfigurationOfZincHTTPComponents project load: #stable a lot and it normally works. Metacello sometimes acts weird when you already have code/projects loaded. I am afraid I don't know what could be wrong. Sven > On 16 Aug 2018, at 17:09, Petr Fischer via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > > From: Petr Fischer <petr.fischer(a)me.com> > Subject: Zinc loading problems (as project dep) > Date: 16 August 2018 at 17:09:41 GMT+2 > To: pharo-users(a)lists.pharo.org > > > Hello, > > I am trying to load stable Zinc as dependency in my project, like this: > > ... > project: 'ZincHTTPComponents' with: [ > spec > className: #ConfigurationOfZincHTTPComponents; > versionString: #'stable'; > loads: #('Core' 'WebSocket' ); > repository: 'http://mc.stfx.eu/ZincHTTPComponents/' ]. > ... > > I need WebSocket package, whiuch is not loaded by default and updated Core package (there is new method ZnClient defaultEncoder: - I need this). > > Actual stable version of ZincHTTPComponents is 2.9.4 (for Pharo 6.x) and in this 2.9.4 stable version, there is Zinc-HTTP package with version Zinc-HTTP-SvenVanCaekenberghe.475. > > Default version in Pharo 6.1 image is Zinc-HTTP-TheIntegrator.461. > > After my project configuration load, there is no updated Zinc in my image. > > When I try to load manually by: > > ConfigurationOfZincHTTPComponents project load: #stable. > > error dialog occurs complaining about Zinc-HTTP have unsaved changes in the image (load/merge/cancel) - so, maybe, automatic load of Zinc as project depenedency is ignored due to this reason. > > How to solve this situation? Can I force dependency to load (in my project ConfigurationOf)? > > Thanks! Petr Fischer > > > > >

2 1

Zinc loading problems (as project dep)
by Petr Fischer Aug. 16, 2018

Aug. 16, 2018

Hello, I am trying to load stable Zinc as dependency in my project, like this: ... project: 'ZincHTTPComponents' with: [ spec className: #ConfigurationOfZincHTTPComponents; versionString: #'stable'; loads: #('Core' 'WebSocket' ); repository: 'http://mc.stfx.eu/ZincHTTPComponents/' ]. ... I need WebSocket package, whiuch is not loaded by default and updated Core package (there is new method ZnClient defaultEncoder: - I need this). Actual stable version of ZincHTTPComponents is 2.9.4 (for Pharo 6.x) and in this 2.9.4 stable version, there is Zinc-HTTP package with version Zinc-HTTP-SvenVanCaekenberghe.475. Default version in Pharo 6.1 image is Zinc-HTTP-TheIntegrator.461. After my project configuration load, there is no updated Zinc in my image. When I try to load manually by: ConfigurationOfZincHTTPComponents project load: #stable. error dialog occurs complaining about Zinc-HTTP have unsaved changes in the image (load/merge/cancel) - so, maybe, automatic load of Zinc as project depenedency is ignored due to this reason. How to solve this situation? Can I force dependency to load (in my project ConfigurationOf)? Thanks! Petr Fischer

1 0

Dynabook and interest based learning
by Hilaire Aug. 16, 2018

Aug. 16, 2018

How can Dynabook and interest based learning can be related? http://blog.drgeo.eu/post/2018/Interest-based-learning Hilaire -- Dr. Geo http://drgeo.eu

2 1

XML Writer not pretty printing
by Peter Uhnak Aug. 16, 2018

Aug. 16, 2018

Hi, I am trying to output a pretty printed document, but it seems that the configuration is being ignored doc := '<root> <tab/> <twoSpaces/> <fourSpaces/> </root>' parseXML. String << [ :stream | doc printOn: stream beforeWritingDo: [ :writer | writer enablePrettyPrinting; enablePlatformSpecificLineBreak. writer formatter indentString: ' '. ] ] produces "'<root> <tab/> <twoSpaces/> <fourSpaces/> </root>'" I thought that maybe #preservesIgnorableWhitespace: has something to do with it, but whether it is true or false, the output is not pretty printed (not to mention, that pretty printing should ignore any preserved whitespaces anyway). Is this a bug? Should I print it in a different way? Thanks, Peter

2 2