Planet Squeak

blogs about Squeak, Pharo, Croquet and family
planet squeak - planet squeak es - planet squeak jp - planet croquet - planet squeak code - planet smalltalk

January 15, 2019

Pierce Ng

OSSubprocess 64-bit macOS Mojave

OSSubprocess works on macOS Mojave with 64-bit Pharo.

Load it the usual way:

Metacello new
  baseline: 'OSSubprocess';
  repository: 'github://pharo-contributions/OSSubprocess:master/repository';
  load. 

Run the tests. If Pharo was started like how applications are usually started on the Mac, by double-clicking the Pharo.app icon, Test Runner will report 40+ test errors.

Run Pharo the Unix way on the command line: ~/MyApps/Pharo.app/Contents/MacOS/Pharo mypharo7.image. Now all 114 tests pass. All 7 stress tests pass too. Tested with Pharo 7.0 pre-release image.

by Pierce Ng at January 15, 2019 10:06 PM

January 13, 2019

PharoWeekly

[ann] Smallapack in Pharo6

Hi,
I announce the availability of Smallapack in Pharo6.

The ConfigurationOfSmallapack is in
http://www.squeaksource.com/MetacelloRepository and there is a copy in metarepo for Pharo 3/4/5/6.

Currently, the ported version uses a derivative of OpalCompiler patched to handle method with 16+ arguments.
External function calls have not been converted yet to UnifiedFFI, but the patched compiler rather has hook to compile legacy FFI.
Though I did not install the hook to call FFI with more than 15 arguments, so there is at least 1 unit test failing (but not crashing).

I have auto-re-generated all the source code for using UnifiedFFI formats, so the dependency on legacy FFI is not a necessity (apart for simplifying cross dialect maintenance).

But I want to review the generated code method by method rather than filing it in blindly (the wrapper functions are also generated, and I might loose comments or improvments if I'm careless). Unfortunately, the state of diff tools in Pharo6, be it thru MC or worse than all, thru legacy change lists, does not enable such a large scale review, so I think that I will edit in Squeak and run in Pharo...

Now that Smallapack supports Opal, there should be no major problem for porting to Pharo7, but I did not have time to try yet. A few more MC regressions, and the fact to forbid protocol beginning with a * was too serious a cross compatibility hurdle for me. But I'll come back to it, tools are generally better in ph7 than ph6. Stay tuned.

Nicolas Cellier

by Stéphane Ducasse at January 13, 2019 08:15 PM

Visual Studio code Configuration for the VM

Hi guys,

We have been using this week with Pablo a combination of Visual Studio Code, cygwin, and gdb to build and debug the VM to chase some issues during ffi calls in win64.

It was overall simple to setup, and though I thought it was going to be just a text editor with vitamines, it ended up being a really light but versatile IDE with code navigation, compilation and debugging integration.

But, since there were some little things over here and there like gdb
source code mapping that was not so straight forward to find in the
documentation, we thought it would be good to share it.

If somebody is interested in using a similar setup to work with the VM, I've left my configuration files in the following gist, including:

 - cygwin bash terminal integration (also with zsh, but that's pure cygwin)
 - task actions to build cog and stack vms on debug mode
 - launch configs to run both in debug mode with gdb attached

https://gist.github.com/guillep/452a9be3d231db6f89dd40bfb8cf4405

Cheers,
Guille & Pablo

by Stéphane Ducasse at January 13, 2019 08:09 PM

[Ann] Discord Pharo news channel

I am happy to annoyance a new channel in our Discord Server , #news

News is a read only channel (members cannot post there only admins) that I
intended to act as a newspaper of short that you can read with your morning
coffee to get all the latest news in the Pharo land.

The rules of the channel are very simple,
1) Only admins can post there. Its not a dicussion channel, all other
relevant channels can be used for discussing the Pharo news. We already
have tons of them.
2) every post must be no more than 2 lines, similarly to twitter, this is
for headlines not for entire articles
3) every post must contain a link for more info
4) every post must mention the author that the news concern
5)  least news must always be related to Pharo, it can be anything
(article, project, update etc)
6) last but not least I am always open to suggestions in case something
escapes my attention

