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

[Pharo 7.0-dev] Build #1179: 22338 Tag Kernel Manifests

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1179 was: SUCCESS. The Pull Request #1697 was integrated: "22338 Tag Kernel Manifests" Pull request url: https://github.com/pharo-project/pharo/pull/1697 Issue Url: https://pharo.fogbugz.com/f/cases/22338 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 20, 2018

[Pharo 7.0-dev] Build #1178: 22345 Tag Manifests in IssueTracking and IssueTracking-Tests

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1178 was: SUCCESS. The Pull Request #1703 was integrated: "22345 Tag Manifests in IssueTracking and IssueTracking-Tests" Pull request url: https://github.com/pharo-project/pharo/pull/1703 Issue Url: https://pharo.fogbugz.com/f/cases/22345 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 20, 2018

Re: [Pharo-dev] A new rule to implement in Pharo ?

by lionelakue

Thanks Marcus, Guille. I look at it. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Aug. 20, 2018

[Pharo 7.0-dev] Build #1177: 22339 Cleanup canZapMethodDictionary

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1177 was: FAILURE. The Pull Request #1698 was integrated: "22339 Cleanup canZapMethodDictionary" Pull request url: https://github.com/pharo-project/pharo/pull/1698 Issue Url: https://pharo.fogbugz.com/f/cases/22339 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 20, 2018

Re: [Pharo-dev] Reducing the cost of documentation

by Torsten Bergmann

Hi Alistair, I don't think the contribution process hold people back from writing documentation since providing a contribution is easy to do now (see [1] and [2]). And (even when more cumbersome) I like the review process - as it helped several times in the past to discuss contributions or even fixing them or find trivial typos. I guess the primary problem is lazyness: people dont like to write documentation as it is always additional effort. Remember that often people do not even write a simple comment on a class to inform about the purpose it was created... I personally doubt that we increase the number and quality of the provided in-image docu with the proposal. Bye T. [1] https://github.com/pharo-project/pharo/blob/development/CONTRIBUTING.md [2] https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo > Gesendet: Montag, 20. August 2018 um 08:37 Uhr > Von: "Alistair Grant" <akgrant0710(a)gmail.com> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Betreff: [Pharo-dev] Reducing the cost of documentation > > Hi Everyone, > > The topic of documentation recently came up again on the squeak list and > it made me wonder about some of the blocks that currently prevent more > contributions to in-image documentation. > > One of the things holding back the in-image documentation is that the > cost of contributing is too high: apart from actually making the change > we currently have to (maybe) open an issue, create a branch, commit and > open a PR. Someone with commit privileges then has to review the PR > enough and decide to merge it. We then need to manually delete the > branch some time later. > > This is one of the reasons that wikis have been successful, they lower > the cost of making changes. > > We could extend iceberg to automatically submit PRs for documentation > only commits (it could be a separate option, so that the doco only > requirement is enforced), and set up github to auto-accept the PR. > Modifying in-image documentation would then become a few extra clicks, > significantly lowering the cost. > > I'm not familiar with Jenkins, or any other CI system, but hunting > around google it looks like it may be possible to directly implement > this, if not there are services such as https://mergify.io/ which > advertise being able to do this by using flags in the CI to determine > whether the PR should be merged (disclaimer, I've never looked at > mergify.io, just found it while thinking about this). > > Thoughts? > > > Cheers, > Alistair > >

Aug. 20, 2018

Reducing the cost of documentation

by Alistair Grant

Hi Everyone, The topic of documentation recently came up again on the squeak list and it made me wonder about some of the blocks that currently prevent more contributions to in-image documentation. One of the things holding back the in-image documentation is that the cost of contributing is too high: apart from actually making the change we currently have to (maybe) open an issue, create a branch, commit and open a PR. Someone with commit privileges then has to review the PR enough and decide to merge it. We then need to manually delete the branch some time later. This is one of the reasons that wikis have been successful, they lower the cost of making changes. We could extend iceberg to automatically submit PRs for documentation only commits (it could be a separate option, so that the doco only requirement is enforced), and set up github to auto-accept the PR. Modifying in-image documentation would then become a few extra clicks, significantly lowering the cost. I'm not familiar with Jenkins, or any other CI system, but hunting around google it looks like it may be possible to directly implement this, if not there are services such as https://mergify.io/ which advertise being able to do this by using flags in the CI to determine whether the PR should be merged (disclaimer, I've never looked at mergify.io, just found it while thinking about this). Thoughts? Cheers, Alistair

Aug. 20, 2018

Uncomitted changes in latest image

by Torsten Bergmann

There are uncomitted changes in the latest Pharo image (Pharo-7.0+alpha.build.1176.sha.eedde11d2331266218204b1bb5c77a9037b7a706 (64 Bit)) for some packages. Got the image out of sync with the sources?

Aug. 19, 2018

Re: [Pharo-dev] PharoLauncher : Image version determination error

by Sean P. DeNigris

