July 2015 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Using Google service discovery API's with Pharo Smalltalk by Richard J. Prinz
by Andy Burnett Nov. 9, 2015

Nov. 9, 2015

Sven wrote <<< I hadn't seen this posted on the mailing list, but this is really cool stuff. Using Google service discovery API's with Pharo Smalltalk by Richard J. Prinz http://www.min.at/prinz/?x=entry:entry150318-104537 < http://www.min.at/prinz/?x=entry:entry150318-104537;comments:1#comments> >>> I totally agree with this. I have played with the code, and started writing some code which manipulates the Google services. It is really powerful. Also, Richard has developed a slick way of dealing with OAuth when running a client app. This is great!

3 4

[ OT ] About Encodings and Character Sets
by Sven Van Caekenberghe Sept. 28, 2015

Sept. 28, 2015

This is a nice article: What Every Programmer Absolutely, Positively Needs to Know About Encodings and Character Sets to Work With Text http://kunststube.net/encoding/ Which refers to this well known article: The Absolute Minimum Every Software Developer Absolutely, Positively Must Know About Unicode and Character Sets (No Excuses!) http://www.joelonsoftware.com/articles/Unicode.html Sven PS: in Pharo, the first part of this draft might help too: Character Encoding and Resource Meta Description http://stfx.eu/EnterprisePharo/Zinc-Encoding-Meta/ A newer version will be part of the upcoming book.

4 4

Rectangle center rounding
by Jan BlizniÄenko Sept. 22, 2015

Sept. 22, 2015

Hello I came to problem with Roassal which originates in Rectangle class. Although rectangle holds its points (origin and corner) in float (not rounded) numbers, the Rectangle>>#center method rounds it down to integers. It causes wierd behavior in Roassal where moving elements in some ocasions are "jumping" to all directions like a jelly. I understand it is for performance reasons, but I think this optimisation is not on the right place. Rectangle origin: 0.9(a)0.9 corner: 3@3 just does not have center 1@1, it is way too far from the real center. Shouldn't the rounded method be separated as for example roundedCenter or something like that to eliminate the confusion? Jan -- View this message in context: http://forum.world.st/Rectangle-center-rounding-tp4837980.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

6 10

New Pharo based solution in the wild
by Esteban A. Maringolo Sept. 8, 2015

Sept. 8, 2015

Hi all, After one year of negotiations (demos, quotes, etc.) and a couple of months of development, by the end of December we released a pilot version of our pharo based solution. The solution consists of a native mobile app (Android), with Pharo 2.0 servers, using Seaside for the web UI, Seaside-REST for the mobile app API and Zinc Websockets to certain "live" features of the web. The persistence is GLORP using the native PostgreSQL driver. I can't disclose much more about the customer or the solution yet, it is a private solution for a multinational consumer goods company operating in Argentina. But I can comment on the numbers: * The pilot will end in ~40 days * It involves 50 mobile users of the Android app using it daily. * An nginx frontend for static files and http proxying to the pharo app servers * Two pharo images as servers, one for the web interface, and one for the REST API. The image is the same, they work as two separate app servers to make use of each server and for improved reliability (I don't want the seaside failures, which has been none yet, to affect the REST API). * Everything running in DigitalOcean droplets based in NYC (they add ~180ms of latency from here but their price/value equations is unmatched). Some performance numbers: * The Pharo server uptime has been no less than perfect, the first 10 days with uninterrupted uptime. Only shutdown to upgrade the image (yesterday night). * The load is minor, with peaks of ~30 concurrent mobile users during a few "business" moments of the day, the server never passed 15% of CPU use. The disk I/O is also small, but the database is small too (growing daily). If the pilot succeeds the plan is to extend the user base to ~1000 mobile users. But some water must pass under the bridge before thinking of that. And if it ever happens, it is going to be gradual. Some anecdotal info I quit my Smalltalk full time job at InfOil (after 9 years of employment) to dedicate 100% to my new company. So I'm betting big on this. By now I'm the sole Smalltalk developer (devops?) of the company. Time has never been more scarce than nowadays. Why Pharo? * Because it is the best open source Smalltalk ("inspired") out there. * Because I have 10+ years of experience with Smalltalk I can't throw away in the context of rapid prototyping and business domain modelling (emphasis on this). * It was a key advantage during the negotiations, we could show a wireframed live app even before our competition prepared a PowerPoint presentation. The development process with Pharo has been rudimentary, only Monticello packages and a couple of workspace scripts to provision new images. I still can't get my head around Metacello. But honestly I haven't dedicated as much time as it needs to be learnt. Having used VAST ENVY's ConfigurationMaps successfully in the past is a proof I can learn Metacello. During the last years at InfOil we were using git with Dolphin Smalltalk, with CI after every git push to the main repo. This was also linked with our issue tracking system, in order to know in which build a certain issue was fixed. We used Dolphin's PAX's files (CVS friendly), Gitlab, JetBrain's TeamCity and YouTrack I'd like to do the same using Monticello's FileTree, BitBucket and JIRA (CI server to be defined). Hopefully with some time, I'll be able to dive deeper into this. My learning of Pharo tooling hasn't been straightforward, but maybe because I'm old and spoiled with other Smalltalk dialects (VSE, VAST, Dolphin). I was managing the Android code (java) with git branching and merging way before I learnt how to use Monticello. Managing the code (files) was the only advantage of working with Eclipse/Java. Everything else was a burden compared with Pharo. I wanted to share my experiences through a blog, but haven't had time to set it up as I'd like, and by now this email is going to be all I can share. After the pilot, we can talk about reporting a success story for Pharo. I felt like this during the last week: http://devopsreactions.tumblr.com/post/68251866244/successful-deployment-at… Best regards, Esteban A. Maringolo CTO (aka DevOps), http://trentosur.com

