- Pharo-dev - lists.pharo.org

[ANN] New window tiling shortcuts
by Pavel Krivanek July 4, 2018

July 4, 2018

Hello, the latest Pharo 7 includes new window tiling shortcuts that should help you to manage windows position and size without the need of using a mouse. In this description, the key â has equivalent in Ctrl on Linux and Windows. I need to notice that some nicer key combinations would be chosen if the VM support of key modifiers would be proper on all platforms but that is a different story... Windows tiling ------------------------ â+Shift+W, A - move the window to the left half of the screen. â+Shift+W, D - right half â+Shift+W, W - top half â+Shift+W, X - bottom half â+Shift+W, Q - move the window to the top left quadrant of the screen â+Shift+W E - top right quadrant â+Shift+W, Z - bottom left quadrant â+Shift+W, C - bottom right quadrant â+Shift+W, S - maximize the window â+Shift+W, Shift+S - minimize the window â+Shift+W, R - centre the window on the screen with a default extent Windows moving ------------------------ â+Shift+W, â - move the window left by half of its width â+Shift+W, â - move the window right by half of its width â+Shift+W, â - move the window up by half of its height â+Shift+W, â - move the window down by half of its height Windows resizing ------------------------ â+Shift+W, hold â+Shift and press: A, A - move left window edge left (by half of the window size) A, S - move left window edge right (by half of the window size) W, W - move top edge up W, S - move top edge down D, D - move right edge right D, S - move right edge left X, X - move bottom edge down X, S - move bottom edge up Cheers, -- Pavel

1 0

[Pharo 7.0-dev] Build #1113: 22232 the test runner should allow to do code coverage on packages having test in the their name
by ci-pharo-ci-jenkins2＠inria.fr July 4, 2018

July 4, 2018

There is a new Pharo build available! The status of the build #1113 was: SUCCESS. The Pull Request #1616 was integrated: "22232 the test runner should allow to do code coverage on packages having test in the their name" Pull request url: https://github.com/pharo-project/pharo/pull/1616 Issue Url: https://pharo.fogbugz.com/f/cases/22232 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1112: 22212 Some cleanups in GrowlMorph
by ci-pharo-ci-jenkins2＠inria.fr July 4, 2018

July 4, 2018

There is a new Pharo build available! The status of the build #1112 was: SUCCESS. The Pull Request #1601 was integrated: "22212 Some cleanups in GrowlMorph" Pull request url: https://github.com/pharo-project/pharo/pull/1601 Issue Url: https://pharo.fogbugz.com/f/cases/22212 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Commenting test classes?
by Denis Kudriashov July 4, 2018

July 4, 2018

Hi. I noticed pull requests which add comments to test cases (class comments). I guess the reason is that in Calypso uncommented classes are marked differently than in Nautilus and the exclamation does not disappear when class provides special icon like status of tests. So the question is do we really want people comment test cases? I did not notice any meaningful comment from those PRs. It's like "Unit tests for mirror primitives" for MirrorPrimitiveTests (case 22207 <https://github.com/pharo-project/pharo/pull/1598>). Personally I don't like such approach to put class name with spaces in the comment. It is useless and duplicated. Alternatively I can change uncommented mark to be like in Nautilus. But I like Calypso approach because #systemIcon is not overridden by exclamation. If we want to keep it we need to introduce some #requiresComment to Class which will be overridden by TestCase. So what you think?

5 6

[Pharo 7.0-dev] Build #1111: 22226 Cleanups in DebuggerModel
by ci-pharo-ci-jenkins2＠inria.fr July 4, 2018

July 4, 2018

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

1 0

ANN: new stable VM promoted to P7
by Esteban Lorenzano July 4, 2018

July 4, 2018

Hi all, I promoted a new stable VM for Pharo 7.0. This one corresponds to build: 201806281256-a8a1dc1 If everything goes fine, I will backport it for Pharo 6.1 in one month. (and if something goes wrong, I will rollback so please let me know any issues). cheers, Esteban

