March 2011 - Pharo-dev - lists.pharo.org

[Pharo-project] a slim holiday present, cpic
by Eliot Miranda March 6, 2011

March 6, 2011

Hi All, don't know if this is useful to you or whether you've already written it yourself but I finally caved and wrote a shell command that copies an image/changes file pair, replacing the hundreds of times I've issued the two parallel commands, cpic = copy image and changes. Happy holidays -------8<------- #!/bin/sh # copy image and changes force=0 if [ "$1" = -f ]; then force=1 shift fi if [ $# != 2 -o "$1" = "-?" -o "$1" = --help ]; then echo "usage: $0 [-f] image-name-no-ext [image-name-no-ext|dir]" test $# != 2 && exit 1 exit 0 fi if [ -f "$2.image" -o -f "$2.changes" ]; then if [ "$force" = 0 ]; then echo "$2.image and/or $2.changes already exist." 1>&2 exit 1 fi elif [ -d "$2" ]; then if [ -f "$2/$1.image" -o -f "$2/$1.changes" ]; then if [ "$force" = 0 ]; then echo "$2/$1.image and/or $2/$1.changes already exist." 1>&2 exit 1 fi fi cp "$1.image" "$1.changes" "$d" exit 0 fi cp "$1.image" "$2.image" cp "$1.changes" "$2.changes"

3 4

[Pharo-project] Fwd: SIXX in Pharo 1.2
by Serge Stinckwich March 6, 2011

March 6, 2011

Thanks to Umezawa-san SIXX is working now on Pharo 1.2 & Squeak 4.2. All 127 tests are green under Pharo 1.2 ! To load the last version of SIXX: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSIXX'; load. (Smalltalk at:#ConfigurationOfSIXX) load. Regards ---------- Forwarded message ---------- From: Masashi UMEZAWA <masashi.umezawa(a)gmail.com> Date: Sat, Mar 5, 2011 at 7:25 PM Subject: Re: SIXX in Pharo 1.2 To: Serge Stinckwich <serge.stinckwich(a)gmail.com> Hi Serge-san, Sorry for the delayed reply. I've updated ConfigurationOfSIXX. I believe the latest SIXX runs on Pharo 1.2 and Squeak 4.2 nicely. Best regards, 2011/2/22 Masashi UMEZAWA <masashi.umezawa(a)gmail.com>: > Hi Serge-san, > > Updating XMLSupport to version: '1.1.7', I was able to reproduce the > test failures. > According to ConfigurationOfSIXX, SIXX assumes XMLSupport 1.0.0. > So I need to catch up new XMLSupport APIs... > > Best regards, > > 2011/2/22 Serge Stinckwich <serge.stinckwich(a)gmail.com>: >> On Mon, Feb 21, 2011 at 8:41 PM, Masashi UMEZAWA >> <masashi.umezawa(a)gmail.com> wrote: >>> Hi Serge-san, >>> >>> I've updated Pharo 1.2 to the latest version.(#12336). >>> And loaded SIXX via ConfigurationOfSIXX ( >=0.3.4 [ConfigurationOfSIXX]). >>> >>> Luckily all the tests were green. Perhaps there were some temporary problems? >> >> Hum ... strange. I try again with a PharoOneClick1.2 version (#12336). >> I have some problems with deprecated methods : >> >> The method XMLNodeWithElements topElement has been deprecated. >> use #firstElement instead >> >> Are you running the SIXXTests ? >> >> Regards, >> -- >> Serge Stinckwich >> UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam >> Every DSL ends up being Smalltalk >> http://doesnotunderstand.org/ >> > -- > [:masashi | ^umezawa] > -- [:masashi | ^umezawa] -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

2 1

[Pharo-project] Fwd: Https Url in Pharo 1.2
by Stephan Eggermont March 6, 2011

March 6, 2011

Stef wrote: >On Mar 6, 2011, at 8:39 AM, laurent laffont wrote: > Is it planed / possible to have SqueakSSL plugin in official VM shipped with Pharo ? >What is the license? You know the last time we got trapped into the game "oh I did not decided yet" so never again. >What is the status? On squeaksource it is MIT, last update from jan. 12. Stephan

1 0

Re: [Pharo-project] [squeak-dev] [ANN] ESUG supports once again SqueakDBX
by Mariano Martinez Peck March 6, 2011

March 6, 2011

