- Pharo-dev - lists.pharo.org

[Pharo-project] Automatic One-Click VM
by Geert Claes Feb. 1, 2011

Feb. 1, 2011

Can we replace the Croquet VM exe file that is bundled in the one-click images generated using Hudson with a with a Pharo branded one? -- View this message in context: http://forum.world.st/Automatic-One-Click-VM-tp3251164p3251164.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

1 0

[Pharo-project] SoundSettings reference in Sound?
by StÃ©phane Ducasse Feb. 1, 2011

Feb. 1, 2011

Hi guy when I take 1.2 latest version I see that there are reference to SoundSetting in SoundPlayer. Now I cannot find any definition of this setting. Henrik I saw that you work on setting in sounds. Does it ring a bell for you? Stef resumePlaying: aSound quickStart: quickStart "Start playing the given sound without resetting it; it will resume playing from where it last stopped. If quickStart is true, then try to start playing the given sound immediately." | doQuickStart | SoundSettings soundsEnabled ifFalse: [^ self]. doQuickStart := quickStart. SoundSettings soundQuickStart ifFalse: [doQuickStart := false]. PlayerProcess == nil ifTrue: [ self canStartPlayer ifFalse: [^ self]. ^self startUpWithSound: aSound]. PlayerSemaphore critical: [ (ActiveSounds includes: aSound) ifTrue: [doQuickStart := false] ifFalse: [ doQuickStart ifFalse: [ActiveSounds add: aSound]]]. "quick-start the given sound, unless the sound player has just started" doQuickStart ifTrue: [self startPlayingImmediately: aSound].

2 1

Re: [Pharo-project] how to use dejavu bitmap fonts
by Marcus Denker Feb. 1, 2011

Feb. 1, 2011

On Feb 1, 2011, at 11:02 AM, Benjamin wrote: > If it's still not working, I can have a look if you want :) > We should integrate that into 1.3 soon... > > Ben > > On Feb 1, 2011, at 7:07 AM, StÃ©phane Ducasse wrote: > >> >>> Hi Doru, >>> I've take a look and I think I've fixed it. >>> Unfortunately the network is much too slow here for this BIG package. >>> You can simply fix it by yourself locally (before it is uploaded on squeaksource). >>> Just edit DejaVuHolder class >> #installSizes: >>> and set it to: >>> >>> installSizes: aListOfInteger >>> "self installSizes: #(7 8 9 10 11 12 13 14 24)" >>> TextConstants TextSharedInformation >>> at: self fontName >>> put: (TextStyle fontArray: (self loadFromStructuresList: (self fontStructureNamesForSizes: aListOfInteger))). >>> StrikeFont useUnderscoreIfOver1bpp. >> >> Yes this should be it. >> >> Doru TextConstants was a dictionary containing poolVariables (old abstractions) AND values that people just added >> as global dictionary. What we did was to define the fixed part of TextConstant = the poolVariables as a real SharedPool and the rest >> the shitty part (where all the system register things in this nice global variables (instead of using adequate class variables)) is now in >> the classVariable TextSharedInformation of TextConstants >> >> Stef > > -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Issue 3642 in pharo: Morphic Keybinding
by pharo＠googlecode.com Feb. 1, 2011

Feb. 1, 2011

Status: New Owner: ---- New issue 3642 by fernando...(a)gmail.com: Morphic Keybinding http://code.google.com/p/pharo/issues/detail?id=3642 It's time to provide a clean and scalable solution for implementing keybindings in Morphic. There are several propositions: Guillermo Pollito work and the Keybindings in use in Gaucho. I'll add the code as changesets attached to this issue, so we can iterate and refine them. To eventually integrate this work of Guillermo's into Morphic.

1 0

Re: [Pharo-project] Tracing bugs/corrections/regressions ... in Pharo
by Marcus Denker Feb. 1, 2011

Feb. 1, 2011

On Feb 1, 2011, at 8:13 AM, StÃ©phane Ducasse wrote: > Tx nicolas > >>>> >>> In a case like that, the changeset was just merged in the release. > > Marcus I thought that there was another fix. No, there was no fix. > May be it was already integrated. No, else the test would not fail > we wrote the test to make sure that > the behavior is documented. > >>> >>> The test is failing, as you can see: >>> >>> https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.3/lastCompleted… >>> >>> >> >> This is probably because you must >> (Object recompile: #perform:withArguments:) >> >> Nicolas > -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Issue 3640 in pharo: better systemVersion API
by pharo＠googlecode.com Feb. 1, 2011

Feb. 1, 2011

Status: fixed Owner: stephane...(a)gmail.com Labels: Milestone-1.3 New issue 3640 by stephane...(a)gmail.com: better systemVersion API http://code.google.com/p/pharo/issues/detail?id=3640 So that we can use it for having different updates.list files

1 1

[Pharo-project] [update 1.3] #13035
by StÃ©phane Ducasse Feb. 1, 2011

Feb. 1, 2011

13035 ----- - Issue 3234: fold: reduce: Merge. - Issue 3640: better systemVersion API

1 0

[Pharo-project] Issue 3641 in pharo: possible new implementation of reduce:
by pharo＠googlecode.com Feb. 1, 2011

Feb. 1, 2011

Status: Accepted Owner: stephane...(a)gmail.com Labels: Milestone-1.3 New issue 3641 by stephane...(a)gmail.com: possible new implementation of reduce: http://code.google.com/p/pharo/issues/detail?id=3641 there is already a version of reduce: made by lukas and I would like to know the difference with this one (proposed by eliot because squeak did not got reduce:) if people can comment on speed... and whatever it would be good. Collection>>reduce: binaryBlock "Apply the argument, binaryBlock cumulatively to the elements of the receiver. For sequenceable collections the elements will be used in order, for unordered collections the order is unspecified." | first nextValue | first := true. self do: [ :each | first ifTrue: [ nextValue := each. first := false ] ifFalse: [ nextValue := binaryBlock value: nextValue value: each ] ]. first ifTrue: [ self errorEmptyCollection ]. ^nextValue! !

1 1

Re: [Pharo-project] Issue 3234 in pharo: fold: reduce: Merge
by pharo＠googlecode.com Feb. 1, 2011

Feb. 1, 2011

Updates: Labels: Milestone-1.3 Comment #1 on issue 3234 by siguc...(a)gmail.com: fold: reduce: Merge http://code.google.com/p/pharo/issues/detail?id=3234 - here the changeset for integrating it Attachments: foldreduce.1.cs 1.1 KB

1 2

Re: [Pharo-project] TODO 1.2
by Marcus Denker Feb. 1, 2011

Feb. 1, 2011

On Jan 31, 2011, at 7:38 PM, Lukas Renggli wrote: >> Can I suggest that we really remove the non show stopper? >> and I'm sorry but we cannot maintain packages we do not know. >> >> Lukas could you integrate the fix I did for OB? > > I suggest that you publish the changes to your own repository. I would > like to keep the code in http://source.lukas-renggli.ch/omnibrowser/ > working in Pharo 1.1. > But it is clear that staying backward compatible forever will not make sense? I personally do not have energy for that. in 1.1, everyone used OB and was happy. So why would anyone using 1.1 (which will not be many people) would need to have an updated OB? I personally think energy should not be wasted for this. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0