- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3803 in pharo: Create an issue tracker for Cog VM development

by pharo＠googlecode.com

Comment #3 on issue 3803 by geert.wl...(a)gmail.com: Create an issue tracker for Cog VM development http://code.google.com/p/pharo/issues/detail?id=3803 Why gitorious? I know GitHub has an integrated issue tracker: https://github.com/features/projects/collaboration

March 10, 2011

Re: [Pharo-project] Issue 3803 in pharo: Create an issue tracker for Cog VM development

by pharo＠googlecode.com

Comment #2 on issue 3803 by geert.wl...(a)gmail.com: Create an issue tracker for Cog VM development http://code.google.com/p/pharo/issues/detail?id=3803 Why gitorious? I know GitBuh has an integrated issue tracker: https://github.com/features/projects/collaboration

March 10, 2011

Re: [Pharo-project] Issue 3728 in pharo: Changed MenuMorph references to go through UIManager default menuClass

by pharo＠googlecode.com

Comment #14 on issue 3728 by fernando...(a)gmail.com: Changed MenuMorph references to go through UIManager default menuClass http://code.google.com/p/pharo/issues/detail?id=3728 Stef, integrate this method please. Seems that when i incorporate the trait TEasilyThemed to the MorphicUIManager i didn't detect that evaluating "UIManager default alert: 'hello'" raises an error. Attachments: MorphicUIManager-openModal.st 957 bytes

March 10, 2011

Re: [Pharo-project] Issue 3803 in pharo: Create an issue tracker for Cog VM development

by pharo＠googlecode.com

Comment #1 on issue 3803 by marianopeck: Create an issue tracker for Cog VM development http://code.google.com/p/pharo/issues/detail?id=3803 does gitourious have that?

March 10, 2011

[Pharo-project] Issue 3804 in pharo: #cannotInterpret: fails to work with JIT Cog, but works with StackInterpreter

by pharo＠googlecode.com

Status: Accepted Owner: siguc...(a)gmail.com New issue 3804 by siguc...(a)gmail.com: #cannotInterpret: fails to work with JIT Cog, but works with StackInterpreter http://code.google.com/p/pharo/issues/detail?id=3804 See tests failing in: http://code.google.com/p/pharo/issues/detail?id=3648 These tests are failing in Cog, but not in StackInterpreter: MessageCatchingProxyTests Update by Eliot: " Just to confirm, I have fixed this in my working image but have yet to push it to the repository because due to other changes I have introduced some regressions by mistake. "

March 10, 2011

[Pharo-project] Issue 3803 in pharo: Create an issue tracker for Cog VM development

by pharo＠googlecode.com

Status: Accepted Owner: siguc...(a)gmail.com New issue 3803 by siguc...(a)gmail.com: Create an issue tracker for Cog VM development http://code.google.com/p/pharo/issues/detail?id=3803 This has to be solved. But of course not just for Pharoers, but for everyone involved.

March 10, 2011

[Pharo-project] Issue 3802 in pharo: A strange superclasses if Canvas

by pharo＠googlecode.com

Status: Accepted Owner: siguc...(a)gmail.com New issue 3802 by siguc...(a)gmail.com: A strange superclasses if Canvas http://code.google.com/p/pharo/issues/detail?id=3802 Imagine that you can do something like: Object new drawOnCanvas: World assuredCanvas no, don't imagine. You can do that! :) At least it is supposed to work, because Canvas inherits from some strange things (NullEncoder, FlattenEncoder), so you can actually instruct any object to draw itself on canvas.. which is makes some sense (sort of): Canvas>>draw: anObject ^anObject drawOn: self Object>>drawOnCanvas:aStream self flattenOnStream:aStream. But as to me, Object should NOT implement #drawOnCanvas:, nor #drawOn:. Period. The real users of protocols placed in NullEncoder and FlattenEncoder is PostscriptCanvas which are not included into core images. So, the proposal is to remove the extra noise by making Canvas to be the subclass of Object. And for things which do care about serializing drawing commands onto some stream (like PostScriptCanvas do), make a subclass and introduce this behavior later.

