Re: [Pharo-dev] [Ann] New TxText version 1.0

2013/5/28 Tudor Girba > Hi, > > I found the issue: the url from the Gofer script was wrong :). > > Here is the correct one: > Gofer it > url: 'http://www.smalltalkhub.com/mc/sig/TxText/main'; > package: 'ConfigurationOfTxText'; > load. > It is true of course. But I can't

Re: [Pharo-dev] [Esug-list] [ANN] SmalltalkHub update

yes! 2013. 5. 27., 저녁 10:17, Serge Stinckwich 작성: > Hourra it works ! > > Thank you Nicolas & Damien > > Now I want to be able to remove projects ;-) > > Regards > > > On Mon, May 27, 2013 at 2:45 PM, Nicolas Petton > wrote: >> Hi! >> >> I've just updated SmalltalkHub with new features an

Re: [Pharo-dev] [Ann] New TxText version 1.0

Hi, I found the issue: the url from the Gofer script was wrong :). Here is the correct one: Gofer it url: 'http://www.smalltalkhub.com/mc/sig/TxText/main'; package: 'ConfigurationOfTxText'; load. ((Smalltalk at: #ConfigurationOfTxText) project version: '1.0') load: #('ALL

Re: [Pharo-dev] SystemAnnouncer api question

On 27 May 2013 19:05, stephane ducasse wrote: > Igor > > can you add a bug entry and propose a fix? > So that we do not forget. > yes. > Stef > > > > >> Hi guys >> >> why there is no variant to on:send:to: >> "SystemAnnouncer uniqueInstance on: AddedLog send: #foo to:

Re: [Pharo-dev] SystemAnnouncer api question

Simpler is better: "Declare that when anAnnouncementClass is raised, anObject should receive the message aSelector. When the message expects one argument (eg #fooAnnouncement:) the announcement is passed as argument. When the message expects two arguments (eg #fooAnnounce

Re: [Pharo-dev] SystemAnnouncer api question

Igor can you add a bug entry and propose a fix? So that we do not forget. Stef > Hi guys > > why there is no variant to on:send:to: > "SystemAnnouncer uniqueInstance on: AddedLog send: #foo to: self. " > that pass also the announcement? > > Just b

Re: [Pharo-dev] SystemAnnouncer api question

> >> Hi guys >> >> why there is no variant to on:send:to: >> "SystemAnnouncer uniqueInstance on: AddedLog send: #foo to: self. " >> that pass also the announcement? >> >> Just because it is better to use on:do;? >> >> Stef >> > Huh? > It should work do do > SystemAnnouncer uniqueInstance

[Pharo-dev] Jenkins build is back to stable : Pharo-2.0-Tests » run 1,vm,mac #244

See

[Pharo-dev] Jenkins build is back to stable : Pharo-2.0-Tests » run 1,vm,win #244

See

[Pharo-dev] Jenkins build is back to stable : Pharo-2.0-Tests » run 1,vm,linux #244

See

[Pharo-dev] [update 2.0] #20605

20605 - 10653 Some Jenkins images show a stdout is closed error https://pharo.fogbugz.com/f/cases/10653 Diff information: http://ss3.gemstone.com/ss/Pharo20/System-CommandLine-MarcusDenker.83.diff

Re: [Pharo-dev] [update 3.0] #30171

On May 27, 2013, at 4:52 PM, Sven Van Caekenberghe wrote: > > On 27 May 2013, at 16:45, Marcus Denker wrote: > >> 10698 add back Block printing >> https://pharo.fogbugz.com/f/cases/10698 >> (Really only if Opal is Active) > > Aah, a good reason to active Opal then ;-) I did that b

Re: [Pharo-dev] [update 3.0] #30171

On 27 May 2013, at 16:45, Marcus Denker wrote: > 10698 add back Block printing > https://pharo.fogbugz.com/f/cases/10698 > (Really only if Opal is Active) Aah, a good reason to active Opal then ;-) Sven

[Pharo-dev] [update 3.0] #30171

30171 - 10764 EyeInspector never terminate refresh process leading to no garbage collection https://pharo.fogbugz.com/f/cases/10764 10767 Object>>#assert:description: should take a block for the description https://pharo.fogbugz.com/f/cases/10767 10698 add ba

Re: [Pharo-dev] SystemAnnouncer api question

On 27 May 2013 12:28, Henrik Johansen wrote: > > On May 27, 2013, at 11:44 AM, Henrik Johansen wrote: > >> >> On May 25, 2013, at 1:11 PM, Stéphane Ducasse wrote: >> >>> Hi guys >>> >>> why there is no variant to on:send:to: >>> "SystemAnnouncer uniqueInstance on: AddedLog send: #foo to: self

Re: [Pharo-dev] SystemAnnouncer api question

On 27 May 2013 16:21, Igor Stasenko wrote: > On 27 May 2013 12:28, Henrik Johansen wrote: >> >> On May 27, 2013, at 11:44 AM, Henrik Johansen wrote: >> >>> >>> On May 25, 2013, at 1:11 PM, Stéphane Ducasse wrote: >>> Hi guys why there is no variant to on:send:to: "SystemA

Re: [Pharo-dev] [Esug-list] [ANN] SmalltalkHub update

Hourra it works ! Thank you Nicolas & Damien Now I want to be able to remove projects ;-) Regards On Mon, May 27, 2013 at 2:45 PM, Nicolas Petton wrote: > Hi! > > I've just updated SmalltalkHub with new features and bug fixes, especially: > > - Packages can now be removed by the project owner

[Pharo-dev] [ANN] SmalltalkHub update

Hi! I've just updated SmalltalkHub with new features and bug fixes, especially: - Packages can now be removed by the project owner - MCZ files can also be removed one by one The update also includes a security fix with contributors discovered by Camillo. Most of the credit for this release goes

Re: [Pharo-dev] Memory leaks with Spec?

2013/5/27 stephane ducasse > we found the problem. It is not spec but the EyeInspector polling update. > So we should find a solution. > Probably it should register WindowClosed and kill the process. > Actually the inspector is already registered on WindowClosed event. This bug was introduced by

Re: [Pharo-dev] SystemAnnouncer api question

On May 27, 2013, at 11:44 AM, Henrik Johansen wrote: > > On May 25, 2013, at 1:11 PM, Stéphane Ducasse wrote: > >> Hi guys >> >> why there is no variant to on:send:to: >> "SystemAnnouncer uniqueInstance on: AddedLog send: #foo to: self. " >> that pass also the announcement? >> >> Just b

Re: [Pharo-dev] libssl on Jenkins-Contribution

thanks -- Pavel On Mon, May 27, 2013 at 11:28 AM, Camillo Bruni wrote: > DONE: installed libssl1.0.0:i386 on > pharo-contribution-linux64-2.ci.inria.fr > > On 2013-05-27, at 11:22, Pavel Krivanek wrote: > > > Hi, > > > > our slaves on Jenkins-Contribution server do not have 32bit libSSL > > ins

Re: [Pharo-dev] SystemAnnouncer api question

On May 25, 2013, at 1:11 PM, Stéphane Ducasse wrote: > Hi guys > > why there is no variant to on:send:to: > "SystemAnnouncer uniqueInstance on: AddedLog send: #foo to: self. " > that pass also the announcement? > > Just because it is better to use on:do;? > > Stef > Huh? It should work

Re: [Pharo-dev] libssl on Jenkins-Contribution

DONE: installed libssl1.0.0:i386 on pharo-contribution-linux64-2.ci.inria.fr On 2013-05-27, at 11:22, Pavel Krivanek wrote: > Hi, > > our slaves on Jenkins-Contribution server do not have 32bit libSSL > installed so If I try to run all jobs there, I got this error: > > ioLoadModule(/builds/wor

[Pharo-dev] libssl on Jenkins-Contribution

Hi, our slaves on Jenkins-Contribution server do not have 32bit libSSL installed so If I try to run all jobs there, I got this error: ioLoadModule(/builds/workspace/PharoKernel3.0-ReloadByMonticello-Tests/phar o-vm/libSqueakSSL.so): libssl.so.1.0.0: cannot open shared object file: No such file o

Re: [Pharo-dev] seaside 31 configuration not loading

thanks for the information. On 2013-05-27, at 09:19, Diego Lont wrote: > Camillo, > > The official stable version of seaside is 3.0.8, that can be found in the > Metacello repo. > location: 'http://www.squeaksource.com/MetacelloRepository' > As far as I know, this version is in the green

Re: [Pharo-dev] Memory leaks with Spec?

we found the problem. It is not spec but the EyeInspector polling update. So we should find a solution. Probably it should register WindowClosed and kill the process. Stef > Le 25/05/2013 13:59, Benjamin a écrit : >> I am pretty sure to only use weak registration (why aren't all the >> registrat

Re: [Pharo-dev] Keeping Pharo CPU usage low: how?

I was looking at the output of "top" for while and Pharo was trusting the top spot indeed. Well, I'll look at all that this evening and give back the impressions. I want to run several instances of Pharo on the box and it will for sure add up. Say, 20 x 2% gives an awful lot. Phil On Mon, May

Re: [Pharo-dev] Keeping Pharo CPU usage low: how?

That feature I know of. It is a nice one for sure! Phil On Mon, May 27, 2013 at 9:58 AM, Norbert Hartl wrote: > It includes as well a button to make a screenshot in the image :) > > Norbert > > Am 27.05.2013 um 09:56 schrieb "p...@highoctane.be" : > > Thanks for the info. > > Norbert, I didn't

Re: [Pharo-dev] Memory leaks with Spec?

Le 25/05/2013 13:59, Benjamin a écrit : I am pretty sure to only use weak registration (why aren't all the registration weak btw ??) It may be a problem somewhere else :( I hit that problem a while ago. I couldn't find where it was holding the instances, even with the help of the strong point

Re: [Pharo-dev] [Ann] New TxText version 1.0

On May 27, 2013, at 9:22 AM, Denis Kudriashov wrote: > 2013/5/27 stephane ducasse > in 30 I get an error asShortCut… DNU. > > > Maybe there is issue about it. Character>>asShortcut was lost during some > update. Yes, there is an issue for that on the tracker: https://pharo.fogbugz.

Re: [Pharo-dev] Keeping Pharo CPU usage low: how?

It includes as well a button to make a screenshot in the image :) Norbert Am 27.05.2013 um 09:56 schrieb "p...@highoctane.be" : > Thanks for the info. > > Norbert, I didn't knew about that UI thread handler in Seaside. I'll check > that out. > > Phil > > > On Mon, May 27, 2013 at 9:49 AM, S

Re: [Pharo-dev] Keeping Pharo CPU usage low: how?

Thanks for the info. Norbert, I didn't knew about that UI thread handler in Seaside. I'll check that out. Phil On Mon, May 27, 2013 at 9:49 AM, Sven Van Caekenberghe wrote: > Phil, > > On 27 May 2013, at 09:19, "p...@highoctane.be" wrote: > > > I am currently experimenting with Pharo on Amaz

[Pharo-dev] Futures

I am currently experimenting with Pharo on Amazon EC2. I'd like to keep the CPU usage low for when Pharo hasn't anything special to do. At the moment, I see that Pharo uses 2-3% of the CPU when just blinking the caret. Is there a way to get that lower? Even if it means tweaking the VM. The OS i

Re: [Pharo-dev] [Ann] New TxText version 1.0

2013/5/27 stephane ducasse > in 30 I get an error asShortCut… DNU. > > Maybe there is issue about it. Character>>asShortcut was lost during some update. But I don't try TxText at latest pharo build > Stef > > On May 26, 2013, at 11:09 PM, Denis Kudriashov > wrote: > > m := TxTextMorph new. >

Re: [Pharo-dev] [update 3.0] #30169

yes we want more of them. I want to free my mind about stupid low level details. Stef > Excellent. I love highly specific rules :). They bring so much more value > than the other ones. > > Cheers, > Doru > > > On May 26, 2013, at 2:59 PM, Marcus Denker wrote: > >> 10621 Create a lint rule t

Re: [Pharo-dev] seaside 31 configuration not loading

Camillo, The official stable version of seaside is 3.0.8, that can be found in the Metacello repo. location: 'http://www.squeaksource.com/MetacelloRepository' As far as I know, this version is in the green. I see that some changes where made to Zinc-Seaside since I last checked … but sti

Re: [Pharo-dev] [Ann] New TxText version 1.0

in 30 I get an error asShortCut… DNU. Stef On May 26, 2013, at 11:09 PM, Denis Kudriashov wrote: > m := TxTextMorph new. > m editDecorator: TxSingleLineEditDecorator smartNumbers. > m textSpec: (TxDecimalTextSpec maxDecimalDigits: 3). > m newTextContents: '1000'. > m addCur

Re: [Pharo-dev] [Ann] New TxText version 1.0

Thanks denis I talked with alain last week and he should finish some work for synectique on his textEditor and told me that after he will really have a look at your work. Stef On May 26, 2013, at 11:09 PM, Denis Kudriashov wrote: > Hello. > > I finish edit validation logic. So new version