Workflow engine open sourced by netstyle

Hi everyone,

Stef has asked me whether Netstyle would release our workflow engine to the public, so here goes:

Workflow (originally called “Aare”) was conceived as part of an application that Netstyle developed back in the day. We can’t release all of that code but we can release the engine. I’ve published it on Github with an MIT license (loadable via baseline): https://github.com/Netstyle/Workflow.

Please note:

– Workflow used to depend on OmniBase for storing objects (one of the main superclasses inherited from an OmniBase class for that). I’ve removed that dependency.

– As this only includes the engine, there’s no UI and the things shown in the whitepaper (see repository) are technically correct but are missing the appropriate model (the UI was written with Magritte and Morphic).

– The code is from 2005 and we haven’t touched it since then, so there might be a couple of hiccups.

– We can’t provide full support for the code but I’ll be happy to talk to anyone interested in maintaining or improving it.

We at Netstyle hope that Workflow may be useful to some of you.

Cheers,

Max

About Pharo Newsletter

As you for sure know, we have now a good monthly rhythm with the newsletter.

http://us11.campaign-archive1.com/home/?u=6f667565c2569234585a7be77&id=048680a940

And the number of subscribers is growing!

If you have ideas for the next newsletters (August is done and will be posted soon, but we need

content for September and later…)

We need both small and larger items. Example for smaller news:

– announcements of new libraries

– new releasese

– links to videos

– links to blog posts

And larger items. These have not just the title and link, but a short description and if possible a picture.

(If you look at the older newsletters it should be clear what is needed).

Another idea I had: we could even have “complete takeover’ of a newsletter by someone who wants to

edit a newsletter for one specific topic. This can be about one project, or just a “theme”  (e.g.

“cloud deployment with Pharo”)

if you are interested —> send a mail to board@pharo.org

Marcus Denker

Profiling blog posts

part 1: http://sophiekaleba.blogspot.fr/2017/08/understanding-basics-behind-profiling.html
part 2: http://sophiekaleba.blogspot.fr/2017/08/understanding-basics-behind-profiling_17.html
part 3: http://sophiekaleba.blogspot.fr/2017/08/understanding-basics-behind-profiling_18.html

Latest Debian, Ubuntu and CentOS packages of the pharo-vm

Hi,

when running Pharo in production you might want to install the image and a VM from distribution packages. So far there were no current public packages and during the last months I have modernized the debian packaging and recently added CentOS rpm packaging as well. The process of generating new source packages is integrated into the pharo-vm travis-ci build as well.

Every time that master of pharo-vm.git is updated a new source package will be uploaded to the Open(SUSE) Build Service and new packages will be built and are available in a “latest” package feed. The generated (and used) sourcecode is inside the source package and will be archived by the OBS platform (one can even nicely diff versions). The “stable” VM is not built from pharo-vm.git (yet?) so it doesn’t show on OBS yet.

Below are some semi-tested installation notes in case you want to try it out. The binary names are picked to allow to install the 32bit and 64bit VM in parallel. The names currently are:

– pharo6-32             (32bit version)
– pharo6-64             (64bit version)
– pharo6-32-ui          (32bit version with X11 dependencies)
– pharo6-64-ui          (64bit version with X11 dependencies)

CentOS 6.8:

# Add the repo
$ yum-config-manager –add-repo http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/CentOS_6/devel:languages:pharo:latest.repo

# Install 32bit packages (with X11 dependency for *-ui or not)

$ yum install pharo6-32-ui.i686 or pharo6-32.i386

# Install 64bit packages

$ yum install pharo6-64-ui.x86_64 pharo6-64.x86_64

CentOS 7 (only 64bit):

$ yum-config-manager –add-repo http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/CentOS_7/devel:languages:pharo:latest.repo
$ yum install pharo6-64-ui.x86_64 pharo6-64.x86_64

Debian 8:

# Add signing key
$ wget -O – http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/Debian_8.0/Release.key | apt-key add –

# Update and install
$ apt update
$ apt install pharo6-32-ui pharo6-64-ui    (or pharo6-32 or pharo6-64)

Ubuntu 14.04 LTS

# Add signing key
$ wget -O – http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/xUbuntu_14.04/Release.key| apt-key add –

# Update and install
$ apt update
$ apt install pharo6-32-ui pharo6-64-ui

Ubuntu 16.04

# Add signing key
$ wget -O – http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/xUbuntu_16.04/Release.key| apt-key add –

# Update and install
$ apt update
$ apt install pharo6-32-ui pharo6-64-ui

 

 

