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

Is it possible to follow an object through a computation?
by PAUL DEBRUICKER Jan. 2, 2019

Jan. 2, 2019

Hi - Is there a way to haltOnChange or some such for an object? I have an instance that gets into a state I don't understand and would like to watch it or several of its inst vars for when they change. I could set a lot of #haltIf: statements and step through but hope someone has a better strategy thanks & happy new year. Paul

1 0

Re: [Pharo-users] [ANN] P3 version 1.1
by Guillermo Polito Jan. 2, 2019

Jan. 2, 2019

Thanks Sven :) On Tue, Jan 1, 2019 at 11:54 PM Tudor Girba via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > Very cool. Thanks! > > 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 > > "To utilize feedback, you first have to acquire it." > > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

1 0

Re: [Pharo-users] [Moose-dev] glamorous toolkit: v0.4.0
by Offray Vladimir Luna CÃ¡rdenas Jan. 1, 2019

Jan. 1, 2019

Hi, Thanks Konrad for the Sketch-n-Sketch link.Â I think that you hit the point about having multiple editors and views for the same object. I think that for interactive documentation that goes beyond software, that is needed, specially when you are targeting single source input and multi device/format output (like here [1]). Several Markdown variants are targeting such scenario, that includes interactive documentation, but is not their only concern. ATM seems that new GT is pretty tied to Pillar and software documentation (which is fine, but not the path I'm primarily interested). [1] https://mutabit.com/repos.fossil/mapeda/ I will see what future Pharo 7 based toolkits bring on that front. Cheers, Offray On 1/1/19 16:50, Tudor Girba via Pharo-users wrote:

1 0

Re: [Pharo-dev] New book: Pharo with Style
by Tudor Girba Jan. 1, 2019

Jan. 1, 2019

Nice work. Doru > On Dec 30, 2018, at 10:13 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Hello Fellow Pharoers > > I'm happy to announce a new little book to improve the culture around Pharo. > I will revise it in the future so you can feel free to send feedback > and pull requests > to https://github.com/SquareBracketAssociates/Booklet-PharoWithStyle > > Stef > > "The best way to predict the future is to invent" so I do it. > <withstylebook.pdf> -- www.feenk.com "To utilize feedback, you first have to acquire it."

1 0

Re: [Pharo-users] [Moose-dev] glamorous toolkit: v0.4.0
by Tudor Girba Jan. 1, 2019

Jan. 1, 2019

> On Dec 28, 2018, at 1:08 PM, Kjell Godo <squeaklist(a)gmail.com> wrote: > > WOW :) What part of it do you like? Cheers, Doru > On Thu, Dec 20, 2018 at 01:57 Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi Luke, > > I am happy this looks exciting :). > > About the confusion part: The Glamorous Toolkit we are working on right now is a complete new world built on a complete new graphical stack that does is not based on the existing stack that ships with Pharo. It is not an evolution. It is a leap. > > The goal of the new GT is to propose a completely reshaped programming experience that enables moldable development. You will find the concepts from the old GT in the new world as well. For example, the Inspector is extensible in similar ways and the API is similar as well. > > But, in the new world, we are bringing the concept much further. For example, Documenter provides a whole new kind of a tool that can mold to unify multiple workflows (like data notebooks, code documentation, or tutorials) right in the IDE. Coder provides the infrastructure for manipulating code that can mold its shape as you type. Transcript allows you to embed various widgets to transform the otherwise dull experience of a console into a live one. > > Behind the scenes GT comes with several engines. The Examples engine enables example-driven development which also bridges the gap between testing and documentation effort, especially when combined with Documenter. Releaser is able to release deeply nested projects. Phlow offers an engine that shares similarities with Glamour. Completer provides moldable completion. Visualizer offers a couple of visualization engines such as Mondrian. > > All of these are possible because of the underlying graphical stack made of Sparta/Bloc/Brick. > > All in all, we believe that the new GT enables a new way of programming. Individual features can be attractive, but our goal is to reshape the development experience. > > Does this address the concern? > > Cheers, > Doru > > > > On Dec 19, 2018, at 2:09 PM, Luke Gorrie <luke(a)snabb.co> wrote: > > > > On Fri, 14 Dec 2018 at 05:13, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Please do let us know what you think .. and, of course, what you feel. > > > > I'm feeling excited and confused :). > > > > Excited because I love seeing all these new demos streaming out and I'm itching to put new capabilities to work. > > > > Confused about the roadmap. How does this "new" Glamorous Toolkit relate to the "old" one that I learned about last year from the Moldable Tools thesis? Is this a new version or a complete rewrite? Is it backwards compatible or completely reimagined? Is adopting the new version a seamless process or is porting required? Are frameworks like Glamour still there behind the scenes or were they replaced? etc. > > > > > > <gt-documenter-magic-markup.gif><gt-0-4-0.png>_______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)list.inf.unibe.ch > > https://www.list.inf.unibe.ch/listinfo/moose-dev > > -- > www.feenk.com > > "Things happen when they happen, > not when you talk about them happening." > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.feenk.com "Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."

4 8

Re: [Pharo-users] (no subject)
by Offray Vladimir Luna CÃ¡rdenas Jan. 1, 2019

Jan. 1, 2019