On Sun, Mar 6, 2011 at 12:40 PM, Levente Uzonyi <leves(a)elte.hu> wrote: > On Fri, 4 Mar 2011, Mariano Martinez Peck wrote: > > We are really happy to announce that ESUG will sponsor us once again >> through >> the ESUG Summer Talk project. This means that we have reached the ESUG >> expectations and that they still think that relational database access is >> an >> important matter in Smalltalk. >> > > snip > > 5) Cog compatibility. >> > > What has to be done? > > Indeed, nothing. We were not sure if FFI was working on it, but it turns out that it was. The idea is to be aware if Eliot releases a threaded VM/FFI so that we do not lock the VM (even if we have our micro-lock strategy when possible) > > >> 6) Use Alien instead of FFI. >> Eliot is working on a threaded CogVM. One of the projects of the GSoC of >> this year was to make something similar to a threaded FFI. What the >> student >> did is a modification in Alien (I think) that can be run in a >> multithreaded >> envirorment. He worked with Eliot. The idea is when Eliot releases the >> threaded CogVM, this FFI would work our of the box, and would avoid >> locking >> the WHOLE vm while a C function is being invoked (as it happens today with >> FFI).....So....when that VM is released, we MUST migrate to that). >> > > How is Alien better than FFI? We do not know. However, we will not spend time in Alien unless it is working out of the box and integrated in all standard VMs. > AFAIK Alien itself is not developed anymore, > parts of it will be merged with FFI. > > Ahh ok, we didn't know. Thnkas. > > Levente > > P.S.: http://www.squeaksource.com/SqueakDBX.html states that code in the > repository has MIT license, but it includes Glorp which has LGPL(S) license. > > Yes, the problem is that SqueakDBX as itself (the database driver), is MIT. Thus, the repository is MIT. Glorp is LGPL. When we started (years after SqueakDBX) with GlorpDBX, we found it easier to commit our changes to SqueakDBX repo instead of the Glorp one (because not everybody may agree with our changes). The good news is that Alan Night was considering making Glorp MIT. I cc'ed him to see if there are news. Cheers Mariano

1 0

[Pharo-project] defaultBorderColor and defaultBorderStyle
by DougEdmunds March 6, 2011

March 6, 2011

Styles ( such as #inset, #raised, etc) should be separated out from non-intuitive "defaultBorderColor" methods and consistently replaced with defaultBorderStyle. For example, Slider>>defaultBorderColor is #inset. Slider>>defaultBorderStyle would be much clearer. -- View this message in context: http://forum.world.st/defaultBorderColor-and-defaultBorderStyle-tp3337429p3… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

2 1

[Pharo-project] Pharo 1.2 and test failures
by Norbert Hartl March 6, 2011

March 6, 2011

Today I had a look at the hudson server. For pharo 1.2 dev there was only one bug left. So I took a look and fixed it http://code.google.com/p/pharo/issues/detail?id=3784 Two hours later there was a new build in hudson and then there were three bugs (one of these is the fixed one which hasn't been integrated). How can this happen? Norbert

3 4

[Pharo-project] Add to website Re: [Pharo-users] Pharo-project weekly summary #4
by Mariano Martinez Peck March 6, 2011

March 6, 2011

Hi. These summaries are awesome. Can we link to them somehow from pharo web site? Maybe we can have two sections under news: one with what is now (the blog) and another one with this summaries (just a text explaining what it is and a link to the original website) cheers mariano On Sun, Mar 6, 2011 at 10:02 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Yes! > > On Mar 5, 2011, at 10:16 PM, Tudor Girba wrote: > > > Thanks :) > > > > Doru > > > > > > On 5 Mar 2011, at 22:06, Francois Stephany wrote: > > > >> Hi guys, > >> > >> The summary for this week is out. Please comment if I said something > stupid or forgot something. > >> > >> http://articles.tulipemoutarde.be/pharo-mailing-list-weekly-summary-4 > >> > >> See you next week ;) > >> > > > > -- > > www.tudorgirba.com > > > > "From an abstract enough point of view, any two things are similar." > > > > > > > > > > >

1 0

Re: [Pharo-project] Pharo 1.2 and test failures
by Marcus Denker March 6, 2011

March 6, 2011

On Mar 6, 2011, at 10:00 AM, StÃ©phane Ducasse wrote: > We should remove the tests only crashing on the server for now. > It's not that simple... a test started failing just yesterday. So I think the problem is that we are not loading a *fixed* set of versions, but a changed one. e.g. someone commits a new version of a project --> it's loaded in 1.2 We need to change that. Especially considering that we want to build 1.3, too. (we never build a 1.3 Full image...). And there is 1.1, too, where the loaded packages seem to change depending on the moon, or something... All in all, maybe we should re-think if how we do the full image is sustainable? Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] OOCompletion not working in Worksapce
by Hilaire Fernandes March 6, 2011

March 6, 2011

I build friday automatically a DrGeo release just to see that now OOCompletion does not work in Workspace. Build done with a Pharo 1.3. Can someone confirm? Hilaire

2 3

[Pharo-project] Pharo-project weekly summary #4
by Francois Stephany March 6, 2011

March 6, 2011

Hi guys, The summary for this week is out. Please comment if I said something stupid or forgot something. http://articles.tulipemoutarde.be/pharo-mailing-list-weekly-summary-4 See you next week ;)

3 2