- Pharo-dev - lists.pharo.org

[Pharo-project] [update 1.2] #12248
by StÃ©phane Ducasse Nov. 20, 2010

Nov. 20, 2010

12248 ----- - Issue 3274: text finding fixes. Thanks Alain Plantec

1 0

[Pharo-project] Issue 3274 in pharo: text finding fixes
by pharo＠googlecode.com Nov. 20, 2010

Nov. 20, 2010

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

1 2

Re: [Pharo-project] Not happy with the issues feed from Google
by StÃ©phane Ducasse Nov. 20, 2010

Nov. 20, 2010

;) 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 >

1 0

Re: [Pharo-project] Infinite recursion
by StÃ©phane Ducasse Nov. 20, 2010

Nov. 20, 2010

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 > >

1 0

[Pharo-project] [update 1.2] #12247
by StÃ©phane Ducasse Nov. 20, 2010

Nov. 20, 2010

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

1 0

Re: [Pharo-project] Issue 3272 in pharo: SelectorChooserMorph improvement
by pharo＠googlecode.com Nov. 20, 2010

Nov. 20, 2010

Updates: Summary: SelectorChooserMorph improvement Comment #3 on issue 3272 by stephane.ducasse: SelectorChooserMorph improvement http://code.google.com/p/pharo/issues/detail?id=3272 (No comment was entered for this change.)

1 0

[Pharo-project] Not happy with the issues feed from Google
by Stephan Eggermont Nov. 20, 2010

Nov. 20, 2010

Hello, I'm not happy to see the feed subscribed to this mailing list. I often have to use the web interface to this list, and the number of one-line comments and status changes makes for a very unpleasant reading experience. In addition it makes it more difficult to find the interesting discussions. As a workflow, it also has problems, as reply mails are not added back to the issue tracker. Stephan

5 5

[Pharo-project] Loading Alien on Pharo 1.1.1
by Esteban Lorenzano Nov. 20, 2010

Nov. 20, 2010

Hi, Does anybody knows if Alien should work with pharo 1.1.1 (non cog vm)? With ConfigurationOfAlien, I'm getting the "invalid array size" prereq violated. Cheers, Esteban

3 8

[Pharo-project] Issue 3272 in pharo: SelectorChooserMorph improving
by pharo＠googlecode.com Nov. 19, 2010

Nov. 19, 2010

Status: Accepted Owner: aplantec Labels: Milestone-1.2 New issue 3272 by aplantec: SelectorChooserMorph improving http://code.google.com/p/pharo/issues/detail?id=3272 New version with a highlighted current prefix (see screenshot). In case of error or if the requestor textMorph is closed, then the SelectorChooser is staying openned behind. The new version fixes this issues. Attachments: selectorChooserImprovement.png 36.0 KB

1 2

Nov. 19, 2010

+1 Sorry guys this is not optimal but after been against when I see it in squeak, I'm in favor because it helps understanding what is happening. Sorry to be blunt but ****YOU**** yes you guys do not look at the bug or bug fixes in general. So often ME myself and I, have to send email about point from the archive to the mailing-list. Often I do not even see that a bug has been posted and YES I have 5 rss feed and I read them all. What is the last time you read the bug archives to see what is happening there? So if you do not read the archive then how can you help? how can we make sure that people are aware? What is the last time you look at the code of the fixes that got integrated? Because if you do not read it how can we do quality control? So if I could I would send the diff of all the package in the mailing-lits as this is done in squeak. Now what we can do to please some of you so far 4, we could create a mailing-list where such mails would be sent. But let us see so far who is really against. Stef > Remember that most email client support filters. You can easily create one. > > Cheers > > Mariano

5 5