- Pharo-users - lists.pharo.org

Re: [Pharo-users] [Demo] Creating Bloc Widgets in Pharo

by Sven Van Caekenberghe

This is nice. Shows off some impressive capabilities. Not sure many people are capable of coming up this kind of code though ;-) > On 16 Sep 2018, at 21:08, stephan <stephan(a)stack.nl> wrote: > > Bloc has improved a lot in the past year. It is ready for your experiments. Here is one of mine: > > https://github.com/StephanEggermont/Presentations > > Bloc supports the creation of beautiful GUIs, > with nice interactions. This one shows a number > of different ways of using drag-and-drop. > > https://github.com/StephanEggermont/Presentations > > A video demonstrating it is at: > > https://vimeo.com/290163891 > > <PharoScreenshot.png>

Sept. 25, 2018

Re: [Pharo-users] [Pharo-dev] [ANN] Pharo Consortium upgrade to Platinum: ZWEIDENKER

by Ben Coman

On Tue, 25 Sep 2018 at 20:03, Marcus Denker <marcus.denker(a)inria.fr> wrote: > The Pharo Consortium is very happy to announce that ZWEIDENKER has ugraded > to be a Platinum member. > Its great to see your support and commitment to Pharo - in addition to the many direct code contributions. cheers -ben

Sept. 25, 2018

Re: [Pharo-users] [Pharo-dev] [ANN] Success story Mobility Map

by Norbert Hartl

