- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [Seaside-dev] Re: [Esug-list] [ANN] SmallHarbour project

by Nick Ager

Hi, We are in the process of adding support for deploying GLASS applications > into the Cloud Foundry, but I wouldn't mind helping folks who are interested > in adding support for other Smalltalks into the Cloud Foundry ... The Cloud > Foundry is written largely in ruby, so you'll need to be wearing your ruby > dancing shoes:) > There certainly a lot of (justified) buzz around CloudFoundry at the moment. Building CloudFoundry infrastructure for Smalltalk deployment would appear to be a great approach - married with a hosting service that provides that infrastructure as a service. Nick

May 18, 2011

[Pharo-project] suppressing the ob ast navigation

by Tudor Girba

Hi, In the latest OB, pressing ctrl+shift+(left/right)arrow gets you to navigate through the AST. This is certainly cool, but I could not find a usage for it yet :). But, the problem is that it overloads the ctrl+shift which in any text editor selects the previous/next word. If this feature is indeed wanted, could we find another keybinding solution for it? If not, how can I disable it in my image? Cheers, Doru -- www.tudorgirba.com "Presenting is storytelling."

May 18, 2011

[Pharo-project] Decompiler problem (leading to infinite loop of opening debuggers)

by Johan Brichau

Hi, In Pharo1.2.x, I get an infinite recursion of a debugger windows opening when I load a metacello config that has a problem in it. The relevant problem can be reconstructed (without the infinite loop :-) by evaluation the following: (MetacelloMCVersionSpec compiledMethodAt: #resolveToLoadableSpecs:map:) decompileWithTemps I'm absolutely no compiler guy, so I'm totally unaware of what is happening. But it's serious because I cannot debug the actual problem of the metacello config because of this. It was tried with Pharo1.2.1 and Pharo1.2.2-12353 and latest Cog VM (27 April 2011). I entered issue 4241 in the bug tracker for this. Johan

May 18, 2011

Re: [Pharo-project] [TODO] 1.3

by Norbert Hartl

That all makes completely sense. As I'm working with zinc now I'm going to switch to 1.3 immediately. Norbert Am 18.05.2011 um 09:18 schrieb Marcus Denker: > Current status: > > ==> all 1.3 builds are green > ==> Open Issues Core: 20 > ==> Open Issues Full: 3 > > So we are now in the state of "we could release next Friday". Thus the idea is now to steadily integrate what will happen, > while keeping the status green. > > Thus we can focus on other things as the Next Most Important Issue. e.g. > > Get VM build system in a state so we can ship 1.3 with VMs build by or Hudson (soon Jenkins): > > The idea here is to > > a) simplify the VM story. There are too many VMs, each with each own version-number. Very confusing. > b) not have to wait with deployment for a "maintainer" to release a VM every 2 years, but instead use the latest code base > within hours of a bugfix. > c) be able to actually improve the VM while in unstable. > > Thus we will > - provide a "Pharo Cog $VersionNumber" vm. This will make it easy to anwer the question of "which VM should I use" > - generate the archives one-click as well as the VMs listed on the website from the self-build VMs > > The good news is that we now have a window build slave, so we will soon have all 3 major architectures covered. > > On May 16, 2011, at 9:15 AM, Marcus Denker wrote: > >> Core >> ==== >> >> Open Issues: 20 >> http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D1.3 >> Failing Tests: 1 >> https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.3/lastCompleted… >> >> Full >> === >> Open Issues: 8 >> http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D1.3-DevImage >> Failing Tests: 3 >> https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.3/lastCompletedBuild/t… >> >> >> => Most important next Issue to tackle: Get all tests green. >> >> It would be nice to get both Core and Full green. Than the idea is that in the spirit of Continuous >> Delivery, we just keep it green. No degeneration of trivial problems (undeclards), fast roll-back of >> problematic changes... >> >> The idea is to keep it in a state that we could, at a minumum, always say "We could release next Friday". >> And the best would be: "We could release today". >> >> -- >> Marcus Denker -- http://www.marcusdenker.de >> INRIA Lille -- Nord Europe. Team RMoD. >> > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

May 18, 2011

Re: [Pharo-project] [Esug-list] [ANN] SmallHarbour project

by laurent laffont

