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

[Pharo 7.0-dev] Build #451: 21059-Make-icon-list-searchable

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

There is a new Pharo build available! The status of the build #451 was: SUCCESS. The Pull Request #730 was integrated: "21059-Make-icon-list-searchable" Pull request url: https://github.com/pharo-project/pharo/pull/730 Issue Url: https://pharo.fogbugz.com/f/cases/21059 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 25, 2018

Re: [Pharo-dev] [Ann] Calypso in progress: Spotter menu and settings

by Tudor Girba

Excellent work! Doru > On Jan 25, 2018, at 1:25 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > Hi, > > I just released new version of Calypso 0.8.11 which includes several fixes and new features. > > The most exiting feature is Spotter menu from Esteban https://youtu.be/RgqiSRFUAIk: > > "Spotter navigation" brings an easy way to access all available panels, tabs and commands in selected browser. > Activation is usually cmd+/ (because is close to the arrows) > > Settings browser includes group for Calypso: > > - trait method visibility (enabled by default) > - hierarchy order for variables (variable mode in full browser) > - hierarchy order of method visibility classes (when expand first item in method groups pane) > - shortcut for spotter menu. It is temporal solution until Commander will provide settings for all shortcuts in system. > > And few other improvements: > - better status bar tool to change protocol and package > - shortcut to change ineditor method protocol: $e meta , $t meta (editor + tag) > - shortcut to change ineditor method package: $e meta, $p meta (editor + package) > - inherited method group is replaced by all methods group with name "instance side" or "class side" depending on browser mode. It should make browser meta level more noticeable. > > Best regards, > Denis -- www.tudorgirba.com www.feenk.com "Things happen when they happen, not when you talk about them happening."

Jan. 25, 2018

[Ann] Calypso in progress: Spotter menu and settings

by Denis Kudriashov

Hi, I just released new version of Calypso 0.8.11 which includes several fixes and new features. The most exiting feature is Spotter menu from Esteban https://youtu.be/RgqiSRFUAIk: "Spotter navigation" brings an easy way to access all available panels, > tabs and commands in selected browser. > Activation is usually cmd+/ (because is close to the arrows) Settings browser includes group for Calypso: - trait method visibility (enabled by default) - hierarchy order for variables (variable mode in full browser) - hierarchy order of method visibility classes (when expand first item in method groups pane) - shortcut for spotter menu. It is temporal solution until Commander will provide settings for all shortcuts in system. And few other improvements: - better status bar tool to change protocol and package - shortcut to change ineditor method protocol: $e meta , $t meta (editor + tag) - shortcut to change ineditor method package: $e meta, $p meta (editor + package) - inherited method group is replaced by all methods group with name "instance side" or "class side" depending on browser mode. It should make browser meta level more noticeable. Best regards, Denis

Jan. 25, 2018

[Pharo 7.0-dev] Build #450: 21034 ep monitor classreset should not create a new instance if current is already empty

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

There is a new Pharo build available! The status of the build #450 was: SUCCESS. The Pull Request #698 was integrated: "21034 ep monitor classreset should not create a new instance if current is already empty" Pull request url: https://github.com/pharo-project/pharo/pull/698 Issue Url: https://pharo.fogbugz.com/f/cases/21034 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 25, 2018

[Pharo 7.0-dev] Build #449: 21065 Super setUp need to be called in HiNodesAndLinksIteratorWithOneLinkModelTest

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

There is a new Pharo build available! The status of the build #449 was: SUCCESS. The Pull Request #712 was integrated: "21065 Super setUp need to be called in HiNodesAndLinksIteratorWithOneLinkModelTest" Pull request url: https://github.com/pharo-project/pharo/pull/712 Issue Url: https://pharo.fogbugz.com/f/cases/21065 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 25, 2018

[Pharo 7.0-dev] Build #448: 21106 Super tearDown need to be called as last message in tearDown of PharoTutorial tests

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

