December 2017 - Pharo-users

Re: [Pharo-users] P3 timeout

by Pierce Ng

On Sun, Nov 26, 2017 at 02:03:13PM +0100, Stephane Ducasse wrote: > It would be cool if we could get a little success stories around what > you are doing. > A success stories does not mean that you get as rich as Steve Jobs, > just that you build > something nice successfully. ;) Hi Stef, Will do when I get somewhere with this. :-) I'm taking your lead by working on some booklets, although for now $DAY_JOB beckons and progress has been slow. Pierce

Dec. 5, 2017

Re: [Pharo-users] P3 timeout

by Pierce Ng

On Sun, Nov 26, 2017 at 07:17:51PM +0100, Sven Van Caekenberghe wrote: > Added P3Client>>#timeout[:] option (thx Pierce Ng) Thank you, Sven. > About Zdc streams. They have their own default timeout (5 seconds). I think > it is not a good idea to have global timeout setting, these should be done > per actual (client) instance. I like relatively short timeouts, so that I get > faster feedback. Agree. Mine was just a quick hack. > BTW, I am also interested in your experience using P3. How did it go ? Very easy to get going. I'm querying my server in 'batch' mode, and trying to work out the best mix of Pharo and PostgreSQL code to process the data. As we all know on this list, rapid development with Pharo is productive and fun. Are you planning to implement the advanced query protocol with parameter binding? Pierce

Dec. 5, 2017

Pharo newsletter archive

by Torsten Bergmann

Hi, the newsletter archive is now available on "newsletter.pharo.org" which is more easy to remember. Thanks Marcus for setting up the redirect! Bye T.

Dec. 4, 2017

Re: [Pharo-users] Behold Pharo: The Modern Smalltalk

by Stephane Ducasse

Hi We have a full mooc with 90 videos, we have books. And we are super busy. You see we cannot do everything. Stef On Mon, Dec 4, 2017 at 5:15 AM, horrido <horrido.hobbies(a)gmail.com> wrote: > Speaking of which, one of my readers said he tried out Pharo recently and > found the documentation wanting. He was expecting a Getting Started guide at > the pharo.org website and couldn't find one. So he had to blunder around a > bit. > > I told him he could've looked at "Chapter 2: A quick tour of Pharo" in the > *Pharo by Example 5* book, but he's right. There ought to be something > obvious at the pharo.org website that helps a newbie get Pharo up and > running, understand how to basically use the Pharo IDE, and write the > standard "Hello World" program. > > I checked out squeak.org and found the same documentation issue! Why is > this??? > > > Offray Vladimir Luna CÃ¡rdenas-2 wrote >> Documentation is going well. In fact the stuff that kept me away of >> Squeak, despite of its potential was the lack of documentation. "The >> artifact is the curriculum" was to powerful but too heavy. You need a >> way to understand how to deconstruct and navigate the artifact that is >> usually anchored with the culture you have (books and reading) instead >> of only launching inspectors os browsing the code. Grafoscopio is my >> attempt to fill that gap between the world of objects/simulations and >> the world of scripts/documents. >> >> Cheers, >> >> Offray > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Dec. 4, 2017

Tonel + Metacello

by Hilaire

Hi, In a configuration, how are we supposed to use Tonel package? Indeed the Tonel only old the most recent package version, versioning is done at an outer lever by the used CVS system. For now, I have baseline and configuration as: baseline1801: spec Â Â Â <version: '18.01-baseline'> Â Â Â spec for: #common do: [ Â Â Â Â Â Â spec blessing: #baseline; Â Â Â Â Â Â Â Â Â repository: 'tonel:///home/hilaire/Travaux/Developpement/DrGeoII/trunk/src'; Â Â Â Â Â Â Â Â Â description: 'Dr. Geo, an interactive geometry application.'; [...] version1801a: spec Â Â Â <version: '18.01a' imports: #('18.01-baseline') > Â Â Â spec for: #common do: [ Â Â Â Â Â Â spec blessing: #development. Â Â Â Â Â Â spec description: '18.01a'. Â Â Â Â Â Â spec package: 'DrGeoII-Core' with: 'DrGeoII-Core'. Â Â Â Â Â Â spec package: 'DrGeoII-Polymorph' with: 'DrGeoII-Polymorph'. [...] Of course absolute path in the repository field is far to be desirable. What is your best practice? Hilaire -- Dr. Geo http://drgeo.eu

Dec. 4, 2017

Re: [Pharo-users] Where is Numerical Methods with Pharo?

by Marcus Denker