On Wed, May 18, 2011 at 10:50 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > You should check out: > > http://vagrantup.com > > It could help you automate the build of virtual environments > (virtual box). > OK, thank you Torsten. Laurent. > > Bye > T. > > > -- > NEU: FreePhone - kostenlos mobil telefonieren und surfen! > Jetzt informieren: http://www.gmx.net/de/go/freephone > >

May 18, 2011

Re: [Pharo-project] [Esug-list] [ANN] SmallHarbour project

by laurent laffont

Thanks a lot Nick for your feedback, it is helpful. Laurent. On Wed, May 18, 2011 at 9:46 AM, Nick Ager <nick.ager(a)gmail.com> wrote: > Hi Romain, Laurent, > > >> Having Amazon ec2 image is also a very good idea, and some >>>> Smalltalkers have already made first important steps like: >>>> >>>> >>>> http://www.nickager.com/blog/Create-a-free-Gemstone-server-in-the-cloud-in-… >>>> >>> > After having shared the above Amazon AMI (Amazon machine image), and > experimented with EC2 hosting, I realised there are some undesirable > properties of AMIs: > > 1) It's an image; with all the benefits and problems that entails; namely > either you like the whole thing or not. It's not composable; it's difficult > to know precisely what has been configured and how, and difficult to choose > the bits you like and replace the bits you don't like. > 2) You can't (currently for Linux), create an AMI locally and upload it, > meaning everything has to be performed remotely and operating remotely in > the IDE over X11 forwarding can be slow. > 3) It's difficult to share across regions. Amazon's data centres operate > autonomously. I created the image in EU-WEST and copying it to US-WEST or > US-EAST is non-trivial. > 4) It's another configuration that I need to keep up to date and I don't. > 5) Not everyone wants to use EC2; other cloud services are available eg > slicehost, linode, cloud-foudry etc > 6) I configured the AMI using Amazon Linux, people might prefer Ubuntu, > RHEL, Suse, Windows!#*? etc > 7) I configured the AMI using Nginx as a front-end server with added > modules (http://nickager.com/blog/compiling-nginx-to-add-extra-modules/) > others might require other modules or other different server eg Apache, > Cherokee etc. Even with the same server the configuration required can vary > (url redirection, static file serving etc). > 8) Everyone has a different way of performing backups, monitoring the > health of the server. > 9) I configured the AMI using Gemstone, others might prefer image based > persistence or MySQL, Postgres etc. > 10) Ideally the configuration would allow you to specify the number of > images (or Gems for Gemstone) you'd like to respond to request, behind a > load balancer. > 11) We currently require infrastructure support for https eg stunnel or > reverse proxy through a webserver eg > http://www.monkeysnatchbanana.com/posts/2010/06/23/reverse-proxying-to-seas… > > Quite a list... The main issue is that I'd like to be able to build server > infrastructure from composable pieces and share configuration knowledge with > others. This led me to Chef (http://opscode.com/chef/) where people create > configuration "recipes" and a specific configuration is composed from these > recipes. The benefit of using something like Chef is that there are > already recipes for the standard parts of the server configuration eg > installing and configuring Apache, Nginx, MySql, Postgres etc have already > been taken care of. Chef abstracts the OS, and the cloud (eg EC2, slicehost > etc). > > The task is then to create recipes for Seaside specific parts. There are a > couple of Gemstone recipes already ( > https://github.com/timfel/gemstone-cookbooks, > https://github.com/johnnyt/gemstone-cookbooks) A few of us (myself > Norbert Hartl, Stephen Eggermont) plan to investigate coding our > configurations is Chef - though it's still early days and it may prove that > it's more complex than we need. > > Our basic requirements are to be able to rapidly deploy production, > staging, backup, Jenkins continuous integration and development VMs. > > Do others have experience with Chef or something similar? > > Ideally ESUG or someone else would provide http://www.heroku.com/ for > Seaside - but it would require formalising more of our stack and providing a > flexible solution to https. > > Hope this helps, > > Nick >

May 18, 2011

Re: [Pharo-project] SqueakDBX and MacOS X

by Olivier Auverlot

