August 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Hudson Question
by Lukas Renggli Aug. 26, 2010

Aug. 26, 2010

Below the Hudson Build Configurations for the images you mentioned: === Pharo === mkdir -p "download" curl --silent --location "$DOWNLOAD" > "download.zip" unzip -p "download.zip" "*/*.image" > "download/download.image" unzip -p "download.zip" "*/*.changes" > "download/download.changes" build-resize.sh download 1280 800 build.sh -i download -s settings -s killtests -o pharo build.sh -i download -s settings -s testrunner -s runalltests -o pharo-test rm -rf download rm download.zip === Development === build.sh -i pharo -s omnibrowser -o omnibrowser build.sh -i omnibrowser -s testrunner -s omnibrowser-tests -o omnibrowser-tests build-oneclick.sh -i omnibrowser -o Pharo-OneClick -n Pharo -t "Pharo Development" -v 1.1 -c Pharo === Seaside 3.0 === build.sh -i omnibrowser -s seaside3 -s seaside3-komanche -s seaside-design -o seaside3 build.sh -i seaside3 -s testrunner -s seaside3-tests -o seaside3-tests build.sh -i seaside3 -s seaside3-swazoo -o seaside3-swazoo build-oneclick.sh -i seaside3 -o Seaside-3.0-OneClick -n Seaside -t Seaside -v 3.0 -c Seaside On 26 August 2010 12:36, Sven Van Caekenberghe <sven(a)beta9.be> wrote: > > On 26 Aug 2010, at 12:08, Lukas Renggli wrote: > >>> If I click on a artifact, say Seaside 3.0, is it then somehow possible to see the actual build script that was used ? >> >> The build script deletes it after a successful build. Maybe the script >> should be left there? >> >>> I know about your github builder repository, and I learned a lot from it, but the scripts their do not seem to match 100%, or do they ? >> >> Yeah, they should match 100%. >> >> However note that I don't build images from scratch all the time, but >> they build on top of each other: >> >> Pharo --> Development --> Seaside 3 --> Magritte 2 --> Pier 2 >> Â Â Â Â Â Â Â Â Â Â Â Â \--> Seaside 2 --> Magritte --> Pier >> Â Â Â Â Â Â Â Â Â Â Â Â \--> PetitParser >> Â Â Â Â Â Â Â Â Â Â Â Â ... >> >> Lukas >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch > > Well, I am looking at the scripts in the git repo. > There seems to be no script for Pharo (I guess you download core and run the tests). > There seems to be no script for Development. > I guess that Seaside 3.0 is seaside3.st + seaside3-komanche.st, but I am not sure. > > I would like to try to build these myself (not that the ones from Hudson are bad, I just want to learn from this). > > Sven > > -- Lukas Renggli www.lukas-renggli.ch

2 4

[Pharo-project] DNU after updating 1.2 core image
by Guillermo Polito Aug. 26, 2010

Aug. 26, 2010

When you right click over the category panel and the method category panel in the system browser. ByteString DNU lines Guille

3 2

Re: [Pharo-project] Hudson Question
by Lukas Renggli Aug. 26, 2010

Aug. 26, 2010

> If I click on a artifact, say Seaside 3.0, is it then somehow possible to see the actual build script that was used ? The build script deletes it after a successful build. Maybe the script should be left there? > I know about your github builder repository, and I learned a lot from it, but the scripts their do not seem to match 100%, or do they ? Yeah, they should match 100%. However note that I don't build images from scratch all the time, but they build on top of each other: Pharo --> Development --> Seaside 3 --> Magritte 2 --> Pier 2 \--> Seaside 2 --> Magritte --> Pier \--> PetitParser ... Lukas -- Lukas Renggli www.lukas-renggli.ch

2 2

[Pharo-project] cog vm
by Tudor Girba Aug. 26, 2010

Aug. 26, 2010

Hi, Is there anybody using the Cog VM on a regular basis? I am using it for most of my development, and it now works quite well (except for the methods as objects issue). It would be interesting to collect problem reports. Cheers, Doru -- www.tudorgirba.com "To lead is not to demand things, it is to make them happen."

9 19