Julien wrote > Is there something wrong with the latest Pharo 7.0 32bits image? > I got this error from Pharo Launcher: This happened to me because Launcher did not create the `pharo.version` file. I copied one from another Pharo 7 image and it then worked. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Aug. 19, 2018

Re: [Pharo-dev] [Moose-dev] feenk log

by Tudor Girba

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

Aug. 17, 2018

Re: [Pharo-dev] [Moose-dev] feenk log

by StÃ©phane Ducasse

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

Aug. 17, 2018

Re: [Pharo-dev] [Moose-dev] feenk log

by Ben Coman

On Fri, 17 Aug 2018 at 12:48, 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: Thanks for the update. Nice to see the progress. > > -- > 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 Nice demos. If possible, it would be interesting to see movement or a selection in the first video, dynamically updating a treeview in a second-Inspector-pane. cheers -ben

Aug. 17, 2018

Re: [Pharo-dev] Collection groupedBy: and groups order

by Petr Fischer

I created test case for desired behaviour: Gofer it url: 'https://dev.cvokhaus.cz/st-public/'; package: 'CollectionGroupedByOrderTest'; load. pf > Despite the interleavement, the order of the grouped elements as they > occurred in the original collection could be preserved. > > On Wed, Aug 15, 2018 at 6:34 AM, Damien Pollet <damien.pollet(a)gmail.com> wrote: > > The problem is, there isn't really an order to preserve in the first place, > > since even if the original collection is a sequencable one, the elements of > > each group would be interleaved in it. I could see the point of sorting the > > keys though. > > > > On Tue, 14 Aug 2018 at 18:32, Petr Fischer via Pharo-dev > > <pharo-dev(a)lists.pharo.org> wrote: > >> > >> Hello, I found a useful method in the collection - groupedBy: - the result > >> container is some PlugableDictionary (integer variant) and group order > >> (keys) is not preserved. > >> > >> Would not it be better to choose some other Dictionary variant, which > >> preserve the order of groups (like in source Collection)? > >> > >> pf > >> > > > > > > -- > > Damien Pollet > > type less, do more [ | ] http://people.untyped.org/damien.pollet >

Aug. 17, 2018

[Pharo 7.0-dev] Build #1176: 22335-Add-Spec-Demo

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1176 was: SUCCESS. The Pull Request #1693 was integrated: "22335-Add-Spec-Demo" Pull request url: https://github.com/pharo-project/pharo/pull/1693 Issue Url: https://pharo.fogbugz.com/f/cases/22335 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 17, 2018

Re: [Pharo-dev] [update 6.1] #60542

by Marcus Denker

> On 17 Aug 2018, at 14:25, Tim Mackinnon <tim(a)testit.works> wrote: > > Hi Marcus - does this mean that a fresh zero conf of 6.1 will have the variable undeclared change? If so - then I should remove my port of your fix into what I load into exercism. Yes! > > This does raise an interesting question - is there a way to get a fixed 6.1 version (like a tag) - so that I donât always have to retest if stuff gets ported? (e.g. have a known tagged version that will work until I retest with later back ports?) > There is the update number. This is 60542. You can treat that like a minor version number 542 of Pharo6. Marcus

Aug. 17, 2018

Re: [Pharo-dev] [update 6.1] #60542

by Tim Mackinnon

Hi Marcus - does this mean that a fresh zero conf of 6.1 will have the variable undeclared change? If so - then I should remove my port of your fix into what I load into exercism. This does raise an interesting question - is there a way to get a fixed 6.1 version (like a tag) - so that I donât always have to retest if stuff gets ported? (e.g. have a known tagged version that will work until I retest with later back ports?) Tim > On 17 Aug 2018, at 07:55, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > 60542 > ----- > > 22305 Backport to Pharo6: "Leave Variable Undeclared" > https://pharo.fogbugz.com/f/cases/22305 <https://pharo.fogbugz.com/f/cases/22305> > <https://pharo.fogbugz.com/f/cases/22305> > 22298 Backport of the fix of Infinite Debugger > https://pharo.fogbugz.com/f/cases/22298 <https://pharo.fogbugz.com/f/cases/22298> >

Aug. 17, 2018

[Pharo 7.0-dev] Build #1175: 22204 new value holder package should be split into new value holder core and new value holder tests packages

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1175 was: SUCCESS. The Pull Request #1596 was integrated: "22204 new value holder package should be split into new value holder core and new value holder tests packages" Pull request url: https://github.com/pharo-project/pharo/pull/1596 Issue Url: https://pharo.fogbugz.com/f/cases/22204 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 17, 2018

[update 6.1] #60542

by Marcus Denker

60542 ----- 22305 Backport to Pharo6: "Leave Variable Undeclared" https://pharo.fogbugz.com/f/cases/22305 <https://pharo.fogbugz.com/f/cases/22305> <https://pharo.fogbugz.com/f/cases/22305> 22298 Backport of the fix of Infinite Debugger https://pharo.fogbugz.com/f/cases/22298 <https://pharo.fogbugz.com/f/cases/22298>