In my previous note, I have forget to say that it's necessary to modify the key SqueakPluginsBuiltInOrLocalOnly in the Info.plist file. The value of this parameter must be "false". There are also a little error. The temporary directory is "opendbx" and not "openDBX". Best regards Olivier ;-) www.auverlot.fr > Thanks a lot Olivier. > I know it is a pain. I suffered with my mac also. > So....I will update: > http://www.squeakdbx.org/Different%20backends%20under%20Mac > with your data. > > Thanks > > On Wed, May 18, 2011 at 10:10 AM, Olivier Auverlot > <olivier.auverlot(a)gmail.com <mailto:olivier.auverlot@gmail.com>> wrote: > > After many hours to try to install OpenDBX and SqueakDBX on my Mac > Intel with a 64 bit processor, I'm very happy to propose you a > little step by step tutorial. > > 1. Download the client libraries for MySQL and PostgreSQL. Warning > ! you must get the 32 bits version. Create a temporary directory > named "openDBX" where you want. For me, I have put the directory > at the root of my system path.My directory contains : > > > mysql > > 5.0 > > include > > lib > > PostgreSQL > > 9.0 > > include > > lib > > 2. Download openDBX and compile it in 32 bits mode (because the > Smalltalk virtual machine is a 32 bits application). I have write > a little shell script to produce the configuration of the > compiler.Of course, you must set the directories for the include > files and the librairies path. > > CFLAGS="-m32" \ > CXXFLAGS="-m32" \ > CPPFLAGS="-m32 -I/opendbx/PostgreSQL/9.0/include > -I/opendbx/mysql/5.0/include" \ > LDFLAGS="-m32 -L/opendbx/PostgreSQL/9.0/lib > -L/opendbx/mysql/5.0/lib" \ > ./configure --disable-utils --with-backends="mysql pgsql sqlite3" > > Run it and do : > make > make install > > All the files are copied in the /usr/local/lib directory and the > /usr/local/lib/opendbx subdirectory. > > 3. Copy the MySQL and PostgreSQL clients librairies into > /usr/local/bin (the include files are unused). > > 4. Now, you must launch Pharo to install SqueakDBX. > > > Gofer new squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfSqueakDBX'; > load. > > ConfigurationOfSqueakDBX project latestVersion load. > > Gofer new squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfGlorpDBX'; > load. > > ConfigurationOfGlorpDBX project latestVersion load. > > 5. You could remove the temporary "openDBX" directory (step 1). > > 6. The installation is completed. > > Olivier ;-) > www.auverlot.fr <http://www.auverlot.fr> > >> Hi Olivier, >> >> IIRC, you should: >> 1) fix the location problem by putting symlink in the right place. >> 2) ensure that your dylib is compiled for the right architecture >> (32bit) considering that current VMs are 32bits >> Perhaps this is your problem? >> what gives: >> >> $ lipo -info libopendbx.dylib >> >> #Luc >> >> >> >> 2011/5/17 Olivier Auverlot <olivier.auverlot(a)gmail.com >> <mailto:olivier.auverlot@gmail.com>> >> >> Hi, >> >> I try to use SqueakDBX on Mac OS X 10.6. I have downloaded >> and compiled the libraries for PostgreSQL, MySQL and finaly >> compiled and installed openDBX. >> >> CPPFLAGS="-I/opendbx/PostgreSQL/9.0/include >> -I/opendbx/mysql/5.0/include" >> LDFLAGS="-L/opendbx/PostgreSQL/9.0/lib -L/opendbx/mysql/5.0/lib" >> ./configure --disable-utils --with-backends="pgsql mysql sqlite3" >> >> Now, I have in /usr/local/lib: >> >> -rwxr-xr-x 1 root wheel 17040 17 mai 09:10 libopendbx.1.dylib >> -rw-r--r-- 1 root wheel 32584 17 mai 09:10 libopendbx.a >> lrwxr-xr-x 1 root wheel 18 17 mai 09:10 >> libopendbx.dylib -> libopendbx.1.dylib >> -rwxr-xr-x 1 root wheel 1001 17 mai 09:10 libopendbx.la >> <http://libopendbx.la> >> -rwxr-xr-x 1 root wheel 74624 17 mai 09:10 >> libopendbxplus.1.dylib >> -rw-r--r-- 1 root wheel 385056 17 mai 09:10 libopendbxplus.a >> lrwxr-xr-x 1 root wheel 22 17 mai 09:10 >> libopendbxplus.dylib -> libopendbxplus.1.dylib >> -rwxr-xr-x 1 root wheel 1054 17 mai 09:10 >> libopendbxplus.la <http://libopendbxplus.la> >> >> and in /usr/local/opendbx : >> -rwxr-xr-x 1 root wheel 17232 17 mai 09:10 >> libmysqlbackend.1.so <http://libmysqlbackend.1.so> >> -rw-r--r-- 1 root wheel 38960 17 mai 09:10 libmysqlbackend.a >> -rwxr-xr-x 1 root wheel 1051 17 mai 09:10 >> libmysqlbackend.la <http://libmysqlbackend.la> >> lrwxr-xr-x 1 root wheel 20 17 mai 09:10 >> libmysqlbackend.so -> libmysqlbackend.1.so >> <http://libmysqlbackend.1.so> >> -rwxr-xr-x 1 root wheel 16904 17 mai 09:10 >> libpgsqlbackend.1.so <http://libpgsqlbackend.1.so> >> -rw-r--r-- 1 root wheel 28624 17 mai 09:10 libpgsqlbackend.a >> -rwxr-xr-x 1 root wheel 1036 17 mai 09:10 >> libpgsqlbackend.la <http://libpgsqlbackend.la> >> lrwxr-xr-x 1 root wheel 20 17 mai 09:10 >> libpgsqlbackend.so -> libpgsqlbackend.1.so >> <http://libpgsqlbackend.1.so> >> -rwxr-xr-x 1 root wheel 16856 17 mai 09:10 >> libsqlite3backend.1.so <http://libsqlite3backend.1.so> >> -rw-r--r-- 1 root wheel 25936 17 mai 09:10 libsqlite3backend.a >> -rwxr-xr-x 1 root wheel 1053 17 mai 09:10 >> libsqlite3backend.la <http://libsqlite3backend.la> >> lrwxr-xr-x 1 root wheel 22 17 mai 09:10 >> libsqlite3backend.so -> libsqlite3backend.1.so >> <http://libsqlite3backend.1.so> >> >> ok... >> >> I have downloaded the OneClick distribution of Pharo 1.2.1 >> and installed SqueakDBX and GlorpDBX. >> >> Gofer new squeaksource: 'MetacelloRepository'; >> package: 'ConfigurationOfSqueakDBX'; >> load. >> >> ConfigurationOfSqueakDBX project latestVersion load. >> >> Gofer new squeaksource: 'MetacelloRepository'; >> package: 'ConfigurationOfGlorpDBX'; >> load. >> >> ConfigurationOfGlorpDBX project latestVersion load. >> >> Now, I try to do a SQL request to MySQL: >> >> connect >> | conn connectionSettings result | >> >> connectionSettings := DBXConnectionSettings >> host: 'mysql.domaine.fr <http://mysql.domaine.fr>' >> port: '3306' >> database: 'test' >> userName: 'username' >> userPassword: 'hello'. >> >> conn := DBXConnection >> platform: DBXMySQLPlatform new >> settings: connectionSettings. >> >> conn connect. >> >> conn open. >> result := conn execute: 'SELECT * from data'. >> >> DBXTranscript show: result. >> >> conn close. >> >> But I get an error : 'Unable to find function address' >> >> SqueakDBX didn't found the libraries ? I have try to copy the >> librairies in /usr/lib and /usr/lib/opendbx but with no >> results. In the Resources subdirectory, I have created a >> symbolic link to /usr/local/lib/libopendbx.dylib but without >> progress. >> >> ln -s /usr/local/lib/libopendbx.dylib opendbx >> >> I get the same error :-( >> >> If i modify the info.plist file to set the SqueakDebug key at >> 1 and the SqueakPluginsBuiltInOrLocalOnly key at false, I can >> see the search of librairies by the SqueakVM. The SqueakVM >> doesn't seem to try to load the openddbx libraries. >> >> You can download the log file at >> http://www.auverlot.fr/squeakdbx/squeakdbx.txt >> >> My previous tests under Linux have worked fine but i didn't >> find a solution with Mac OS X. Someone has an idea for help >> me ??? >> >> Thanks for your help. >> >> Best regards >> Olivier >> www.auverlot.fr <http://www.auverlot.fr> >> >> >> > > > > > -- > Mariano > http://marianopeck.wordpress.com >

