Moose-dev December 2018

moose-dev@list.inf.unibe.ch

14 participants
10 discussions

Fwd: [Pharo-users] [ ANN ] Pharo Days 2016
by Tudor Girba 08 Mar '24

08 Mar '24

> Begin forwarded message: > > From: Sven Van Caekenberghe <sven(a)stfx.eu> > Subject: [Pharo-users] [ ANN ] Pharo Days 2016 > Date: December 9, 2015 at 9:52:09 AM EST > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org>, Pharo Development List <pharo-dev(a)lists.pharo.org>, Pharo Business <pharo-business(a)lists.pharo.org> > Reply-To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > > Dear fellow Pharoers, > > Mark your calendars: on Thursday March 31 & Friday April 1 we are organising the Pharo Days 2016. This year we moved the location to Namur, Belgium, just a bit south of Brussels, at the very beautiful location of the ‘Cercle de Wallonie’ overlooking the river Meuse. > > We’ll update the following page moving forward. > > https://medium.com/concerning-pharo/pharo-days-2016-c52fe4d7caf > > You can ask questions on any of the Pharo mailing lists or you can email the Pharo Board. > > Let's make this another success, together ! We hope to see as many of you as possible. > > -- www.tudorgirba.com "We are all great at making mistakes."

4 3

glamorous toolkit: v0.4.0
by Tudor Girba 01 Jan '19

01 Jan '19

Hi, Things are moving fast in the glamorous land. We now reached v0.4.0: https://gtoolkit.com There are several significant advances in this version. The first thing to note is that v0.4.0 is a reproducible version that can be loaded with: Metacello new baseline: 'GToolkit'; repository: 'github://feenkcom/gtoolkit:v0.4.0/src'; load. https://github.com/feenkcom/gtoolkit/releases/tag/v0.4.0 The version was created with Releaser the new member of GT that is able to release deeply nested projects: https://twitter.com/girba/status/1073407418460225536 The rest of the environment has seen a few key changes as well: - Documenter received support for dynamic markup edit. This is an almost magic ability that makes the markup appear when the cursor nears the markup. With this we have reached a seamless experience that supports both viewing without markup and editing on demand. https://twitter.com/feenkcom/status/1067879286143676419 - Playground uses Coder and snippets are now collapsable. https://twitter.com/feenkcom/status/1070806168459767809 - The Inspector updates when the code changes. https://twitter.com/feenkcom/status/1072581283925159936 https://twitter.com/feenkcom/status/1072107898900238337 - The Meta view from Inspector was enhanced to show the super classes and method categories, each of these act list filters. On top of that, we can also filter methods by name. https://twitter.com/feenkcom/status/1072223641583149057 A more complete list of issues we addressed is found here: https://github.com/feenkcom/gtoolkit/milestone/2?closed=1 Please do let us know what you think .. and, of course, what you feel. Have fun, The feenk team -- www.feenk.com “How do you feenk today?"

7 30

Roassal: Adjusting to fixed canvas size
by Hernán Morales Durand 30 Dec '18

30 Dec '18

Hi guys, Using Pharo 6.1/Win here. Is there any way to adjust a RTView canvas to a fixed size, say 620 x 744 px, before the elements gets added into the view? This is what I've tried so far: 1) Empty canvas manually set to 620 x 744 px produces 1x1 image: | view | view := RTView new setCanvas: (TRCanvas new extent: 620 @ 744; yourself); yourself. (RTCanvasExporter canvas: view canvas) format: #png; fileName: 'test_empty.png'; export. 2) Non-empty canvas manually set to 620 x 744 px produces 25x15 image: | view elems | view := RTView new setCanvas: (TRCanvas new extent: 620 @ 744; yourself); yourself. elems := (RTBox new color: Color blue) elementsOn: (1 to: 5). view addAll: elems. RTGridLayout on: view elements. (RTCanvasExporter canvas: view canvas) format: #png; fileName: 'test_5elems.png'; export. 3) Idem 2) adding #scale: 10 -> 250x150px ... #scale: 24.8 -> 620 px | view elems | view := RTView new setCanvas: (TRCanvas new extent: 620 @ 744; yourself); yourself. elems := (RTBox new color: Color blue) elementsOn: (1 to: 5). view addAll: elems. RTGridLayout on: view elements. (RTCanvasExporter canvas: view canvas) format: #png; scale: 12.4; fileName: 'test_5elems_scaled.png'; export. 4) Adding #oversizedBy: to 3) finally makes the trick: | view elems | view := RTView new setCanvas: (TRCanvas new extent: 620 @ 744; yourself); yourself. elems := (RTBox new color: Color blue) elementsOn: (1 to: 5). view addAll: elems. RTGridLayout on: view elements. (RTCanvasExporter canvas: view canvas) format: #png; scale: 24.8; oversizedBy: 0 @ 15; fileName: 'test_5elems_scale2_osized.png'; export. - So setting manually canvas extent doesn't have any effect? - Any way also to set a fixed margin or padding size (distance between image element and border)? Cheers, Hernán

