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

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

Nov. 19, 2010

>> > > Stef, > > I'm subscribed to some issues through standard Google Code "star this > issue" feature. So, I'm aware of the changes happening to these bugs. > I'm also subscribed to the RSS channel of the Pharo Google Code site, same here > but I do not follow it closely so far -- just have not enough time. So > my point is that interested people still are able to follow the > bugflow without subscribing the whole list to the updates. yes but you have to individually register. > > And if you want to make sure people are aware of the work you're > doing, I'd rather recommend you to pay more attention to the news page > of the pharo-project.org website. We cannot do that if this is not automated. Then the news are reviewed by native english speakers..... Probably we should have a dev news where we could push the issues comments but so far I do not know if this is possible > And having a list of immediate goals > and time line for them could also help, I think. Yes this is why I propose a IRC monthly meeting > Forcing people to follow all the minor activities happening on the tracker (I mean > changing milestones, statuses and so on) won't rather help (IMHO). > I've also created a filter to ignore all such messages after I've seen > them flooding my inbox. So I even don't see them and this fact somehow > contradicts to your point of making people aware. So other people just read them. I have a filter and I read them in batch. Sometimes just passing 0.5 s on an issue. > I still think important things are worth talking abouth them. I mean bootstraping > from kernel or new compiler or something else but in the form of > goals, plans, progress made and so on. Yeah, I know it's easier to > speak than actually do :), but effect might be better. Yes we do not want to replace the communication :) > You may now ask, why I'm so concerned about this issue, if I do not > even receive these autogenerated emails :) Ok, I just think that it's > wrong. But I may be wrong too of course :) There are two things I find > not practical. One of them is that replying to autogenerated mail in > the list and not copying these replies to the tracker actually splits > the discussion and makes it harder for people to track it later. Yes true may be we will need more discipline. > The other thing is mailing list archives like the one on Nabble. It's just > becoming harder to surfe them. And I'm not aware of the other > opensource projects doing the same with their mailing lists. > >> 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. > > You can't do quality control this way. Oh yes believe you do. I will tell you a small story that explained why I was mad against 3.10 process. One guy that is in network/web sent a fix and I thought as a 3.9 integrator that I would integrate it. Then bert reviewed the fix and said that this was bogus so it was not integrated in 3.9. In 3.10 there was little communication about bugs and I raised this concerned to the squeakfoundation board. Because if experts do not have access fast to what is happening then they will not look at it then your overall quality will decrease. This is why I really want the new recentMessage browser because it is gorgeous and I want to use it daily especially when others are doing integrations ( we want to open the process ). > Everyone won't look at the code of these fixes, interested people are already looking at them so you > won't gain anything. No this is where you are wrong. People are not. I have to add lukas in the bug entry manually .... I have to ask personnally people to look at specific issue. > And it's iterative process after all: you make > changes, people look at the code of these changes doing their job in > Pharo, and if they're unhappy with these changes you'll know about it > :) No because when you have time you do not look at other code. You hack your own great stuff. > But important changes still need to be reviewed by experienced > community members, no doubts here. > >> 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. > > Don't get me wrong, I'm not extremely against this change. I just > think that this is not the best way to achieve your goals. Thanks for sharing that with us. We will create a separated mailing-list to see how it works. > > My apologies for the long mail. > > George >

3 2

Re: [Pharo-project] [Pharo-users] could not search contents at http://book.pharo-project.org
by Mariano Martinez Peck Nov. 19, 2010

Nov. 19, 2010

Thanks! I can reproduce. Doru can you help us? Thanks Mariano On Thu, Oct 7, 2010 at 10:40 PM, Bernardo Ezequiel Contreras < vonbecmann(a)gmail.com> wrote: > Hi All, > > Description: > Could not search contents at http://book.pharo-project.org. > I would like to search some expression in the contents of the book. > > Steps to reproduce: > * goto to http://book.pharo-project.org > * click on main image > * add any string on search contents and press Enter > Actual Result: > Seaside Walkback Error: subscript is out of bounds: 8218Expected Result: > a list of results that matches your input string > > > Thanks, > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > >

2 3