November 2008 - Pharo-dev - lists.pharo.org

[Pharo-project] small cleanup
by Pavel Krivanek Nov. 1, 2008

Nov. 1, 2008

This command removes some obsolete classes: (Preferences preferenceAt: #allowEtoyUserCustomEvents) changeInformee: nil changeSelector: nil. -- Pavel

2 1

[Pharo-project] about timesRepeat: changes?
by StÃ©phane Ducasse Nov. 1, 2008

Nov. 1, 2008

Hi one person is saying the following in the seaside mailinglist "In Pharo, some OmniBrowser functionality was broken and as I said timesRepeat: was broken. It had a '<' rather than '<=' for the loop comparison so the loop ran one too few times. I ran an update which fixed both problems. " Does one of you remember that we got a change changing timesRepeat: I have serious doubts this is why I"m asking. stef

2 1

[Pharo-project] How to load OmniBrowser into Pharo
by David RÃ¶thlisberger Nov. 1, 2008

Nov. 1, 2008

Hi, during the recent days we worked hard on OmniBrowser to extend, improve and stabilize it. We also improved the loading process of all required packages to run OmniBrowser (system and package browser). In the latest version of ScriptLoader you will find three load methods for OB: #loadOB loads the latest stable version linked in Universe. Use this to be on the safe side #loadOBAlpha loads the latest development version of all required packages stored in source.wiresong.ca/ob. Use this if you want to be on the cutting edge. ;) #loadSuperOB does the same as #loadOBAlpha, but also loads additional packages, for instance to get visualizations directly in OB. You use this to get everything. ;) Cheers, David

2 1

[Pharo-project] Preferences should be optional: aka towards reall OOP preferences
by StÃ©phane Ducasse Nov. 1, 2008

Nov. 1, 2008

Hi all Here is a call for good design sharing. I already posted a mail on that design issue but I want to restate it. I really want in the future to be able to remove Preferences (we need preferences but not the way they are). right now when I'm LittApp an application and run my little flow I will suddenly invoke the HUGE Global center (Preferences) to see what **I** have to do.... So at the end of the day we got, debugger, compiler, Morphic.... depending on preferences and this is WRONG. What we should have (illustrated really well with the MC sorting menu) is LittApp is responsible for its own preferences So it runs, and check **Itself**: "oh how should I behave, let me see ***my own*** state tell me to turn right, to be novice friendly... and I do it. Notice how little application does NOT reference to the HUGE Preference Global Now the BIG Preferences setter will just change the configuration of the little app. Preferences>>sortingLittleApp LittleApp sortTop Now of course, littApp could be a bit smarter and say BIGPreferenceSetter here are my preferences we could use pragmas to define preferences that BIGPreferences would gather and present to the user. Stef

1 0

Nov. 1, 2008

Hi guys We are really sorry about that but we will not accept code submitted with initials anymore because we do not know who is submitting. Just use your full name instead of initials. we will fix the Author class to ask for your full name! Stef and Marcus

4 10

[Pharo-project] [update] #1025
by Marcus Denker Nov. 1, 2008

Nov. 1, 2008

update1025 --------- Issue 303: TODO: remove profiling methods Issue 300: unimplemented call in AlignmentMorphBob1>>acceptDroppingMorph:event: Issue 299: Mantis 007007 and 007008 correct toggle break on entry -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

2 1