March 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [OT]: Fwd: Why GSoC? Why me?

by Sven Van Caekenberghe

I meant things like [2] which could be embedded directly. Also, [4] is something that you can link to. The 'Ideas for research' could all be links as well. I cannot find [1] in the text itself. You could also add some (relevant or just nice) pictures. > On 15 Mar 2015, at 17:00, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Thanks for the feedback! Could you be more specific? For example, I clicked the links and they seem to work... > > On Mar 15, 2015, at 5:54 AM, "Sven Van Caekenberghe-2 [via Smalltalk]" <[hidden email]> wrote: > >> Sean, >> >> The article is very good, but it could use some editing/cleanup. Have a look at what is possible in https://medium.com/concerning-pharo. You should at least make the links work. >> >> Sven >> >> > On 15 Mar 2015, at 02:57, Sean P. DeNigris <<a href="x-msg://52/user/SendEmail.jtp?type=node&node=4811959&i=0" target="_top" rel="nofollow" link="external">[hidden email]> wrote: >> > >> > philippeback wrote >> >> Because Sven articles are there already. >> > >> > Ah, okay :) I also posted to my blog and shared on reddit >> > http://redd.it/2z2ysg and HN https://news.ycombinator.com/item?id=9205061 >> > >> > >> > >> > ----- >> > Cheers, >> > Sean >> > -- >> > View this message in context: http://forum.world.st/OT-Fwd-Why-GSoC-Why-me-tp4811878p4811912.html >> > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >> > >> >> >> >> If you reply to this email, your message will be added to the discussion below: >> http://forum.world.st/OT-Fwd-Why-GSoC-Why-me-tp4811878p4811959.html >> To unsubscribe from [OT]: Fwd: Why GSoC? Why me?, click here. >> NAML > > Cheers, > Sean > > View this message in context: Re: [OT]: Fwd: Why GSoC? Why me? > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 15, 2015

Re: [Pharo-dev] [Pharo4] 203 issues tagged tagged for Pharo4

by Marcus Denker

Progress! Pharo4: 188 Pharo3: 5 Overall: 635 âclosed last weekâ: 71 > On 15 Mar 2015, at 11:40, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > We have 203 issues right now that have the Pharo4 Milestone: > > https://pharo.fogbugz.com/f/filters/103/4-0-All > > -> we need to go through that list and remove the tag for everything that is not > a show stopper. > -> if you know of an issue that is *not* on this list but should, please add the Pharo4 tag. > > Marcus >

March 15, 2015

Re: [Pharo-dev] [pharo-project/pharo-core] bea5e5: 40548

by Ben Coman