May 18, 2011

Re: [Pharo-project] [TODO] 1.3

by Tudor Girba

Thanks, Marcus. This is great! We are now moving Moose to build on 1.3. Cheers, Doru On 18 May 2011, at 09:18, Marcus Denker wrote: > Current status: > > ==> all 1.3 builds are green > ==> Open Issues Core: 20 > ==> Open Issues Full: 3 > > So we are now in the state of "we could release next Friday". Thus the idea is now to steadily integrate what will happen, > while keeping the status green. > > Thus we can focus on other things as the Next Most Important Issue. e.g. > > Get VM build system in a state so we can ship 1.3 with VMs build by or Hudson (soon Jenkins): > > The idea here is to > > a) simplify the VM story. There are too many VMs, each with each own version-number. Very confusing. > b) not have to wait with deployment for a "maintainer" to release a VM every 2 years, but instead use the latest code base > within hours of a bugfix. > c) be able to actually improve the VM while in unstable. > > Thus we will > - provide a "Pharo Cog $VersionNumber" vm. This will make it easy to anwer the question of "which VM should I use" > - generate the archives one-click as well as the VMs listed on the website from the self-build VMs > > The good news is that we now have a window build slave, so we will soon have all 3 major architectures covered. > > On May 16, 2011, at 9:15 AM, Marcus Denker wrote: > >> Core >> ==== >> >> Open Issues: 20 >> http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D1.3 >> Failing Tests: 1 >> https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.3/lastCompleted… >> >> Full >> === >> Open Issues: 8 >> http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D1.3-DevImage >> Failing Tests: 3 >> https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.3/lastCompletedBuild/t… >> >> >> => Most important next Issue to tackle: Get all tests green. >> >> It would be nice to get both Core and Full green. Than the idea is that in the spirit of Continuous >> Delivery, we just keep it green. No degeneration of trivial problems (undeclards), fast roll-back of >> problematic changes... >> >> The idea is to keep it in a state that we could, at a minumum, always say "We could release next Friday". >> And the best would be: "We could release today". >> >> -- >> Marcus Denker -- http://www.marcusdenker.de >> INRIA Lille -- Nord Europe. Team RMoD. >> > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > -- www.tudorgirba.com "When people care, great things can happen."

