January 2019 - Pharo-users - lists.pharo.org

Managing Code - Creating a Library/Package from scratch?

by Todd Blanchard

The bit I always struggle with on various Smalltalk environments is the right way to manage code. It keeps changing. Which is fine. But I've been away for a bit and I'm lost now. I want to create a new package that can be loadable and lives in a git repo. I guess Metacello is part of that. And Iceberg. And...what else? I want to build a library but am no longer clear on what a library (or package I guess) definition is built from. Thanks.

Jan. 5, 2019

Re: [Pharo-users] Updating singletons

by Konrad Hinsen

Dale, > This looks like a case where you are using a metadata-less repository > ... if so you, should add the following method to your baseline class: Sorry, that's way above my understanding of baselines and repository handling in general. I started from https://github.com/pharo-open-documentation/pharo-wiki/blob/master/General/… and adapted the examples there to my own situation, my project being hosted on GitHub: https://github.com/khinsen/leibniz-pharo/ > This mod will cause packages to be unconditionally loaded ... Monticello > does a definition comparison on package load so only changed definitions > are loaded into the image ... I'd say that a new dependency should be treated like a changed one, but again I am still very much lost in the jungle of Monticello, Metacello, Gofer, Iceberg, etc. It's the most opaque aspect of Pharo I have encountered so far. Cheers, Konrad.

Jan. 5, 2019

Re: [Pharo-users] [ANN] P3 version 1.1

by Sven Van Caekenberghe

Beautiful. > On 5 Jan 2019, at 00:02, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > You can now query a Postgres database from the new GT. The initial code is available here: > https://github.com/feenkcom/gt4p3 > > It currently looks like this: > <gt-inspector-p3-query.png> > > Cheers, > Doru > > > >> On Dec 31, 2018, at 12:33 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> 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 >> >> >> -- >> Sven Van Caekenberghe >> Proudly supporting Pharo >> http://pharo.org >> http://association.pharo.org >> http://consortium.pharo.org >> >> >> >> > > -- > www.feenk.com > > "What is more important: To be happy, or to make happy?" >

Jan. 5, 2019

Re: [Pharo-users] [ANN] P3 version 1.1

by Ben Coman

very cool. thanks Doru & team. cheers -ben On Sat, 5 Jan 2019 at 07:02, Tudor Girba <tudor(a)tudorgirba.com> wrote: > You can now query a Postgres database from the new GT. The initial code is > available here: > https://github.com/feenkcom/gt4p3 > > It currently looks like this: > > Cheers, > Doru > > > > On Dec 31, 2018, at 12:33 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > 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 > > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > > > > > -- > www.feenk.com > > "What is more important: To be happy, or to make happy?" > >

Jan. 5, 2019

Re: [Pharo-users] [ANN] P3 version 1.1

by Tudor Girba

You can now query a Postgres database from the new GT. The initial code is available here: https://github.com/feenkcom/gt4p3 It currently looks like this: Cheers, Doru > On Dec 31, 2018, at 12:33 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > 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 > > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > > > -- www.feenk.com "What is more important: To be happy, or to make happy?"

Jan. 4, 2019

Re: [Pharo-users] Updating singletons

by Gabriel Cotelli

