- Pharo-users - lists.pharo.org

Re: [Pharo-users] Athens on Pharo 3.0 on Ubuntu

by Damien Cassou

On Mon, Jan 6, 2014 at 5:03 PM, Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> wrote: > For Ubuntu x64 users, here's what you need to do: no! All Ubuntu users should use http://www.pharo-project.org/pharo-download/ubuntu -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Jan. 6, 2014

Special characters in Ubuntu (Pharo 2.0)

by Esteban A. Maringolo

For some reason I don't know the special "mute" characters stopped working in my Ubuntu 13.10 Pharo environment. They do work in the console and everywhere else, but it doesn't work inside Pharo. Ubuntu is running inside of a VMWare VM. I have to press Alt Gr+{ to get the caret (^), but when I press that I get a ? symbol instead. Also the numpad is totally weird. :) I'm sure this is something trivial, because it used to work in the past! As said, it works everywhere else but Pharo. This is the vm version: 'NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 Dec 12 2013 NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 Dec 12 2013 https://github.com/pharo-project/pharo-vm.git Commit: 71adca113a9aff2876288927e5c1c86bf7ac13e2 Date: 2013-12-07 05:00:47 -0800 By: Philippe Back <philippeback(a)gmail.com> Jenkins build #14777 ' Regards, Esteban A. Maringolo

Jan. 6, 2014

Re: [Pharo-users] Athens on Pharo 3.0 on Ubuntu

by Igor Stasenko

On 6 January 2014 17:03, Bernat Romagosa <tibabenfortlapalanca(a)gmail.com>wrote: > Sorry guys, what a stupid mistake! > > Of course you can't call a 64b library, I hadn't thought about that... > > For Ubuntu x64 users, here's what you need to do: > > apt-get install libcairo2-dev:i386 > > > amen :) > > 2014/1/6 Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> > >> Hi list, >> >> I was just testing the new Pharo 3.0 on an Ubutu box, and I found the >> Athens Cairo examples are not working. The first bug is just about the path >> of libcairo.so.2 in Ubuntu x64, which is as follows: >> >> /usr/lib/x86_64-linux-gnu/libcairo.so.2 >> >> So, this path should be added to CairoLibraryLoader class >> >> pathToCairoOnLinux. >> >> Still, after adding it, I get: 'failed to get a symbol address: >> cairo_image_surface_create', and here I'm lost... any ideas what's going on? >> >> Thanks! >> >> -- >> Bernat Romagosa. >> > > > > -- > Bernat Romagosa. > -- Best regards, Igor Stasenko.

Jan. 6, 2014

Re: [Pharo-users] Athens on Pharo 3.0 on Ubuntu

by Bernat Romagosa

Sorry guys, what a stupid mistake! Of course you can't call a 64b library, I hadn't thought about that... For Ubuntu x64 users, here's what you need to do: apt-get install libcairo2-dev:i386 2014/1/6 Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> > Hi list, > > I was just testing the new Pharo 3.0 on an Ubutu box, and I found the > Athens Cairo examples are not working. The first bug is just about the path > of libcairo.so.2 in Ubuntu x64, which is as follows: > > /usr/lib/x86_64-linux-gnu/libcairo.so.2 > > So, this path should be added to CairoLibraryLoader class >> > pathToCairoOnLinux. > > Still, after adding it, I get: 'failed to get a symbol address: > cairo_image_surface_create', and here I'm lost... any ideas what's going on? > > Thanks! > > -- > Bernat Romagosa. > -- Bernat Romagosa.

Jan. 6, 2014

Athens on Pharo 3.0 on Ubuntu

by Bernat Romagosa

Hi list, I was just testing the new Pharo 3.0 on an Ubutu box, and I found the Athens Cairo examples are not working. The first bug is just about the path of libcairo.so.2 in Ubuntu x64, which is as follows: /usr/lib/x86_64-linux-gnu/libcairo.so.2 So, this path should be added to CairoLibraryLoader class >> pathToCairoOnLinux. Still, after adding it, I get: 'failed to get a symbol address: cairo_image_surface_create', and here I'm lost... any ideas what's going on? Thanks! -- Bernat Romagosa.

Jan. 6, 2014

Two videos to explain what we do when integrating a fix.

by StÃ©phane Ducasse

Hi guys I produced two videos to show how simple is an integration now (It could be better see below). This can influence some of you to help us: sven, ben, igor :)? First one: install some scripts http://stephane.ducasse.free.fr/Videos/PharoIntegration/DownloadingScripts.… Second one http://stephane.ducasse.free.fr/Videos/PharoIntegration/integratingAChange.… ./prepare start menu merge 9look at the fixâ¦.) freeze menu publish menu ./publish I do not think that Monticello is the best tool for managing our changes and code (and I asked money in the past to get an engineer but it was refused and I spent the holiday building a new case to ask money to pay an engineer to get a real integration with Git) but for now this is what we have and it is working. I do not want that end users to get expose to git on the command-line with different platforms. We should keep the simplicity of Pharo. Stef

Jan. 6, 2014

Re: [Pharo-users] ZdcSecureSMTPClient mail sending.

by Sven Van Caekenberghe

On 05 Jan 2014, at 19:34, irfankhan1 <irfankhan(a)hotmail.ca> wrote: > Ok, the test for plugin passes seems like thats not the problem, here is what > i got when i run zodiac-Test. <http://forum.world.st/file/n4734424/2.png> How did you install Pharo on Ubuntu ? Like this ? http://www.pharo-project.org/pharo-download/ubuntu Or using this ? http://get.pharo.org AFAIK, all Zodiac test pass on the Linux (Ubuntu) slaves on the CI servers. Sven

Jan. 5, 2014

Re: [Pharo-users] ZdcSecureSMTPClient mail sending.

by irfankhan1

Ok, the test for plugin passes seems like thats not the problem, here is what i got when i run zodiac-Test. <http://forum.world.st/file/n4734424/2.png> -- View this message in context: http://forum.world.st/ZdcSecureSMTPClient-mail-sending-tp4734027p4734424.ht… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Jan. 5, 2014

Re: [Pharo-users] New Pharo based solution in the wild

by Sven Van Caekenberghe

Great, impressive work, Esteban, thanks for sharing. I wish you luck in completing your pilot. Let us known if you need help in critical areas. Sven On 04 Jan 2014, at 20:16, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > 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 >

Jan. 4, 2014

Re: [Pharo-users] New Pharo based solution in the wild

by StÃ©phane Ducasse

thanks for sharing that with us. We are happy. I want to share this story with you. I hope one day it will be public for real. I will tell you what a guy in bank in a east european country told me: For his first Smalltalk application he used Pharo 1.4 + magritte + seaside + fuel It took him 3 months of work and only three forms where coded by hand :) The business unit asked before the IT groups there and the estimate were 1.5 year in C# and 2 years in Java. It passed all the security tests of the bank. Now another bank is interested :) Stef On 04 Jan 2014, at 20:16, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > 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 >

Jan. 4, 2014