February 2014 - Pharo-users

About validation
by StÃ©phane Ducasse March 11, 2018

March 11, 2018

Hi I read the chapter on validation of the mentoring course book of andres valloud. http://www.lulu.com/fr/fr/shop/andres-valloud/a-mentoring-course-on-smallta… And I love this extension of SUnit. I loved the idea when I saw it for the first time at Lugano (presentation of Leandro Caniglia). I encourage everybody to read it. Now does anybody implemented in Pharo the SUnit extension? I would like to play with it and eventually write a chapter on it for the next book. The idea is so good. Stef

2 1

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

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

New methods for the String class
by Daniela Meneses July 28, 2015

July 28, 2015

Hi to all, As you may know I'm working on in some improvements for the String class. Until now I implemented some missing tests. Right now I'm looking forward to add new methods that could be useful based on Ruby API ( http://www.ruby-doc.org/core-2.1.0/String.html) These are a few of the methods that I'm planning to implement: - chomp(separator=$/) -> new_str - chop() -> new_str - ljust(integer, padstr='') ->new_str - next -> new_str - partition(sep) -> [head, sep, tail] Could you help to find out if these methods are already available for the String class? If you have any idea of new methods for the string class, will be really welcome. -- Cheers , Daniela Meneses

5 6

Re: [Pharo-users] Slot questions
by Paul Davidowitz June 2, 2015

June 2, 2015

To Camillo Bruni: I'm not using any slot image (I only looked over the paper). According to the Pharo book, 'pvt' should be implemented in the mainstream image. To Marcus Denker: There are actually several methods in the image with the 'pvt' prefix. Please update the doc (Pharo book) to remove talking about 'pvt'. It would have saved me a little headache :)

11 15

funny idea Symbol vs. Selector
by stephane ducasse May 14, 2015

May 14, 2015

Hi guys I'm thinking aloud... I was wondering if we could not take advantage of a new class: Selector. MethodDict would only contain selectors and not symbols. I remember that I talked about that with hernan. Stef

8 27

How do I save contents of Workspace into a collection?
by Frank Church Jan. 31, 2015

Jan. 31, 2015

Hi guys, My images are gathering a number of Workspaces whose contents I don't want to delete. I want to create a collection of Workspace contents along this defintion: Description Date Category Content (the actual text in the Workspace). In the final version I would like to be able to select a workspace and simply click a button or a menu item and get a dialog where I can enter the Description, Category and Date with the Workspace contents automatically captured into a text box. Copying and pasting the contents would be okay to start with. Filing it out would be another aspect later. What kind of array would best suited to the task? There is quite a number of them depicted here: http://www.jmcsweeney.co.uk/computing/m206/collections_intro.php What could be the best way to go about it? For those who are curious I am experimenting with the original ideas of Smalltalk where a computer user would do everything in Smalltalk workspace/desktop. I am intrigued by the possibility and somehow it seems eminently doable. -- Frank Church ======================= http://devblog.brahmancreations.com

10 36

Jan. 18, 2015

Hi guys if Pharo is key for you then you should ask yourself what you did for Pharo recently. Writing code, writing documentation helping closing bug entries, participating to the association, to the consortium... Pharo is not happening from spontaneous generation. Stef

4 6

[ANN] Spec documentation in PFTE book finished
by Johan Fabry Jan. 2, 2015

Jan. 2, 2015

Hi all, I am happy to announce that Ben and I finished the documentation of Spec for the Pharo For The Enterprise book. This documentation is up-to-date with the latest version of Spec, and is focused towards people wanting to use it and even extend it (in contrast to the academic papers which are â¦ academic ;-) ). I hope that this text will help all the people that are building UIs in Pharo, and it will clear up any doubts that they may have. The chapter is available in source form from the GitHub project of the PFTE book: https://github.com/SquareBracketAssociates/PharoForTheEnterprise-english The easiest way to read the chapter is from the continuous integration server, which produces a html file of the chapter here: https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSucces… (The same server also produces pdf and markdown files, but there are some strange artifacts there, currently. I guess this will be cleared up in the future) We tried our best to make it understandable and complete, but if you have any doubts or comments please do not hesitate to let us know !! Ben prefers Github apparently, but if you are oldskool like me you can also send a mail (privately or to the mailing list). Now it's time to build some cool user interfaces! :-) ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

10 18

Slots
by Thomas Worthington May 19, 2014

May 19, 2014

I notice that "Slots" are slated for addition in Pharo 3.0. Is there anywhere I can see which model of "slots" is being suggested? I'm not sure that slots, in the sense of Javascript, are a good idea generally and, in the broader context, I'm very unhappy with the idea of messing with Smalltalk's generally clean syntax by adding new language features. Could the desired effects be achieved by subclassing Behavour or somesuch high-level approach? -- Thomas Worthington

12 22