Copy
View this email in your browser

Pharo and Mastodon

Mastodon is an alternative to twitter, with a different philosophy that will fit better some people's interests: 
  • It is decentralised (there is no central instance, but a "federation" of instances)
  • each instance has different moderation rules. Its purpose is eliminate trolling and harassment. 
  • you are the owner of your content
  • users are first, mastodon is not a platform to sell you 
  • is open source and free. It you want to create your own instance with your own rules, you can.
Read about mastodon here: http://joinmastodon.org
For Pharo, we have:
  • Implementation of the API: GitHub 
  • A small application to mirror twitter accounts into mastodon: GitHub
To see the Pharo Mirror in action, have a look at:
                           https://mastodon.social/@pharoproject

GT Connector


Towards the end of last year we worked on GT Connector, a new kind of interface that allows us to exercise and test the limits (or the lack thereof) of Bloc. It looks like this:
You can see it in action here:
https://twitter.com/feenkcom/status/936109463462965248
 
In the current implementation, the Connector allows us to navigate and connect example methods. The focus is not on examples, but on the connections. We used examples because the engine was already around and offered us a nice use case. We want to extend it in the near future to other kinds of objects.

There are a couple of things that are worth noting:
  • The editor works live, and the connection points appear and disappear as you type.
  • The layout of the editor elements is based on a tree-based graph layout that only works with constrains (no actual visible edges between the editor elements).
  •  The editor works live, so adding new elements to the scene properly rearranges the scene.
  • But, perhaps, the most exciting part is the fact that the lines connect an element from inside the text editor element with another that lives outside of the editor element.
All these validate the architecture of Bloc of having exactly one rendering tree. It was not an obvious goal a couple of years ago, but we are really happy that it works.
To put it in perspective, let's compare this with the html world. Text is text is rendered through the DOM tree. If you want graphics you might use something like SVG which comes with its own tree. However, these are two distinct worlds, and you cannot go from one to another, or at least not easily. This is the case in most engines we looked at.
Why is this important? One thing we learn in the Smalltalk world is that covering the same space with less concepts opens up a whole dimension of creativity that is simply not possible outside of it.
 
The goal with Bloc is to enable new kinds of user interfaces. As we are late to the game of modern interfaces, even though the field was invented in Smalltalk, our only chance to take the lead again is to rethink the model.
 
Let's look at the Connector again. In most user interfaces we have panes on the outside, and visuals confined within the boundaries of those panes. Interestingly, we can trace this pattern to the very first Smalltalk interfaces. In the Connector interface we have no boundaries with text and visualization being intertwined to form a new kind of workflow.
 
Talking about workflows, we now have two distinct and novel ways to explore examples: one is Connector, and the other one is the expandable code editor. For example, the scene from above looks like this in the example expanding editor:
Both of these interfaces are not found in other infrastructures, and yet they were both inexpensive to implement in Bloc.

We believe this will have a deep impact for all sorts of interfaces, and especially for the IDE. If you are interested in more details related to the IDE, take a look at this paper from 2015.
 
Please let us know what you think.
 
Cheers,
The feenk team

New Releases, Libraries and Stuff

  • How to Apply for Google Summer of Code Link
  • Topics for Google Summer of Code: Link
  • New Release Pharo Launcher GitHub
  • fari.sh — fresh, ready-to-hack Pharo images GitHub
  • Woden2 for Pharo 7 (3D Engine) Link
  • Calypso Spotter tool: Link
  • Iceberg history in Calypso Link
  • Moose2Model 1.1.0 software exploration tool GitHub
  • PHANtom A modern aspect language for Pharo GitHub
  • Pharo and Bittrex API GitHub
  • Pharo TechTalk Dates Link
  • Pharo Sprints Link

Pharo Consortium News

Launch of InriaSoft, software community

The Pharo Consortium is part of the new InriaSoft. More infos here

New Member
The Pharo Consortium is very happy to announce that KnowRoaming
has joined the Consortium as a Gold Member.

About
  • KnowRoaming: https://www.knowroaming.com
  • Pharo Consortium: http://consortium.pharo.org
For more infomation, see http://consortium.pharo.org, individuals can support Pharo via joining the Pharo Association: https://association.pharo.org

Job Corner

  • Inria Permanent Research Position: Link
  • ObjectProfile  Santiago, Chile: Engineering position (with a strong research activity) in the field of artificial intelligence and software engineering. Link
  • ZWEIDENKER GmbH is looking for Pharo developers (Cologne, Germany). Contact mail@zweidenker.de for more information.
  • [PhD] From Relational to NoSQL databases. Link
  • [PhD] Infrastructure and Language Kernels for IoT Systems Link
  • Engineer 1 year: Pharo IoT platform. Link
Copyright © 2018 Pharo Association, All rights reserved.


Want to change how you receive these emails?
You can update your preferences or unsubscribe from this list.