1 0

[Pharo 7.0-dev] Build #1110: 22225 Lint and formatting improvements in Compression package
by ci-pharo-ci-jenkins2＠inria.fr July 3, 2018

July 3, 2018

There is a new Pharo build available! The status of the build #1110 was: FAILURE. The Pull Request #1610 was integrated: "22225 Lint and formatting improvements in Compression package" Pull request url: https://github.com/pharo-project/pharo/pull/1610 Issue Url: https://pharo.fogbugz.com/f/cases/22225 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1109: 21671 - MemoryStore returns nil for file modificationTime (regression)
by ci-pharo-ci-jenkins2＠inria.fr July 2, 2018

July 2, 2018

There is a new Pharo build available! The status of the build #1109 was: FAILURE. The Pull Request #1584 was integrated: "21671 - MemoryStore returns nil for file modificationTime (regression)" Pull request url: https://github.com/pharo-project/pharo/pull/1584 Issue Url: https://pharo.fogbugz.com/f/cases/21671 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ann] gt documenter
by Tudor Girba July 2, 2018

July 2, 2018

Hi, We are happy to announce a new leap of GToolkit Documenter, the tool for manipulating live documents directly in the development environment: https://github.com/feenkcom/gtoolkit-documenter Documenter is part of the second generation GToolkit project, it is based on Bloc and works with the latest Pillar. It is mainly developed by Juraj Kubelka. Attached you can see a preview of how documents look like: At its core it offers a live editor for manipulating Pillar documents. The interaction happens seamlessly directly in the text editor, and it can be combined with different types of previews to serve several classes of use cases: â¢ code documentation â¢ tutorials â¢ interactive data notebook Code documentation ---- Documenter complements the GToolkit Examples engine to redefine code documentation. When practicing example-driven development, examples get written as part of the typical development. Once examples exist, they can be quickly put together in a document to form documentation. For example, the linked picture shows the comment of a class containing a visual explanation: https://twitter.com/feenkcom/status/973899862482866176 You can see a live example of documentation by inspecting the following snippet: GtDocumenter editorForText: BrToggleExamples comment. Tutorials: ---- Documenter offers a new experience of writing tutorials for Pharo by enabling the creation and embedding of Epicea change sessions directly in the document. For example, take a look at the following animation: https://twitter.com/feenkcom/status/999975333972541440 The document shows a method on top, and a change preview at the bottom showing both the code and the associated diff to the state from the image. Applying the change updates both the change view (no more diff), and method preview. This speeds up significantly the process of going through a tutorial. Furthermore, given that now the document shows the diff to the current image, the reader can safely explore alternative scenario and come back to the tutorial at any time without losing the overview. The size of the preview can also be adjusted live: https://twitter.com/feenkcom/status/1001152789874167808 https://twitter.com/feenkcom/status/1001407762285375490 You can see a live tutorial by inspecting: IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit-examples' / 'doc' / 'tutorial' / 'examples-tutorial.pillarâ. Interactive data notebook: ---- A Documenter document can also be used as an interactive notebook. Internally it essentially acts as a playground: â¢ it supports defining variables in code snippets, and â¢ the execution of code shows an embedded inspector. For example: https://twitter.com/feenkcom/status/996310432225820672 https://twitter.com/feenkcom/status/1002851190475026432 An example, can be seen by inspecting: IceRepository repositoriesLocation / 'feenkcom'/ 'gtoolkit' / 'doc' / 'gtoolkit' / 'gtoolkit.pillar'. As always, please do let us know what you think. Enjoy, The feenk team -- www.tudorgirba.com www.feenk.com "If you can't say why something is relevant, it probably isn't."

3 3

[Pharo 7.0-dev] Build #1108: Small improvement of DateAndTimeTest
by ci-pharo-ci-jenkins2＠inria.fr July 2, 2018

July 2, 2018

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

1 0