1 0

New book: Pharo with Style
by Stéphane Ducasse 30 Dec '18

30 Dec '18

Hello Fellow Pharoers and Smalltalk lovers I'm happy to announce a new little book to improve the culture around Pharo. I will revise it in the future so you can feel free to send feedback and pull requests to https://github.com/SquareBracketAssociates/Booklet-PharoWithStyle Stef "The best way to predict the future is to invent" so I do it. :) -------------------------------------------- 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

1 0

About a separate mailing-list about GT
by Stéphane Ducasse 29 Dec '18

29 Dec '18

Hi doru Would it be possible to have a separate mailing-list for GT? 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

2 5

PetitParser release: v2.1.0
by Julien 22 Dec '18

22 Dec '18

Hello, This email to announce that a new minor release of PetitParser (1) has been published on GitHub (v2.1.0). Here is the change log: Summary ----------- - Each package has its tests separated in a separated package. - Cleaned baseline, made it more modular. - Created more groups to let people load the part of the project they want. - Some cleaning in `PetitParser` package. - Integrated PetitPreprocessor and PetitParserExtensions in the project as separated groups Changelog ----------- #31 Extract PPTextHighlighter into a separated package. #21 Add contribution guidelines #13 Update README with new groups #9 Fix CI configuration #19 A TODO comment in PPMemoizedParser>>#parseOn: might need to be fixed cleaning #11 Inconsistent method classification #15 Split tests in their own packages cleaning #22 PetitPreprocessor is missing some extensions #3 Use `>>>` notation for examples inside method #8 PPStream>>#column: has commented code that should be removed #7 PPCharSetPredicate and PPContextMemento need to be commented #1 Replace 'Oops' error message with a meaningful message #4 PPContext>>#on:stream: should be removed #2 Integrate PetitParserExtensions package from Smalltalkhub #5 Integrate PetitPreprocessor package from Smalltalkhub Thanks to Cyril Ferlicot for his help. Cheers, 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

4 5

Help: how to follow Parameters
by Erik Stel 14 Dec '18

14 Dec '18

Through a jdt2famix parsed model of an application I'm trying to follow the usage of a (FAMIX)Parameter. How can this be done? >From a method parameter I can access its enclosing method and from there on find invocations within that method for example. The problem is that there does not seem to be a direct way to retrieve the fact that a parameter is part of a method invocation (both direct or as part of an expression). It seems I have to parse a piece of the source code (the invocation signature to be precise). This does not feel okay. Can anyone give some pointers on how to find parameter usage without resorting to parsing the source code (if such a solution exists)? (Googling didn't help so far, or I'm not using the right search parameters ;-) Example Java source code, for which I want to follow the 'x' parameter: void startPoint(String x, int y) { // Here is first 'simple' parameter usage this.doSomething(x, y); // Here parameter is part of an expression this.that.doAnother("[" + x + "]"); // Parameter is part of expression again (twice) this.doLast(x.substring(0, y) + x.substring(y + 8)); } Cheers, Erik -- Sent from: http://forum.world.st/Moose-f1310756.html

3 5

[ANN] PetitParser (1) has been migrated to Github
by Julien 04 Dec '18

04 Dec '18

Hello, I just finished the migration of PetitParser (1) on Github: https://github.com/moosetechnology/PetitParser <https://github.com/moosetechnology/PetitParser> . I created a release v1.9.2 which mirrors latest release of Smalltalkhub. Cheers, 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

2 1

Users of Phexample are trapped
by Stéphane Ducasse 04 Dec '18

04 Dec '18

We should pay attention to super vicious dependencies. For example ConfigurationOfPhexample dependent on a new version of StateSpecs. baseline21: spec <version: '2.1-baseline'> spec for: #'common' do: [ spec blessing: #'baseline'. spec repository: 'http://www.smalltalkhub.com/mc/Phexample/Phexample/main'. spec baseline: 'StateSpecs' with: [ spec repository: 'github://dionisiydk/StateSpecs:v2.4.x’]. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ spec package: 'Phexample' ]. Since this baseline is referring to github, it means that old users of Phexample cannot load anymore their code. This is funny because they cannot load their code to be able to fix it to load in recent pharo version. So Alain cannot migrate his project because petitparser use Phexample. 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

3 5

Migrate PetitParser (1) on GitHub under moosetechnology organisation?
by Julien 03 Dec '18

03 Dec '18

Hello, I’d like to migrate PetitParser (1) on GitHub under moosetechnology organisation. I have a project depending on it and there are some stuff I’d like to fix on PetitParser 1 ConfigurationOf (which will become a baseline on GitHub). Is it ok to migrate it? Cheers, 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

2 3

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev December 2018