On Thu, Mar 12, 2015 at 10:34 PM, stepharo <stepharo(a)free.fr> wrote: > Ben > > thanks a lot for your effort! > I would love to get a little description of the new architecture. > > Stef > yes, I'll do this. I'll deliver after we clean up the mess I caused with the CI build. cheers -ben > > > > YAY!! Thanks Esteban for integration, and Nicolai and Max for code > reviews. > > To observe the new behaviour: > > 1. Tools > Process Browser > Observe at the top "(80) Delay Scheduling Process: > DelayMicrosecondScheduler>>runTimerEventLoop" > This based on the new primitive by Eliot that rolls over every 50,000 > years. > > 2. System > Settings > System > Delay Scheduler - select > "DelayMillisecondScheduler" > > 3. Right-click back in Process Browser, and select [update list]. > Observe at the top "(80) Delay Scheduling Process: > DelayMillisecondScheduler>>runTimerEventLoop" > This is the old primitive that rolls over every 6 days. > > Actually not really very exciting to look at ;) - but there you go! I'm > glad its integrated. Now we'll see if any corner case bugs shake out of > the woodwork. > > Note that the option list also includes "DelayScheduler". This is the > old scheduler I refactored out from the class side of Delay. This was only > kept as-is to smooth this integration step. It essentially became > DelayMillisecondScheduler and will be removed from that list to allow some > required cleanup to proceed. > > In the "super fast delay" thread I'll advise that it is solved. > > cheers -ben > > > On Tue, Mar 10, 2015 at 11:43 PM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > >> >> > On 10 Mar 2015, at 16:31, GitHub <noreply(a)github.com> wrote: >> > >> > Branch: refs/heads/4.0 >> > Home: https://github.com/pharo-project/pharo-core >> > Commit: bea5e5edece36093f82ab3a8854b61377dfbd0a1 >> > >> https://github.com/pharo-project/pharo-core/commit/bea5e5edece36093f82ab3a8… >> > Author: Jenkins Build Server <board(a)pharo-project.org> >> > Date: 2015-03-10 (Tue, 10 Mar 2015) >> > >> > Changed paths: >> > M Kernel.package/Delay.class/README.md >> > R Kernel.package/Delay.class/class/enable new code/newCodeEnabled.st >> > A Kernel.package/Delay.class/class/settings/delaySchedulerClass.st >> > A Kernel.package/Delay.class/class/settings/delaySchedulerClass_.st >> > A Kernel.package/Delay.class/class/settings/systemSettingOn_.st >> > M Kernel.package/Delay.class/definition.st >> > R Kernel.package/Delay.class/instance/enable new >> code/newCodeEnabled.st >> > A Kernel.package/Delay.class/instance/printing/millisecondsToGo.st >> > M Kernel.package/Delay.class/instance/printing/printOn_.st >> > A Kernel.package/Delay.class/instance/private - >> scheduler/schedulerBeingWaitedOn.st >> > A Kernel.package/Delay.class/instance/private - >> scheduler/schedulerBeingWaitedOn_.st >> > A Kernel.package/Delay.class/instance/private - >> scheduler/schedulerResumptionTime.st >> > A Kernel.package/Delay.class/instance/private - >> scheduler/schedulerResumptionTime_.st >> > A Kernel.package/Delay.class/instance/private - >> scheduler/schedulerSignalWaitingProcess.st >> > A Kernel.package/Delay.class/instance/private - >> scheduler/scheduler_resumptionTime_.st >> > M Kernel.package/Delay.class/instance/private/setDelay_.st >> > M >> Kernel.package/Delay.class/instance/private/setDelay_forSemaphore_.st >> > M Kernel.package/Delay.class/instance/public/delayDuration.st >> > A >> Kernel.package/Delay.class/instance/public/millisecondDelayDuration.st >> > A Kernel.package/DelayMicrosecondScheduler.class/README.md >> > A Kernel.package/DelayMicrosecondScheduler.class/definition.st >> > A Kernel.package/DelayMicrosecondScheduler.class/instance/low >> priority processes/schedule_.st >> > A >> Kernel.package/DelayMicrosecondScheduler.class/instance/primitives/primSignal_atUTCMicroseconds_.st >> > A >> Kernel.package/DelayMicrosecondScheduler.class/instance/printing/millisecondsUntilResumptionTime_.st >> > A >> Kernel.package/DelayMicrosecondScheduler.class/instance/snapshotting/adjust_resumptionTimeOldBase_newBase_.st >> > A >> Kernel.package/DelayMicrosecondScheduler.class/instance/snapshotting/restoreResumptionTimes.st >> > A >> Kernel.package/DelayMicrosecondScheduler.class/instance/snapshotting/saveResumptionTimes.st >> > A >> Kernel.package/DelayMicrosecondScheduler.class/instance/snapshotting/startUp.st >> > A Kernel.package/DelayMicrosecondScheduler.class/instance/timer >> process/handleTimerEvent_.st >> > A Kernel.package/DelayMicrosecondScheduler.class/instance/timer >> process/runTimerEventLoop.st >> > A Kernel.package/DelayMicrosecondScheduler.class/instance/timer >> process/scheduleDelay_.st >> > A Kernel.package/DelayMicrosecondScheduler.class/instance/timer >> process/startTimerEventLoop.st >> > A Kernel.package/DelayMicrosecondScheduler.class/instance/timer >> process/stopTimerEventLoop.st >> > A Kernel.package/DelayMicrosecondScheduler.class/instance/timer >> process/unscheduleDelay_.st >> > A Kernel.package/DelayMillisecondScheduler.class/README.md >> > A Kernel.package/DelayMillisecondScheduler.class/definition.st >> > A Kernel.package/DelayMillisecondScheduler.class/instance/low >> priority processes/schedule_.st >> > A >> Kernel.package/DelayMillisecondScheduler.class/instance/primitives/primSignal_atMilliseconds_.st >> > A >> Kernel.package/DelayMillisecondScheduler.class/instance/printing/millisecondsUntilResumptionTime_.st >> > A >> Kernel.package/DelayMillisecondScheduler.class/instance/snapshotting/adjust_resumptionTimeOldBase_newBase_.st >> > A >> Kernel.package/DelayMillisecondScheduler.class/instance/snapshotting/restoreResumptionTimes.st >> > A >> Kernel.package/DelayMillisecondScheduler.class/instance/snapshotting/saveResumptionTimes.st >> > A Kernel.package/DelayMillisecondScheduler.class/instance/timer >> process/handleTimerEvent_.st >> > A Kernel.package/DelayMillisecondScheduler.class/instance/timer >> process/runTimerEventLoop.st >> > A Kernel.package/DelayMillisecondScheduler.class/instance/timer >> process/scheduleDelay_.st >> > A Kernel.package/DelayMillisecondScheduler.class/instance/timer >> process/startTimerEventLoop.st >> > A Kernel.package/DelayMillisecondScheduler.class/instance/timer >> process/stopTimerEventLoop.st >> > A Kernel.package/DelayMillisecondScheduler.class/instance/timer >> process/unscheduleDelay_.st >> > M Kernel.package/DelayScheduler.class/README.md >> > M Kernel.package/DelayScheduler.class/instance/class initialization/ >> initialize.st >> > A >> Kernel.package/DelayScheduler.class/instance/printing/millisecondsUntilResumptionTime_.st >> > M >> Kernel.package/DelayScheduler.class/instance/testing/nextWakeUpTime.st >> > M Kernel.package/DelayScheduler.class/instance/timer >> process/stopTimerEventLoop.st >> > A >> Kernel.package/DelayWaitTimeout.class/instance/signaling/schedulerSignalWaitingProcess.st >> > A Kernel.package/Duration.class/instance/converting/asMicroseconds.st >> > A >> Kernel.package/MonitorDelay.class/instance/private/schedulerSignalWaitingProcess.st >> > A KernelTests.package/DelayMicrosecondSchedulerTest.class/README.md >> > A KernelTests.package/DelayMicrosecondSchedulerTest.class/ >> definition.st >> > A >> KernelTests.package/DelayMicrosecondSchedulerTest.class/instance/running/tearDown.st >> > A >> KernelTests.package/DelayMicrosecondSchedulerTest.class/instance/support/busyWaitMilliseconds_.st >> > A >> KernelTests.package/DelayMicrosecondSchedulerTest.class/instance/tests/testDurationLessThanMaxTicks.st >> > A >> KernelTests.package/DelayMicrosecondSchedulerTest.class/instance/tests/testDurationMoreThanMaxTicks.st >> > A >> KernelTests.package/DelayMicrosecondSchedulerTest.class/instance/tests/testForMilliseconds.st >> > A >> KernelTests.package/DelayMicrosecondSchedulerTest.class/instance/tests/testForSeconds.st >> > A >> KernelTests.package/DelayMicrosecondSchedulerTest.class/instance/tests/testMillisecondsToGo.st >> > A >> KernelTests.package/DelayMicrosecondSchedulerTest.class/instance/tests/testTestInterferenceWithSystemTimingSemaphore.st >> > A KernelTests.package/DelayMillisecondSchedulerTest.class/README.md >> > A KernelTests.package/DelayMillisecondSchedulerTest.class/ >> definition.st >> > A >> KernelTests.package/DelayMillisecondSchedulerTest.class/instance/running/tearDown.st >> > A >> KernelTests.package/DelayMillisecondSchedulerTest.class/instance/support/busyWaitMilliseconds_.st >> > A >> KernelTests.package/DelayMillisecondSchedulerTest.class/instance/tests/testDurationLessThanMaxTicks.st >> > A >> KernelTests.package/DelayMillisecondSchedulerTest.class/instance/tests/testDurationMoreThanMaxTicks.st >> > A >> KernelTests.package/DelayMillisecondSchedulerTest.class/instance/tests/testForMilliseconds.st >> > A >> KernelTests.package/DelayMillisecondSchedulerTest.class/instance/tests/testForSeconds.st >> > A >> KernelTests.package/DelayMillisecondSchedulerTest.class/instance/tests/testMillisecondsToGo.st >> > A >> KernelTests.package/DelayMillisecondSchedulerTest.class/instance/tests/testTestInterferenceWithSystemTimingSemaphore.st >> > R KernelTests.package/DelaySchedulerTest.class/README.md >> > R KernelTests.package/DelaySchedulerTest.class/definition.st >> > R >> KernelTests.package/DelaySchedulerTest.class/instance/running/tearDown.st >> > R >> KernelTests.package/DelaySchedulerTest.class/instance/tests/testMaxTickLessThanDuration.st >> > R >> KernelTests.package/DelaySchedulerTest.class/instance/tests/testMaxTickMoreThanDuration.st >> > R >> KernelTests.package/DelaySchedulerTest.class/instance/tests/testTestInterferenceWithSystemTimingSemaphore.st >> > R ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/ >> script547.st >> > A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/ >> script548.st >> > R ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/ >> update40547.st >> > A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/ >> update40548.st >> > M >> ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st >> > >> > Log Message: >> > ----------- >> > 40548 >> > 14353 Delay refactoring (part 2) - change from milliseconds to >> microseconds >> > https://pharo.fogbugz.com/f/cases/14353 >> > >> > http://files.pharo.org/image/40/40548.zip >> >> a distinctive four-note "short-short-short-long" motif twice ;-) >> >> it seems to work fine, great work Ben ! >> >> Sven >> >> >> > >

