October 2017 - Pharo-users - lists.pharo.org

Can't find Cairo
by Steven R. Baker Oct. 8, 2017

Oct. 8, 2017

Heya, I need some help telling Pharo where to find things. I've installed Bloc into my image, and it can't find cairo. Cairo is installed, but as far as I can tell Bloc is not looking for it in /usr/lib/x86_64-linux-gnu/ which is where it can be found. I don't care to go making symlinks around my system: is there a sensible way to tell Pharo where to find libcairo? Thanks! -Steven

2 1

How to make pharo find sqlite?
by Herby VojÄÃk Oct. 8, 2017

Oct. 8, 2017

Hello! I try to deploy UDBCSQLite-using image in a 32bit ubuntu 16.04.3. I do have libsqlite3: root@32bit-agent:~# find / -name '*libsqlite*' -type f 2>>/dev/null /usr/lib/i386-linux-gnu/libsqlite3.so.0.8.6 /var/lib/dpkg/info/libsqlite0.list /var/lib/dpkg/info/libsqlite3-0:i386.postinst /var/lib/dpkg/info/libsqlite3-0:i386.md5sums /var/lib/dpkg/info/libsqlite3-0:i386.shlibs /var/lib/dpkg/info/libsqlite0.postrm /var/lib/dpkg/info/libsqlite3-0:i386.symbols /var/lib/dpkg/info/libsqlite3-0:i386.list /var/lib/dpkg/info/libsqlite3-0:i386.triggers /var/cache/apt/archives/libsqlite0_2.8.17-12fakesync1_i386.deb but I get this in the output of the CI: 17:16:54.233 + ../pharo/pharo ./filmtower.image conf/run-tests.st 17:16:54.508 pthread_setschedparam failed: Operation not permitted 17:16:54.509 This VM uses a separate heartbeat thread to update its internal clock 17:16:54.509 and handle events. For best operation, this thread should run at a 17:16:54.509 higher priority, however the VM was unable to change the priority. The 17:16:54.509 effect is that heavily loaded systems may experience some latency 17:16:54.509 issues. If this occurs, please create the appropriate configuration 17:16:54.509 file in /etc/security/limits.d/ as shown below: 17:16:54.509 17:16:54.509 cat <<END | sudo tee /etc/security/limits.d/pharo.conf 17:16:54.509 * hard rtprio 2 17:16:54.509 * soft rtprio 2 17:16:54.509 END 17:16:54.509 17:16:54.509 and report to the pharo mailing list whether this improves behaviour. 17:16:54.512 17:16:54.512 You will need to log out and log back in for the limits to take effect. 17:16:54.512 For more information please see 17:16:54.512 https://github.com/OpenSmalltalk/opensmalltalk-vm/releases/tag/r3732#linux 17:16:54.785 17:16:54.786 TowergameSyncTests 17:16:54.831 Error: External module not found 17:16:54.832 ExternalLibraryFunction(Object)>>error: 17:16:54.832 ExternalLibraryFunction(Object)>>externalCallFailed 17:16:54.833 ExternalLibraryFunction(ExternalFunction)>>invokeWithArguments: 17:16:54.833 UDBCSQLite3DatabaseExternalObject class>>finalizeResourceData: 17:16:54.834 FFICalloutAPI>>function:module: 17:16:54.834 UDBCSQLite3Library(Object)>>ffiCall:module: 17:16:54.835 UDBCSQLite3DatabaseExternalObject class>>finalizeResourceData: 17:16:54.836 FFIExternalResourceExecutor>>finalize 17:16:54.836 WeakFinalizerItem>>finalizeValues 17:16:54.845 [ each finalizeValues ] in [ :each | [ each finalizeValues ] on: Exception fork: [ :ex | ex pass ] ] in WeakRegistry>>finalizeValues in Block: [ each finalizeValues ] 17:16:54.846 BlockClosure>>on:do: 17:16:54.852 [ Processor terminateActive ] in [ :ex | 17:16:54.852 | copy onDoCtx process handler bottom thisCtx | 17:16:54.852 onDoCtx := thisContext. 17:16:54.852 thisCtx := onDoCtx home. 17:16:54.852 17:16:54.852 "find the context on stack for which this method's is sender" 17:16:54.852 [ onDoCtx sender == thisCtx ] 17:16:54.852 whileFalse: [ onDoCtx := onDoCtx sender. 17:16:54.852 onDoCtx 17:16:54.852 ifNil: [ "Can't find our home context. seems like we're already forked 17:16:54.852 and handling another exception in new thread. In this case, just pass it through handler." ^ handlerAction cull: ex ] ]. 17:16:54.852 bottom := [ Processor terminateActive ] asContext. 17:16:54.853 onDoCtx privSender: bottom. 17:16:54.853 handler := [ handlerAction cull: ex ] asContext. 17:16:54.853 handler privSender: thisContext sender. 17:16:54.853 (Process forContext: handler priority: Processor activePriority) 17:16:54.853 resume. 17:16:54.853 17:16:54.853 "cut the stack of current process" 17:16:54.853 thisContext privSender: thisCtx. 17:16:54.853 nil ] in BlockClosure>>on:fork: in Block: [ Processor terminateActive ] 17:16:54.989 Look like pharo was not able to find the sqlite3 lib. Any help? Thanks, Herby