If you have not done so make sure you join our Discord server following
this link

https://discord.gg/QewZMZa

You wont be getting only news but a very active community always willing to
help you with any questions and problems you may have, real time.

All people are welcomed :)

Kilon

by Stéphane Ducasse at January 13, 2019 09:02 AM

January 12, 2019

Gilad Bracha

Much Ado About Nothing

What sweet nothing does the title refers to? It could be about null, but it in fact will say nothing about that. The nothing in question is whitespace in program text. Specifically, whether whitespace should be significant in a programming language.

My instinct has always been that it should not. Sadly, there are always foolish souls who will not accept my instinct as definitive evidence, and so one must stoop to logical arguments instead.

Significant whitespace, by definition, places the burden of formatting on the programmer. In return, it can be leveraged to reduce syntactic noise such as semicolons and matching braces. The alleged
benefit is that in practice, programmers often deal with both formatting and syntactic noise, so eliminating one of the two is a win.

However, this only holds in a world without civilized tooling, which in turn may explain the fondness for significant whitespace, as civilized tooling (and anything civilized, really),  is scarce. Once you assume proper tooling support, a live pretty printer can deal with formatting as you type, so there is no reason for you to be troubled by formatting. So now you have a choice between two inconveniences. Either:


At this point, you might say this a matter of personal preference, and can devolve into the kind of religious argument we all know and love. To tip the scales, pray consider the line of reasoning below. I don’t recall encountering it before which is what motivated this post.

In the absence of significant whitespace, a pretty printing (aka code formatting) is an orthogonal concern. We can choose whatever pretty printing style we like and implement a tool to enforce it.  Such a pretty-printer/code-formatter can be freely composed with any code source we have - a programmer typing into an editor, an old repository, and most importantly, other tools that spit out code - whether they transpile into our language or generate code in some other way.

Once whitespace is significant, all those code sources have to be cognizant of formatting.  The tool writer has to be worried about both syntax and formatting, whereas before only syntax was a concern.

You might argue that the whitespace is just another form of syntax; the problem is that it is not always context-free syntax. For example, using indentation to nest constructs is context sensitive, as the number of spaces/tabs (or backspaces/backtabs) depends on context.

In short, significant whitespace (or at least significant indentation) is a tax on tooling. Taxing tooling not only wastes the time and energy of tool builders - it discourages tooling altogether. And so, rather than foist significant whitespace on a language, think in terms of a broader system which includes tools. Provide a pretty printer with your language (like in Go).  Ideally, there's a version of the pretty printer that live edits your code as you type.

As a bonus,  all the endless discussions about formatting Go away, as the designers of Go have noted.  Sometimes the best way to address a problem is to define it away.

There. That was mercifully brief, right? Nothing to it.

by Gilad Bracha (noreply@blogger.com) at January 12, 2019 07:05 PM

January 11, 2019

PharoWeekly

New Pharo Discord channel

Since we got some bots attacks we use now the following discord link to get into discord: https://discord.gg/QewZMZa

 

 

 

by Stéphane Ducasse at January 11, 2019 01:16 PM

January 10, 2019

PharoWeekly

[ann] MaterialDesignLite v2.0.0

Hello,