There is a new Pharo build available! The status of the build #448 was: SUCCESS. The Pull Request #725 was integrated: "21106 Super tearDown need to be called as last message in tearDown of PharoTutorial tests" Pull request url: https://github.com/pharo-project/pharo/pull/725 Issue Url: https://pharo.fogbugz.com/f/cases/21106 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 25, 2018

[ANN] Pharo Consortium New Gold Member: KnowRoaming

by Marcus Denker

The Pharo Consortium is very happy to announce that KnowRoaming has joined the Consortium as a Gold Member. About - KnowRoaming: https://www.knowroaming.com - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: - http://association.pharo.org

Jan. 25, 2018

[Pharo 7.0-dev] Build #447: 21101 Super tearDown need to be called as last message in tearDown of OpalCompiler tests

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

There is a new Pharo build available! The status of the build #447 was: SUCCESS. The Pull Request #729 was integrated: "21101 Super tearDown need to be called as last message in tearDown of OpalCompiler tests" Pull request url: https://github.com/pharo-project/pharo/pull/729 Issue Url: https://pharo.fogbugz.com/f/cases/21101 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 25, 2018

Re: [Pharo-dev] [Pharo 7.0-dev] Build #445: 20903-isTranslucentColor-should-be-removed-as-flagged

by Marcus Denker

> On 24 Jan 2018, at 17:46, ci-pharo-ci-jenkins2(a)inria.fr wrote: > > There is a new Pharo build available! > > The status of the build #445 was: SUCCESS. > > The Pull Request #701 was integrated: "20903-isTranslucentColor-should-be-removed-as-flagged" > Pull request url: https://github.com/pharo-project/pharo/pull/701 In the end we did not remove it but added a deprecation-rewriter to transform isTranslucentColor to isTranslucent. Marcus

Jan. 25, 2018

Re: [Pharo-dev] Moving from mc to tonel?

by Peter UhnÃ¡k

Hi Martin, there are some pull requests regarding encoding, I finally have a bit more time so I'll look into that in the coming days. Peter On Thu, Jan 25, 2018 at 3:57 AM, Martin Dias <tinchodias(a)gmail.com> wrote: > Hi, any news or experiences on the migration tools? I'd try again on next > days. > MartÃn > > On Sat, Dec 16, 2017 at 5:06 AM, Stephane Ducasse <stepharo.self(a)gmail.com > > wrote: > >> It would be great to be able to sanitize the files. >> We should get a test about tonel misbehavior. >> >> Stef >> >> On Thu, Dec 14, 2017 at 3:11 PM, Henrik Sperre Johansen >> <henrik.s.johansen(a)veloxit.no> wrote: >> > Stephan Eggermont-3 wrote >> >> On 05-12-17 08:59, Peter UhnÃ¡k wrote: >> >>> > In my case, it turned out to be a non-UTF8 encoded character in one >> >>> of the commit messages. >> >>> >> >>> I've ran into this problem in a sister project (tonel-migration), and >> do >> >>> not have a proper resolution yet. I was forcing everything to be >> >>> unicode, so I need a better way to read and write encoded strings. :< >> >> >> >> To be exact, exactly none of the older commits will be UTF8 encoded. >> For >> >> most it doesn't matter as they are ASCII, but if we want to have a >> >> change of converting older french or german code (or japanese), we need >> >> support for what was done with WideString. That probably needs a look >> in >> >> the squeak mailing list archives. >> >> >> >> Stephan >> > >> > The mcz reader used to import the .bin file (which contained correctly >> > serialized WideStrings), only falling back to reading the .st file if >> .bin >> > was not present, has this changed? >> > >> > Or do these tools explicitly ignore the .bin file and try to read the >> .st >> > file directly? >> > If so, the MCDataStream class used to read .bin format still seems to >> be in >> > the image... >> > >> > One could also create a tool to check/convert all mcz in a repo as a >> > preprocess; >> > if .bin contents decode as WideString, >> > check that .st starts with utf8 BOM, >> > if not, convert. >> > >> > Cheers, >> > Henry >> > >> > >> > >> > -- >> > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.ht >> ml >> > >> >> >

Jan. 25, 2018