March 15, 2015

Re: [Pharo-dev] [OT]: Fwd: Why GSoC? Why me?

by Sean P. DeNigris

Thanks for the feedback! Could you be more specific? For example, I clicked the links and they seem to work... On Mar 15, 2015, at 5:54 AM, "Sven Van Caekenberghe-2 [via Smalltalk]" <ml-node+s1294792n4811959h17(a)n4.nabble.com> wrote: > Sean, > > The article is very good, but it could use some editing/cleanup. Have a look at what is possible in https://medium.com/concerning-pharo. You should at least make the links work. > > Sven > > > On 15 Mar 2015, at 02:57, Sean P. DeNigris <[hidden email]> wrote: > > > > philippeback wrote > >> Because Sven articles are there already. > > > > Ah, okay :) I also posted to my blog and shared on reddit > > http://redd.it/2z2ysg and HN https://news.ycombinator.com/item?id=9205061 > > > > > > > > ----- > > Cheers, > > Sean > > -- > > View this message in context: http://forum.world.st/OT-Fwd-Why-GSoC-Why-me-tp4811878p4811912.html > > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > > > > > > > If you reply to this email, your message will be added to the discussion below: > http://forum.world.st/OT-Fwd-Why-GSoC-Why-me-tp4811878p4811959.html > To unsubscribe from [OT]: Fwd: Why GSoC? Why me?, click here. > NAML ----- Cheers, Sean -- View this message in context: http://forum.world.st/OT-Fwd-Why-GSoC-Why-me-tp4811878p4812019.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 15, 2015