Today I released the version v2.0.0 of MaterialDesignLite for Seaside.
(https://github.com/DuneSt/MaterialDesignLite/releases/tag/v2.0.0)

This release does not brings much new features but it contains all
breaking changes that accumulated in the issue tracker. (That's why it's
a major release).

The main changes are:
- Migration to Tonel (People using Gemstone might need to stick to v1.x.x)
- Removal of all deprecated classes and methods
- I added named URLs in the demo to be able to send links of pages or
example
- Addition of a Pagination widget as extension of MDL
(https://mdl.ferlicot.fr/mdl/Extensions/Pagination)

A migration guide can be found here:

https://github.com/DuneSt/MaterialDesignLite/blob/v2.0.0/resources/migration/v1_to_v2_migration_guide.md

This release is tagged with v2.0.0 and I also introduced tags v2.x.x and
v2.0.x which are moving tags following patch and minor versions.

Here is the full changelog of the release:
https://github.com/DuneSt/MaterialDesignLite/blob/v2.0.0/CHANGELOG.md

If you have issues, need a new feature or have a comment on the project
feel free to open a issue:

https://github.com/DuneSt/MaterialDesignLite/issues

I also updated the demo: https://mdl.ferlicot.fr/

Have a nice day!

-- 
Cyril Ferlicot
https://ferlicot.fr

by Stéphane Ducasse at January 10, 2019 07:53 PM

January 08, 2019

Pierce Ng

P3 with Parameter Binding

Sven Van Caekenberghe has announced a new release of P3, which also implements parameter binding using the PostgreSQL extended query protocol.

Both P3 and PostgresV3 support TLS, the former's being Pharo-specific and the latter's being Squeak-specific.

Which to use? Simple - on Pharo, use P3; on Squeak, use PostgresV3.

by Pierce Ng at January 08, 2019 09:51 AM

January 01, 2019

PharoWeekly

[Ann] Raw Pharo 70 ChangeLog

Hi,
I’m trying to summarize the changelog for Pharo 7 (based on about 2500 merged PRs, not counting standalone commits to Iceberg and Calypso). If something more should be mentioned, please let me know.
Revolutionary kernel changes
– bootstrap
– modular stateful traits
– traits flattening in kernel packages
– new sources file for every bootstrapped version, empty changes
– new class builder
– binary packages loading (Hermes)
Infrastructure changes
– switch to GitHub
– Tonel code format
– update building infrastructure to Jenkins 2
Code management
– Calypso, the new system browser
  – new navigation model
  – faster UI
  – tabs toolbar instead of single source code panel
  – explicit commands instead of duplicated menu and shortcuts
  – extendable by plugins
  – suitable for the remote scenario
  – “dynamic protocols”, support multiple tags per method
  – not required star convention for class extension
  – support multiple tags per class
  – visibility option for inherited methods
  – methods inherited from traits are not shown by default
  – variable view as the special mode for method group view.
  – better keyboard navigation
  – and many more
Iceberg
– a new friendly user interface
– simplification of solving problems with repositories
– workflow simplification
– better GitHub, BitBucket, GitLab support
– improved code merging and comparisons
– new code serialization format (Tonel)
– repositories metadata
– documentation
– better error handling, tags support
– improved Iceberg-Metacello integration
– credentials store
Cleanups
– remove Nautilus
– remove UpdateStream
– remove all Configurations
– remove ShoreLine-Report
– remove TxText
– remove PluggableTabBarMorph
– remove the old Compiler
– remove Watery theme
– remove Versionner
– remove Komitter
– remove LegacyWeakSubscription
– continue on deprecation of FileStream
– dead code cleanups
– code organization cleanups
– unify categorization of common methods
– cleanups of object inspection protocol
– start with Ring deprecation
– better structure of packages
– package comments
Updates
– Zinc
– Epicea
– FFI
– Metacello
– Fuel
New
– Calypso
– integrate WebBrowser
– integrate ReferenceFinder
– Hermes
– Refactoring 2
– Commander
– ClassAnnotation
Spec
– ComposableModel renamed to ComposablePresenter
– new calendar presenter
– Spec-Demo
– improve Spec linking to domain models
Look & Feel
– use the white theme by default
– improve themes switching
– main menu bar
– new window management shortcuts
– better support of fallback bitmap fonts
– improved Inspector refreshing
– Spotter is looking for opened windows
– display scale factor
– FastTable improvements
VM interface
– DoubleWord and DoubleByte arrays
– add EncoderForSistaV1
– read-only literals support
– improvements and fixes for 64-bit support
– fixes for FullBlockClosure
– support of the new bytecode set
Reflectivity
– breakpoints improvements
– test coverage using metalinks
– reflectivity and metalinks improvements
Other
– startup running in a fresh process
– better pin messages
– NewValueHolder and Model API unification
– better working and image directories meaning separation
– SortFunctions composable
– better OSWindow support
– convert rules to the Renraku architecture
– class and method comments improvements
– extensible Playground (pageActionOrder:)
– optional password management for command line handlers
– system dependencies tests
– unify way to obtain package manifests
Pavel

by Stéphane Ducasse at January 01, 2019 11:33 AM

December 31, 2018

PharoWeekly

[ANN] P3 version 1.1

Hi,

I created a new release of P3, the modern, lean and mean PostgreSQL client for Pharo.

https://github.com/svenvc/P3

Version 1.1 contains the following changes:

- added support for Postgres Extended Query protocol (P3PreparedStatement) (thx Jan @jvdsandt)
- added support for reading array type values (currently INTEGER[] FLOAT[] BOOLEAN[] TEXT[] VARCHAR[])
- added P3-Tests package and moved all tests there
- more comments
- more unit tests

https://github.com/svenvc/P3/releases/tag/v1.1


Especially Jan's contribution adds a lot of functionality: the ability to work with prepared statements.

Here is an example doing a batch insert of 100 records (which is more efficient).

| client statement |

client := P3Client url: 'psql://sven@localhost'.

client execute: 'DROP TABLE IF EXISTS table1'.
client execute: 'CREATE TABLE table1 (id SERIAL PRIMARY KEY, created_at TIMESTAMP DEFAULT NOW(), name TEXT)'.

statement := client prepare: 'INSERT INTO table1 (name) VALUES ($1)'.
statement executeBatch: ((1 to: 100) collect: [ :index | Array with: ('Text #', index printString) ]).

client query: 'SELECT * FROM table1'.
client execute: 'DROP TABLE table1'.

statement close.
client close.


Season's Greetings to you all.

Sven

by Stéphane Ducasse at December 31, 2018 09:06 PM

[Ann] Pharo with Style

Hello,

To finish well this year, I’m happy to announce the release of a new book: Pharo with Style.

This little book focuses on key aspects of code: how it communicates with you and your collaborators. I hope it will help you to write great communicating applications.

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

PDF on Bintray

S. Ducasse

by Stéphane Ducasse at December 31, 2018 09:50 AM

December 30, 2018

PharoWeekly

PostgresV3 with parameter binding

Hi all,

I've modified PostgresV3 to do parameter binding, i.e., parsing SQL and
binding/executing with data are performed in separate protocol steps.
I've add a simple client API with some examples demonstrating usage. The
examples require a PostgreSQL server loaded with the Sakila database.
Instructions on bringing the database up and running the examples are in
my blog post:

  https://www.samadhiweb.com/blog/2018.12.25.postgresv3.html

Season's greetings!

Pierce

by Stéphane Ducasse at December 30, 2018 10:24 AM

December 29, 2018

PharoWeekly

[ANN] Pharo Lambda Ultimate

Hi,

Last month Amazon extended their serverless runtime platform AWS Lambda with support for custom runtimes. I created a Pharo Lambda Runtime so now we can implement Lambda functions in Smalltalk and easily deploy them on the Lambda platform.

Lamba has quite a large “free-tier”, more than enough to do some experiments and to host small applications for free.

See the GitHub project for more details https://github.com/jvdsandt/pharo-aws-toolbox

Cheers, Jan.

by Stéphane Ducasse at December 29, 2018 09:54 AM

[Ann] P8 issue tracker is now github

Hi, 

As part of our constant try to enhance process, we are moving the issue tracker to GitHub.
You can now declare issues here: 

https://github.com/pharo-project/pharo/issues <https://github.com/pharo-project/pharo/issues>

FAQ: 

Q: Why we do this?
A: 
- Because reuniting all development process in just one point will enhance traceability
- … and communication (there are a lot of conversations that now happens in different places (list, issue, PR). With this move we put issue and PR discussion in same place.
- … and people historically has complained that “they need to log to fogbugz to just see the issues” 
- … and this allows us to decommission one server we have now just to get the issues names when creating branches (and before slides).

Q: Does that means fogbugz is bad?
A: Not at all! It is a great tool and we are very grateful of it. Is just that we want to reunite our communication into a single point.

Q: What will happen with issues reported in FogBugz?
A: Pharo 7.0 issues will be taken as before. Pharo 8.0 issues need to be re-opened in GitHub. There are less than 25 right now and we ask people reporting it to move them again (maybe we would do it, but better is owners do).

Q: How can we “branch from issue” now if we do not have FogBugz?
A: We already added a tool “branch from issue” that uses GitHub issue tracker. This will be the same as before. 
And for the same price, we add that option to other projects: All GitHub projects now can benefit from “branch from issue” functionality.

Cheers!
Esteban

by Stéphane Ducasse at December 29, 2018 09:43 AM

[Ann] Pharo 8.0 alpha started

Hello all,

We are preparing to release Pharo 7.0 (which will be in January, as soon as we finish some last details). And in the meantime impatient people has asked (and obtained) the aperture of Pharo 8.0 development! 🙂 So you now can start making Pull Requests against Pharo8.0 branch 🙂

Esteban

by Stéphane Ducasse at December 29, 2018 09:40 AM

December 25, 2018

Pierce Ng

PostgresV3 with Parameter Binding

PostgresV3 is a pure Smalltalk implementation of the PostgreSQL v3 wire protocol. I've modified PostgresV3-Core to do parameter binding and added PostgresV3-DBAPI, a very simple client API.

In PostgresV3-DBAPI, there are a number of examples in PG3ExampleClient. These examples require a PostgreSQL server loaded with the Sakila database. To set that up, firstly, download the Sakila database files. Place the PostgreSQL files in ~/data, say.

The quickest way to get PostgreSQL up and running is by Docker. Here's my docker-compose file that uses the official Postgres-11 image. Data is kept in a separate volume 'pgdata'.

version: '3.6'

services:
  postgres:
    image: postgres:11
    ports:
      - "5432:5432"
    volumes:
      - type: bind
        source: /home/pierce/data
        target: /tmp/data
      - type: volume
        source: pgdata
        target: /var/lib/postgresql/data/datavolume
    environment:
      PGDATA: /var/lib/postgresql/data/datavolume
    restart: unless-stopped

volumes:
  pgdata:
    name: pgdata
    external: true

Bring up PostgreSQL, create roles, load the Sakila data, assign permissions:

% sudo docker-compose up -d
Creating network "postgres-sakila_default" with the default driver
Creating postgres-sakila_postgres_1 ... done

% sudo docker ps
CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                    NAMES
936cc31523e3        postgres:11         "docker-entrypoint.s…"   36 seconds ago      Up 34 seconds       0.0.0.0:5432->5432/tcp   postgres-sakila_postgres_1

% sudo docker exec -it 936cc31523e3 bash
root@936cc31523e3:/# su - postgres
postgres@936cc31523e3:~$ psql 
psql (11.1 (Debian 11.1-1.pgdg90+1))
Type "help" for help.
postgres=# create role testuser login password 'secret';
CREATE ROLE
postgres=# create database sakila owner testuser;
CREATE DATABASE
postgres=# \c sakila
You are now connected to database "sakila" as user "postgres".
sakila=> \i /tmp/data/postgres-sakila-schema.sql 
...
GRANT
GRANT
sakila=> \i /tmp/data/postgres-sakila-data.sql 
...
COPY 2
ALTER TABLE
sakila=# grant all privileges on all tables in schema public to testuser;
GRANT
sakila=# grant all privileges on all sequences in schema public to testuser;
GRANT
sakila=# \q
postgres@936cc31523e3:~$ logout
root@936cc31523e3:/# exit
%

In a fresh Squeak image - I'm using 5.2 - evaluate in a workspace:

Installer monticello http: 'http://www.squeaksource.com/';
  project: 'PostgresV3';
  install: 'PostgresV3-Core';
  install: 'PostgresV3-Tests-Core';
  install: 'PostgresV3-DBAPI'.

PG3ExampleClient selectSakilaSimple.
PG3ExampleClient selectSakila.
PG3ExampleClient selectSakilaOneStringParam.
PG3ExampleClient selectSakilaOneStringParam2.
PG3ExampleClient selectSakilaOneStringParamNoResult.
PG3ExampleClient selectSakilaOneIntegerParam.
PG3ExampleClient selectSakilaTwoParams.
PG3ExampleClient insertThenSelectSakila.

In a fresh Pharo image - I'm using the latest 7.0 pre-release - evaluate in a playground:

Gofer it 	
  url: 'http://squeaksource.com/PostgresV3';
  package: 'PostgresV3-Core';
  package: 'PostgresV3-Tests-Core';
  package: 'PostgresV3-DBAPI';
  load. 

PG3ExampleClient selectSakilaSimple.
PG3ExampleClient selectSakila.
PG3ExampleClient selectSakilaOneStringParam.
PG3ExampleClient selectSakilaOneStringParam2.
PG3ExampleClient selectSakilaOneStringParamNoResult.
PG3ExampleClient selectSakilaOneIntegerParam.
PG3ExampleClient selectSakilaTwoParams.
PG3ExampleClient insertThenSelectSakila.

As this is a pure Smalltalk implementation, it should also work in earlier versions of Squeak and Pharo.

Testing and comments welcome.

by Pierce Ng at December 25, 2018 03:35 PM

December 21, 2018

PharoWeekly

PetitParser v2.1.0

Hello,

This email to announce that a new minor release of PetitParser (1) has been published on GitHub (v2.1.0).

Here is the change log:

Summary
-----------
- Each package has its tests separated in a separated package.
- Cleaned baseline, made it more modular.
- Created more groups to let people load the part of the project they want.
- Some cleaning in `PetitParser` package.
- Integrated PetitPreprocessor and PetitParserExtensions in the project as separated groups

Changelog
-----------
#31 Extract PPTextHighlighter into a separated package.
#21 Add contribution guidelines
#13 Update README with new groups
#9 Fix CI configuration
#19 A TODO comment in PPMemoizedParser>>#parseOn: might need to be fixed cleaning
#11 Inconsistent method classification
#15 Split tests in their own packages cleaning
#22 PetitPreprocessor is missing some extensions
#3  Use `>>>` notation for examples inside method
#8 PPStream>>#column: has commented code that should be removed
#7  PPCharSetPredicate and PPContextMemento need to be commented
#1  Replace 'Oops' error message with a meaningful message
#4 PPContext>>#on:stream: should be removed
#2 Integrate PetitParserExtensions package from Smalltalkhub
#5 Integrate PetitPreprocessor package from Smalltalkhub

Thanks to Cyril Ferlicot for his help.

Cheers,

Julien

by Stéphane Ducasse at December 21, 2018 08:58 PM

December 19, 2018

PharoWeekly

GeoSphere

Hi All,

If anyone is interested, I've created the beginnings of a library for
handling coordinates at: https://github.com/akgrant43/GeoSphere

It only:

- Parses string coordinates
- Calculates the distance between coordinates
- Opens a web browser in OpenStreetMap at the receiver's coordinates

Examples of string formats that can be parsed:

- 144.61025 @ -38.28697
- 38° 17′ 13.09″ S, 144° 36′ 36.9″ E
- 38 deg 17' 13.09" S, 144 deg 36' 36.9" E
- https://www.openstreetmap.org/#map=18/-38.28697/144.61025

The distance calculation uses haversine (assumes the earth is a
sphere), which is good enough for my needs at the moment.

Thanks again to Sven, Benoit, Pierce and Richard for their input.

Cheers,
Alistair

by Stéphane Ducasse at December 19, 2018 07:11 PM

Torsten Bergmann

Dispatching tasks to multiple Pharo VMs using SystemProcess

is described here.

by Torsten (noreply@blogger.com) at December 19, 2018 03:36 PM

MachineLearning in #Pharo

Want to check out MachineLearning in Pharo? Then use this awesome list of projects, books, booklets, papers, and applications related to machine learning, AI, data science in Pharo

by Torsten (noreply@blogger.com) at December 19, 2018 03:35 PM

Releaser

Releaser is a new tool for releasing nested #pharo projects residing in multiple repositories. Read more.

by Torsten (noreply@blogger.com) at December 19, 2018 03:32 PM

TimeMachine in Pharo

Funny experiment of Manuel Leuenberger about using Bloc and Pharo to get a déjà vu

by Torsten (noreply@blogger.com) at December 19, 2018 03:21 PM

Glamorous Toolkit v0.4.0

Glamorous Toolkit v0.4.0 is out. Read more.

by Torsten (noreply@blogger.com) at December 19, 2018 03:19 PM

Maizo and Pharo

Maizo - a Chemistry project developed with Pharo.

To quote research gate:

Maizo is aimed toward molecular- and reaction discovery based on big data of quantum mechanical global reaction route mappings. The global reaction data includes equilibrium structures (EQs), dissociation channels (DCs), and transition structures (TSs), which are automatically calculated by a global search on a potential energy surface using the GRRM (global reaction route mapping) method. Applications to molecular- and synthesis design are an important part of the project. Machine learning and visualization techniques as well as chemoinformatics methods are essential to acquire useful information from the large reaction data space. The team developed an RMapViewer, which was developed to visualize and analyze the GRRM outputs.  

Read the PDF on "Maizo"-chemistry Project: toward Molecular- and Reaction Discovery from Quantum Mechanical Global Reaction Route Mappings".

by Torsten (noreply@blogger.com) at December 19, 2018 03:18 PM

Pharo Git Thermite

A visual tool developed in Pharo for assessing Git commits and GitHub Pull Requests

The project is available on GitHub: https://github.com/ronsaldo/pharo-git-thermite

and now also integrates with Iceberg:
 


Read more details here.

by Torsten (noreply@blogger.com) at December 19, 2018 03:11 PM

JupyterTalk

JupyterTalk makes good progress - nice!

 Project is on GitHub: https://github.com/jmari/JupyterTalk

by Torsten (noreply@blogger.com) at December 19, 2018 03:07 PM

Exploring Pharo

There is a nice blog post about his initial experience with Pharo from Konrad Hinsen. He overall likes Pharo and especially the explorability but also has two primary points to criticize:


  1. he mentions that Pharo is not reproducible and can not be bootstrapped from its own source code 
  2. it is not easy for beginners to follow Pharo
The first point is actually invalid. Konrad seem to have missed that Pharo since two years IS ACTUALLY  BOOTSTRAPPED - so we can build a image from scratch and from our own source code. This is actualy in place and used to build Pharo now. Even smaller images (like the minimal one) beside what is provided in the default Pharo download.

People interested in this topic should read this blog post from 2014 and check the "bootstrap" folder in the Pharo github project. This is based on the PharoBootstrap work. Someone interested in this topic might also be interested in this video.

For the second point I agree as Pharo is moving fast it might not be easy to follow. Also the community is small. Due to this we can not invest our sparce resources into making things easy for newbees - but rather will continue to focus on moving forward. Especially with the upcoming Pharo 7 including better git support and the new Calypso browser many things have changed compared to Pharo 6.

But there are books available and there is the mailinglists as well as the Discord chat to ask questions and get answers. Situation is far better than in 1994 when I dived into Smalltalk and where it was not easy to get informations or even a free system to enjoy the openess and productivity of such a system.

Nonetheless - as one of the primary contributors of the Pharo project I really enjoy such blog posts. It shows we are on the right track. There is still a long way to go - but step by step it goes...

by Torsten (noreply@blogger.com) at December 19, 2018 11:30 AM

GeoSphere in Pharo

A project to compute distances, parse coordinates, etc. using Pharo.

See https://github.com/akgrant43/GeoSphere

by Torsten (noreply@blogger.com) at December 19, 2018 10:51 AM

How to use Extensions in Pharo

In Pharo it was always possible for a package to extend a class within another Package. So far it was done by putting a * in front of the method name.

In Pharo 7 this changes a little bit as you can directly select the extension from the new Calypso system browser.

Here is a description about the differences.

by Torsten (noreply@blogger.com) at December 19, 2018 10:50 AM

Mobile Apps Development with PharoJS

A new description on how to use PharoJS is available.

by Torsten (noreply@blogger.com) at December 19, 2018 10:45 AM