January 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3469 in pharo: [Failing Test] ShoutTests.Parsing.SHParserST80Test.testCollectionHierarchy

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #6 on issue 3469 by marcus.d...(a)gmail.com: [Failing Test] ShoutTests.Parsing.SHParserST80Test.testCollectionHierarchy http://code.google.com/p/pharo/issues/detail?id=3469 (No comment was entered for this change.)

Jan. 30, 2011

Re: [Pharo-project] Issue 3470 in pharo: [Failing Tests] OBKeyBindingsTest

by pharo＠googlecode.com

Comment #6 on issue 3470 by marcus.d...(a)gmail.com: [Failing Tests] OBKeyBindingsTest http://code.google.com/p/pharo/issues/detail?id=3470 Issue 3619 proposed a fix (I merged it into this report)

Jan. 30, 2011

Re: [Pharo-project] Issue 3470 in pharo: [Failing Tests] OBKeyBindingsTest

by pharo＠googlecode.com

Comment #5 on issue 3470 by marcus.d...(a)gmail.com: [Failing Tests] OBKeyBindingsTest http://code.google.com/p/pharo/issues/detail?id=3470 Issue 3619 has been merged into this issue.

Jan. 30, 2011

[Pharo-project] TODO 1.2

by Marcus Denker

Hi, So for a release, we need to fix the following bugs: http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2-DevImage Now as these are all problems of packages, not of the Core, I can not just commit to core. So we need to actually fix the package in the place where the package is loaded from. (potentially by discussion this with the maintainer) This is something anyone can do. We do not need to wait for Mariano to ne back from holiday (which will be in 3 weeks), nor will I do this. I am a bit sick of 1.2... Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Jan. 30, 2011

Re: [Pharo-project] Issue 3619 in pharo: Hudson Pharo 1.2dev OBBrowser keybinding

by pharo＠googlecode.com

Updates: Status: Duplicate Mergedinto: 3470 Comment #1 on issue 3619 by marcus.d...(a)gmail.com: Hudson Pharo 1.2dev OBBrowser keybinding http://code.google.com/p/pharo/issues/detail?id=3619 (No comment was entered for this change.)

Jan. 30, 2011

Re: [Pharo-project] Issue 3471 in pharo: [Failing Test] OBCmdAutoCategorizeWithAMCTest.testOBAutocategorizeCommandOverride

by pharo＠googlecode.com

Comment #8 on issue 3471 by marcus.d...(a)gmail.com: [Failing Test] OBCmdAutoCategorizeWithAMCTest.testOBAutocategorizeCommandOverride http://code.google.com/p/pharo/issues/detail?id=3471 Issue 3613 has an (alternative?) fix

Jan. 30, 2011

Re: [Pharo-project] Issue 3471 in pharo: [Failing Test] OBCmdAutoCategorizeWithAMCTest.testOBAutocategorizeCommandOverride

by pharo＠googlecode.com

Updates: Cc: marianopeck Comment #7 on issue 3471 by marcus.d...(a)gmail.com: [Failing Test] OBCmdAutoCategorizeWithAMCTest.testOBAutocategorizeCommandOverride http://code.google.com/p/pharo/issues/detail?id=3471 Issue 3613 has been merged into this issue.

Jan. 30, 2011

Re: [Pharo-project] Issue 3613 in pharo: Hudson 1.2 dev : testOBAutocategorizeCommandOverride

by pharo＠googlecode.com

Updates: Status: Duplicate Mergedinto: 3471 Comment #1 on issue 3613 by marcus.d...(a)gmail.com: Hudson 1.2 dev : testOBAutocategorizeCommandOverride http://code.google.com/p/pharo/issues/detail?id=3613 (No comment was entered for this change.)

Jan. 30, 2011

Re: [Pharo-project] Vision

by Igor Stasenko

I think the main point that we are not making software for some virtual users. We are making it for ourselves. For example - i was needed some level of guarantees from image when running in headless mode, so i can easily detect any problems and address them quickly. This lead me to implementing non-interactive ui manager stuff. So, now when image runs on Hudson server, any unexpected errors/behavior could be observed and fixed afterwards. -- Best regards, Igor Stasenko AKA sig.

Jan. 30, 2011

Re: [Pharo-project] Vision

by NicolÃ¡s Paez

I DO like this Vision. I remember myself about 8 years ago trying to give my first steps in Smalltalk on my own. Despite I had solid OOP knowledge it took a while to understand that there was no "main" function. All my experience was with Java and C++ and I couldn't understand where was the entry point of my application if there were no main. Of course, today things are totally different, there are many resources on the web but I think that we still can improve that, implementing improvements in the environment and generating more and better training resources. Saludos! Nico. blog: nicopaez.wordpress.com > Hi guys > > Some days ago we were chatting with igor and he made an interesting remark > about a kind of hidden philosophy > behind pharo: the idea that we systematically want to make the system > better. > In fact I realized that what we are doing is to make a system nice, robust > and powerful so that everybody can use > to realize their goals. But we want to have a system where not only smart > guys can manage to do something with it but also > less talented people like me (I know that some of you will say but stef you > are good, I'm a newbie in a lot of domains but > I learn fast if I can get a chance to avoid to bump on the walls). I want a > system that let me learn from itself. > I think that lot of things fall naturally in place from this vision > (documentation, oo practices - not having car inheriting from wheel, tests > comments, adequate abstractions, modularity). I want a system that > everybody can nicely build his own software. > So in short I want pharo to be like a nice garden with greenhouses for > building new garden with tools versus a jungle where > only skilled adventurers can make it through. > > Stef > > >

Jan. 30, 2011