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

Re: [Pharo-project] Issue 3583 in pharo: Shout should only be active in code panes

by pharo＠googlecode.com

Comment #15 on issue 3583 by stephane...(a)gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 Ben should we load the two changeset in 1.3?

Jan. 29, 2011

Re: [Pharo-project] Issue 3583 in pharo: Shout should only be active in code panes

by pharo＠googlecode.com

Comment #14 on issue 3583 by Benjamin...(a)gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 Here comes a new changeset which finally add shouting in the browser ^^ I've done it like I like to have shouting, but it can be changed easily ^^ Attachments: AddShoutingInTools.1.cs 11.9 KB

Jan. 29, 2011

[Pharo-project] How to take advantage of SimpleMorphic

by StÃ©phane Ducasse

Hi juan I'm not sure that this is possible to port all the changes of Morphic/Polymorph on top of SimpleMorphic. So I have questions: - what would be a process? - should we compare classes by classes (starting with which ones) and migrate the code in Morphic or doing the inverse? What could a migration plan? I have the impression that since SimpleMorphic is simpler I would - start to remove the stuff we already fixed from SimpleMorphic - start to migrate some widgets to SimpleMorphic Stef

Jan. 29, 2011

Re: [Pharo-project] Issue 3592 in pharo: MenuMorph uses action: and selector: to mean the same thing

by pharo＠googlecode.com

Updates: Status: Accepted Comment #1 on issue 3592 by stephane...(a)gmail.com: MenuMorph uses action: and selector: to mean the same thing http://code.google.com/p/pharo/issues/detail?id=3592 Reducing duplication is always good. Now action: is different from selector: to me in the sense that selector: #symbol and action: could be a block. But in any case it would be good to clean it.

Jan. 29, 2011

Re: [Pharo-project] Issue 3604 in pharo: Timespan created from Date>>to: missing last date

by pharo＠googlecode.com

Updates: Status: Accepted Comment #2 on issue 3604 by stephane...(a)gmail.com: Timespan created from Date>>to: missing last date http://code.google.com/p/pharo/issues/detail?id=3604 (No comment was entered for this change.)

Jan. 29, 2011

[Pharo-project] Vision

by StÃ©phane Ducasse

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. 29, 2011

Re: [Pharo-project] Issue 3599 in pharo: Serial Port

by pharo＠googlecode.com

Updates: Status: Closed Comment #3 on issue 3599 by stephane...(a)gmail.com: Serial Port http://code.google.com/p/pharo/issues/detail?id=3599 (No comment was entered for this change.)

Jan. 29, 2011

Re: [Pharo-project] Issue 3610 in pharo: Should remove Morphic-Undo

by pharo＠googlecode.com

Updates: Status: Closed Comment #6 on issue 3610 by stephane...(a)gmail.com: Should remove Morphic-Undo http://code.google.com/p/pharo/issues/detail?id=3610 in 13029

Jan. 29, 2011

Re: [Pharo-project] Issue 3608 in pharo: Fix failing MessageTally tests

by pharo＠googlecode.com

Updates: Status: Closed Comment #1 on issue 3608 by stephane...(a)gmail.com: Fix failing MessageTally tests http://code.google.com/p/pharo/issues/detail?id=3608 in 13029

Jan. 29, 2011

Re: [Pharo-project] Issue 3506 in pharo: TextMorph's #autoFit: and #wrapFlag: are confusing

by pharo＠googlecode.com

Comment #6 on issue 3506 by sean.p.d...(a)gmail.com: TextMorph's #autoFit: and #wrapFlag: are confusing http://code.google.com/p/pharo/issues/detail?id=3506 I can't find the mcz. I'm attaching the changes - "Fix-3506-TextMorphs-autoFit-and-wrapFlag-are-confusing-SeanDeNigris.1.cs". Attachments: Fix-3506-TextMorphs-autoFit-and-wrapFlag-are-confusing-SeanDeNigris.1.cs 571 bytes

Jan. 29, 2011