Re: [Pharo-project] About Monticello Meta Data...

2013-02-13 Thread Frank Shearar
On 13 February 2013 07:59, Marcus Denker marcus.den...@inria.fr wrote: On Feb 13, 2013, at 8:55 AM, Frank Shearar frank.shea...@gmail.com wrote: So you're saying that it's just that ReleaseBuilder needs to actually do these things - condense sources etc. - and then run some tests to show

Re: [Pharo-project] [ann] glamorous debugger (alpha)

2013-02-13 Thread Andrei Vasile Chis
Hi Stef, The bug with Run to Here should be fixed. This and al the other actions should work just like in the current debugger. This means that when the current debugger breaks they would also break :) There are still some issues with the ui when there is unsaved content in the editor but it is

Re: [Pharo-project] [ann] glamorous debugger (alpha)

2013-02-13 Thread Tudor Girba
Great work, Andrei! Doru On Wed, Feb 13, 2013 at 9:49 AM, Andrei Vasile Chis chisvasileand...@gmail.com wrote: Hi Stef, The bug with Run to Here should be fixed. This and al the other actions should work just like in the current debugger. This means that when the current debugger breaks

Re: [Pharo-project] About Monticello Meta Data...

2013-02-13 Thread stephane ducasse
So concretely what can we do? Let us try to condense sources and see if it is working. Stef

Re: [Pharo-project] [ann] glamorous debugger (alpha)

2013-02-13 Thread Damien Cassou
On Wed, Feb 13, 2013 at 11:04 AM, stephane ducasse stephane.duca...@free.fr wrote: excellent we should push it in 3.0 :) along with Glamour? Or do you want a spec-based UI as well? -- Damien Cassou http://damiencassou.seasidehosting.st Success is the ability to go from one failure to another

Re: [Pharo-project] [ann] glamorous debugger (alpha)

2013-02-13 Thread stephane ducasse
On Feb 13, 2013, at 11:09 AM, Damien Cassou damien.cas...@gmail.com wrote: On Wed, Feb 13, 2013 at 11:04 AM, stephane ducasse stephane.duca...@free.fr wrote: excellent we should push it in 3.0 :) along with Glamour? Or do you want a spec-based UI as well? there is already a spec version.

Re: [Pharo-project] About Monticello Meta Data...

2013-02-13 Thread Craig Latta
Hoi-- Marcus writes: we need to get rid of all ways of doing things that makes us distinguish the release from any other image. Aka: .changes and .sources are evil. Evil, I say. Yes, evil and anachronistic. Buggy whips for a Tesla. Frank writes: ...devs need to dogfood,

Re: [Pharo-project] [ann] glamorous debugger (alpha)

2013-02-13 Thread Andrei Vasile Chis
There is both a spec and a glamour interface and both work quite well. After moose is moved to Pharo 2.0 I'll write some configurations to load things nicely. Andrei On Wed, Feb 13, 2013 at 11:15 AM, stephane ducasse stephane.duca...@free.fr wrote: On Feb 13, 2013, at 11:09 AM, Damien

[Pharo-project] [update 2.0] #20543

2013-02-13 Thread Marcus Denker
20543 - Issue 7502: Failing test: DiskFileSystemTest#testDefaultWorkingDirectory http://code.google.com/p/pharo/issues/detail?id=7502 Diff information: http://ss3.gemstone.com/ss/Pharo20/FileSystem-Tests-Disk-MarcusDenker.13.diff

Re: [Pharo-project] Clock/Delay problems

2013-02-13 Thread Camillo Bruni
Yes that is a very nasty bug, and I think it is not that easy to fix. If you really want to fix it we will have to fiddle with the whole startup mess. see comments in: https://code.google.com/p/pharo/issues/detail?id=7129 strangely enough it was introduced in 20460! image 20459 worked without

Re: [Pharo-project] CommandShell and OSProcess updated for Pharo 2.0

2013-02-13 Thread Sean P. DeNigris
David T. Lewis wrote I thought that I got rid of all the explicit references to FileDirectory and ReferenceStream, so check to make sure you're using the latest version of OSProcess. Maybe I missed a few of the references, there were quite a few. I think you're right... don't know what I was

Re: [Pharo-project] CommandShell and OSProcess updated for Pharo 2.0