7 21

Futures, in Scale (was: Re: Embeddable Smalltalk (was: Re: Behold Pharo: The Modern Smalltalk))
by Herby VojÄÃk Oct. 8, 2017

Oct. 8, 2017

Hi, I have looked at Scale b/c of different question, and I see it uses futures. I'd like to ask if those futures are one-off, or is there any consensus on how futures should look like in Pharo. The reason I ask is b/c Amber already has something like that - Promises, which do not use the native JS API directly (though it is inspired), but do have an API of their own; and since those concepts seems to be similar (or maybe are the same, just called differently), if the API used shouldn't be sort-of standardized / used the same way in all occasions. Herby P.S.: Including state-of-the-art Promises.st from Amber master branch to get a picture: Smalltalk createPackage: 'Kernel-Promises'! Object subclass: #Promise instanceVariableNames: '' package: 'Kernel-Promises'! !Promise class methodsFor: 'composites'! all: aCollection "Returns a Promise resolved with results of sub-promises." <inlineJS: 'return Promise.all($recv(aCollection)._asArray())'> ! any: aCollection "Returns a Promise resolved with first result of sub-promises." <inlineJS: 'return Promise.race($recv(aCollection)._asArray())'> ! ! !Promise class methodsFor: 'instance creation'! forBlock: aBlock "Returns a Promise that is resolved with the value of aBlock, and rejected if error happens while evaluating aBlock." ^ self new then: aBlock ! new "Returns a dumb Promise resolved with nil." <inlineJS: 'return Promise.resolve()'> ! new: aBlock "Returns a Promise that is eventually resolved or rejected. Pass a block that is called with one argument, model. You should call model value: ... to resolve the promise and model signal: ... to reject the promise. If error happens during run of the block, promise is rejected with that error as well." <inlineJS: 'return new Promise(function (resolve, reject) { var model = {value: resolve, signal: reject}; aBlock._value_(model); })'> ! signal: anObject "Returns a Promise rejected with anObject." <inlineJS: 'return $recv(anObject)._in_(function (x) {return Promise.reject(x)})'> ! value: anObject "Returns a Promise resolved with anObject." <inlineJS: 'return $recv(anObject)._in_(function (x) {return Promise.resolve(x)})'> ! ! Trait named: #TThenable package: 'Kernel-Promises'! !TThenable methodsFor: 'promises'! catch: aBlock <inlineJS: 'return self.then(null, function (err) {return $core.seamless(function () { return aBlock._value_(err); })})'> ! on: aClass do: aBlock <inlineJS: 'return self.then(null, function (err) {return $core.seamless(function () { if (err._isKindOf_(aClass)) return aBlock._value_(err); else throw err; })})'> ! on: aClass do: aBlock catch: anotherBlock ^ (self on: aClass do: aBlock) catch: anotherBlock ! then: aBlockOrArray "Accepts a block or array of blocks. Each of blocks in the array or the singleton one is used in .then call to a promise, to accept a result and transform it to the result for the next one. In case a block has more than one argument and result is an array, first n-1 elements of the array are put into additional arguments beyond the first. The first argument always contains the result as-is." <inlineJS: ' var array = Array.isArray(aBlockOrArray) ? aBlockOrArray : [aBlockOrArray]; return array.reduce(function (soFar, aBlock) { return soFar.then(typeof aBlock === "function" && aBlock.length > 1 ? function (result) {return $core.seamless(function () { if (Array.isArray(result)) { return aBlock._valueWithPossibleArguments_([result].concat(result.slice(0, aBlock.length-1))); } else { return aBlock._value_(result); } })} : function (result) {return $core.seamless(function () { return aBlock._value_(result); })} ); }, self)'> ! then: aBlockOrArray catch: anotherBlock ^ (self then: aBlockOrArray) catch: anotherBlock ! then: aBlockOrArray on: aClass do: aBlock ^ (self then: aBlockOrArray) on: aClass do: aBlock ! then: aBlockOrArray on: aClass do: aBlock catch: anotherBlock ^ ((self then: aBlockOrArray) on: aClass do: aBlock) catch: anotherBlock ! ! Promise setTraitComposition: {TThenable} asTraitComposition! ! ! phil(a)highoctane.be wrote: > https://github.com/guillep/Scale <https://github.com/guillep/Scale> is > quite cool for quick scripts on *nix. > > Now for embeddable, yes it would help. Bootstrapping will be helpful but > the current main issue is the VM interpret loop that is in the current VMs. > > It is not an intrinsic problem. Telepharo is also a great step to enable > that to exist. > > Phil > > On Oct 7, 2017 13:05, "Herby VojÄÃk" <herby(a)mailbox.sk > <mailto:herby@mailbox.sk>> wrote: > > Ben Coman wrote: > > Nice article. I like the way you've structured it and pushed the > "updated" angle. > > I feel a bit too strong a claim is laid on Pharo producing the > CogVM. > Much of the Cog + Spur + 64bit VM work was originally done for > Squeak > with Pharo riding the coat-tails of that work. Lately Pharo > community > has been involved in improving VM with hotspot optimisation with > Sista > and moving towards making Pharo embeddable.. (@Clement, is "hotspot > > > Hi, this made me curious. I always had the problem with Amber (and, > all the rest of Smalltalks in similar vein) that it is hard to use > to one-off scripting, as it presumes existence of the not really > small class library (objects, classes, collections, etc.). This > disadvantaged it IMO in the field of "can I just embed it here and > script it with a few lines?" scenarios. > > Did you (the Pharo community that is "moving towards making Pharo > embeddable") find some way to work this around? > > cheers -ben > > > Herby > > >