[Pharo-project] A look at seaside and pharo from a Rails/Ruby perspective
by Marcus Denker Aug. 26, 2010

Aug. 26, 2010

Hi, It's always interesting how things are seen from the outside... (from http://on-ruby.blogspot.com/2010/08/rubyweb-interview-with-pat-maddox.html seems there will be a talk about seaside at a ruby conference early september...) --> begin quote Seaside is interesting technology, how did you discover it? ------------------------------------------------------------ Pat Seaside is a fascinating and fun technology!! I came across it a few years ago, not long after I got into Rails. Over the years I had a couple of false starts with it...it's a bit opaque at first because the development environment is so different from anything I'm used to. And it's only fairly recently with Pharo that it's become easier to get started, because it's such a clean environment geared towards development. Also the documentation for both Pharo and Seaside are getting really good. There are free books on each at pharobyexample.org and book.seaside.st/book. Okay as for what's so interesting to me about Seaside... it's 50% the framework and 50% the Pharo environment. Seaside itself represents a step forward in web development similar to how Rails did. Rails takes care of a lot of the plumbing for you - you don't have to parse query params, set up response headers, manage the session (unless you want to of course). Seaside does all that of course but also manages application state for you. So you don't have to worry about putting stuff into a database, then pulling it back out and operating on it. I can't do it justice in a few sentences, but that's why I'll be showing lots of examples at the conference! :) At any rate, that same feeling you get when you code Rails for the first time and see how much easier things are, you get that same feeling with Seaside. It's not a replacement for Rails by any means - Rails definitely has a sweet spot, particularly when it comes to RESTful websites and interoperability with the unix ecosystem - but for the things that Seaside is strong at (which for me so far has been complex and/or configurable workflows), it runs circles around everything else. The other thing I'm loving about Seaside development is Pharo, an open-source smalltalk environment. Smalltalk is a great language, and Pharo has great tools that allow you to discover everything in the system. Honestly it makes RubyMine or etags look plain silly. The best bit is that nearly everything in Pharo is implemented in smalltalk, including all of the tools. So if you want to see the mechanics of a refactoring tool, and even build your own, it's trivial to do so, because it's just smalltalk code. Wow this answer got long. I could go on all day about this stuff. Gonna stop now. --> end quote -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] [update 1.2] #12113
by Marcus Denker Aug. 26, 2010

Aug. 26, 2010

12113 ----- Issue 2863: BlockClosure>>assert: is the same as in Object Issue 2861: tiny dead code removal, mostly Morph Issue 2853: Unnecessary URLArgumentList>>associationsDo Issue 2845: remove PluggableMultiColumnListMorphByItem and some unsent partbin related methods. -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Philippe's WebClient patches
by StÃ©phane Ducasse Aug. 26, 2010

Aug. 26, 2010

Hi guys Philippe sent me these patches that apparently did not get into the webclient trunk. I will integrate them later with our fork since it does not seem possible otherwise. Stef > Anyway here are my patches. > > > Cheers > Philippe >

4 11

[Pharo-project] [update 1.2] #12112
by stephane ducasse Aug. 25, 2010

Aug. 25, 2010

- Issue 1899: MethodDictionary improvement. Part two. - Issue 2560: Convenient methods from Grease for Strings. We should get more of them. We need cool libraries. - Issue 2857: improve String to Number conversion. readFrom: now raises an error instead of silently returning 0. Thanks Guillermo Polito. Stef

1 0

[Pharo-project] Really funny bug... :(
by stephane ducasse Aug. 25, 2010

Aug. 25, 2010

Hi guys I was integrated the methodDictionary enh of levente. And after I integrated the addition of some methods into String. Then it seems that I got all the packages extending String dirty. I checked the changes and nothing special. The changed methods are not logged in the changeSorter. So may be the dictionary got rehashed, changed and all the methods went to get "changed". Strange. Stef

1 0

Aug. 25, 2010

12111 ----- - Issue 1899: MethodDictionary improvement part one. Thanks Levente Uzonyi and Guillermo Polito. - Philipp fixes for WebClient. Thanks Philippe Marshall and Sven Van Caekenberghe. Stef

1 0