PharoVM for openindiana

by Andreas Wacknitz

Hi all, I decided to build a PharoVM as of today for openindiana following my notes I took last year when I did it last. For this build I am using the PharoVM sources as of today (15th March, 2015) from https://github.com/pharo-project/pharo-vm. I am bootstrapping it from my Mac. First finding: Running newImage.sh shows a problem with an outdated class in the SoundSystem which leads to the error log that I appended to this mail. The reason for this problem is an outdated class BaseSoundSystem which inherits from AbstractSoundSystem. Pharo 3.0 changed the name from AbstractSoundSystem to SoundSystem. Thus, Sound.Package (GuillermoPolito.69) needs an update. Regards Andreas

March 15, 2015

Re: [Pharo-dev] [Issue Tracker] open issues down to 644

by Marcus Denker

Down to 641. Can *you* get it to 640? Every single one counts! > On 14 Mar 2015, at 09:48, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > We managed to get the issue tracker to 644 open issuesâ¦. with e.g. 60 issues closed the last 7 days > alone. > > For one this is nice: number of issues is decreasing even though new issues are reported. > > Yes 644 is very high. > > Ca everyone please check the reports, especially you own old ones? Maybe an issue open > since >12 months of the âwould be niceâ kind actually can be closed? Or things that only > you care about but even that not enough to actually do something? > > Keep in mind that it would be trivial to add literally *thousands* of âthis looks strangeâ âmaybe > this could be simplerâ or âit would be nice ifâ issues. Just that it does not help anyone, as nobody > will ever do this if it is already not important enough for *you* to do. > > Marcus

