- Pharo-dev - lists.pharo.org

[Pharo-project] Replacing the pharo logo
by Olivier Auverlot Feb. 24, 2011

Feb. 24, 2011

Hi, How to replacing the pharo logo with a custom picture ? In the collaboractive book, I found an article about "Putting a background picture" but it changes the background without modify the logo. Best regards Olivier ;-) www.auverlot.fr

3 7

[Pharo-project] Issue 3750 in pharo: The desktop logo should be changeable from the SettingBrowser
by pharo＠googlecode.com Feb. 24, 2011

Feb. 24, 2011

Status: Accepted Owner: aplan...(a)gmail.com New issue 3750 by aplan...(a)gmail.com: The desktop logo should be changeable from the SettingBrowser http://code.google.com/p/pharo/issues/detail?id=3750 very simple to do. I will add it soon

1 0

[Pharo-project] Metacello tests failing in 1.2
by Guillermo Polito Feb. 24, 2011

Feb. 24, 2011

Hi Dale! There are 13 failing tests on the 1.2 dev build since a week ago ( https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/141/testReport/ ). Do we have the right version? Do you have any clue so I don't dive in the code blindly? :) Cheers, Guille

3 9

[Pharo-project] MetacelloBrowser
by Alexandre Bergel Feb. 24, 2011

Feb. 24, 2011

Hi All, I am happy to announce that MetacelloBrowser is ready for public consumption. http://metacellobrowser.dcc.uchile.cl I am not releasing it because the idea of maintaining yet another software makes me particularly happy. I have been using it for a couple of months already for Mondrian, Spy and other projects. MetacelloBrowser has a great impact on the way I manage versions. My wish is to see the libraries that I use everyday better maintained and versioned. We should not let Pharo die because there is no GUI for Metacello. This is what MetacelloBrowser is about. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

4 5

[Pharo-project] Browser class list/switches
by Gary Chambers Feb. 24, 2011

Feb. 24, 2011

The white "border" (actually due to layout inset) has been bugging me for a while ;-) cs attached. Regards, Gary

1 0

[Pharo-project] Pharo 1.2 build failing - XML issue
by laurent laffont Feb. 24, 2011

Feb. 24, 2011

in Console: Error: Could not resolve: XML-Parser [XML-Parser-OttoBehrens.125] in /builds/workspace/Pharo 1.2/Pharo-1.2/package-cache http://www.squeaksource.com/XMLSupport Laurent Laffont - @lolgzs <http://twitter.com/#!/lolgzs> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/

1 0

[Pharo-project] Two methods I don't understand in FileDirectory
by Adrien BARREAU Feb. 24, 2011

Feb. 24, 2011

Hello, I'm taking a look in the Files package, and I don't understand what pieces of information these two methods are manipulating: - getMacFileTypeAndCreator: fileName - setMacFileNamed: fileName type: typeString creator: creatorString If somebody can explain me, it would be cool :) Thanks, Adrien.

2 1

[Pharo-project] [COTDC] 17 - MCSnapshotReader
by laurent laffont Feb. 23, 2011

Feb. 23, 2011

Today: MCSnapshotReader Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest Laurent

3 5

[Pharo-project] [update 1.3] #13062
by laurent laffont Feb. 23, 2011

Feb. 23, 2011

13062 ----- COTDC: - 9. HTTPDownloadRequest - L.Laffont - 10. DummyUIManager - L.Laffont - 11. ColorMappingCanvas - I.Stasenko, L.Laffont - 12. PluggableListMorphByItem - G.Chambers - 13. NullEncoder - I.Stasenko - 14. MCSnapshotReader - H.Johansen - 15. PSMCPatchMorph - G.Polito - 16. GoferReinitialize - L.Renggli Laurent

2 1

[Pharo-project] Issue 3748 in pharo: The Dark Side of Pharo: Keyboard Inputs
by pharo＠googlecode.com Feb. 23, 2011

Feb. 23, 2011

Status: New Owner: ---- New issue 3748 by camillob...(a)gmail.com: The Dark Side of Pharo: Keyboard Inputs http://code.google.com/p/pharo/issues/detail?id=3748 It seems that handling keyboard events is more or less random in pharo. These are the properties of the KeyboardEvent for different inputs under OSX: Cmd-home: [keystroke '<Cmd-home>'] keyVal=1 keyCode=1 scanCode=115 buttons=64 cmd=true ctrl=false Ctrl-home: [keystroke '<Cmd-home>'] keyVal=97 keyCode=1 scanCode=115 buttons=64 cmd=true ctrl=false ??? Cmd-a: [keystroke '<Cmd-a>'] keyVal=97 keyCode=97 scanCode=0 buttons=64 cmd=true ctrl=false Ctrl-a: [keystroke '<Cmd-home>'] keyVal=97 keyCode=1 scanCode=0 buttons=64 cmd=true ctrl=false ??? Alt-a: [keystroke '<Opt-Ã¥>'] keyVal=140 keyCode=229 scanCode=0 buttons=32 cmd=false ctrl=false Under Ubuntu: Cmd-home: NOT WORKING! (maybe virtualbox issues...) Ctrl-home: [keystroke '<Cmd-home>'] keyVal=97 keyCode=1 scanCode=97 buttons=64 cmd=true ctrl=false Cmd-a: NOT WORKING! (maybe virtualbox issues...) Ctrl-a: [keystroke '<Cmd-a>'] keyVal=97 keyCode=97 scanCode=97 buttons=64 cmd=true ctrl=false Alt-a: [keystroke '<Cmd-a>'] keyVal=97 keyCode=97 scanCode=97 buttons=64 cmd=true ctrl=false ??? Under Windose: Cmd-home: NOT WORKING! (maybe virtualbox issues...) Ctrl-home: [keystroke '<Cmd-home>'] keyVal=97 keyCode=1 scanCode=97 buttons=64 cmd=true ctrl=false Cmd-a: NOT WORKING! (maybe virtualbox issues...) Ctrl-a: [keystroke '<Cmd-home>'] keyVal=97 keyCode=1 scanCode=65 buttons=64 cmd=true ctrl=false??? Alt-a: [keystroke '<Cmd-a>'] keyVal=97 keyCode=97 scanCode=65 buttons=64 cmd=true ctrl=false ??? ---- I am your father Luke! ---- Several problems can be identified here: 1. There is no clear platform distinction between cmd and ctrl 2. missing support for meta (command under OSX) and alt under win/unix prohibits extended shortcuts 3. unification of different keyboard events under the same platform. which is undone for instance for ctrl-a and cmd-a under OSX select the whole text, although the input keyboardEvent shows no distinction in ctrlKeyPressed and cmdKeyPressed! Fix requires several steps: 1. fix the VM to forward clearly distinct keyboard events for ctrl and meta/command and alt 2. Unify the keyboard inputs on all three platforms, the inputs right now are unbearable and obey to obscure rules! 3. adapt the UI keyboard event handling to not rely on the internals of the keyboard event but a nice API 4. provide system dependent firstCommandKeyPressed and secondCommandKeyPressed in order to avoid the following ugly checks all over the system (aKeyboardEvent commandKeyPressed and: [ aKeyboardEvent controlKeyPressed ]) ---- may the force be with you ----

2 2