- Pharo-dev - lists.pharo.org

[Pharo-project] Issue 3544 in pharo: Rename Morphic-Themes into Themes
by pharo＠googlecode.com April 8, 2011

April 8, 2011

Status: Accepted Owner: stephane...@gmail.com Labels: Milestone-1.2 New issue 3544 by stephane...@gmail.com: Rename Morphic-Themes into Themes http://code.google.com/p/pharo/issues/detail?id=3544 we should rename the Morphic-Themes package into what: Themes?

1 3

[Pharo-project] [update 1.3] #13136
by Marcus Denker April 8, 2011

April 8, 2011

13136 ----- Issue 3969: MorphTreeMorph performance Issue 3870: [Failing Test] 1.3 KernelTests.Methods.CompiledMethodTest.testNew -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Issue 3940 in pharo: BlockNode has undeclared ivar optimizedMessageNode
by pharo＠googlecode.com April 8, 2011

April 8, 2011

Status: Accepted Owner: marcus.d...@gmail.com Labels: Milestone-1.3 New issue 3940 by marcus.d...@gmail.com: BlockNode has undeclared ivar optimizedMessageNode http://code.google.com/p/pharo/issues/detail?id=3940 accessed in noteOptimizedIn: analyseTempsWithin: scopeBlock "<BlockNode>" rootNode: rootNode "<MethodNode>" assignmentPools: assignmentPools

1 3

[Pharo-project] Issue 3870 in pharo: [Failing Test] 1.3 KernelTests.Methods.CompiledMethodTest.testNew
by pharo＠googlecode.com April 8, 2011

April 8, 2011

Status: Accepted Owner: marcus.d...@gmail.com Labels: Milestone-1.3 New issue 3870 by marcus.d...@gmail.com: [Failing Test] 1.3 KernelTests.Methods.CompiledMethodTest.testNew http://code.google.com/p/pharo/issues/detail?id=3870 >>> KernelTests.Methods.CompiledMethodTest.testNew 0.0 1

1 5

Re: [Pharo-project] Issue 3969 in pharo: MorphTreeMorph performance
by pharo＠googlecode.com April 8, 2011

April 8, 2011

Updates: Status: FixProposed Comment #3 on issue 3969 by marcus.d...@gmail.com: MorphTreeMorph performance http://code.google.com/p/pharo/issues/detail?id=3969 (No comment was entered for this change.)

1 2

[Pharo-project] Metacello chapter
by StÃ©phane Ducasse April 8, 2011

April 8, 2011

Hi guys here is a new version of the metacello chapter. So we wrote it, rewrote it, rerewrote it. Now if this is of interest for you you can read it. But if you don't it means that I'm losing my time and I should stop writing and like that you can cry that there is no doc about Pharo. Stef

8 20

[Pharo-project] A step toward reducing complexity
by DougEdmunds April 8, 2011

April 8, 2011

Reduce the complexity of user interface themes In general, user interface themes should inherit directly from UITheme, not from a chain of themes. When you have a chain of themes, you are stuck with the intermediate themes, whether you need/use them or not. Consider GLMUITheme. Currently it is under UIThemeWatery2, which is under UIThemeWatery, which is under UITheme. Some characteristics inherited from the chain are missing, but in principal, GLMUITheme can be moved directly under UITheme with just 3 changes. 1. Add an instanceVariable 'windowActiveDropShadowStyle' UITheme subclass: #GLMUITheme instanceVariableNames: 'windowActiveDropShadowStyle' classVariableNames: '' poolDictionaries: '' category: 'Glamour-Morphic-Theme' 2. Add a class method isAbstract "Answer whether the receiver is considered to be abstract." ^false 3. Add an instance method windowActiveDropShadowStyle: anObject "Set the value of windowActiveDropShadowStyle" windowActiveDropShadowStyle := anObject Because GLMOrangeUITheme inherits these changes, it does not need modification. -- View this message in context: http://forum.world.st/A-step-toward-reducing-complexity-tp3404504p3404504.h… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

4 10

[Pharo-project] Making layouts using anchors
by Igor Stasenko April 8, 2011

April 8, 2011

Hi, i hacked morphs a bit to use anchors for laying out the morphs. The idea that you can force morph to make one of its edges (left, top, bottom, right) be dependent from other morph's edge. Here an example: | window morph morph2 | window := StandardWindow labelled: 'foo'. window color: Color red. morph := Morph new. morph anchorLeft: window leftAnchor + (window widthAnchor * 0.5) - 20. morph anchorRight: window leftAnchor + (window widthAnchor * 0.5) + 20. morph anchorTop: window topAnchor + 20. morph anchorBottom: window bottomAnchor - 20. morph2 := Morph new. morph2 color: Color green. morph2 anchorLeft: morph rightAnchor + 10. morph2 anchorRight: morph rightAnchor + 50. morph2 anchorTop: window topAnchor + 20. morph2 anchorBottom: window bottomAnchor - 20. window addMorph: morph2. window addMorph: morph. window openInWorld. window extent: 200@200. You can of course implement same layout using proportional layouts i.e. you can do window addMorph: fullFrame: ... but note that while its okay for first morph you add , a morph2 left edge is actually depending on first morph right edge. So, if it will be resized by other means (like stretched by inner morph), you won't be able to align sibling accordingly, and then you are forced to use table layout or something else. What i like about anchors that it reflects the natural way of thinking of UI designer i.e. : "I want this morph to align to window right edge" or "I want this morph to align to previous morph right edge with 10 pixels offset" For example, if i have two morphs, left and right, and i want to put my morph in the middle of them to fill the space between them, i can simply do: middle := Morph new. middle anchorLeft: leftMorph rightAnchor + 10. middle anchorRight: rightMorph leftAnchor - 10. so, you will get a following layout: [leftMorph] [ 10 pixels ] [ ... middle morph ..... ] [ 10 pixels ] [right morph ] with just two lines of code! P.S. Of course , anchors are in conflict with layouts, because you cannot have both. But some combination of them could still be used. -- Best regards, Igor Stasenko AKA sig.

3 7

[Pharo-project] Debugging Cog crash
by Schwab,Wilhelm K April 8, 2011

April 8, 2011

Hello all, I have an account on an Ubuntu terminal server (at least I think that's what it would be called) running 10.10. The Cog one-click image crashes with "Segmentation fault" (if run from a terminal); the legacy VM seems to run the image nicely on the box. Any ideas? I will happily collect any facts that will be of help, but I need some direction. Bill

3 2

[Pharo-project] Issue 3965 in pharo: Turn off Smart Characters in Full Image by default
by pharo＠googlecode.com April 8, 2011

April 8, 2011

Status: Accepted Owner: marcus.d...@gmail.com Labels: Milestone-1.2.2-DevImage New issue 3965 by marcus.d...@gmail.com: Turn off Smart Characters in Full Image by default http://code.google.com/p/pharo/issues/detail?id=3965 .. because they make it very hard to type for many people

2 2