Monthly Archives: February 2019

Running Pharo in Windows Subsystem for Linux

https://fuhrmanator.github.io/Pharo-in-WSL/

Cool blog post!

Advertisements

Google Summer of Code 2019

Dear all,
Pharo Consortium has been selected this year as a Google Summer of Code 2019 mentor organization. This is the first time since 2017.
I would like to thank other GSOC co-admin Jigyasa Grover and Oleksandr Zaytsev for their commitment and hard work, Peter Uhnak for his help for the website, Alexandre Bergel, Yuriy Tymchuk and Stéphane Ducasse for their interactions.
We will prepare the call for students soon. We have already a website with a list of subject: http://gsoc.pharo.org/
More subjects can be added, but we will focus on topics that will have the bigger impact on the Pharo community.
We will use the #gsoc-planning channel on Discord to discuss.
If you have students that might be interested, please let them know about this opportunity. There is #gsoc-students channel for them.
Regards,

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

SETT (Store to Tonel)

GemTalkSystems is pleased to announce SETT (Store Export to Tonel Tools)[1]. SETT is open source project with an MIT license.
SETT (Store Export to Tonel Tools) is a set of tools to export Smalltalk code from Store and
write into the Tonel file format managed using Git.
SETT is:
a Pharo 6.1 application, that
connects to a Postgres Database
containing source code history in VisualWorks Store format; and
writes to a Git repository
in Tonel format
maintaining all version history, source code and SCM metadata.
SETT was developed last year to support one of our commercial customers in their conversion From Store to Rowan[2]. Rowan artifacts are produced as part of the output of SETT, but the Rowan artifacts can be ignored. The important bit is that SETT converts from Store to Tonel and maintains version history in git.
Please see the project ReadMe[3] and Wiki[4] for additional details.
Dale
[1] https://github.com/GemTalk/SETT
[2] https://github.com/GemTalk/Rowan
[3] https://github.com/GemTalk/SETT#overview
[4] https://github.com/GemTalk/SETT/wiki

[ANN] Buoy v5.0.0 released!

Buoy, the project aiming to complement Pharo adding useful extensions reached it’s 5.0.0 version.

The supported Pharo versions are 6.1 — 32 bits and 7.0 — 32 & 64 bits. The breaking changes are just in the package organization, so you may have to adapt your baseline dependencies but the rest of the code is backwards compatible with version 4.

You can see the detailed release notes here.

Regards,

Gabriel

[ANN] ba-st Web stack updated to P70 (RenoirSt, Willow and HighchartsSt)

Now that Pharo 7 is finally released, we took some time to update the whole web stack hosted at ba-st.

As a general update all the projects now follow the brand new community guidelines and support Pharo 6.1–32 bits and Pharo 7–32 & 64 bits. The build matrix now includes Pharo 8 as a preview.

This includes new versions of RenoirSt, HighchartsSt, Boardwalk, Willow and it’s related projects.
You can see the detailed announcement here.
Regards,
Gabriel

Iceberg testimony!

Hi,

This is a thank you note about Iceberg.

I have been moving all my external and internal Pharo code to git/tonel/7 and on multiple occasions I have been pleasantly surprised about the functionality and performance of Iceberg. Basically, it just works.

Finally, Pharo code lives in standard open source and commercial repositories (git, GitHub, Bitbucket, …), without losing anything.

I know that it took years to get here and that lots of code and community battles had to be fought. So thank you, to the whole team, you did a great job !

Sven


Sven Van Caekenberghe
Proudly supporting Pharo
http://pharo.org
http://association.pharo.org
http://consortium.pharo.org

[Ann] Iceberg for Pharo60

 

Hi all,

I'm on vacations, so I've produced a new patch version of Iceberg :). This version restores compatibility with Pharo6, which was broken since latest changes done for Pharo7 64bit support.

https://github.com/pharo-vcs/iceberg/releases/tag/v1.5.7

I hope people still using Pharo6 find this useful. You should be able now to use again the update script to use latest iceberg on it. I've updated the doc to point to the latest supported version:

"load iceberg"Metacello new
  	baseline: 'Iceberg';
  	repository: 'github://pharo-vcs/iceberg:v1.5.?';
	onWarningLog;
  	load.


On this same direction, we have been discussing that v1.5.* will be the latest minor version supporting Pharo6. Still, we will keep integrating bugfixes and patches as they come.

New versions (>= 1.6) will host the new features and will be available and maintained for both the stable Pharo7 and the in-development Pharo8 versions.

Enjoy,
Guille

[Ann] new release of P3 (postgreSQL)

Hi,

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

https://github.com/svenvc/P3

Version 1.2 contains the following changes:

- P3PreparedStatement is now joined by a polymorphic P3FormattedStatement working client side on text strings
- P3PreparedStatement & P3FormattedStatement now share the same double dispatch mechanism to process argument binding
- Added convenience methods #listDatabases #listSchemas & #listTablesInSchema: to P3Client
- Added convenience methods #firstColumnData & #firstFieldOfFirstRecord to P3Result
- Added dynamic ENUM support via #loadEnums in P3Client
- Add support for the 7 geometric types POINT, CIRCLE, LINE, LSEG, POLYGON & PATH with corresponding objects P3Point, P3Circle, P3Line, P3LineSegment, P3Polygon & P3Path
- Add support for the INTERVAL type with P3Interval object
- Added P3Client>>#serverVersion accessor
- Add support for BIT & VARBIT types with P3FixedBitString & P3BitString objects
- Add TIMETZ support
- Organised P3 package with tags
- More & better documentation & unit tests

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

The quality of open source software is determined by it being alive, supported and maintained.

The first way to help is to simply use P3 in your projects and report back about your successes and the issues that you encounter. You can ask questions on the Pharo mailing lists.

Enjoy,

Sven
Advertisements