2 1

What does RMoD stand for?
by horrido Oct. 7, 2017

Oct. 7, 2017

It is bizarre. Nowhere on the web can I find any reference to what INRIA's *RMoD* acronym stands for. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

4 3

Embeddable Smalltalk (was: Re: Behold Pharo: The Modern Smalltalk)
by Herby VojÄÃk Oct. 7, 2017

Oct. 7, 2017

Ben Coman wrote: > Nice article. I like the way you've structured it and pushed the > "updated" angle. > > I feel a bit too strong a claim is laid on Pharo producing the CogVM. > Much of the Cog + Spur + 64bit VM work was originally done for Squeak > with Pharo riding the coat-tails of that work. Lately Pharo community > has been involved in improving VM with hotspot optimisation with Sista > and moving towards making Pharo embeddable.. (@Clement, is "hotspot Hi, this made me curious. I always had the problem with Amber (and, all the rest of Smalltalks in similar vein) that it is hard to use to one-off scripting, as it presumes existence of the not really small class library (objects, classes, collections, etc.). This disadvantaged it IMO in the field of "can I just embed it here and script it with a few lines?" scenarios. Did you (the Pharo community that is "moving towards making Pharo embeddable") find some way to work this around? > cheers -ben Herby

3 2

FocusFrog
by Steven R. Baker Oct. 7, 2017

