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.frhttp://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
Hi doru
Would it be possible to have a separate mailing-list for GT?
Stef
--------------------------------------------
Stéphane Ducasse
http://stephane.ducasse.free.frhttp://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
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
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
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.frhttp://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
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
Greetings Fellow Smalltalkers,
We would like to invite you to Camp Smalltalk, March 29th – March 31st
2019 in Charlotte, North Carolina. Event details and registration
info are available at the following link: Camp Smalltalk Charlotte 2019
<https://www.eventbrite.com/e/camp-smalltalk-charlotte-2019-tickets-52380940…>
Hope to see you there!
--
Mariano
A question on normalizing edges in RTMondrian:
I want to show the "strength" of the edges, computed according to some
metric.
How can I normalize for example the color of the edge to reflect this
"strength" ?
Or maybe, normalize the "boldness" of the edge ?
nicolas
--
Nicolas Anquetil
RMod team -- Inria Lille
Hi,
Glamorous Toolkit has evolved quite a bit over the past months, and we now would like to announce that we reached alpha.2 version. It runs on top of Pharo 7:
feenk.com/gt
There quite a number of new things. Some highlights are:
- We added extensive documentation for GT, Bloc and Brick. By running "GtWorld openTour” you essentially transform the image into an elaborate wiki.
- We worked on Coder, a new set of tools that are dedicated for affecting code. For example, in the picture below we see an editor on embedded examples that can be edited and run independently.
And this one shows how we can visualize and edit the result of querying.
Just a note: To make Coder work the way we want, we extended Brick with several widgets, and enhanced significantly the linear and grid layouts.
- We added the first version of xdoc in order to serialize the Playground every time you evaluate something.
As always, we are looking forward to your feedback.
Have fun,
The feenk team
--
www.feenk.com
--
www.feenk.com
"Every thing should have the right to be different."
