December 2018 - Pharo-users

Re: [Pharo-users] (no subject)

by Offray Vladimir Luna CÃ¡rdenas

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

Dec. 31, 2018

Re: [Pharo-users] (no subject)

by Konrad Hinsen

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). Ben Coman <btc(a)openinworld.com> writes: > This may not be what you are looking for, but maybe help flesh out ideas. > Try debugging... > OpalCompiler new evaluate: '1 + 2' An interesting experience indeed! Tim Mackinnon <tim(a)testit.works> writes: > I was going to chip in that every class inherits what compiler it > uses and so you can easily override that to do something special > (like wrapping classes). An interesting feature, though it seems a bit too low-level for my project, and definitely too low-level for my current Pharo competence. > However, is this possibly an area where the meta-links kicks in so > you donât have to do this and get a more generic solution? (I havenât > played with this, but there are a few threads where people are using > it, and itâs progressed quite a lot in Pharo 7). That sent me off research meta-links: https://pharoweekly.wordpress.com/2018/03/27/understanding-metalinks/ Interesting stuff as well, but the same comment applies: this looks too low-level for what I consider boring code implementing routine techniques. Steffen MÃ¤rcker via Pharo-users <pharo-users(a)lists.pharo.org> writes: > Did you already try to measure the impaired overhead of a wrapper > solution? It might very well be negligible in an otherwise purely > symbolic computation. I did not look into performance questions at all for now. What scares me most is the overhead in code size, in particular in my test suite. > A hybrid solution might be - instead of wrapping each value - to add a > single method to the value classes that wraps a value on the fly if > needed, e.g. > > Integer>>asExpression > ^ExpressionWrapper wrap: self. That looks like an interesting compromise, and one that I have seen used elsewhere. > Another option might be to build a trait that adds the behavior to the > value classes. A nice suggestion as well - I haven't looked at traits yet in any detail. Serge Stinckwich <serge.stinckwich(a)gmail.com> writes: > in your case I would write a parser for your specific concrete syntax > with PetitParser and then generate an instance of the abstract syntax > you have defined. My first reaction was that this looks like overkill for my problem. But then, considering that I will eventually need a parser anyway, why not start that way and use it in my own test cases? A path worth exploring. Thanks again to everyone - your comments will keep me busy for a while! Konrad.

Dec. 31, 2018

Re: [Pharo-users] rotating a morph through messaging

by K K Subbu

On 31/12/18 1:54 AM, Steve Quezadas wrote: > I am experimenting with pharo right now, particularly with Morphs. The > weird thing is that some morphs can have a rotation halo and others do not. > > This has a "rotate halo": > bar := EllipseMorph new. > bar openInWorld. > > This does not: > foo := Morph new. > foo openInWorld A morph has to implement #prepareToRotate method for rotate Halo button to appear and also implement rotationDegrees: method to do the actual transformation. Otherwise, you can add a flex shell to the morph and request it to rotate it. Morph does not support rotation, so there is no rotation button in its halo. EllipseMorph has a dummy rotationDegrees: method. CircleMorph and PolygonMorph go the whole way. foo := Morph new addFlexShell openCenteredInWorld foo topRendererOrSelf rotationDegrees: 45 bar := (PolygonMorph vertices: {261@400. 388@519. 302@595} color: Color blue borderWidth: 2 borderColor: Color black) openInWorld. bar rotationDegrees: 45 HTH .. Subbu

Dec. 31, 2018

[ANN] P3 version 1.1

by Sven Van Caekenberghe

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

Dec. 31, 2018

Re: [Pharo-dev] New book: Pharo with Style

by Benoit St-Jean

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)

Dec. 31, 2018

Re: [Pharo-dev] New book: Pharo with Style

by Benoit St-Jean

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)

Dec. 31, 2018

Re: [Pharo-users] rotating a morph through messaging

by Ben Coman

On Mon, 31 Dec 2018 at 04:24, Steve Quezadas <steve(a)thestever.net> wrote: > > I am experimenting with pharo right now, particularly with Morphs. The > weird thing is that some morphs can have a rotation halo and others do not. > > This has a "rotate halo": > bar := EllipseMorph new. > bar openInWorld. > > This does not: > foo := Morph new. > foo openInWorld > > Am I missing something? Also, how do I send message "rotate" to a morph? > I can't seem to find a "rotate" method anywhere in the browser. I don't know anything about this area, but here is how I discovered something to get you started... (somewhat recursively...) open new halos on the ellipse-rotation-halo, then click the spanner halo to Debug > Inspect Morph. To confirm you are in the right place confirm you can see... owner ==> HaloMorph. extension > balloonText ==> 'Rotate' Now dive into... extension > eventHandler > subscriptions, and you'll see a Dictionary with three items... #mouseDown > Items > aMorphEventSubscription > selector ==> #startRot:with: #mouseMove > Items > aMorphEventSubscription > selector ==> #doRot:with: #mouseUp > Items > aMorphEventSubscription > selector ==> #endInteraction HTH, cheers -ben