8 9

Creating a Class in a Temporary Environment
by Sean P. DeNigris Sept. 5, 2015

Sept. 5, 2015

I used to have creatingAClassInATemporaryNamespace | testingEnvironment morph | testingEnvironment := SystemDictionary new. ClassBuilder new name: #AClassForTesting inEnvironment: testingEnvironment subclassOf: Object type: Object typeOfClass instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'TemporaryTesting'. How do I do this with Slots? I tried: creatingAClassInATemporaryNamespace | testingEnvironment morph | testingEnvironment := SystemDictionary new. PharoClassInstaller make: [ :builder | builder superclass: Object; name: #AClassForTesting; environment: testingEnvironment; category: 'TemporaryTesting' ]. but got "key #SystemOrganization not found in SystemDictionary". ----- Cheers, Sean -- View this message in context: http://forum.world.st/Creating-a-Class-in-a-Temporary-Environment-tp4825963… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

4 5

"Oops! Invalid username or password" when saving Settings on smalltalkhub
by Damien Cassou Sept. 3, 2015

Sept. 3, 2015

Hi, I'm trying to update the description of the Pillar project at http://www.smalltalkhub.com/#!/~Pier/Pillar/settings. Unfortunately, when I press the green "Update" button, I face a Oops! Invalid username or password red warning on top of the page and my changes are not saved. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

4 4

Is RBClassNotReferencedRule ~200x slower in Pharo 4 vs Pharo 3 ?
by Paul DeBruicker Aug. 19, 2015

Aug. 19, 2015

I think I'm setting this up wrong in Pharo 4 but am not sure. I use the following code for the test: rule:=RBClassNotReferencedRule new. environment:=RBBrowserEnvironment new forPackageNames: #('MyPackage'). AndreasSystemProfiler spyOn:[RBSmalllintChecker runRule: rule onEnvironment: environment] In Pharo 4 it spends most of the time in Behavior>>#includesDefinedSelector:ofClassName: and takes 300s. In Pharo 3 its only 1.5 s Is there something that can be done to get Pharo 4 up to the speed of Pharo 3? Thanks Paul

4 11

Mongo lost references - bug?
by Sabine KnÃ¶fel Aug. 17, 2015

Aug. 17, 2015