Oct. 7, 2017

Hey all! Thanks for the help on all of my little issues. I've been plugging away at FocusFrog, my application for Getting Things Done.Â I have pushed the current code (mostly UI stuff in there just now) to GitLab: https://gitlab.com/srbaker/FocusFrog I am not sure how to manage projects, or even how someone goes about importing this stuff. If anyone of you cares to pull that down and provide suggestions, I will be more than happy to take them! Currently, I'm fixing up the view switching when you click the sidebar buttons, and improving the task item views. Is there a document somewhere about how you're supposed to publish things for Pharo? I'd like to make sure this follows the "established best practices." Cheers! -Steven

2 1

So how do you use Live Coding ?
by Dimitris Chloupis Oct. 7, 2017

Oct. 7, 2017

I think this deserves a seperate thread by itself, I was wondering what tricks , ideas and workflows you guys have come up with using live coding in Pharo ? What you like ? what you dont like ? What kinda of libraries you have made to enhance your live coding workflow ? What ideas you have that could enhance live coding workflow , inside and outside Pharo ? Any opinion is welcomed whether you just started coding in Pharo or coding in it for many years , I welcome any kind of brainstorming as long as it is relevant to live coding itself. Offray already was kind enough to share his workflow but I am sure other have something to add as well Its important to share because I am thinking of making a special mention in the Pharo wiki about live coding workflows so anything you share will be copy pasted there to help other people to get deeper into live coding If you can please offer practical examples , will make it easier for me and others to understand. So dont be shy, sharing is caring ;)

1 0

Equals and HashCode Builder
by Vitor Medina Cruz Oct. 7, 2017

Oct. 7, 2017

Hello! Is there, in Pharo, builders for equals (=) and hash messages similar to: https://commons.apache.org/proper/commons-lang/javadocs/api-release/org/apa… and https://commons.apache.org/proper/commons-lang/javadocs/api-release/org/apa… ? Thanks in advance, 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…>. <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

8 24

Re: [Pharo-users] Deploying on Linux with LibC version < 2.15
by Bruce O'Neel Oct. 7, 2017

Oct. 7, 2017

Hi, Well, our redhat 6.9 systems have 2.12, so, that qualifies. And yes, we still have RedHat 6, and 6.9 was released only 6 months ago! Â It will finish extended support in a mind-blowing 7 more years in 2024. Redhat 5, still supported for another 3 years till 2020 has glibc 2.5. cheers bruce

7 9

Re: [Pharo-users] Embeddable Smalltalk (was: Re: Behold Pharo: The Modern Smalltalk)
by phil＠highoctane.be Oct. 7, 2017

Oct. 7, 2017

https://github.com/guillep/Scale is quite cool for quick scripts on *nix. Now for embeddable, yes it would help. Bootstrapping will be helpful but the current main issue is the VM interpret loop that is in the current VMs. It is not an intrinsic problem. Telepharo is also a great step to enable that to exist. Phil On Oct 7, 2017 13:05, "Herby VojÄÃk" <herby(a)mailbox.sk> wrote: Ben Coman wrote: > Nice article. I like the way you've structured it and pushed the > "updated" angle. > > I feel a bit too strong a claim is laid on Pharo producing the CogVM. > Much of the Cog + Spur + 64bit VM work was originally done for Squeak > with Pharo riding the coat-tails of that work. Lately Pharo community > has been involved in improving VM with hotspot optimisation with Sista > and moving towards making Pharo embeddable.. (@Clement, is "hotspot > Hi, this made me curious. I always had the problem with Amber (and, all the rest of Smalltalks in similar vein) that it is hard to use to one-off scripting, as it presumes existence of the not really small class library (objects, classes, collections, etc.). This disadvantaged it IMO in the field of "can I just embed it here and script it with a few lines?" scenarios. Did you (the Pharo community that is "moving towards making Pharo embeddable") find some way to work this around? cheers -ben > Herby

1 0