> Am 25.09.2018 um 12:52 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > Wow. Very nice, well done. > > Any chance on some more technical details, as in what 'connected by a message queue for the communication' exactly means ? How did you approach micro services exactly ? > Sure :) The installation spawns multiple physical machines. All the machines are joined to a docker swarm. The installation is reified as either task or service from the view on the docker swarm. Meaning you instantiate an arbitrary amount of services and docker swarm distributes them among the physical machines. Usually you donât take control which is running where but you can. At this point you have spread dozens of pharo images among multiple machines and each of them has an IP address. Furthermore in docker swarm you have a reification of a network meaning that every instance in a network can see all other instances on this network. Each service can be reached by its service name in that network. Docker swarm does all the iptables/firewall and DNS setup for you. In order to have communication between those runtimes we use rabbitmq because you were so nice writing a driver for it ;) The rabbitmq does have a support for cluster setup, meaning each of the physical machines has a rabbitmq installation and they know each other. So it does not matter to which instance you send messages to and on which you register for receiving messages. So every pharo image connects to the service rabbitmq and opens a queue for interaction. Each service like the car sharing opens a queue e.g. /queue/carSharing and listens on it. The broker images are stateful so they open queues like /queue/mobility-map-afdeg32 where afdeg32 is the container id of the instance (hostname in docker). In each request the queue name to reply is sent as a header. So we can make sure that the right image gets the message back. This way we can have sticky sessions keeping volatile data in memory for the lifecycle of a session. There is one worker image which opens a queue /queue/mobility-map where session independent requests can be processed. In order to ease development we are sharing code between the broker and the micro service. Each micro service has a -Common package where the classes are in that build the interface. The classes in here are a kind of data entity facades. They use NeoJSON to map to and from a stream. The class name is send with the message as a header so the remote side knows what to materialize. The handling is unified for the four cases - Request as inquiry to another micro service - Response returns values to a Request - Error is transferred like a Response but is then signalled on the receiving side - Notification connects the announcers on the broker and the micro service side. Asynchronous calls we solved using Promises and Futures. Each async call to the Q becomes a promise (that blocks on #value) and is combined to a future value containing all promises with support to generate a delta of all resolved promises. This we need because you issue a search that takes longer and you want to display results as soon as they are resolved not after all haven been resolved. And a lot more. This is a coarse grained overview over the architecture. Iâm happy to answer further questions about this. Norbert >> On 25 Sep 2018, at 12:20, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> As presented on ESUG here is the brief description of one of our current projects. >> >> Mobility Map >> ââââââ >> >> Mobility Map is a broker for mobility services. It offers multi-modal routing search enabling users to find the best travel options between locations. Travel options include car sharing, bikes, trains, busses etc. Rented cars can be offered for ride sharing on booking time letting other people find it to participate in the ride. Single travel options are combined in travel plans that can be booked and managed in a very easy way. >> >> For this project main requirements were scalability to serve a large user base and flexibility to add more additional providers to the broker. The application has been realized using web technologies for the frontend and pharo for the backend. Using a microservice architecture combined with a broker it is easy to extend the platform with additional brokers. Deployment is done using docker swarm for distributing dozens of pharo images among multiple server machines connected by a message queue for the communication. Pharo supported that scenario very well enabling us the meet the requirements with less effort. >> >> Pharo turned out to be a perfect fit to develop the application in a agile way. Small development cycles with continuous integration and continuous delivery enables fast turnarounds for the customers to validate progress. >> >> This is a screenshot of the search page for multi-modal results: >> >> >> <Screen Shot 2018-09-21 at 16.54.30.png> > >

Sept. 25, 2018

[ANN] Pharo Consortium upgrade to Platinum: ZWEIDENKER

by Marcus Denker

The Pharo Consortium is very happy to announce that ZWEIDENKER has ugraded to be a Platinum member. About - ZWEIDENKER: http://zweidenker.de - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: - http://association.pharo.org

Sept. 25, 2018

Re: [Pharo-users] [Pharo-dev] [ANN] Success story Mobility Map

by Sven Van Caekenberghe

Wow. Very nice, well done. Any chance on some more technical details, as in what 'connected by a message queue for the communication' exactly means ? How did you approach micro services exactly ? > On 25 Sep 2018, at 12:20, Norbert Hartl <norbert(a)hartl.name> wrote: > > As presented on ESUG here is the brief description of one of our current projects. > > Mobility Map > ââââââ > > Mobility Map is a broker for mobility services. It offers multi-modal routing search enabling users to find the best travel options between locations. Travel options include car sharing, bikes, trains, busses etc. Rented cars can be offered for ride sharing on booking time letting other people find it to participate in the ride. Single travel options are combined in travel plans that can be booked and managed in a very easy way. > > For this project main requirements were scalability to serve a large user base and flexibility to add more additional providers to the broker. The application has been realized using web technologies for the frontend and pharo for the backend. Using a microservice architecture combined with a broker it is easy to extend the platform with additional brokers. Deployment is done using docker swarm for distributing dozens of pharo images among multiple server machines connected by a message queue for the communication. Pharo supported that scenario very well enabling us the meet the requirements with less effort. > > Pharo turned out to be a perfect fit to develop the application in a agile way. Small development cycles with continuous integration and continuous delivery enables fast turnarounds for the customers to validate progress. > > This is a screenshot of the search page for multi-modal results: > > > <Screen Shot 2018-09-21 at 16.54.30.png>

Sept. 25, 2018

[ANN] Success story Mobility Map

by Norbert Hartl

As presented on ESUG here is the brief description of one of our current projects. Mobility Map ââââââ Mobility Map is a broker for mobility services. It offers multi-modal routing search enabling users to find the best travel options between locations. Travel options include car sharing, bikes, trains, busses etc. Rented cars can be offered for ride sharing on booking time letting other people find it to participate in the ride. Single travel options are combined in travel plans that can be booked and managed in a very easy way. For this project main requirements were scalability to serve a large user base and flexibility to add more additional providers to the broker. The application has been realized using web technologies for the frontend and pharo for the backend. Using a microservice architecture combined with a broker it is easy to extend the platform with additional brokers. Deployment is done using docker swarm for distributing dozens of pharo images among multiple server machines connected by a message queue for the communication. Pharo supported that scenario very well enabling us the meet the requirements with less effort. Pharo turned out to be a perfect fit to develop the application in a agile way. Small development cycles with continuous integration and continuous delivery enables fast turnarounds for the customers to validate progress. This is a screenshot of the search page for multi-modal results:

Sept. 25, 2018

[ANN] Pharo Consortium New Bronze Member: Spesenfuchs

by Marcus Denker

The Pharo Consortium is very happy to announce that Spesenfuchs has joined the Consortium as a Bronze Member. About - Spesenfuchs: http://spesenfuchs.de - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: - http://association.pharo.org

Sept. 25, 2018

Re: [Pharo-users] TextEditor

by Hilaire

Okay may be it is. I guess I need to see more of it then. I played a bit with the tutorial, and I felt it to beÂ too geeky for my targeted users (teacher and mid hight school learner). Hilaire Le 24/09/2018 Ã 17:42, Serge Stinckwich a Ã©critÂ : > > I don't understand, why this is not appropriate. I'm interested to use it > for PolyMath or CORMAS, in order to put the same document, text, > simulations, piece of code, etc ... -- Dr. Geo http://drgeo.eu

Sept. 24, 2018

Re: [Pharo-users] TextEditor

by Serge Stinckwich

On Sun, Sep 23, 2018 at 2:47 PM Hilaire <hilaire(a)drgeo.eu> wrote: > I know about GTDocumenter but this is not what I am looking for. > > I am looking at the idea of an infinite roll with text, code and morph. > > I don't understand, why this is not appropriate. I'm interested to use it for PolyMath or CORMAS, in order to put the same document, text, simulations, piece of code, etc ... -- Serge Stinckwic h Int. Research Unit on Modelling/Simulation of Complex Systems (UMMISCO) Sorbonne University (SU) French National Research Institute for Sustainable Development (IRD) U niversity of YaoundÃ© I, Cameroun "Programs must be written for people to read, and only incidentally for machines to execute." https://twitter.com/SergeStinckwich

Sept. 24, 2018

[ANN] Next Pharo Sprint: Sept 28

by Marcus Denker

We will organize a Pharo sprint / Moose dojo Sept 28, 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 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-2973620

Sept. 24, 2018