Talking about metadataless, I just bumped into: https://pharo.manuscript.com/f/cases/22865/ using *MetacelloCypressBaselineProjec*t. I'm pushing a PR as an attempt to fix it but for sure if Dale can give it a review it will be great! https://github.com/pharo-project/pharo/pull/2173 Then we need to fix it upstream in Metacello. Regards, Gabriel On Fri, Jan 4, 2019 at 3:04 PM Dale Henrichs < dale.henrichs(a)gemtalksystems.com> wrote: > Konrad, > This looks like a case where you are using a metadata-less repository ... > if so you, should add the following method to your baseline class: > > projectClass > Smalltalk at: #'MetacelloCypressBaselineProject' ifPresent: [ :cl | ^ cl ]. > ^ super projectClass > > This mod will cause packages to be unconditionally loaded ... Monticello > does a definition comparison on package load so only changed definitions > are loaded into the image ... > > Hope this helps, > > Dale > > On 1/4/19 5:12 AM, Konrad Hinsen via Pharo-users wrote: > > Subject: > Re: [Pharo-users] Updating singletons > > From: > Konrad Hinsen <konrad.hinsen(a)fastmail.net> <konrad.hinsen(a)fastmail.net> > > Date: > 1/4/19, 5:12 AM > > To: > pharo-users(a)lists.pharo.org > > H Cyril, > > > Fetching, loading and post loads should leave a trace during the > execution in the Transcript. > > Thanks, that helps to confirm that my postload is never executed when I > update a package + baseline in an image that already had an earlier > version loaded. Nothing at all is shown in the Transcript. Reloading the > package and/or the baseline package doesn't leave any trace either. And > if I add a dependency, then update the package again, the new dependency > is not loaded either. > > Hypothesis: baseline changes have no effect for already installed packages. > > When I load my modified package + baseline into a fresh image, lots of > actions are shown in the Transcript, including the execution of my > postload action. But in that situation, I don't actually need it. > > Cheers, > Konrad. > > >

Jan. 4, 2019

Re: [Pharo-users] Updating singletons

by Dale Henrichs

Konrad, This looks like a case where you are using a metadata-less repository ... if so you, should add the following method to your baseline class: projectClass Smalltalk at: #'MetacelloCypressBaselineProject' ifPresent: [ :cl | ^ cl ]. ^ super projectClass This mod will cause packages to be unconditionally loaded ... Monticello does a definition comparison on package load so only changed definitions are loaded into the image ... Hope this helps, Dale On 1/4/19 5:12 AM, Konrad Hinsen via Pharo-users wrote: > Subject: > Re: [Pharo-users] Updating singletons > From: > Konrad Hinsen <konrad.hinsen(a)fastmail.net> > Date: > 1/4/19, 5:12 AM > > To: > pharo-users(a)lists.pharo.org > > > H Cyril, > >> Fetching, loading and post loads should leave a trace during the >> execution in the Transcript. > Thanks, that helps to confirm that my postload is never executed when I > update a package + baseline in an image that already had an earlier > version loaded. Nothing at all is shown in the Transcript. Reloading the > package and/or the baseline package doesn't leave any trace either. And > if I add a dependency, then update the package again, the new dependency > is not loaded either. > > Hypothesis: baseline changes have no effect for already installed packages. > > When I load my modified package + baseline into a fresh image, lots of > actions are shown in the Transcript, including the execution of my > postload action. But in that situation, I don't actually need it. > > Cheers, > Konrad. >

Jan. 4, 2019

Re: [Pharo-users] Updating singletons

by Konrad Hinsen

Hi Steffen, > Have you considered to yield (an) proxy object(s) instead of the actual > Singleton in uniqueInstance? This way it suffices to update the proxy > with each update of the code. I am not sure I understand what you are proposing. My problem is figuring out how to change in-memory objects when they become obsolete after a code change. So I'd say it doesn't matter much if the object I need to change is the singleton or a proxy to it, but maybe I am missing something! Cheers, Konrad.

Jan. 4, 2019

Re: [Pharo-users] Updating singletons

by Konrad Hinsen

H Cyril, > Fetching, loading and post loads should leave a trace during the > execution in the Transcript. Thanks, that helps to confirm that my postload is never executed when I update a package + baseline in an image that already had an earlier version loaded. Nothing at all is shown in the Transcript. Reloading the package and/or the baseline package doesn't leave any trace either. And if I add a dependency, then update the package again, the new dependency is not loaded either. Hypothesis: baseline changes have no effect for already installed packages. When I load my modified package + baseline into a fresh image, lots of actions are shown in the Transcript, including the execution of my postload action. But in that situation, I don't actually need it. Cheers, Konrad.

Jan. 4, 2019

Re: [Pharo-users] Updating singletons

by Cyril Ferlicot D.

Hello, Fetching, loading and post loads should leave a trace during the execution in the Transcript. For pre/post load it should have something like: Evaluated -> baseline [BaselineOfMyProject] >> selector This is the primary source of informations I use to debug baselines. -- Cyril Ferlicot https://ferlicot.fr

Jan. 3, 2019