- Pharo-users - lists.pharo.org

[ANN] (Re)Introducing Mars (Spec 2.0 Gtk3 bindings)
by Esteban Lorenzano April 24, 2019

April 24, 2019

People that assisted to Pharo Days 2019 (or that follow my twitter account) already know this, but it needs to be formally announced: We are working on Spec 2.0, and it will provide not just the classic Morphic bindings but also a new option for developers: Gtk3 bindings! Why we want a Spec 2.0 with different backends? There are reasons that converged to decide us to make it: First, to provide a validated abstract Spec 2.0 that can be used with different backends, preparing Pharo to be able to switch backends without needing to recreate the full IDE from scratch each time (a problem we have partially now in our way to deprecate Morphic). Second, because we receive from different sources the requirement of having the possibility of developing real native-looking desktop applications. Yes, in moment where people talk about the cloud, SaaS and web-applications as the "next big thing" (something that is been declared since years, by the way), we believe is important to provide this, for two big reasons: Because there is still an important place for desktop applications market and most medium-size to big business still require them. Because Pharo itself is a desktop application! (And we need to provide the best experience possible on it). For us, this is a fundamental step to continue improving Pharo itself, and it matches also the work we are doing on going real-headless: Pharo users will be able to start the Morphic world, a Gtk application or the next backend to come. Why Gtk3? There are some other important players in the "native widgets scene", so why we choose Gtk3? Again, several reasons were taken into account: Gtk3 is cross platform. Yes, technically is just "native" in linux, but it works on Windows and macOS too. It is very mature and popular. It is made in plain C. Next step: tool migration The only way to know if you have covered what is needed is actually taking real-life use cases and implementing them. We have a list of tools that needs to be migrated and we are starting from them: Old GT tools will be replaced by new Spec tools (while preserving its power). Calypso UI needs to be rewritten in Spec 2.0 (it is in plain Morphic now). Pharo launcher as a standalone application is a good example of what you can do with the Gtk3 bindings. And that's it. Pharo 8.0 will come with Spec 2.0 and users will be able to benefit of it immediately :) A small screenshot of the new Inspector (WIP): Esteban

8 17

Pharo 7.0.3 dialog information at startup
by Trussardi Dario Romano April 24, 2019

April 24, 2019

Ciao, i download the last Pharo 70 image ( on Ubuntu 16.04 LTS system ) with the commannd: wget -O- https://get.pharo.org/64/70+vm | bash When i launch the relative ./pharo-ui after the opening the Pharo window the Pharo system open an information with: Information Cannot read stored value of #pharoSystem#delaySchedulerClass. Exception: KeyNotFound: key #DelaySpinScheduler not found in SystemDictionary Should i consider it as an important problem or can i proceed ignoring it? Thanks, Dario

2 1

OneClick image
by N. Bouraqadi April 24, 2019

April 24, 2019

Hi, Few years ago, there was a zip file called 'oneclick' that included everything to run Pharo on all 3 major OSes. All one had to do is unzip it, and launch a script that opens the image. What happen to that? Any idea why it isn't generated anymore? Noury

4 3

Gettext
by Pavel Krivanek April 23, 2019

April 23, 2019

Hi, I made some little tweaks on the Gettext project and I wrote few lines of documentation about it: https://github.com/pharo-contributions/Gettext Feel free to contribute if it may be interesting for your applications. Notice that I am not the original author of this project, I'm just passing by ;-) Cheers, -- Pavel

2 1

Revisiting the inheritance of tests in 2019....
by Tim Mackinnon April 23, 2019

April 23, 2019

I just got burned by tests not inheriting from a TestCase superclassâ¦ I note that in 2017, Cyril tried to argue to get this changed to work just like normal objects (proposing that for P7 tests works like any other objectâ¦) but I think it was just too difficult to argue against a decision made so long ago. I tried to follow the 2017 logic about why you would want tests to operate differently than other objects, but I couldnât understand it. I did see that some numbers run against Squeak Trunk argued that it was fine â¦. but Iâm left wondering about all the people with individual projects like me that just expect objects to behave like objects and not have unexpected behaviour. Deviating seems like extra complexity that Iâd prefer not to have to worry about. Given Pharo is revisiting the concept of testing (with Dr Test) - could we possibly introduce the normal object behaviour somehow? Possibly we could have a new superclass for Tests - and use it to move forward without breaking existing stuff and those who want to stick with this other way of thinking? Tim

2 3

A4BP and BpmFlow
by BrunoBB April 22, 2019

April 22, 2019

Serge, I just created another thread to talk about both projects (we can discuss all here as Norbert request): A4BP https://github.com/A4BP BpmFlow https://github.com/brunobuzzi/BpmFlow Regards, Bruno -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

5 10

[ANN| Moved ImageWorker to smalltalkhub
by Norbert Hartl April 22, 2019

April 22, 2019

I migrated the source of ImageWorker from smalltalkhub to github https://github.com/pharo-contributions/ImageWorker <https://github.com/pharo-contributions/ImageWorker> Now Iâm changing voyage to use the github ImageWorker. FYI, Norbert

2 1

NewWave - WorkflowEngine
by Sebastijan Kaplar April 22, 2019

April 22, 2019

Hello everyone, we've been working on a workflow engine written in Pharo. You can check it out at: https://github.com/skaplar/NewWave It is still in the early development and we discussed about making it public so everyone interested can join, take a look or provide any kind of feedback. I'm also at discord so you can contact me @skaplar. Best regards, Sebastijan Kaplar

5 5

Why are package tags not proper sub-packages?
by Tim Mackinnon April 22, 2019

April 22, 2019

Does anyone remember why we decided to consider package tags (as in: Kernel-BasicObjects) not fully fledged sub-packages? The implication here is that extension methods canât live on the tag (they live on the parent package - in the above case Kernel - and not Kernel-BasicObjects), and equally the code critic works on the package level and not on an individual tag. Equally, refactoring can work at the package level â¦ the list goes on. Having decided that it seemed to make it more understandable that Exercism exercises would simply be tags of the package exercism (its tidy to have the exercises neatly organised under a common parent with some generic menu options), I am finding that the above are starting to bite me. Extensions, Code critic (and sometimes refactoring) are awkward or more difficult to explain, and I was left wondering what the rational was to not make the tags fully fledged sub projects? Iâm now wondering if I should bite the bullet and migrate every exercise tag to being a fully formed project (although in most cases it seems overkill for a class and a test). But Iâm interested in the history of this one as maybe it can guide me? Tim

3 6

Small Pharo developer contract
by ducasse April 20, 2019

April 20, 2019

Hi guys This may interest some of you. Stef

1 0