March 15, 2015

[Pharo4] 203 issues tagged tagged for Pharo4

by Marcus Denker

Hi, We have 203 issues right now that have the Pharo4 Milestone: https://pharo.fogbugz.com/f/filters/103/4-0-All -> we need to go through that list and remove the tag for everything that is not a show stopper. -> if you know of an issue that is *not* on this list but should, please add the Pharo4 tag. Marcus

March 15, 2015

Re: [Pharo-dev] [OT]: Fwd: Why GSoC? Why me?

by Sven Van Caekenberghe

Sean, The article is very good, but it could use some editing/cleanup. Have a look at what is possible in https://medium.com/concerning-pharo. You should at least make the links work. Sven > On 15 Mar 2015, at 02:57, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > philippeback wrote >> Because Sven articles are there already. > > Ah, okay :) I also posted to my blog and shared on reddit > http://redd.it/2z2ysg and HN https://news.ycombinator.com/item?id=9205061 > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/OT-Fwd-Why-GSoC-Why-me-tp4811878p4811912.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

March 15, 2015

[pharo-project/pharo-core] d8b27c: 40557

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: d8b27c365f890dcfa13b642bdbb12e87693d3cfd https://github.com/pharo-project/pharo-core/commit/d8b27c365f890dcfa13b642b… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-03-15 (Sun, 15 Mar 2015) Changed paths: R ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script556.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script557.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40556.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40557.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Slot-Tests.package/SlotErrorsTest.class/instance/tests/testDangerousClassesEnabling.st M Slot-Tests.package/SlotIntegrationTest.class/instance/tests-compact index/testReshapeCompactClass.st A Slot.package/DangerousClassNotifier.class/class/accessing/disableDuring_.st R Slot.package/DangerousClassNotifier.class/class/accessing/disableForTesting.st R Slot.package/DangerousClassNotifier.class/class/accessing/restoreAfterTesting.st M Slot.package/DangerousClassNotifier.class/class/validation/check_.st M Tests.package/SystemNavigationOnNewlyCreatedEnvironmentTest.class/instance/testing/testEnsureDefaultEnvironmentNotUsed.st M Tool-TxWorkspace.package/TxWorkspace.class/README.md M Tool-TxWorkspace.package/TxWorkspace.class/class/instance creation/open.st Log Message: ----------- 40557 15128 Class comment and #open on TxWorkspace https://pharo.fogbugz.com/f/cases/15128 14834 I cant add classVariable to context https://pharo.fogbugz.com/f/cases/14834 http://files.pharo.org/image/40/40557.zip

March 15, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40557 Home: https://github.com/pharo-project/pharo-core

March 15, 2015