- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

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

Nov. 6, 2014

[pharo-project/pharo-core] d4a5a3: 40357

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: d4a5a3a667e591820e299b43518e88207176bdfb https://github.com/pharo-project/pharo-core/commit/d4a5a3a667e591820e299b43… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-11-06 (Thu, 06 Nov 2014) Changed paths: M AST-Core.package/RBConfigurableFormatter.class/instance/private/newLinesBeforeStartingAt_.st M OpalTools.package/GTIRBrowser.class/instance/building/sourceIn_.st M SUnit-Tests.package/TestCaseTest.class/instance/events/testAnnouncement.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script357.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40357.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Versionner-Tests-Core-Model.package/MBConfigurationRootTest.class/instance/tests/test0021ConfigurationInfoCreated.st M Versionner-Tests-Core-Model.package/MBConfigurationRootTest.class/instance/tests/test0031ConfigurationInfoChanged.st M Versionner-Tests-Core-Model.package/MBConfigurationRootTest.class/instance/tests/test0032InfoListChanged.st M Versionner-Tests-Core-Model.package/MBConfigurationRootTest.class/instance/tests/test0061ConfigurationInfoChanged.st M Versionner-Tests-Core-Model.package/MBConfigurationRootTest.class/instance/tests/test0062InfoListChanged.st M Versionner-Tests-Core-Model.package/MBConfigurationRootTest.class/instance/tests/test0082ConfigurationInfoChanged.st M Versionner-Tests-Core-Model.package/MBConfigurationRootTest.class/instance/tests/test0083InfoListChanged.st M Versionner-Tests-Core-Model.package/MBConfigurationRootTest.class/instance/tests/test0101ConfigurationInfoDeleted.st M Versionner-Tests-Core-Model.package/MBConfigurationRootTest.class/instance/tests/test0111InfoListChanged.st Log Message: ----------- 40357 14401 GTIRBrowser shows only decompiled source https://pharo.fogbugz.com/f/cases/14401 14406 Replace Announcer>>#on:do:s senders in SUnit-Tests https://pharo.fogbugz.com/f/cases/14406 14408 Replace Announcer>>#on:do:s senders in Versionner-Tests-Core-Model https://pharo.fogbugz.com/f/cases/14408 14394 RBConfigurableFormatter>>newLinesBeforeStartingAt: fails if originalSource is nil https://pharo.fogbugz.com/f/cases/14394 http://files.pharo.org/image/40/40357.zip

Nov. 6, 2014

EventHandler cleanup: test / review needed

by Marcus Denker

Hi, There is still EventHandler, MouseOverEventHandler and MorphicEventHandler. After these two we can remove EventHandler and MouseOverEventHandler: https://pharo.fogbugz.com/f/cases/14403/never-use-EventHandler-but-MorphicE… https://pharo.fogbugz.com/f/cases/14404/extend-MorphicEventHandler-with-mou… Can someone check if how this was done is Ok? Marcus

Nov. 6, 2014

Re: [Pharo-dev] Browse anObject?

by Sean P. DeNigris

Ben Coman wrote > I thoughtâ¦ the least surprising would be... > > Object>>#browse > self browseClass This was exactly what I was objecting to. How is #browse sent to anObject not surprising when you mean #browseClass (which already exists)? Saying that "what else could browse mean in this context?" looks at the issue from someone who is already an expert. The point is that it may mean nothing to a newbie, and rightly so because IMHO it /is/ meaningless. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Browse-anObject-tp4788401p4788650.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Nov. 5, 2014

Re: [Pharo-dev] pane for repositories in the Configuration Browser

by Sean P. DeNigris

Luc Fabresse wrote > I agree with you and Stephan there. It must be simple for newcomers. I agree also. And, I think forbidding adding repositories is a bit Draconian. Keeping the feature "hidden" in the context menu seems like a reasonable compromise. ----- Cheers, Sean -- View this message in context: http://forum.world.st/pane-for-repositories-in-the-Configuration-Browser-tp… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Nov. 5, 2014

New Cog VMs available

by Eliot Miranda

... at http://www.mirandabanda.org/files/Cog/VM/VM.r3126/ CogVM binaries as per VMMaker.oscogvm-eem.923/r3126 Include the Unicode plugin in linux Squeak VMs. Include the vm-sound-pulse plugin in all linux VMs. Spur Newspeak: Fix possible forwarding of receiver in implicit receiver sends. -- best, Eliot

Nov. 5, 2014

Re: [Pharo-dev] Test Pharo website with Nibbler

by Yuriy Tymchuk

Pretty good :) My personal web page is 5.7 :P > On 05 Nov 2014, at 13:29, Torsten Bergmann <astares(a)gmx.de> wrote: > > > http://nibbler.silktide.com/en/reports/pharo.org >

Nov. 5, 2014

Re: [Pharo-dev] Fix 'Search Code' menu item in Nautilus