May 18, 2011

[Pharo-project] [Esug-list] [ANN] SmallHarbour project

by Torsten Bergmann

You should check out: http://vagrantup.com It could help you automate the build of virtual environments (virtual box). Bye T. -- NEU: FreePhone - kostenlos mobil telefonieren und surfen! Jetzt informieren: http://www.gmx.net/de/go/freephone

May 18, 2011

[Pharo-project] Branded Cog for Win32 for Build slave (Was: [TODO] 1.3)

by Torsten Bergmann

>provide a "Pharo Cog $VersionNumber" vm. > >The good news is that we now have a window build slave, so we will soon have >all 3 major architectures covered Nice - the windows build slave arrived! Who maintains it? So I expect the build slave to 1. get the code from Eliots svn repository 2. patch the code to "brand" the vm with custom Pharo icon and label 3. Replace the name of the VM to build in the Makefile 4. build it for use in OneClick or installer or to provide a zip Similar to what I've done so far manually. OK, so attached is the "patch" for branding the Cog VM for Win32 back from the Cog2378 that I used for Pharo 1.2.2. - PharoCog.def.in (always a copy of Squeak.def.in) - PharoCog.ico (the custom icon for PharoCog) - PharoCog.rc (the resource file including labeling and version) Copy these three files in the same directory as the "Makefile" Now set the name in the Makefile: # The name of the VM to build VM:=PharoCog Now you can build. Best would be to generate the "PharoCog.rc" from a Smalltalk in the Hudson slave build script, so the version number (which is the same as the one Eliot gives to Cog) is set dynamically. VALUE "FileDescription", "Pharo Cog Virtual Machine Revision 2378\0" VALUE "FileVersion", "1.2.2378\0" So 1.2.2378 means Pharo 1.2 with Cog 2378. If in doubt ask me. Who is building the slave? We should do the same also for the standard VM (which is a little bit different and with a different icon). We can also let the build slave (beside one click) create the full setup/installer. Thx Torsten -- NEU: FreePhone - kostenlos mobil telefonieren und surfen! Jetzt informieren: http://www.gmx.net/de/go/freephone

May 18, 2011