March 10, 2011

Re: [Pharo-project] Issue 3801 in pharo: FSystemNavigation>>#methodHierarchyBrowserForClass

by pharo＠googlecode.com

Updates: Summary: FSystemNavigation>>#methodHierarchyBrowserForClass Status: Accepted Comment #1 on issue 3801 by Benjamin...(a)gmail.com: FSystemNavigation>>#methodHierarchyBrowserForClass http://code.google.com/p/pharo/issues/detail?id=3801 Yep, but it come from SystemNavigation ... SystemNavigation default methodHierarchyBrowserForClass: Boolean selector: #ifTrue:.

March 10, 2011

Re: [Pharo-project] New widget

by Benjamin

Even if it looks strange, it's the expected behavior since the compiled methods are equals Ben On Mar 10, 2011, at 8:57 AM, Patrick Barroca wrote: > Same selection behavior as described by Mariano for me in 1.2. > > On Wed, Mar 9, 2011 at 10:01 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Indeed, in 1.2 it works fine. But I guess I am so stupid to understand it or there is a bug ;) > When I select for example, #isLiteral, then the #isSelfEvaluating is also with color. > > Or if select #and: then, #ifFalse: #ifTrue: and #or: are selected. > > is this normal, if true, what does it mean? > > thanks! > > mariano > > > On Wed, Mar 9, 2011 at 9:02 PM, laurent laffont <laurent.laffont(a)gmail.com> wrote: > I've tried in Pharo 1.2, it works. I'm waiting for a real usage before giving feedback ;) > > Laurent. > > On Wed, Mar 9, 2011 at 6:09 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > Hello everyone, > > I've done a new Morphic widget, that allow to easily switch from a categorized view to a "all elements" view (quite hard to explain, let me give you an example ^^) > > > > Gofer new > squeaksource: 'SwitchableTreeWidget'; > package: 'SwitchableTreeWidget'; > load. > > SwitchableCategoriesTreeExample new openInWorld. > > If you click on the button or just double click on the tree, you will switch the view :) > > I wrote that widget to integrate it in a new browser (and if I succeed, to create a new Glamour widget) > > > > Thanks in for your feedback :) > > > Ben > > > > > > -- > Patrick Barroca

March 10, 2011

Re: [Pharo-project] New widget

by Patrick Barroca

Same selection behavior as described by Mariano for me in 1.2. On Wed, Mar 9, 2011 at 10:01 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > Indeed, in 1.2 it works fine. But I guess I am so stupid to understand it > or there is a bug ;) > When I select for example, #isLiteral, then the #isSelfEvaluating is also > with color. > > Or if select #and: then, #ifFalse: #ifTrue: and #or: are selected. > > is this normal, if true, what does it mean? > > thanks! > > mariano > > > On Wed, Mar 9, 2011 at 9:02 PM, laurent laffont <laurent.laffont(a)gmail.com > > wrote: > >> I've tried in Pharo 1.2, it works. I'm waiting for a real usage before >> giving feedback ;) >> >> Laurent. >> >> On Wed, Mar 9, 2011 at 6:09 PM, Benjamin < >> benjamin.vanryseghem.pharo(a)gmail.com> wrote: >> >>> Hello everyone, >>> >>> I've done a new Morphic widget, that allow to easily switch from a >>> categorized view to a "all elements" view (quite hard to explain, let me >>> give you an example ^^) >>> >>> >>> >>> Gofer new >>> squeaksource: 'SwitchableTreeWidget'; >>> package: 'SwitchableTreeWidget'; >>> load. >>> >>> SwitchableCategoriesTreeExample new openInWorld. >>> >>> If you click on the button or just double click on the tree, you will >>> switch the view :) >>> >>> I wrote that widget to integrate it in a new browser (and if I succeed, >>> to create a new Glamour widget) >>> >>> >>> >>> Thanks in for your feedback :) >>> >>> >>> Ben >>> >> >> > -- Patrick Barroca

March 10, 2011