by Paul DeBruicker

Hi Marcus, I agree with your points. I'm just so habituated to using the three things I've 'fixed' in the past couple days it was really annoying to work in Pharo 3 vs. 1.4. FWIW - I don't really care if it gets into the 3.0 image as long as I can load the fix into my own Pharo 3. I contributed it back because it seems generally useful to let the computer find and format stuff, which I think has been missing since Pharo 2. I don't expect to fix anything else, if that helps.... ;) Paul Marcus Denker-4 wrote > In general we need to discuss about Pharo3 non-bug improvementsâ¦ > > => we need to take care not to overdue it. If we change Pharo3 a lot, this > will add a lot of > double work and might introduce new bugs. > > => My personal rule is: even for bug fixes, if they are to be back ported > to Pharo3 not just > because âit would be niceâ. My personal threshold for that is simple: I > will not do it, but if the > fix is important enough *for someone else* to back port, than this is of > a kind that should be > considered. > > => We need to be cautious with new featuresâ¦ but then there might be cases > where it makes sense. > >> On 04 Nov 2014, at 17:45, Paul DeBruicker < > pdebruic@ > > wrote: >> >> Thanks for the tip Max. I've uploaded the packages to the Pharo30Inbox >> repo. >> >> >> >> >> >> Max Leske wrote >>> Hi Paul, >>> >>> You also need to include the two dependencies of the slice, those need >>> to >>> be uploaded to the inbox too. >>> >>> Cheers, >>> Max >>> >>>> On 04.11.2014, at 06:19, Paul DeBruicker < >> >>> pdebruic@ >> >>> > wrote: >>>> >>>> Hi - >>>> >>>> The attached slice makes the 'Search Code' menu item in Nautilus work >>>> like it did prior to the adoption of Nautilus in Pharo 3. I do not >>>> have >>>> commit rights to Pharo30Inbox but would submit it there if I did. I >>>> have not sent the contributor agreement but will tomorrow. >>>> >>>> >>>> The issue in fogbugz is: >>>> https://pharo.fogbugz.com/f/cases/14382/Fix-Search-Code-refactoring-menu-it… >>>> >>>> >>>> Paul >>>> >>>> >>> > <SLICE-Issue-14382-Fix-Search-Code-refactoring-menu-item-in-Nautilus-PaulDeBruicker.1.mcz> >> >> >> >> >> >> -- >> View this message in context: >> http://forum.world.st/Fix-Search-Code-menu-item-in-Nautilus-tp4788273p47883… >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> -- View this message in context: http://forum.world.st/Fix-Search-Code-menu-item-in-Nautilus-tp4788273p47885… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Nov. 5, 2014

Re: [Pharo-dev] Fix 'Search Code' menu item in Nautilus

by Max Leske

> On 05.11.2014, at 09:39, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > In general we need to discuss about Pharo3 non-bug improvementsâ¦ > > => we need to take care not to overdue it. If we change Pharo3 a lot, this will add a lot of > double work and might introduce new bugs. > > => My personal rule is: even for bug fixes, if they are to be back ported to Pharo3 not just > because âit would be niceâ. My personal threshold for that is simple: I will not do it, but if the > fix is important enough *for someone else* to back port, than this is of a kind that should be > considered. > > => We need to be cautious with new featuresâ¦ but then there might be cases where it makes sense. Agreed. > >> On 04 Nov 2014, at 17:45, Paul DeBruicker <pdebruic(a)gmail.com> wrote: >> >> Thanks for the tip Max. I've uploaded the packages to the Pharo30Inbox repo. >> >> >> >> >> >> Max Leske wrote >>> Hi Paul, >>> >>> You also need to include the two dependencies of the slice, those need to >>> be uploaded to the inbox too. >>> >>> Cheers, >>> Max >>> >>>> On 04.11.2014, at 06:19, Paul DeBruicker < >> >>> pdebruic@ >> >>> > wrote: >>>> >>>> Hi - >>>> >>>> The attached slice makes the 'Search Code' menu item in Nautilus work >>>> like it did prior to the adoption of Nautilus in Pharo 3. I do not have >>>> commit rights to Pharo30Inbox but would submit it there if I did. I >>>> have not sent the contributor agreement but will tomorrow. >>>> >>>> >>>> The issue in fogbugz is: >>>> https://pharo.fogbugz.com/f/cases/14382/Fix-Search-Code-refactoring-menu-it… >>>> >>>> >>>> Paul >>>> >>>> >>> <SLICE-Issue-14382-Fix-Search-Code-refactoring-menu-item-in-Nautilus-PaulDeBruicker.1.mcz> >> >> >> >> >> >> -- >> View this message in context: http://forum.world.st/Fix-Search-Code-menu-item-in-Nautilus-tp4788273p47883… >> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >> > >

Nov. 5, 2014

[pharo-project/pharo-core]

by GitHub

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

Nov. 5, 2014