[book] new version of Pharo with Style

Just a little announce to mention that there is a new version of Pharo with Style.

https://github.com/SquareBracketAssociates/Booklet-PharoWithStyle/releases

S.

Advertisements

[GSoC] Student Introductions

Google Summer of Code 2019 has officially started with its community bonding period. Pharo Consortium has accepted 7 students from 4 different countries to participate in this year’s GSoC.

Every week our students will publish blog posts to announce and document their progress. In this first week, we asked students to introduce themselves, tell us a little about their background and the projects they will be working on.

These are the blog posts where our students introduce themselves to the community. Feel free to contact them personally with questions, feedback, or just words of encouragement.

  1. Atharva Khare, GSoC 2019: Extending DataFrame library for Pharo Consortium
  2. Nikhil Pinnaparaju, My Journey Into Google Summer of Code — 2019
  3. Dayne Lorena Guerra Calle, GSoC 2019 introducing my project: Next Generation of Unit Testing
  4. Evelyn Cusi Lopez, Better and more refactorings for Pharo — Part 1
  5. Myroslava Romaniuk, Improving Code Completion @ GSoC 2019: introduction
  6. Nina Medic, GSoC Project
  7. Smiljana Knezev, New Collections for Pharo
Tagged , , ,

[Ann] TF-IDF in Pharo

A little library to learn super basic technique for document processing.

https://github.com/olekscode/TF-IDF

Stef

[Ann] Pharo VM generated from Pharo

Hi all,

Just to keep everyone informed, last week I’ve spent a couple of days making slang work on Pharo again, based on the initial effort of Eliot.
The summary of what I did is:
 – we can generate, compile and run a stack vm
 – we can generate, compile and run a cog vm
 – for this, I’ve done a couple of patches to VMMaker
  – the ones specific to Pharo has been pushed
  – the ones that touch cross dialect code are still in review (I think)
To do this work
 – I had to review the AST-to-AST transformation, checking the output, comparing it to what squeak does and so on…
 – I’ve written several unit tests to ensure that future migrations are easier to do
 – I’ve introduced several compatibility classes/methods related to PackageInfo, Time and so on…
Cheers,
Guille

[Ann] Two nice books for the forthcoming mooc!

To support the start of the new season of the Pharo Mooc (https://www.fun-mooc.fr/courses/course-v1:inria+41010+self_paced/about) on May 6th, we are happy to announce a new version of the book: TinyBlog: a First web App in Pharo in English and French.

 

http://books.pharo.org/tinyblog-tutorial/ and http://books.pharo.org/tinyblog-tutoriel/

Stéphane, Luc and Olivier. http://mooc.pharo.org

Best paper award in the “Industrial Robot” category @ ICARSC 2019

IMTDouai Team (L. Fabresse/N. Bouraqadi) just won the Best paper award in the “Industrial Robot” category @ ICARSC 2019 () with our paper titled “PolySLAM: A 2D Polygon-based SLAM Algorithm” implemented in Pharo @johannDichtl @glozenguez

Well done!

Agile Artificial Intelligence

Dear All, I have a good and bad news
the good news is that the book Agile Artificial Intelligence will be published by Apress, a major publisher in computer science. This will bring visibility to Pharo at a large scale
👍🏻

3
The bad news is that the website https://agileartificialintelligence.github.io/ will be shut off soon
Agile Artificial Intelligence
Source of the book Agile Artificial Intelligence
However, the source code given in the book will have its own GitHub repository and will remain free of access

[Pre-ann] Spec 2.0 Gtk3 bindings

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: 
    1. Because there is still an important place for desktop applications market and most medium-size to big business still require them.
    2. 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: 
  1. Old GT tools will be replaced by new Spec tools (while preserving its power).
  2. Calypso UI needs to be rewritten in Spec 2.0 (it is in plain Morphic now).
  3. 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 🙂
Pharo 80 will not need Gtk3. We will provide packages for Gtk3 for the people that need it. We will also release Spec20 soon so that people can try Spec 20 – independently of Gtk3
Pharo Consortium mainly Esteban, Pablo and Guille

[ann] Workflow engine in Pharo

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