https://books.pharo.org/numerical-methods/ > On 4 Dec 2017, at 16:21, horrido <horrido.hobbies(a)gmail.com> wrote: > > What happened to the "Numerical Methods with Pharo" book? It suddenly > vanished from pharo.org. > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Dec. 4, 2017

Where is Numerical Methods with Pharo?

by horrido

What happened to the "Numerical Methods with Pharo" book? It suddenly vanished from pharo.org. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Dec. 4, 2017

[Ann][Local]1. Smalltalker Treff LÃ¼beck ist Heute

by Christian Haider

Moin, der 1. Smalltalker Treff LÃ¼beck findet heute Abend statt: ab 20 Uhr im Hieronymus, FleischhauerstraÃe 81, LÃ¼beck, Germany Alle Interessierte sind herzlich willkommen. Dazu gibt es auch ein Meetup: https://www.meetup.com/de-DE/Smalltalker-Treff-Lubeck/ Happy hacking, Christian

Dec. 4, 2017

feenk log

by Tudor Girba

Hi, Here is an update of the work on Bloc and GT: Bloc: - Bezier curves (cubic and quadratic). https://twitter.com/feenkcom/status/934765444464021504 https://twitter.com/feenkcom/status/934856909001252865 - Dragging is now possible through a BlDragHandler that can be attached to any element. - Pixel accurate line heads and tails https://twitter.com/feenkcom/status/936704646290305025 - More flexible scalable element. https://twitter.com/feenkcom/status/934003681539907585 - Improved scalability of the rendering. For example, on Mac, we are on par with the speed of Firefox. https://twitter.com/feenkcom/status/931462535861108736 - Sparta is now able to load custom fonts. https://twitter.com/feenkcom/status/930919637214285824 - Text insertion works now much better. Deletion and Selection still require more work. - The rope data structure can now be better inspected. https://twitter.com/feenkcom/status/937298739584172032 - Sparta/Moz2D has a visual loader that also provides more specific details in case of errors. https://twitter.com/feenkcom/status/936501909581688832 - Moz2D is now installed by default on Linux 64b. GT: - The GT Visualizer sub-project now contains two tools: -- GT Mondrian is a graph visualization engine that is both performant and shows how Bloc works well for visualizations. More details in a follow up post. https://twitter.com/feenkcom/status/937682660704563202 -- GT Connector is a new tool for browsing connected examples. More details about it in a follow up post. https://twitter.com/feenkcom/status/936109463462965248 Enjoy, The feenk team -- www.tudorgirba.com www.feenk.com "If you can't say why something is relevant, it probably isn't."

Dec. 4, 2017

Re: [Pharo-users] Building a Baseline

by Denis Kudriashov

Hi Andrew. It is known and super annoying bug Metacello script never checkout/switch to requested branch/tag/commit <https://github.com/pharo-vcs/iceberg/issues/479>. 2017-12-04 13:04 GMT+01:00 Prof. Andrew P. Black <black(a)cs.pdx.edu>: > In the baseline configuration of my project, it says > > spec > baseline: 'SmaCC' > with: [ spec repository: 'github://apblack/SmaCC:working' ]. > > Later, I have a parser that depends on 'SmaCC'. > > However, when I load my baseline, it seems to load from the current branch > of the local clone of *apblack/SmaCC* in my file system. That is, my > local clone was on branch *master*, so *master* was loaded, rather than > *working*. > > What am I doing wrong, and how do I fix the baseline so that the correct > branch is loaded? > > Andrew > > The complete baseline is as follows: > > baseline: spec > <baseline> > > spec for: #'common' do: [ > spec > baseline: 'SmaCC' > with: [ spec repository: 'github://apblack/SmaCC:working' ]. > spec > baseline: 'FileDialog' > with: [ spec repository: 'github://peteruhnak/file-dialog/repository' ]. > spec package: 'Grace-Scope'. > spec package: 'Grace-Names' with: [ spec requires: {'Grace-Parser' . > 'Grace-Scope'} ]. > spec package: 'Grace-Parser' with: [ spec requires: {'SmaCC' . > 'Grace-Scope'} ]. > spec package: 'Grace-IDE' with: [ > spec requires: {'FileDialog' . 'Grace-Compiler'} ]. > spec package: 'Grace-Compiler' with: [ > spec requires: {'Grace-Parser' . 'Grace-Names'} ]. > spec package: 'GraceTests' with: [ spec requires: {'Grace-Parser' . > 'Grace-Names'} ] > ] > >

Dec. 4, 2017