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

Re: [Pharo-project] Website RSS feed broken?

by Max Leske

I'll check if this might be a cmsbox bug. Since Adrian's Blog is also affected, this might well be the case. I'll keep you posted. Max On 31.08.2011, at 07:41, Damien Cassou wrote: > On Tue, Aug 30, 2011 at 10:46 PM, Mariano Martinez Peck > <marianopeck(a)gmail.com> wrote: >> Hi Stefan, I've noticed the same problem :( > > I confirm, and this also happens with Adrian's blog: > http://www.adrian-lienhard.ch/blog > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Lambdas are relegated to relative obscurity until Java makes them > popular by not having them." James Iry >

Aug. 31, 2011

Re: [Pharo-project] Website RSS feed broken?

by Damien Cassou

On Tue, Aug 30, 2011 at 10:46 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Hi Stefan, I've noticed the same problem :( I confirm, and this also happens with Adrian's blog: http://www.adrian-lienhard.ch/blog -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Aug. 31, 2011

Re: [Pharo-project] Squeaksource.com (was: [squeak-dev] Re: Addition to "About Pharo" dialog)

by Alexander LazareviÄ

2011/8/30 Tobias Pape <Das.Linux(a)gmx.de> > What do you mean by project page? > Just a simple page that has some Whys, Whos, Hows, Whats and Whats nots! Maybe something like this [1]. Alex [1] http://swagger.wordnik.com/

Aug. 31, 2011

Re: [Pharo-project] Deprecation policy

by csrabak＠bol.com.br

Aug. 31, 2011

Re: [Pharo-project] Gofer/Metacello problem in 1.4 [WAS] Re: DBXTalkand Pharo 1.4

by Dale Henrichs

Laszlo, Good ... I am planning a new release of Metacello in the near future (got to clear a couple of other things from my plate first) and it will include the pharo1.4.x attribute I will also run full test suite etc. on Pharo1.4 at that time ... Dale ----- Original Message ----- | From: "Laszlo Zsolt Kiss" <lzskiss(a)dublin.ie> | To: Pharo-project(a)lists.gforge.inria.fr | Sent: Tuesday, August 30, 2011 3:27:59 PM | Subject: Re: [Pharo-project] Gofer/Metacello problem in 1.4 [WAS] Re: DBXTalkand Pharo 1.4 | | hi. | I tested this. | First load the: | | | 'Metacello-Base-DaleHenrichs.19' | 'Metacello-Core-DaleHenrichs.455' | 'Metacello-MC-DaleHenrichs.505' | | | then: | | | | Gofer it | squeaksource: 'MetacelloRepository'; | package: 'ConfigurationOfOpenDBXDriver'; | load. | | | then: | | | ((Smalltalk globals at: #ConfigurationOfOpenDBXDriver) project | version: '1.0') load. | | | I gived just two warnings, after I proceed these warnings the DBXTalk | was loaded to the 1.4 #14112 image | Not the nice solution, but working with the 1.4. | I tested with the Firebird 2.5 on the Win32 platform. | | | Best regards. | | | Laszlo Zsolt | | | | ----- Original Message ----- | | | From: Pharo-project(a)lists.gforge.inria.fr | | To: <Pharo-project(a)lists.gforge.inria.fr> | | Cc: <dbxtalk(a)googlegroups.com> | | Sent: Tue, 30 Aug 2011 14:26:28 -0700 (PDT) | | Subject: Re: [Pharo-project] Gofer/Metacello problem in 1.4 [WAS] Re: | DBXTalk and Pharo 1.4 | | | Mariano, | | I think that addVersion: is very old gofer/metacello code ... not | fancy new code. It sounds like an old version of Metacello is being | loaded/bootstrapped. #addVersion: isn't sent from the current code | base ... At a minimum, you should have these packages loaded: | | 'Metacello-Base-DaleHenrichs.19' | 'Metacello-Core-DaleHenrichs.455' | 'Metacello-MC-DaleHenrichs.505' | | if the bootstrapping process is working. | | Keep in mind that pharo1.4.x has not yet been defined in Metacello | (see Issue 4613[1]), so there will be other Metacello issues in 1.4 | for the moment ... the proposed bugfix in 4613 would mean that a new | version of Metacello would no longer be needed to define the | platform specific attributes ... | | Dale | | [1] http://code.google.com/p/pharo/issues/detail?id=4613 | | ----- Original Message ----- | | From: "Mariano Martinez Peck" < marianopeck(a)gmail.com > | | To: dbxtalk(a)googlegroups.com , "Pharo Development" < | | pharo-project(a)lists.gforge.inria.fr > | | Sent: Tuesday, August 30, 2011 2:00:26 PM | | Subject: [Pharo-project] Gofer/Metacello problem in 1.4 [WAS] Re: | | DBXTalk and Pharo 1.4 | | | | | | | | | | On Tue, Aug 30, 2011 at 9:14 PM, Laszlo Zsolt Kiss < | | lzskiss(a)gmail.com > wrote: | | | | | | | | | | hi. | | first i load the ConfigurationOfOpenDBX and the 1.4 version is | | missing from the spec.: | | | | | | | | stable: spec | | <symbolicVersion: #stable> | | | | spec for: #'pharo1.2.x' version: '1.0'. | | spec for: #'pharo1.3.x' version: '1.0'. | | | | | | then i added the next line to the spec: | | | | | | spec for: #'pharo1.4.x' version: '1.0'. | | | | | | then i probally do it this: | | | | | | (((Smalltalk globals at: #ConfigurationOfOpenDBXDriver) perform: | | #project) perform: #version: with: #stable) load. | | | | | | i gived back a warring: | | | | | | | | "The method Gofer addVersion: has been deprecated. | | Instead of #addVersion: simply use #version: | | | | Hi. Yes, I can reproduce this problem :( | | | | | | | | | | | | | | | | | | Select Proceed to continue, or close this window to cancel the | | operation." | | | | | | I proceed this warrning. | | | | | | Then gived back an error message, I think this error came from the | | Metacello. | | | | I attached the PharoDebug file. | | | | | | | | | | The error is in the method #updateProject where it does: | | | | (GoferPackageReference name: mgr packageName repository: mgr | | repositoryGroup) versionReference. | | | | GoferPackageReference dnu #name:repository: instead, it is | | implemented in GoferResolvedReference | | | | | | Dale any idea? | | | | Versions: Gofer-Core-StephaneDucasse.135. | | Metacello version is ...... ConfigurationOfMetacello project | | currentVersion raises dnu #setName | | | | So...I guess Pharo 1.4 is using a very new version of Gofer, which | | brings lot of changes that break Metacello ? | | | | Thanks! | | | | | | | | | | | | | | | | | | Byte | | Laszlo Zsolt | | | | | | Ps: the image is clean #14112 and the CogVM is the last.. | | | | | | inez Peck < marianopeck(a)gmail.com > | | | | | | | | | | | | | | | | | | | | On Tue, Aug 30, 2011 at 9:53 AM, Laszlo Zsolt Kiss < | | lzskiss(a)gmail.com > wrote: | | | | | | Hi Developers! | | | | | | Can I use any way this combination: DBXTalk with Pharo 1.4? | | | | Hi. Yes, sure. Did you try it? You shouldn't have any problem. | | Please let us know if you do have. | | | | | | -- | | Mariano | | http://marianopeck.wordpress.com | | | | | | | | | | | | -- | | Mariano | | http://marianopeck.wordpress.com | | | | | |

Aug. 30, 2011

Re: [Pharo-project] Gofer/Metacello problem in 1.4 [WAS] Re: DBXTalkand Pharo 1.4

by Laszlo Zsolt Kiss

hi.I tested this.First load the: Â 'Metacello-Base-DaleHenrichs.19' 'Metacello-Core-DaleHenrichs.455' 'Metacello-MC-DaleHenrichs.505' then: Gofer itÂ Â squeaksource: 'MetacelloRepository';Â Â package: 'ConfigurationOfOpenDBXDriver';Â Â load. then: ((Smalltalk globals at: #ConfigurationOfOpenDBXDriver) project version: '1.0') Â load. I gived just two warnings, after I proceed these warnings the DBXTalk was loaded to the 1.4 #14112 image.Not the nice solution, but working with the 1.4.I tested with the Firebird 2.5 on the Win32 platform. Best regards. Laszlo Zsolt ----- Original Message ----- From: Pharo-project(a)lists.gforge.inria.fr To: Cc: Sent:Tue, 30 Aug 2011 14:26:28 -0700 (PDT) Subject:Re: [Pharo-project] Gofer/Metacello problem in 1.4 [WAS] Re: DBXTalk and Pharo 1.4 Mariano, I think that addVersion: is very old gofer/metacello code ... not fancy new code. It sounds like an old version of Metacello is being loaded/bootstrapped. #addVersion: isn't sent from the current code base ... At a minimum, you should have these packages loaded: 'Metacello-Base-DaleHenrichs.19' 'Metacello-Core-DaleHenrichs.455' 'Metacello-MC-DaleHenrichs.505' if the bootstrapping process is working. Keep in mind that pharo1.4.x has not yet been defined in Metacello (see Issue 4613[1]), so there will be other Metacello issues in 1.4 for the moment ... the proposed bugfix in 4613 would mean that a new version of Metacello would no longer be needed to define the platform specific attributes ... Dale [1] http://code.google.com/p/pharo/issues/detail?id=4613 [1] ----- Original Message ----- | From: "Mariano Martinez Peck" | To: dbxtalk(a)googlegroups.com [3], "Pharo Development" | Sent: Tuesday, August 30, 2011 2:00:26 PM | Subject: [Pharo-project] Gofer/Metacello problem in 1.4 [WAS] Re: DBXTalk and Pharo 1.4 | | | | | On Tue, Aug 30, 2011 at 9:14 PM, Laszlo Zsolt Kiss < | lzskiss(a)gmail.com [5] > wrote: | | | | | hi. | first i load the ConfigurationOfOpenDBX and the 1.4 version is | missing from the spec.: | | | | stable: spec | | | spec for: #'pharo12.x' version: '1.0'. | spec for: #'pharo1.3.x' version: '1.0'. | | | then i added the next line to the spec: | | | spec for: #'pharo1.4.x' version: '1.0'. | | | then i probally do it this: | | | (((Smalltalk globals at: #ConfigurationOfOpenDBXDriver) perform: | #project) perform: #version: with: #stable) load. | | | i gived back a warring: | | | | "The method Gofer addVersion: has been deprecated. | Instead of #addVersion: simply use #version: | | Hi. Yes, I can reproduce this problem :( | | | | | | | | | Select Proceed to continue, or close this window to cancel the | operation." | | | I proceed this warrning. | | | Then gived back an error message, I think this error came from the | Metacello. | | I attached the PharoDebug file. | | | | | The error is in the method #updateProject where it does: | | (GoferPackageReference name: mgr packageName repository: mgr | repositoryGroup) versionReference. | | GoferPackageReference dnu #name:repository: instead, it is | implemented in GoferResolvedReference | | | Dale any idea? | | Versions: Gofer-Core-StephaneDucasse.135. | Metacello version is ...... ConfigurationOfMetacello project | currentVersion raises dnu #setName | | So...I guess Pharo 14 is using a very new version of Gofer, which | brings lot of changes that break Metacello ? | | Thanks! | | | | | | | | | Byte | Laszlo Zsolt | | | Ps: the image is clean #14112 and the CogVM is the last.. | | | inez Peck < marianopeck(a)gmail.com [6] > | | | | | | | | | | On Tue, Aug 30, 2011 at 9:53 AM, Laszlo Zsolt Kiss < | lzskiss(a)gmail.com [7] > wrote: | | | Hi Developers! | | | Can I use any way this combination: DBXTalk with Pharo 1.4? | | Hi. Yes, sure. Did you try it? You shouldn't have any problem. | Please let us know if you do have. | | | -- | Mariano | http://marianopeck.wordpress.com [8] | | | | | | -- | Mariano | http://marianopeck.wordpress.com [9] | | Links: ------ [1] http://code.google.com/p/pharo/issues/detail?id=4613 [2] mailto:marianopeck@gmail.com [3] mailto:dbxtalk@googlegroups.com [4] mailto:pharo-project@lists.gforge.inria.fr [5] mailto:lzskiss@gmail.com [6] mailto:marianopeck@gmailcom [7] mailto:lzskiss@gmail.com [8] http://marianopeck.wordpress.com [9] http://marianopeck.wordpress.com

Aug. 30, 2011

Re: [Pharo-project] Gofer/Metacello problem in 1.4 [WAS] Re: DBXTalk and Pharo 1.4

by Dale Henrichs

Mariano, I think that addVersion: is very old gofer/metacello code ... not fancy new code. It sounds like an old version of Metacello is being loaded/bootstrapped. #addVersion: isn't sent from the current code base ... At a minimum, you should have these packages loaded: 'Metacello-Base-DaleHenrichs.19' 'Metacello-Core-DaleHenrichs.455' 'Metacello-MC-DaleHenrichs.505' if the bootstrapping process is working. Keep in mind that pharo1.4.x has not yet been defined in Metacello (see Issue 4613[1]), so there will be other Metacello issues in 1.4 for the moment ... the proposed bugfix in 4613 would mean that a new version of Metacello would no longer be needed to define the platform specific attributes ... Dale [1] http://code.google.com/p/pharo/issues/detail?id=4613 ----- Original Message ----- | From: "Mariano Martinez Peck" <marianopeck(a)gmail.com> | To: dbxtalk(a)googlegroups.com, "Pharo Development" <pharo-project(a)lists.gforge.inria.fr> | Sent: Tuesday, August 30, 2011 2:00:26 PM | Subject: [Pharo-project] Gofer/Metacello problem in 1.4 [WAS] Re: DBXTalk and Pharo 1.4 | | | | | On Tue, Aug 30, 2011 at 9:14 PM, Laszlo Zsolt Kiss < | lzskiss(a)gmail.com > wrote: | | | | | hi. | first i load the ConfigurationOfOpenDBX and the 1.4 version is | missing from the spec.: | | | | stable: spec | <symbolicVersion: #stable> | | spec for: #'pharo1.2.x' version: '1.0'. | spec for: #'pharo1.3.x' version: '1.0'. | | | then i added the next line to the spec: | | | spec for: #'pharo1.4.x' version: '1.0'. | | | then i probally do it this: | | | (((Smalltalk globals at: #ConfigurationOfOpenDBXDriver) perform: | #project) perform: #version: with: #stable) load. | | | i gived back a warring: | | | | "The method Gofer addVersion: has been deprecated. | Instead of #addVersion: simply use #version: | | Hi. Yes, I can reproduce this problem :( | | | | | | | | | Select Proceed to continue, or close this window to cancel the | operation." | | | I proceed this warrning. | | | Then gived back an error message, I think this error came from the | Metacello. | | I attached the PharoDebug file. | | | | | The error is in the method #updateProject where it does: | | (GoferPackageReference name: mgr packageName repository: mgr | repositoryGroup) versionReference. | | GoferPackageReference dnu #name:repository: instead, it is | implemented in GoferResolvedReference | | | Dale any idea? | | Versions: Gofer-Core-StephaneDucasse.135. | Metacello version is ...... ConfigurationOfMetacello project | currentVersion raises dnu #setName | | So...I guess Pharo 1.4 is using a very new version of Gofer, which | brings lot of changes that break Metacello ? | | Thanks! | | | | | | | | | Byte | Laszlo Zsolt | | | Ps: the image is clean #14112 and the CogVM is the last.. | | | inez Peck < marianopeck(a)gmail.com > | | | | | | | | | | On Tue, Aug 30, 2011 at 9:53 AM, Laszlo Zsolt Kiss < | lzskiss(a)gmail.com > wrote: | | | Hi Developers! | | | Can I use any way this combination: DBXTalk with Pharo 1.4? | | Hi. Yes, sure. Did you try it? You shouldn't have any problem. | Please let us know if you do have. | | | -- | Mariano | http://marianopeck.wordpress.com | | | | | | -- | Mariano | http://marianopeck.wordpress.com | |

Aug. 30, 2011

[Pharo-project] Gofer/Metacello problem in 1.4 [WAS] Re: DBXTalk and Pharo 1.4

by Mariano Martinez Peck

On Tue, Aug 30, 2011 at 9:14 PM, Laszlo Zsolt Kiss <lzskiss(a)gmail.com>wrote: > hi. > first i load the ConfigurationOfOpenDBX and the 1.4 version is missing from > the spec.: > > stable: spec > <symbolicVersion: #stable> > > spec for: #'pharo1.2.x' version: '1.0'. > spec for: #'pharo1.3.x' version: '1.0'. > > then i added the next line to the spec: > > spec for: #'pharo1.4.x' version: '1.0'. > > then i probally do it this: > > (((Smalltalk globals at: #ConfigurationOfOpenDBXDriver) perform: #project) > perform: #version: with: #stable) load. > > i gived back a warring: > > "The method Gofer addVersion: has been deprecated. > Instead of #addVersion: simply use #version: > Hi. Yes, I can reproduce this problem :( > > Select Proceed to continue, or close this window to cancel the operation." > > I proceed this warrning. > > Then gived back an error message, I think this error came from the > Metacello. > I attached the PharoDebug file. > > The error is in the method #updateProject where it does: (GoferPackageReference name: mgr packageName repository: mgr repositoryGroup) versionReference. GoferPackageReference dnu #name:repository: instead, it is implemented in GoferResolvedReference Dale any idea? Versions: Gofer-Core-StephaneDucasse.135. Metacello version is ...... ConfigurationOfMetacello project currentVersion raises dnu #setName So...I guess Pharo 1.4 is using a very new version of Gofer, which brings lot of changes that break Metacello ? Thanks! Byte > Laszlo Zsolt > > Ps: the image is clean #14112 and the CogVM is the last.. > > inez Peck <marianopeck(a)gmail.com> > >> >> >> On Tue, Aug 30, 2011 at 9:53 AM, Laszlo Zsolt Kiss <lzskiss(a)gmail.com>wrote: >> >>> Hi Developers! >>> >>> Can I use any way this combination: DBXTalk with Pharo 1.4? >>> >> >> Hi. Yes, sure. Did you try it? You shouldn't have any problem. >> Please let us know if you do have. >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >> > -- Mariano http://marianopeck.wordpress.com

Aug. 30, 2011

Re: [Pharo-project] Website RSS feed broken?

by Mariano Martinez Peck

Hi Stefan, I've noticed the same problem :( On Tue, Aug 30, 2011 at 10:41 PM, Stefan Marr <pharo(a)stefan-marr.de> wrote: > Hi: > > Every single time a new news item gets posted on the pharo website, Google > Reader reports some old items as being new. > When looking at the RSS content itself, there does not immediately stick > anything out as broken. > But still, since this happens every time, and only with the Pharo web page, > I assume you got at bug somewhere. > Perhaps the guid's of the posts are not stable? > > Best regards > Stefan > > > > -- > Stefan Marr > Software Languages Lab > Vrije Universiteit Brussel > Pleinlaan 2 / B-1050 Brussels / Belgium > http://soft.vub.ac.be/~smarr > Phone: +32 2 629 2974 > Fax: +32 2 629 3525 > > > -- Mariano http://marianopeck.wordpress.com

Aug. 30, 2011

[Pharo-project] Website RSS feed broken?

by Stefan Marr

Hi: Every single time a new news item gets posted on the pharo website, Google Reader reports some old items as being new. When looking at the RSS content itself, there does not immediately stick anything out as broken. But still, since this happens every time, and only with the Pharo web page, I assume you got at bug somewhere. Perhaps the guid's of the posts are not stable? Best regards Stefan -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

Aug. 30, 2011