- Pharo-dev - lists.pharo.org

What tools or methods we have in Smalltalk (Pharo) for Model Driven programming?
by ponyatov Aug. 26, 2018

Aug. 26, 2018

I mean MDP in a wide, in a more generic way, not the things like UML and other OMG derivatives. As an example, I defined a little set of generic classes <http://ponyatov.quora.com/Smalltalk-etudes-Model-Driven-MetaProgramming> for metaprogramming in terms of generic programming elements. My idea is about - creating domain-specific models, then - translate them into generic language-independent models, and finally - transform them into some code-synthesizable representation for the specific target programming language (which let me write in Smalltalk in any mainstream language and avoid no-vacancy lock) What tools or methods we have in Smalltalk (Pharo) for this approach? - data structure visualization - model transformation - logic-like inference over such a like models -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

1 0

Sign of Impending Iceberg Doom on Pharo 6.1
by Sean P. DeNigris Aug. 26, 2018

Aug. 26, 2018

Sometimes while working in Iceberg on 6.1, I see a progress bar(s) like the following: <http://forum.world.st/file/t128965/Screenshot_2018-08-24_12.jpeg> This seems to usually signal that a crash is not far away. It's doubly concerning because there is no clear way to stop the troubled process (interrupts often bring up a debugger on something else) and because, since one is now unable to save any code, it's unclear how to start over easily in a new image. In an extreme scenario, I recently panicked during such an experience and accidentally clicked "Save" instead of "Save Asâ¦" resulting in an image that took hours worth of code (I know maybe not a great practice) with it to the grave. Any idea why this happens or what we might be able to do anything about it? p.s. I was so concerned that I immediately resolved to move to Pharo 7, but that turned out not to be an option do to the recently reported bug with extension methods (that don't exactly match the package name) ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

6 7

[Pharo 7.0-dev] Build #1193: 22365 Introduced dynamic presenters list builder and tests.
by ci-pharo-ci-jenkins2＠inria.fr Aug. 25, 2018

Aug. 25, 2018

There is a new Pharo build available! The status of the build #1193 was: SUCCESS. The Pull Request #1718 was integrated: "22365 Introduced dynamic presenters list builder and tests." Pull request url: https://github.com/pharo-project/pharo/pull/1718 Issue Url: https://pharo.fogbugz.com/f/cases/22365 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Extension methods in p7
by Norbert Hartl Aug. 24, 2018

Aug. 24, 2018

Iâm about preparing magritte to be loadable in pharo 7. I encountered a bit strange behaviour where I had to take cumbersome measures. Magritte has method extensions that are called e.g. *Magritte-model-builder These methods get loaded but when I commit something all of these methods are to be removed. The only thing I could do was to rename the extension methods. Is this intended? Doing the renaming I encountered of few things. Magritte had the extension method above in the Magritte-Model package. When I rename the category *Magritte-model-builder to *Magritte-Model the method gets removed. Not a very usual case but still strange. In order to create a method extension one needs first to create a new protocol before converting to extension method. If the new protocol is empty and you convert it to an extension method it gets removed. So I had to first create a protocol, move a method in and then convert. This combined with the behaviour that if you select two methods the method pane jumps to the beginning of the list is a lot of work just to do this job. Still it is not a very usual case but some might be interested. Norbert

4 5

Startup Error in Recent Pharo 7
by Sean P. DeNigris Aug. 23, 2018

Aug. 23, 2018

Did something change in the last two or three days with Iceberg/Metcello/Monticello? I was loading a project successfully in a startup script via: Metacello new repository: 'filetree://', (repoFolder / 'src') fullName; baseline: 'DeNigrisPreferences'; onConflict: [ :ex | ex allow ]; load. That now fails with "IceCloneLocationAlreadyExists": IceGenericError: '~/Dynabook/Working Images/MM 23 1021/pharo-local/iceberg/seandenigris/Pharo-Preferences' exists and is not an empty directory. The crazy thing is that the directory does *not* exist! This only fails at startup. If I run manually after startup, the load succeeds. Ideas? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

1 1

[Pharo 7.0-dev] Build #1192: Implement ZnNewLineWriterStream >> #flush
by ci-pharo-ci-jenkins2＠inria.fr Aug. 22, 2018

Aug. 22, 2018

There is a new Pharo build available! The status of the build #1192 was: SUCCESS. The Pull Request #1709 was integrated: "Implement ZnNewLineWriterStream >> #flush" Pull request url: https://github.com/pharo-project/pharo/pull/1709 Issue Url: https://pharo.fogbugz.com/f/cases/22353 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1191: 22360-add-pharo-version-next-to-the-image-file
by ci-pharo-ci-jenkins2＠inria.fr Aug. 22, 2018

Aug. 22, 2018

There is a new Pharo build available! The status of the build #1191 was: SUCCESS. The Pull Request #1714 was integrated: "22360-add-pharo-version-next-to-the-image-file" Pull request url: https://github.com/pharo-project/pharo/pull/1714 Issue Url: https://pharo.fogbugz.com/f/cases/22360 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] Next Pharo Sprint: Aug 31
by Marcus Denker Aug. 22, 2018

Aug. 22, 2018

We will organize a Pharo sprint / Moose dojo Aug 31, starting at 10:00am. (Local Time Paris). Goals of this sprint: â¢ Pharo 7 issues Remote Sprint: Remotely, you can join us on Discord. During the sprint, we synchronize local and remote Pharo sprinters: http://pharo.org/contribute-events <http://pharo.org/contribute-events> Known Local Sprint meetings Lille/France: It will be at the Inria Lille, Building B, third floor (RMoD offices). As the building is not open to the public, please contact us before if you plan to come https://association.pharo.org/event-2973616 <https://association.pharo.org/event-2973616>

1 0

Reducing the cost of documentation
by Alistair Grant Aug. 21, 2018

Aug. 21, 2018

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

2 2

[Pharo 7.0-dev] Build #1190: 22352 Better tagging in ReflectionMirrors-Primitives and related tests
by ci-pharo-ci-jenkins2＠inria.fr Aug. 21, 2018

Aug. 21, 2018

There is a new Pharo build available! The status of the build #1190 was: SUCCESS. The Pull Request #1708 was integrated: "22352 Better tagging in ReflectionMirrors-Primitives and related tests" Pull request url: https://github.com/pharo-project/pharo/pull/1708 Issue Url: https://pharo.fogbugz.com/f/cases/22352 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0