For the .deb based distributions the adding of the repo is missing. This would be for

Ubuntu 16.04

echo “deb http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/xUbuntu_16.04/ ./” > /etc/apt/sources.list.d/pharo.list

Ubuntu 14.04

echo “deb http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/xUbuntu_14.04/ ./” > /etc/apt/sources.list.d/pharo.list

Debian 8

Ubuntu 16.04

echo “deb http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/Debian_8.0/ ./” > /etc/apt/sources.list.d/pharo.list

As nobody noticed I’m not sure if this is really needed 😉

Feedback is highly appreciated!

Tealight: Building superfast a web server

https://github.com/astares/Tealight

the page includes the full documentation and after reading it you should be able to see:

– that you can even start the server quickly from the world menu after loading
– how easy it is to tinker and experiment with dynamic routes and Teapot in an interactive way
– how easy it is to provide a REST interface by having methods annotated with REST specific pragmas
– to even provide a versioned REST interface (also defined using pragmas)

The document should easily explain all this, esepcially read “Defining a REST based interface”.

This project is around since last october now (see http://forum.world.st/ANN-Tealight-td4918431.html)

Lately I even added the possibility to remove one or all the dynamic routes in a teapot inspector. That makes it even easier to experiment lively with a teapot instance
and different URLs one wants to catch.

Have fun

Between 6.0 and 6.1

Hello,

I think there is a bit  of a confusion of how we do fixed for Pharo6.

I will explain:

-> if people find bugs, they end up on the issue tracker
-> Some of these get fixed. If a fix is ready, we will integrate it very
quickly. This means that only the update number changes, not the
main version number (these are bug fixes, they do not change APIs).

A good name for these updates is “hot fixes”.
They are announced to the dev list only with the automatic lists that are send
for each update.

We integrated already quite some into Pharo6 like that. The release was I think
around #60500, while 6.1 was done around #60510

Then there are cases that are more grave: 6.1 was done because it contains bigger
changes.

What I think would have been good is to list all the updates that where done between
releasing 6.0 and 6.1 *as part of the changelog* of 6.1 (even though they were already
in the image that you got a minute before Pharo6.1 was released, as they where released as
hot fixes before).

Now if the image includes all fixes needed for DrGeo depends on a) has that issue been
fixed and b) if yes was all massaging done to have the update actually integrated.

Marcus

The changelog of things done between releasing 6.0 and the release of 6.1:

20262 Update Iceberg to 0.5.4
https://pharo.fogbugz.com/f/cases/20262

20268 update iceberg v0.5.5
https://pharo.fogbugz.com/f/cases/20268

20226 TabMorph should use stepping mechanism for animating background building
https://pharo.fogbugz.com/f/cases/20226

20238 Run out of memory the image hangs without out of memory warning
https://pharo.fogbugz.com/f/cases/20238

20218 Master branch (Pharo 6) needs to be safely merged into development branch (Pharo 7).
https://pharo.fogbugz.com/f/cases/20218

20187 Request use of block in certain methods
https://pharo.fogbugz.com/f/cases/20187

20188 Request representation of integer literal without float exponent
https://pharo.fogbugz.com/f/cases/20188

20182 Extra dot in literal array
https://pharo.fogbugz.com/f/cases/20182

18760 Failing test: WeakAnnouncerTest>>#testNoDeadWeakSubscriptions
https://pharo.fogbugz.com/f/cases/18760

20186 Request removal of extra statement separators (dot)
https://pharo.fogbugz.com/f/cases/20186

20185 Request pipe after block argments
https://pharo.fogbugz.com/f/cases/20185

20183 TraitDescription>>fileOutLocalMethodsInCategory:on: method temp var name overlap
https://pharo.fogbugz.com/f/cases/20183

20184 Request space between argument and selector in StdioStream>>next:
https://pharo.fogbugz.com/f/cases/20184

20167 Regression with PNGReaderWriter in P6
https://pharo.fogbugz.com/f/cases/20167

20198 inner structure access does not work on multiple architecture
https://pharo.fogbugz.com/f/cases/20198

20110 AllocationTest>>#testOutOfMemorySignal not well suited to 64-bit
https://pharo.fogbugz.com/f/cases/20110

20096 Add script pragma to SpaceTally>>printSpaceAnalysis
https://pharo.fogbugz.com/f/cases/20096

20174 In the debug halo of a morph: clicking on “inspect morph” and “explore morph” bring up the same window.
https://pharo.fogbugz.com/f/cases/20174

20093 Missing source stamp makes changes hard to view
https://pharo.fogbugz.com/f/cases/20093