Konrad, On 31/12/18 8:59, Konrad Hinsen via Pharo-users wrote: > > Thanks to everyone who replied - the sum of the answers is actually a > lot more useful than each one individually, as each one points to a part > of the puzzle that Pharo is (for me, at least, after roughly one month > of use). It's really nice to have you hear. I remember some of our Twitter conversations about reproducible research and the advantages that Pharo could bring in that front and is good to know that they will continue here with the stuff you're working on. I restarted with Pharo in 2014, after a short revealing experience with Squeak, EToys and Bots Inc in 2006-2007 and now I'm enjoying the Joyride[1] [1] https://twitter.com/offrayLC/status/493979407011561473 Yes, Pharo is strange and awesome and the same time. Be around, you'll be amazed. Offray

2 1

Re: [Pharo-dev] New book: Pharo with Style
by Sven Van Caekenberghe Jan. 1, 2019

Jan. 1, 2019

That is a useful contribution, thank you (again) for your efforts ! > On 30 Dec 2018, at 22:13, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Hello Fellow Pharoers > > I'm happy to announce a new little book to improve the culture around Pharo. > I will revise it in the future so you can feel free to send feedback > and pull requests > to https://github.com/SquareBracketAssociates/Booklet-PharoWithStyle > > Stef > > "The best way to predict the future is to invent" so I do it. > <withstylebook.pdf>

1 0

Re: [Pharo-users] [Pharo-dev] New book: Pharo with Style
by Tim Mackinnon Jan. 1, 2019

Jan. 1, 2019

Iâve always felt the XP book nailed it - donât use comments as a crutch to avoid fixing confusing code and donât do work twice by simply writing a comment that says the same as the code. (You can of course try to write the comment and auto-generate the code, but weâve tried that before). Smalltalk is an expressive language that should read like comments naturally - both with the name of a method, the variables and the statements in it. This leaves comments as a good place to tell a story about the wider context and where to look to get started or learn more. I think this is possibly where Documentor is going to help you navigate along the real code. Of course if after all of this you canât figure out how to fix the code - then a comment is a good last resort. Tim Sent from my iPhone > On 1 Jan 2019, at 12:43, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Richard, > >> On Tue, 1 Jan 2019 at 07:26, Richard O'Keefe <raoknz(a)gmail.com> wrote: >> >> ... >> >> To get an example, I did (String allSelectors atRandom), getting >> #copyWithoutAll:. That has only one definition, in Collection: >> copyWithoutAll: aCollection >> "Answer a copy of the receiver that does not contain any elements >> equal to those in aCollection." >> >> ^ self reject: [:each | aCollection includes: each] >> >> The comment simply paraphrases the rather simple code. > > I agree with pretty much everything you've written, but have a > slightly different view here. > > Including what the method does, even when the code is fairly simple > (OK, not getter / setter methods), is still useful. If the comment is > absent, I have to look at the code, figure out what it does, and then > either figure out if that's what it is supposed to do, or just assume > that I'm correct. Having to figure out whether I've interpreted the > code correctly just increases the cognitive load. If the comment > includes what it is supposed to do, I have a context in which to read > and evaluate the code, and it becomes much less effort. > > Cheers, > Alistair >

1 0

Re: [Pharo-users] [Pharo-dev] New book: Pharo with Style
by Richard O'Keefe Jan. 1, 2019

Jan. 1, 2019

On naming protocols: it would be nice to have clear guidance about when to use '-ion' and when to use '-ing'. In my own code I've been using '-ing' except for a few traditional categories like 'instance creation'. One reason for this was that I didn't want to keep on re-deciding "is it 'enumerating' or 'enumeration'". On Mon, 31 Dec 2018 at 22:04, Benoit St-Jean via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > Besides, I forgot to add one comment : you should have guidelines for > protocol naming. It's not critical per se but I find it quite annoying > to look for stuff in "enumerating" when it's been put in "printing" ! loll > > On 2018-12-31 03:51, Stephane Ducasse wrote: > > Thanks! Thanks! > > I will go over it (now laying on my back :(( stupid muscles strike back!) > > > > On Mon, Dec 31, 2018 at 2:18 AM Benoit St-Jean <bstjean(a)yahoo.com> > wrote: > >> On 2018-12-30 16:13, Stephane Ducasse wrote: > >>> Hello Fellow Pharoers > >>> > >>> I'm happy to announce a new little book to improve the culture around > Pharo. > >>> I will revise it in the future so you can feel free to send feedback > >>> and pull requests > >>> to https://github.com/SquareBracketAssociates/Booklet-PharoWithStyle > >>> > >>> Stef > >>> > >>> "The best way to predict the future is to invent" so I do it. > >> StÃ©phane, > >> > >> You'll find, attached, a revised PDF version with my comments. > >> > >> > >> > >> -- > >> ----------------- > >> BenoÃ®t St-Jean > >> Yahoo! Messenger: bstjean > >> Twitter: @BenLeChialeux > >> Pinterest: benoitstjean > >> Instagram: Chef_Benito > >> IRC: lamneth > >> Blogue: endormitoire.wordpress.com > >> "A standpoint is an intellectual horizon of radius zero". (A. Einstein) > >> > -- > ----------------- > BenoÃ®t St-Jean > Yahoo! Messenger: bstjean > Twitter: @BenLeChialeux > Pinterest: benoitstjean > Instagram: Chef_Benito > IRC: lamneth > Blogue: endormitoire.wordpress.com > "A standpoint is an intellectual horizon of radius zero". (A. Einstein) > > >

2 2

how to use indexes to copy a substring out of a string
by Roelof Wobben Jan. 1, 2019

Jan. 1, 2019

4 5