2013-02-13 Thread Sean P. DeNigris
stephane ducasse wrote @sean what was the problem because I tested it several time on 1.4 and 2.0 The tests were failing due to FS differences between 1.4 and 2.0. I uploaded fixes, so we could do a 4.5.1 with the latest packages (4.5 is tagged release so we shouldn't change it). Also, I moved

[Pharo-project] OSProcess and CommandShell in Pharo 2.0

2013-02-13 Thread Sean P. DeNigris
I think we have it now: - ConfigurationOfOSProcess and ConfigurationOfCommandShell have been updated to work in 1.4 and 2.0 - Each config has been copied to its project repo (e.g. sqs/CommandShell). I was starting to get confused with all the locations (sqs/MetacelloRepository, xyz/MetaRepoForAbc,

Re: [Pharo-project] Clock/Delay problems

2013-02-13 Thread stephane ducasse
Sven can you add a bug entry because igor and camillo were discussing about the strange logic of DateAndTime? Stef On Feb 11, 2013, at 2:54 PM, Sven Van Caekenberghe s...@stfx.eu wrote: I have seen this before, and it is probably related to other problems that we have been seeing lately:

Re: [Pharo-project] CommandShell and OSProcess updated for Pharo 2.0

2013-02-13 Thread stephane ducasse
On Feb 13, 2013, at 4:06 PM, Sean P. DeNigris s...@clipperadams.com wrote: stephane ducasse wrote @sean what was the problem because I tested it several time on 1.4 and 2.0 The tests were failing due to FS differences between 1.4 and 2.0. I uploaded fixes, so we could do a 4.5.1 with the

Re: [Pharo-project] Enums with negative values don't work properly.

2013-02-13 Thread Igor Stasenko
Good news: - i reverted the image-side code back in 2.1 version i don't like adding new primitives, and since i found the way to access required symbols on windows VM by exporting them, this will allow the old versions of NB to run without changes on newer VMs. In new VMs, there are also changes

Re: [Pharo-project] Clock/Delay problems

2013-02-13 Thread Igor Stasenko
On 13 February 2013 18:01, stephane ducasse stephane.duca...@free.fr wrote: Sven can you add a bug entry because igor and camillo were discussing about the strange logic of DateAndTime? yeah.. i was looking at it recently (remember my post about DateAndTime nanosecond precision handling)..

Re: [Pharo-project] Clock/Delay problems

2013-02-13 Thread Igor Stasenko
My personal take about this issue: - when image starting up, all Delays should be reset by unblocking all waiting processes (regardless how much extra time there left to be waiting). Because, to my opinion, a code which uses delays to cross session boundaries will fail badly anyways, so imo it

Re: [Pharo-project] Clock/Delay problems

2013-02-13 Thread p...@highoctane.be
Is this related to that large list of [delaySemaphore wait] in Delaywait that I do see in the Process Browser? This thing wasn't so large in the past. Phil 2013/2/13 Igor Stasenko siguc...@gmail.com: My personal take about this issue: - when image starting up, all Delays should be reset by

Re: [Pharo-project] Clock/Delay problems

2013-02-13 Thread Sven Van Caekenberghe
On 13 Feb 2013, at 18:17, p...@highoctane.be p...@highoctane.be wrote: Is this related to that large list of [delaySemaphore wait] in Delaywait that I do see in the Process Browser? This thing wasn't so large in the past. Let's hope so: it seems related, but we see it during startup (and

Re: [Pharo-project] CommandShell and OSProcess updated for Pharo 2.0

2013-02-13 Thread Frank Shearar
On 13 February 2013 16:03, stephane ducasse stephane.duca...@free.fr wrote: On Feb 13, 2013, at 4:06 PM, Sean P. DeNigris s...@clipperadams.com wrote: stephane ducasse wrote @sean what was the problem because I tested it several time on 1.4 and 2.0 The tests were failing due to FS

Re: [Pharo-project] Clock/Delay problems

2013-02-13 Thread p...@highoctane.be
Don't know if this is related but the 2.0 image seems to runs slower on my box (20543 now). Also a question: why is there a ZnServer in the StartUpList ? I saw discussions on the loading of .changes if there is none in the image folder. Phil 2013/2/13 Sven Van Caekenberghe s...@stfx.eu: On 13

Re: [Pharo-project] Clock/Delay problems

2013-02-13 Thread Sven Van Caekenberghe
Hi Phil, On 13 Feb 2013, at 18:39, p...@highoctane.be p...@highoctane.be wrote: Don't know if this is related but the 2.0 image seems to runs slower on my box (20543 now). That is hard to quantify, but any regressions should be investigated. Also a question: why is there a ZnServer in the

Re: [Pharo-project] CommandShell and OSProcess updated for Pharo 2.0

2013-02-13 Thread stephane ducasse
On Feb 13, 2013, at 6:28 PM, Frank Shearar frank.shea...@gmail.com wrote: On 13 February 2013 16:03, stephane ducasse stephane.duca...@free.fr wrote: On Feb 13, 2013, at 4:06 PM, Sean P. DeNigris s...@clipperadams.com wrote: stephane ducasse wrote @sean what was the problem because I

Re: [Pharo-project] CommandShell and OSProcess updated for Pharo 2.0

2013-02-13 Thread Sean P. DeNigris
Frank Shearar-3 wrote As a general rule this is a very bad idea +1. It's a bad habit to get into and subverts part of MetaC's usefulness, as Frank described. In fact, I find 4.5.1 very exciting, because it uses semantic versioning to communicate a whole world to the user without a long comment.

Re: [Pharo-project] Clock/Delay problems

2013-02-13 Thread stephane ducasse
On Feb 13, 2013, at 6:39 PM, p...@highoctane.be wrote: Don't know if this is related but the 2.0 image seems to runs slower on my box (20543 now). this is strange because people told me exactly the inverse yesterday (comparing to 1.4). So this is difficult to assess. Stef Also a

[Pharo-project] Fwd: A question about lookup and message reification

2013-02-13 Thread Stéphane Ducasse
I repost the mail to the mailing-list since I do not see it in the vm-dev Stef Hi I was reading the following method in the VM code and I have a couple of questions: - I do not understand why lookupMethodInClass: may return a class. I was thinking that it would return a method.

Re: [Pharo-project] CommandShell and OSProcess updated for Pharo 2.0

2013-02-13 Thread Frank Shearar
On 13 February 2013 19:35, stephane ducasse stephane.duca...@free.fr wrote: On Feb 13, 2013, at 6:28 PM, Frank Shearar frank.shea...@gmail.com wrote: On 13 February 2013 16:03, stephane ducasse stephane.duca...@free.fr wrote: On Feb 13, 2013, at 4:06 PM, Sean P. DeNigris

Re: [Pharo-project] Clock/Delay problems

2013-02-13 Thread p...@highoctane.be
How can I test that? Really it feels sluggish when scrolling lists, autocomplete with Spotlight etc. Didn't have that with my 1.4. I am using a Mac with a Core2Duo CPU. RAM is of no concern (8GB). Phil 2013/2/13 stephane ducasse stephane.duca...@free.fr: On Feb 13, 2013, at 6:39 PM,

Re: [Pharo-project] Fwd: A question about lookup and message reification

2013-02-13 Thread Eliot Miranda
Hi Stef, On Wed, Feb 13, 2013 at 11:40 AM, Stéphane Ducasse stephane.duca...@inria.fr wrote: I repost the mail to the mailing-list since I do not see it in the vm-dev did you post to vm-dev? Stef Hi I was reading the following method in the VM code and I have a couple of questions:

Re: [Pharo-project] OSProcess and CommandShell in Pharo 2.0

2013-02-13 Thread David T. Lewis
Thanks a lot Sean! Dave On Wed, Feb 13, 2013 at 07:16:25AM -0800, Sean P. DeNigris wrote: I think we have it now: - ConfigurationOfOSProcess and ConfigurationOfCommandShell have been updated to work in 1.4 and 2.0 - Each config has been copied to its project repo (e.g. sqs/CommandShell). I

Re: [Pharo-project] Clock/Delay problems

2013-02-13 Thread Camillo Bruni
On 2013-02-13, at 21:04, p...@highoctane.be p...@highoctane.be wrote: How can I test that? Really it feels sluggish when scrolling lists, that is wrong, taking the latest 1.4 and the latest 2.0 there is a massive visual difference in scrolling speed on a huge list. I looked for senders of

Re: [Pharo-project] Fwd: A question about lookup and message reification

2013-02-13 Thread Eliot Miranda
On Wed, Feb 13, 2013 at 12:11 PM, Eliot Miranda eliot.mira...@gmail.comwrote: Hi Stef, On Wed, Feb 13, 2013 at 11:40 AM, Stéphane Ducasse stephane.duca...@inria.fr wrote: I repost the mail to the mailing-list since I do not see it in the vm-dev did you post to vm-dev? Stef Hi I

Re: [Pharo-project] [Vm-dev] Fwd: A question about lookup and message reification

2013-02-13 Thread Stéphane Ducasse
Hi eliot I repost the mail to the mailing-list since I do not see it in the vm-dev did you post to vm-dev? yes but since I'm travelling may be the mail was lost or I could not see appearing because one of my rules pushed it somewhere. I changed machines and I have to get used to 10.8. My

Re: [Pharo-project] Rectangleintersects: change Rationale

2013-02-13 Thread Igor Stasenko
On 13 February 2013 22:55, Nicolas Cellier nicolas.cellier.aka.n...@gmail.com wrote: Rectangleintersects: has been changed recently (GuillermoPolito 2/8/2013) rCorner x origin x ifTrue: [ ^ false ]. rCorner y origin y ifTrue: [ ^ false ]. rOrigin x corner x ifTrue: [

Re: [Pharo-project] Rectangleintersects: change Rationale

2013-02-13 Thread stephane ducasse
Nicolas what I know is that with igor we fixed all the senders of fractions:offset: and after igor introduced intersect:ifNone: to avoid generating wrong rectangles with negative values. I thought that intersect: was deprecated. or the precondition should be clearer. Stef On Feb 13, 2013,

Re: [Pharo-project] Rectangleintersects: change Rationale

2013-02-13 Thread Igor Stasenko
yes.. and i'd like to add that in some places i replaced senders of rect1 intersect: rect2 with: rect1 intersect: rect2 ifNone: [ self error: 'should not happen']. as it appears, it happens in some places... because of the above inconsistency. -- Best regards, Igor Stasenko.

Re: [Pharo-project] Rectangleintersects: change Rationale

2013-02-13 Thread Nicolas Cellier
Ah, and the change is the other way around, = was replaced with ... I ask because we had a request in squeak-dev after I changed Rectangleintersects: and was wondering if this should be in Squeak too http://lists.squeakfoundation.org/pipermail/squeak-dev/2013-January/167855.html 2013/2/13

Re: [Pharo-project] Rectangleintersects: change Rationale

2013-02-13 Thread Igor Stasenko
On 13 February 2013 23:41, Nicolas Cellier nicolas.cellier.aka.n...@gmail.com wrote: Ah, and the change is the other way around, = was replaced with ... I ask because we had a request in squeak-dev after I changed Rectangleintersects: and was wondering if this should be in Squeak too

[Pharo-project] bug metacello toolbox / pharo2

2013-02-13 Thread Christophe Demarey
Hi, Pharo 2.0 is shipped with Metacello. Metacello version installed is based on the stable version (1.0-beta.31.1.5). This version loads Metacello-ToolBox-dkh.130 but strangely, the Metacello-ToolBox package shipped in Pharo 2.0 is Metacello-ToolBox-MarkusDenker.135. Its ancestor is

Re: [Pharo-project] Rectangleintersects: change Rationale

2013-02-13 Thread Nicolas Cellier
I tried to put a halt in RectanglesetOrigin: topLeft corner: bottomRight in latest Pharo (20543) if width 0 or height 0 and of course the image hung... which means that degenerated Rectangles are pretty much in use I think I will juts raise a Notification, and catch it with a MessageTally hack

Re: [Pharo-project] Rectangleintersects: change Rationale

2013-02-13 Thread Igor Stasenko
On 13 February 2013 23:47, Nicolas Cellier nicolas.cellier.aka.n...@gmail.com wrote: I tried to put a halt in RectanglesetOrigin: topLeft corner: bottomRight in latest Pharo (20543) if width 0 or height 0 and of course the image hung... which means that degenerated Rectangles are pretty much

Re: [Pharo-project] Rectangleintersects: change Rationale

2013-02-13 Thread Igor Stasenko
On 14 February 2013 00:01, Nicolas Cellier nicolas.cellier.aka.n...@gmail.com wrote: So here is what I did: . My feeling is that you are not thru with degenerated rectangles :) You'd better enforce the invariant in http://code.google.com/p/pharo/issues/detail?id=2601 rathert than remove

Re: [Pharo-project] Rectangleintersects: change Rationale

2013-02-13 Thread Igor Stasenko
On 14 February 2013 00:15, Nicolas Cellier nicolas.cellier.aka.n...@gmail.com wrote: Please use my MessageTally trick above and you'll unfortunately see that intersect: is just one producer of empty Rectangle among many... So I think that the ifNone: protection is quite vain given the flow of