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

Re: [Pharo-project] Issue 3247 in pharo: Remodel Text Constants

by pharo＠googlecode.com

Comment #16 on issue 3247 by Benjamin.VanRyseghem.Pharo: Remodel Text Constants http://code.google.com/p/pharo/issues/detail?id=3247 A new version of TextConstants is available which patch on the fly methods which invoke TextSharedInformation. If some people could test it, it could be great ^^ (when I've done some tests, there was no problem) Thx to Jannik for his help :)

Nov. 20, 2010

[Pharo-project] Issue 3275 in pharo: Bug in Finder

by pharo＠googlecode.com

Status: Fixed Owner: Benjamin.VanRyseghem.Pharo New issue 3275 by Benjamin.VanRyseghem.Pharo: Bug in Finder http://code.google.com/p/pharo/issues/detail?id=3275 Fixed and commited on PharoTaskForces

Nov. 20, 2010

Re: [Pharo-project] Issue 3274 in pharo: text finding fixes

by pharo＠googlecode.com

Updates: Status: Fixed Comment #1 on issue 3274 by aplantec: text finding fixes http://code.google.com/p/pharo/issues/detail?id=3274 SLICE-Issue-3274-text-finding-fixes

Nov. 20, 2010

Re: [Pharo-project] Not happy with the issues feed from Google

by George Herolyants

Ok. +1 to this list. -1 to the special "bug tracker" list. George

Nov. 20, 2010

[Pharo-project] Issue 3274 in pharo: text finding fixes

by pharo＠googlecode.com

Status: Accepted Owner: aplantec Labels: Milestone-1.2 New issue 3274 by aplantec: text finding fixes http://code.google.com/p/pharo/issues/detail?id=3274 * it is too slow * the textmorph has not the keyboard focus after * when the PluggableTextMorph has to scroll down, the selected token is only partially visible at the bottom of the visible area

Nov. 20, 2010

Re: [Pharo-project] Not happy with the issues feed from Google

by StÃ©phane Ducasse

The other mailing-list is created and we can change no time now. so decide. Stef On Nov 20, 2010, at 10:04 AM, George Herolyants wrote: > Stef, > > After some thinking about it I changed my mind. I agree now that the > initial idea of sending messages from the tracker to this list was not > so bad. And definitely better than having a separate mailing list for > it. You say that that's the pharo developers mailing list after all, > so it's intended for such processes. And I agree with this statement > also. > > The only concern I still have is not splitting a discussion between > the mailing list and the tracker. I propose that if someone wants to > answer to the issue, he'd rather do it on the tracker, because this > way his message will appear on both sides: the tracker and the mailing > list, which is good. But the other way, if someone answers to the > issue on the mailing list, it won't appear on the tracker (at least > until google provides such feature) and this is not good. > > So you can strike me now from the list of opponents :) > > George >

Nov. 20, 2010

Re: [Pharo-project] Not happy with the issues feed from Google

by StÃ©phane Ducasse

;) Stef On Nov 20, 2010, at 10:04 AM, George Herolyants wrote: > Stef, > > After some thinking about it I changed my mind. I agree now that the > initial idea of sending messages from the tracker to this list was not > so bad. And definitely better than having a separate mailing list for > it. You say that that's the pharo developers mailing list after all, > so it's intended for such processes. And I agree with this statement > also. > > The only concern I still have is not splitting a discussion between > the mailing list and the tracker. I propose that if someone wants to > answer to the issue, he'd rather do it on the tracker, because this > way his message will appear on both sides: the tracker and the mailing > list, which is good. But the other way, if someone answers to the > issue on the mailing list, it won't appear on the tracker (at least > until google provides such feature) and this is not good. > > So you can strike me now from the list of opponents :) > > George >

Nov. 20, 2010

Re: [Pharo-project] Infinite recursion

by StÃ©phane Ducasse

ideally there should be (may be there is one) a watchdog on the stack but may be this is on the vm side close to the gc. On Nov 19, 2010, at 1:30 PM, Guillermo Polito wrote: > I will insist here :P. > > What is the desired behavior for this situation? So if it is an Issue, I may open an entry in the tracker... > > On Wed, Nov 17, 2010 at 1:46 PM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > I asked this some time back. One dark side of doing this is that it *can* result in unwanted/inappropriate failures. In practice though, Dolphin's limits on the stack has been a good thing. > > > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Guillermo Polito [guillermopolito(a)gmail.com] > Sent: Wednesday, November 17, 2010 11:44 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: [Pharo-project] Infinite recursion > > Hi, > > Yesterday I got into an infinite recursion, because of adding an ordered collection into itself. And #hash is defined in terms of its containees, hehe. > > Why I did that? It doesn't really matters. I was testing a little project I'm doing for the University. > > So I came into an infinite recursion, which didn't stop until the VM run out of memory... And the question is.. Shouldn't it throw an error like a stack overflow when we run into those cases? > > Cheers, > Guille > >

Nov. 20, 2010

Re: [Pharo-project] Issue 3266 in pharo: Clean TextEditor

by StÃ©phane Ducasse

On Nov 19, 2010, at 1:07 PM, Alain Plantec wrote: > Le 19/11/2010 08:21, Fernando Olivero a Ã©crit : >> Hi Alain, i took a better look at the changes and have to say...once >> again..excellent! > Thanks Fernando! >> I think the next step is to improve the keybindings hardcoding in >> TextEditor>>initialize >> self initializeCmdKeyShortcuts. >> self initializeShiftCmdKeyShortcuts. > yes yes! >> I have a keybindings/command model in Gaucho, for applying a >> keybinding to any morph. >> I will work on decoupling it from GauchoMorph into Morph. >> And later rewrite the Morphs for textediting to use this. > I was thinking of something like your KeyBinding.. > so, very good. > What I would like is to be able to control all alt-ctrl-cmd-shift etc possible combinations for any morph. > It implies to review the way events are handled by Morph/HandMorph and > to remove the ugly "control and alt key" setting (Full matching, partial matching, Swapped). We should get in the sophie events hierarchy. no ? Stef > Cheers > Alain > >

Nov. 20, 2010

[Pharo-project] [update 1.2] #12247

by StÃ©phane Ducasse

12247 ----- - Issue 3272: SelectorChooserMorph improvement.

Nov. 20, 2010