20148 transforming deprecations should take #showWarning into account
https://pharo.fogbugz.com/f/cases/20148

20146 ZnHTTPSTests>>#testGetPharoVersion started to fail
https://pharo.fogbugz.com/f/cases/20146

 

 

Data Activism with Pharo :)

Hi :-),

A little announcement, that can be interesting for several communities
and practices to bridge them and make them more visible (so, that’s why
the cross posting).

At mid September I’m going to give a little workshop at a local
university for undergrad journalism and communication sciences students
using the Pharo live coding environment [1] and Roassal agile
visualization engine [2] combined with Grafoscopio[3]. We’re going to
retake our Twitter Data Selfies project[4], as is usual with our
recurrent Data Week[5] hackathon+workshop.

[1] http://pharo.org/
[2] http://agilevisualization.com/
[3] http://mutabit.com/grafoscopio/index.en.html
[4] http://mutabit.com/offray/blog/en/entry/ds-twitter-mockup
[5] http://mutabit.com/dataweek/

Also as usual, we will make real time memories, via etherpads, and more
elaborated thematic ones via interactive notebooks that we will be
sharing with you in (Fossil) source repositories and other “pocket
infrastructures”, under a permissive and solidary copy(far)left license.
I’ll give you more details as we advance.

Cheers,

Offray

Pharo 70 is starting to roll for real :)

[Pharo 70 ] build 40 – PR 133 FileReference-EnsureCreateFile

• https://pharo.fogbugz.com/f/cases/18084/FileReference-EnsureCreateFile
• https://github.com/pharo-project/pharo/pull/133

[Pharo 70 ] build 39 – PR 210 20165/Support-segment-path-printing

• https://pharo.fogbugz.com/f/cases/20165/Support-segment-path-printing
• https://github.com/pharo-project/pharo/pull/210

[Pharo 70 ] build 38 – PR 199 FileReference-size-needs-a-comment

• https://pharo.fogbugz.com/f/cases/20269/FileReference-size-needs-a-comment
• https://github.com/pharo-project/pharo/pull/199

[Pharo 70 ] build 37 – PR 206 File names should not be canonicalised by default

• https://pharo.fogbugz.com/f/cases/20307/File-names-should-not-be-canonicalised-by-default
• https://github.com/pharo-project/pharo/pull/206

[Pharo 70 ] build 36 – PR 204 Improve-comment-of-SmallDictionary

• https://pharo.fogbugz.com/f/cases/20091/Improve-comment-of-SmallDictionary
• https://github.com/pharo-project/pharo/pull/204

[Pharo 70 ] build 35 – PR 172 Implement-WeakIdentityValueDictionary

• https://github.com/pharo-project/pharo/pull/172
• https://pharo.fogbugz.com/f/cases/20105/Implement-WeakIdentityValueDictionary

[ Pharo 70 ] build 32  – PR 73

• https://github.com/pharo-project/pharo/pull/73
• https://pharo.fogbugz.com/f/cases/18650/VTermOutputDriver

[ Pharo 70 ] build 30  – PR 69

• https://github.com/pharo-project/pharo/pull/69
• https://pharo.fogbugz.com/f/cases/19802/Make-sure-Symbol-concatenation-results-in-a-Symbol-not-a-String/

[ Pharo 70 ] Build 29 – PR 191 20302 world menu help should have a comment

• https://github.com/pharo-project/pharo/pull/191
• https://pharo.fogbugz.com/f/cases/20302/

[Pharo 70] Build 28 / PR 194

• https://github.com/pharo-project/pharo/pull/194
• https://pharo.fogbugz.com/f/cases/20305/

[Pharo 70] Build 26 / PR 192

• https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/26/
• https://github.com/pharo-project/pharo/pull/192
• https://pharo.fogbugz.com/f/cases/13217/FS-basename-with-compound-path-string

[Pharo 70] Build 27 / PR 103

• https://github.com/pharo-project/pharo/pull/192
• https://pharo.fogbugz.com/f/cases/20009/Recompilation-of-trait-methods-creates-changes-record-in-the-users

“codeAndMusic choses Pharo” testimony

http://www.codeandmusic.com/why-i-chose-pharo-smalltalk-to-build-my-bot/

 

Tx for the testimony Sergio!

Pharo: a soup of stones with great developers.

I always loved the soup of stones. To me it captures a key aspect of the philosophy behind Pharo. Sharing to empowering us all. And it is working!

https://en.wikipedia.org/wiki/Stone_Soup

Stef