Hi Esteban, I found a problem in mongo/voyage and I have reduced and extracted it for repro. I ask for your opinion if this is a bug. If you file in the code below, the method >>testDemo creates a simple model: Paper has 1:1 reference to Planet. Paper has 1:1 reference to Star. Star has 1:N reference to Planet. Star has 1:1 reference to Paper. Planet has 1:1 reference to Paper. If you run >>testDemo, you see that the model which was created is ok with all its references. (self assert: thePaper planet = thePaper star planets first.) ==> ok If you reset the repository and load Paper from database with Paper select all and make the same check, the references are lost. VORepository current reset. theReloadedPaper := Paper selectAll first. self assert: theReloadedPaper planet = theReloadedPaper star planets first ==>not ok But if you remove the comment within >>mongoPlanets which leads to sending a message to the newly loaded object, then it works. write: [ :star :planets | star planets: (planets "select: [:each | each someMethod]") ]); Do I have to send a message to each of the instances after loading? I think no. If I did not understand correctly how to use voyage, please tell me. Regards Sabine Object subclass: #Planet instanceVariableNames: 'planetname star paper' classVariableNames: '' poolDictionaries: '' category: 'RKA24-Demo'! !Planet methodsFor: 'accessing' stamp: 'sabineknoefel 12/2/2013 12:05'! paper ^ paper! ! !Planet methodsFor: 'accessing' stamp: 'sabineknoefel 12/2/2013 12:05'! paper: anObject paper := anObject! ! !Planet methodsFor: 'accessing' stamp: 'sabineknoefel 7/18/2013 16:17'! planetname ^ planetname! ! !Planet methodsFor: 'accessing' stamp: 'sabineknoefel 7/18/2013 16:17'! planetname: anObject planetname := anObject! ! !Planet methodsFor: 'accessing' stamp: 'sabineknoefel 12/2/2013 11:53'! star ^ star! ! !Planet methodsFor: 'accessing' stamp: 'sabineknoefel 12/2/2013 11:53'! star: anObject star := anObject! ! !Planet methodsFor: 'testing' stamp: 'sabineknoefel 12/2/2013 12:25'! someMethod ^true! ! "-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- "! Planet class instanceVariableNames: ''! !Planet class methodsFor: 'as yet unclassified' stamp: 'sabineknoefel 7/18/2013 16:16'! isVoyageRoot ^true! ! !Planet class methodsFor: 'as yet unclassified' stamp: 'sabineknoefel 12/2/2013 12:23'! mongoStar <mongoDescription> ^ VOMongoToOneDescription new attributeName: 'star'; kind: Star; accessor: (MAPluggableAccessor read: [ :planet | planet star ] write: [ :planet :star | planet star: star ]); yourself! ! !Planet class methodsFor: 'as yet unclassified' stamp: 'sabineknoefel 12/2/2013 12:30'! testDemo "self testDemo" | thePlanet theStar thePaper theReloadedPaper | "create simple model" thePaper := Paper new theme: 'a paper about 42'. thePlanet := Planet new planetname: 'Orion'; paper: thePaper. theStar := Star new starname: 'Betelgeuse'; paper: thePaper. theStar addPlanet: thePlanet. thePaper star: theStar. thePaper planet: thePlanet. thePaper save. "check references - ok" self assert: thePaper planet = thePaper star planets first. VORepository current reset. theReloadedPaper := Paper selectAll first. "references are lost now" self assert: theReloadedPaper planet = theReloadedPaper star planets first! ! Object subclass: #Star instanceVariableNames: 'starname planets paper' classVariableNames: '' poolDictionaries: '' category: 'RKA24-Demo'! !Star methodsFor: 'api' stamp: 'sabineknoefel 7/18/2013 16:21'! addPlanet: aPlanet self planets add: aPlanet. aPlanet star: self! ! !Star methodsFor: 'accessing' stamp: 'sabineknoefel 12/2/2013 12:05'! paper ^ paper! ! !Star methodsFor: 'accessing' stamp: 'sabineknoefel 12/2/2013 12:05'! paper: anObject paper := anObject! ! !Star methodsFor: 'accessing' stamp: 'sabineknoefel 7/18/2013 16:20'! planets planets ifNil: [ self planets: OrderedCollection new ]. ^ planets! ! !Star methodsFor: 'accessing' stamp: 'sabineknoefel 7/18/2013 16:20'! planets: anObject planets := anObject! ! !Star methodsFor: 'accessing' stamp: 'sabineknoefel 7/18/2013 16:18'! starname ^ starname! ! !Star methodsFor: 'accessing' stamp: 'sabineknoefel 7/18/2013 16:18'! starname: anObject starname := anObject! ! "-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- "! Star class instanceVariableNames: ''! !Star class methodsFor: 'as yet unclassified' stamp: 'sabineknoefel 7/18/2013 16:16'! isVoyageRoot ^true! ! !Star class methodsFor: 'as yet unclassified' stamp: 'sabineknoefel 12/2/2013 12:31'! mongoPlanets "remove comment below then references are not lost anymore" <mongoDescription> ^ VOMongoToManyDescription new attributeName: 'planets'; kind: Planet; accessor: (MAPluggableAccessor read: [ :star | star planets ] write: [ :star :planets | star planets: (planets "select: [:each | each someMethod]") ]); yourself ! ! Object subclass: #Paper instanceVariableNames: 'star planet theme' classVariableNames: '' poolDictionaries: '' category: 'RKA24-Demo'! !Paper methodsFor: 'accessing' stamp: 'sabineknoefel 12/2/2013 11:54'! planet ^ planet! ! !Paper methodsFor: 'accessing' stamp: 'sabineknoefel 12/2/2013 11:54'! planet: anObject planet := anObject! ! !Paper methodsFor: 'accessing' stamp: 'sabineknoefel 12/2/2013 11:54'! star ^ star! ! !Paper methodsFor: 'accessing' stamp: 'sabineknoefel 12/2/2013 11:54'! star: anObject star := anObject! ! !Paper methodsFor: 'accessing' stamp: 'sabineknoefel 12/2/2013 11:54'! theme ^ theme! ! !Paper methodsFor: 'accessing' stamp: 'sabineknoefel 12/2/2013 11:54'! theme: anObject theme := anObject! ! "-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- "! Paper class instanceVariableNames: ''! !Paper class methodsFor: 'as yet unclassified' stamp: 'sabineknoefel 12/2/2013 11:48'! isVoyageRoot ^true! ! !Paper class methodsFor: 'as yet unclassified' stamp: 'sabineknoefel 12/2/2013 12:23'! mongoPlanet <mongoDescription> ^ VOMongoToOneDescription new attributeName: 'planet'; accessor: (MAPluggableAccessor read: [ :paper | paper planet ] write: [ :paper :planet | paper planet: planet ]); yourself! ! !Paper class methodsFor: 'as yet unclassified' stamp: 'sabineknoefel 12/2/2013 12:23'! mongoStar <mongoDescription> ^ VOMongoToOneDescription new attributeName: 'star'; accessor: (MAPluggableAccessor read: [ :paper | paper star ] write: [ :paper :star | paper star: star ]); yourself! ! -- View this message in context: http://forum.world.st/Mongo-lost-references-bug-tp4726673.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