Dec. 31, 2018

rotating a morph through messaging

by Steve Quezadas

I am experimenting with pharo right now, particularly with Morphs. The weird thing is that some morphs can have a rotation halo and others do not. This has a "rotate halo": bar := EllipseMorph new. bar openInWorld. This does not: foo := Morph new. foo openInWorld Am I missing something? Also, how do I send message "rotate" to a morph? I can't seem to find a "rotate" method anywhere in the browser. - Steve

Dec. 30, 2018

Re: [Pharo-users] Magritte seaside save

by Vitor Medina Cruz

OMG Thank You! I figure the first part, but I went crazy here debugging, and I probably would never ever figure the second part, a list with a block... Is there documentation for that somewhere? In https://github.com/magritte-metamodel/magritte most of docs links are broken.... :Â´( <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_cam…> Livre de vÃrus. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_cam…>. <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Sun, Dec 30, 2018 at 4:51 PM Diego Lont <diego.lont(a)delware.nl> wrote: > Hi Vitor, > > It has been a while that I really used Magritte, but basically the problem > that you encounter is that the save is not called on MyObject, but on the > component that is created from MyObject (in the method asComponent). The > save method calls the save on the component, and in Magritte that is > implemented, so without doing much it should perform the following code: > > MAContainerComponent >> save > self validate ifFalse: [ ^ self ]. > self commit; answer: self model > > The validate calls the validation rules on the magritteDescription, the > commit stores the changes the user made in the object, and answer allows > the container to do further actions for the same event (as the button is > actually created in the decoration, and not in the container itself). > > So when you want to intercept the save method, you could use a block > instead of a simple symbol: > > MyObject new asComponent addValidatedForm : { [ :container | > | myObject | > â do something you want to do before the save takes place â > container save. > myObject := container model. > â when it reaches here, the save was successful and you can send a message > to myObject, i.e. â > myObject save ] -> 'save'. #cancel -> 'cancel'}. > > Another approach is to change the component that is created by overriding > the componentClass of MyObject, and implementing the save in the new > subclass you created. > > Regards, > Diego > > On 29 Dec 2018, at 17:14, Vitor Medina Cruz <vitormcruz(a)gmail.com> wrote: > > Hello, > > So: > >> >> MyObject new asComponent addValidatedForm >> > > How do I define save callBack? > > I tried: > > MyObject new asComponent addValidatedForm : {#save -> 'save'. #cancel -> >> 'cancel'}. >> > > and defined save in both instance or class side of MyObject, but that > didn't work. > > Regards, > Vitor. > > > <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_cam…> Livre > de vÃrus. www.avg.com > <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_cam…>. > > > >

Dec. 30, 2018

Re: [Pharo-users] Magritte seaside save

by Diego Lont

Hi Vitor, It has been a while that I really used Magritte, but basically the problem that you encounter is that the save is not called on MyObject, but on the component that is created from MyObject (in the method asComponent). The save method calls the save on the component, and in Magritte that is implemented, so without doing much it should perform the following code: MAContainerComponent >> save self validate ifFalse: [ ^ self ]. self commit; answer: self model The validate calls the validation rules on the magritteDescription, the commit stores the changes the user made in the object, and answer allows the container to do further actions for the same event (as the button is actually created in the decoration, and not in the container itself). So when you want to intercept the save method, you could use a block instead of a simple symbol: MyObject new asComponent addValidatedForm : { [ :container | | myObject | â do something you want to do before the save takes place â container save. myObject := container model. â when it reaches here, the save was successful and you can send a message to myObject, i.e. â myObject save ] -> 'save'. #cancel -> 'cancel'}. Another approach is to change the component that is created by overriding the componentClass of MyObject, and implementing the save in the new subclass you created. Regards, Diego > On 29 Dec 2018, at 17:14, Vitor Medina Cruz <vitormcruz(a)gmail.com> wrote: > > Hello, > > So: > > MyObject new asComponent addValidatedForm > > How do I define save callBack? > > I tried: > > MyObject new asComponent addValidatedForm : {#save -> 'save'. #cancel -> 'cancel'}. > > and defined save in both instance or class side of MyObject, but that didn't work. > > Regards, > Vitor. > > <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_cam…> Livre de vÃrus. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_cam…>. > <x-msg://13/#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

Dec. 30, 2018