Aug. 17, 2018

PharoLauncher : Image version determination error

by Julien

Hello, Is there something wrong with the latest Pharo 7.0 32bits image? I got this error from Pharo Launcher: Cannot determine image version: image version file not found! Try to run this command in a shell to get more information on the problem: cd "/Users/julien/Documents/Pharo/vms/private/6521/Pharo.app/Contents/MacOS" && "/Users/julien/Documents/Pharo/vms/private/6521/Pharo.app/Contents/MacOS/Pharo" --headless "/Users/julien/Documents/Pharo/images/RTFExperiment-Iceberg/RTFExperiment-Iceberg.image" eval "(Smalltalk imagePath asFileReference parent) / 'pharo.version' writeStreamDo: [ :stream | |major minor| major := SystemVersion current major. minor := SystemVersion current minor. (major = 6 and: [ SystemVersion current highestUpdate >= 60509 ]) ifTrue: [ minor := 1 ]. stream << major asString; << minor asString ]" When trying to start it. If I run this script in the terminal, nothing is print but the process crashes returning 1 as exit code. Can someone relate this issue as well? Julien --- Julien Delplanque Doctorant Ã lâUniversitÃ© de Lille http://juliendelplanque.be/phd.html Equipe Rmod, Inria BÃ¢timent B 40, Avenue Halley 59650 Villeneuve d'Ascq NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40

Aug. 17, 2018

Re: [Pharo-dev] A new rule to implement in Pharo ?

by Guillermo Polito

We had another idea yesterday with Julien. Add a rule to check that in a test `self skip` is only present in the first statement of a test case. On Fri, Aug 17, 2018 at 9:38 AM Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > > On 13 Aug 2018, at 14:59, Lionel Akue <lionelakue(a)gmail.com> wrote: > > > > Hello, > > > > Do you have a rule you would like to get implement in Pharo? > > > > I am reading about Renraku and I would like to exercise. > > > > Thanks, > > > > Lionel > > Some ideas: > > - Test Class not in Package with name -Tests > - add rule: non-exisitng selector send in a method that has itself no > senders means that the whole method most likely is dead code > > Improvements: > > - SharedPool subclasses should not trigger âexcessive number of varsâ QA > rule (as their duty is to define variables) > > > Marcus > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Aug. 17, 2018

Re: [Pharo-dev] [Pharo-users] feenk log

by Marcus Denker

Thanks, recorded for the newsletter: http://newsletter.pharo.org (the one after the next which is going out today, I think). > 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." > >

Aug. 17, 2018

Re: [Pharo-dev] A new rule to implement in Pharo ?

by Marcus Denker

> On 13 Aug 2018, at 14:59, Lionel Akue <lionelakue(a)gmail.com> wrote: > > Hello, > > Do you have a rule you would like to get implement in Pharo? > > I am reading about Renraku and I would like to exercise. > > Thanks, > > Lionel Some ideas: - Test Class not in Package with name -Tests - add rule: non-exisitng selector send in a method that has itself no senders means that the whole method most likely is dead code Improvements: - SharedPool subclasses should not trigger âexcessive number of varsâ QA rule (as their duty is to define variables) Marcus

Aug. 17, 2018

feenk log

by Tudor Girba

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

Aug. 17, 2018

Re: [Pharo-dev] Collection groupedBy: and groups order

by Chris Muller

Despite the interleavement, the order of the grouped elements as they occurred in the original collection could be preserved. On Wed, Aug 15, 2018 at 6:34 AM, Damien Pollet <damien.pollet(a)gmail.com> wrote: > The problem is, there isn't really an order to preserve in the first place, > since even if the original collection is a sequencable one, the elements of > each group would be interleaved in it. I could see the point of sorting the > keys though. > > On Tue, 14 Aug 2018 at 18:32, Petr Fischer via Pharo-dev > <pharo-dev(a)lists.pharo.org> wrote: >> >> Hello, I found a useful method in the collection - groupedBy: - the result >> container is some PlugableDictionary (integer variant) and group order >> (keys) is not preserved. >> >> Would not it be better to choose some other Dictionary variant, which >> preserve the order of groups (like in source Collection)? >> >> pf >> > > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet

Aug. 16, 2018

Re: [Pharo-dev] Collection groupedBy: and groups order

by Petr Fischer

I created two tests, here: Gofer it url: 'https://dev.cvokhaus.cz/st-public/'; package: 'CollectionGroupedByOrderTest'; load. What do you think? pf > Hi Petr > > do you have a test illustrating what behavior you think should be good? > > Stef > -------------------------------------------- > 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 >

Aug. 16, 2018

Re: [Pharo-dev] Collection groupedBy: and groups order

by StÃ©phane Ducasse

Hi Petr do you have a test illustrating what behavior you think should be good? Stef -------------------------------------------- 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

Aug. 16, 2018