3 4

Help regarding Scroll Pane usage
by Jigyasa Grover Aug. 11, 2015

Aug. 11, 2015

Hi I have built an accordion widget using *ExampleBuilderMorph* and *ExpanderMorph*. I would like to add the expanders to a scroll pane in the dialog. I tried using *#newScrollPaneFor:* but in vain. The corresponding code snippet is as: *builder := WidgetExamples exampleBuilder.* *dialog := (builder newPluggableDialogWindow: 'RESULTS').* *searchResultsAccordion := dialog contentMorph:* *(* * dialog newColumn:* * (* * SearchQuick myResult collect: [ :r |* * dialog newRow: {* * (* * (* * dialog newExpander: r title asString* * forAll: { * * (dialog newTextEditorFor: (ValueHolder new contents: r content asString )* * getText: #contents setText: #contents:)minHeight: 150.* * }* * )minWidth:750; minHeight: 10* * )* * cellInset: 0;* * borderStyle: (BorderStyle inset baseColor: dialog paneColor; width: 1)* * } * * ]* * )* * );* *model: nil.* *dialog newScrollPaneFor: searchResultsAccordion.* *builder openModal: dialog.* *dialog extent: 775(a)350.* *dialog position: 500(a)200.* I am able to design the accordion widget as desired, except the scroll pane. Help appreciated. Thanks JIGYASA

1 1

XMLRPC?
by Arturo Zambrano Aug. 11, 2015

Aug. 11, 2015

Hi all, I tried this: Gofer it url: 'http://ss3.gemstone.com/ss/XMLRPC'; package: 'ConfigurationOfXMLRPC'; load. ConfigurationOfXMLRPC project latestVersion load: 'All'. And got this message: This package depends on the following classes: BlockContext ContextPart You must resolve these dependencies before you will be able to load these definitions: forkWithBindings forkWithBindings: forkWithClampedBindings forkWithClampedBindings: forkWithIsolatedBindings forkWithIsolatedBindings: newProcessWithBindings newProcessWithBindings: newProcessWithClampedBindings newProcessWithClampedBindings: newProcessWithIsolatedBindings newProcessWithIsolatedBindings: valueWithBindings: valueWithBindingsContext: bindings Is XMLRPC supported in Pharo 4/Moose 5? best art

6 6