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

Re: [Pharo-dev] Spec MenuModel not working

by Peter UhnÃ¡k

I created an issue here https://pharo.fogbugz.com/f/cases/14829/Spec-MenuModel-submenu-not-working I also found the breaking commit https://github.com/pharo-project/pharo-core/commit/1c3c757366ba2cad8f367ee9… but Stef probably knows best what was going on there. Peter On Sat, Dec 20, 2014 at 8:03 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > 2014-12-20 9:54 GMT+01:00 stepharo <stepharo(a)free.fr>: > >> Hi nicolai >> >> could you publish your code somewhere? >> > > see attachement dock_menu_spec.cs > > > >

Jan. 30, 2015

[pharo-project/pharo-core]

by GitHub

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

Jan. 30, 2015

[pharo-project/pharo-core] 13864c: 40469

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 13864c112fbf1b6d2a2d6ba7a6a0a9d3596ba35d https://github.com/pharo-project/pharo-core/commit/13864c112fbf1b6d2a2d6ba7… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-01-30 (Fri, 30 Jan 2015) Changed paths: M OpalCompiler-Core.package/AbstractCompiler.class/class/settings/compilerSettingsOn_.st M OpalCompiler-Core.package/CCompilationContext.class/class/initialize/initialize.st M OpalCompiler-Core.package/CCompilationContext.class/definition.st A OpalCompiler-Core.package/CCompilationContext.class/instance/accessing/encoderClass.st A OpalCompiler-Core.package/CCompilationContext.class/instance/accessing/encoderClass_.st M OpalCompiler-Core.package/CompilationContext.class/class/initialize/initialize.st M OpalCompiler-Core.package/CompilationContext.class/definition.st A OpalCompiler-Core.package/CompilationContext.class/instance/accessing/encoderClass.st A OpalCompiler-Core.package/CompilationContext.class/instance/accessing/encoderClass_.st M OpalCompiler-Core.package/IRBytecodeDecompiler.class/instance/quick methods/quickMethod.st A OpalCompiler-Core.package/IRBytecodeGenerator.class/class/instance creation/newWithEncoderClass_.st M OpalCompiler-Core.package/IRBytecodeGenerator.class/definition.st M OpalCompiler-Core.package/IRBytecodeGenerator.class/instance/accessing/encoderClass.st A OpalCompiler-Core.package/IRBytecodeGenerator.class/instance/accessing/encoderClass_.st M OpalCompiler-Core.package/IRTranslatorV2.class/instance/initialize/initialize.st M OpalCompiler-Tests.package/OCBytecodeGeneratorTest.class/instance/helper/newBytecodeGen.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script469.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40469.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Tool-Base.package/PharoCommonTools.class/class/settings/settingsOn_.st Log Message: ----------- 40469 14811 Fix settings for OpalCompiler with new bytecode generator https://pharo.fogbugz.com/f/cases/14811 10529 ToolRegistry need to support multiple registrations per tool https://pharo.fogbugz.com/f/cases/10529 http://files.pharo.org/image/40/40469.zip

Jan. 30, 2015

Plague Doctor

by Roberto Minelli

To follow Stefâs advice of advertising our projects, here is the Plague Doctor! During development your Pharo IDE will quickly become overcrowded with unused windows. The Plague Doctor is a tool, inspired by Autumn Leaves, that helps you to mitigate this issue by closing the windows that you are less likely to use in the future. If you want to try our prototype, please install it with the following script or ask me for a quick demo (I am Lille for the PharoDays!). Gofer new smalltalkhubUser: 'RobertoMinelli' project: 'PlagueDoctor'; package: 'ConfigurationOfPlagueDoctor'; load. (Smalltalk at: #ConfigurationOfPlagueDoctor) loadDevelopment. http://smalltalkhub.com/#!/~RobertoMinelli/PlagueDoctor P.s. If you report a problem or a feature request, please file in an entry https://github.com/RobertoMinelli/PlagueDoctor/issues

Jan. 30, 2015

Re: [Pharo-dev] Create window group for Playground

by kilon alios

you dont watch my video tutorials ? ;D here is one for window groups https://www.youtube.com/watch?v=GGJZeajjWGU&index=12&list=PLqbtQ7OkSta0ULYA… I agree this one of the features that I really miss and I think I was the first one to report it in this least when Playground was announced it for Pharo 4. Yes Peter I am using your workaround to compensate for this. Do you want to hear the irony , I only use Workspace to create a window group to act as a container for Playgrounds :D Actually finding a way to create tabs for the guis in Pharo had been one of my first priorities to develop but when I reported my idea in this mailing list I was informed that the feature already existed. I was so happy I made a video tutorial about it because its a pity so useful features to be so hidden from the user. Probably an Icon would have made it way more obvious to most users. On Fri, Jan 30, 2015 at 12:11 PM, stepharo <stepharo(a)free.fr> wrote: > Another features that nobody knows (even us). > > Stef > > Le 29/1/15 18:51, Torsten Bergmann a Ã©crit : > > Previous (and still included) Workspace, Transcript and Nautilus >> provide Window grouping by selecting "Create window group" from the >> window menu and then dragging two windows onto each other. >> They are grouped together in one single window then and each one >> gets a tab. >> >> Looks like Playground does not support this feature yet - so currently >> I end up with many many windows which for me is a step backwards >> compared to working with workspaces in Pharo 3.0 >> >> What is necessary to provide this for the Playground so we have a >> common behavior for all the tools and a cleaner desktop? >> >> Thanks >> T. >> >> >> > >

Jan. 30, 2015

Re: [Pharo-dev] Create window group for Playground

by stepharo

Another features that nobody knows (even us). Stef Le 29/1/15 18:51, Torsten Bergmann a Ã©crit : > Previous (and still included) Workspace, Transcript and Nautilus > provide Window grouping by selecting "Create window group" from the > window menu and then dragging two windows onto each other. > They are grouped together in one single window then and each one > gets a tab. > > Looks like Playground does not support this feature yet - so currently > I end up with many many windows which for me is a step backwards > compared to working with workspaces in Pharo 3.0 > > What is necessary to provide this for the Playground so we have a > common behavior for all the tools and a cleaner desktop? > > Thanks > T. > >

Jan. 30, 2015

Re: [Pharo-dev] pharo-os : a fantasy!

by stepharo

Keep pushing this idea. Stef Le 26/1/15 14:17, Mayuresh Kathe a Ã©crit : > hi, > > i have been investigating a full blown gnu/linux based distribution > focused entirely on pharo as the the user interface layer. > > looks like, if the entire base 'os' functionality is exposed via this > little environment/toolkit called "sysctl", building a pure object > oriented layer of shell scripts to support all calls exposed via sysctl > and managed via pharo looks feasible. > > i might be wrong, and look forward to experienced folks pointing out > flaws in my thought process. > > if this organization/architecture feels sound, i would like to get a > go-ahead to hire the services of a gnu/linux expert to start building > the base layer atop which pharo can be run as the only application. > > this effort would be funded out of my own pockets (which aren't very > deep). :) > > ~mayuresh > > >

Jan. 30, 2015

[pharo-project/pharo-core] 7b0188: 40468

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 7b01889418cc4bededd2c57794088a708178666c https://github.com/pharo-project/pharo-core/commit/7b01889418cc4bededd2c577… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-01-30 (Fri, 30 Jan 2015) Changed paths: R AST-Core.package/RBArrayNode.class/instance/accessing/start_.st R AST-Core.package/RBArrayNode.class/instance/accessing/stop_.st R AST-Core.package/RBAssignmentNode.class/instance/accessing/start_.st R AST-Core.package/RBAssignmentNode.class/instance/accessing/stop_.st R AST-Core.package/RBBlockNode.class/instance/accessing/start_.st R AST-Core.package/RBBlockNode.class/instance/accessing/stop_.st R AST-Core.package/RBCascadeNode.class/instance/accessing/start_.st R AST-Core.package/RBCascadeNode.class/instance/accessing/stop_.st R AST-Core.package/RBIdentifierToken.class/instance/accessing/stop.st R AST-Core.package/RBIdentifierToken.class/instance/accessing/stop_.st R AST-Core.package/RBKeywordToken.class/instance/accessing/stop.st R AST-Core.package/RBKeywordToken.class/instance/accessing/stop_.st R AST-Core.package/RBLiteralArrayNode.class/instance/accessing/start_.st R AST-Core.package/RBLiteralArrayNode.class/instance/accessing/stop_.st R AST-Core.package/RBLiteralValueNode.class/instance/accessing/start_.st R AST-Core.package/RBLiteralValueNode.class/instance/accessing/stop_.st R AST-Core.package/RBMessageNode.class/instance/accessing/start_.st R AST-Core.package/RBMessageNode.class/instance/accessing/stop_.st R AST-Core.package/RBParseErrorNode.class/instance/accessing/start_.st R AST-Core.package/RBParseErrorNode.class/instance/accessing/stop_.st R AST-Core.package/RBPragmaNode.class/instance/accessing/start_.st R AST-Core.package/RBPragmaNode.class/instance/accessing/stop_.st R AST-Core.package/RBProgramNode.class/instance/accessing/start_.st R AST-Core.package/RBProgramNode.class/instance/accessing/stop_.st R AST-Core.package/RBProgramNode.class/instance/replacing/calculateInnerCommentsSize_.st R AST-Core.package/RBProgramNode.class/instance/replacing/calculateSourceInterval_.st R AST-Core.package/RBProgramNode.class/instance/replacing/checkMessageNodesIn_withDifference_with_.st M AST-Core.package/RBProgramNode.class/instance/replacing/replaceWith_.st R AST-Core.package/RBReturnNode.class/instance/accessing/start_.st R AST-Core.package/RBSequenceNode.class/instance/accessing/start_.st R AST-Core.package/RBSequenceNode.class/instance/accessing/stop_.st R AST-Core.package/RBToken.class/instance/accessing/sourcePointer_.st R AST-Core.package/RBVariableNode.class/instance/accessing/start_.st R AST-Core.package/RBVariableNode.class/instance/accessing/stop_.st M AST-Tests-Core.package/RBProgramNodeTest.class/instance/testing-replacing/testReplaceAssignment.st M AST-Tests-Core.package/RBProgramNodeTest.class/instance/testing-replacing/testReplaceBlock.st M AST-Tests-Core.package/RBProgramNodeTest.class/instance/testing-replacing/testReplaceLiteral.st M AST-Tests-Core.package/RBProgramNodeTest.class/instance/testing-replacing/testReplaceLiteralArray1.st M AST-Tests-Core.package/RBProgramNodeTest.class/instance/testing-replacing/testReplaceLiteralArray2.st M AST-Tests-Core.package/RBProgramNodeTest.class/instance/testing-replacing/testReplaceMessage.st M AST-Tests-Core.package/RBProgramNodeTest.class/instance/testing-replacing/testReplaceMessageArgument.st M AST-Tests-Core.package/RBProgramNodeTest.class/instance/testing-replacing/testReplaceMessageReceiver.st M AST-Tests-Core.package/RBProgramNodeTest.class/instance/testing-replacing/testReplaceVariable.st M NECompletion.package/NECMenuMorph.class/instance/drawing/drawLine_on_rectangle_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script468.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40468.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40468 14815 NECMenuMorph should clip the canvas during menu items drawing https://pharo.fogbugz.com/f/cases/14815 14730 Reverting 14254 https://pharo.fogbugz.com/f/cases/14730 http://files.pharo.org/image/40/40468.zip

Jan. 30, 2015

[pharo-project/pharo-core]

by GitHub

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

Jan. 30, 2015

Re: [Pharo-dev] [Vm-dev] New Cog VMs available

by Chris Muller

Congratulations Eliot! This is a major milestone for Spur's stability and robustness. With this release, I am comfortable to move the rest of my production to Spur. This is so great! On Thu, Jan 29, 2015 at 7:26 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > at http://www.mirandabanda.org/files/Cog/VM/VM.r3236/ > > CogVM binaries as per VMMaker.oscog-eem.1029/r3236 > > Fix stupid, stupid bug in copying vm profile samples between buffers when the > circular buffer index has wrapped. > > Fix monumental blunder in jitted store-check code. The saved registers mask > needs to be the *or* of the value reg and the caller-saved registers, not the > *and*!! > > Make the pin primitives Spur-only. > > Never inline mapStackPages, for debugging. > > Spur: > Reduce the max num literals in the alternate header format to 15, and steal > the bit for the Sista optimized method flag. > > Make postBecomeAction's stack sweep only occur in Spur (fix regression). > Refactor so that the scan is not inlined. Don't assume newMethod is > non-immediate in post-become actions. > > Fix stack adjust slip in primitiveSmallFloatTimesTwoPower > > Make ensureBehaviorHash: fail for uninitialized > behaviours and hence fix the Behavior basicNew basicNew hang. > > Optionalize some api methods the Spur Cogit doesn't use. > > Rename and correct ensureSemaphoreForwardedThroughContext: to > ensureSemaphoreUnforwardedThroughContext:, its intended function. > > Make shouldRemapObj: filter-out objects already in newSpace > since mapStackPages, via mapInterpreterOops, can visit objects > twice in a scavenge, GC, compact sequence. > > Make sure the caller (& saved) context(s) in base frames stack page are > followed post-become in followForwardingPointersInStackZone:. > > Fix bad bug introduced in become changes in VMMaker.oscog-eem.841 through 844. > The class table contains puns, e.g. using Array and WeakArray. These class > index puns must not mislead the allInstances primitive into concluding that > the class in question is at multiple indices and wrongly purge it. > > Fix slip in primitivePin. Also be lenient w.r.t. unpinning married contexts. > Move the check down into StackInterpreter's version. This allows e.g. > self allObjectsDo: [:o| o unpin] > > Bow to the inevitable and add a manual override for primitive accessor depth. > Use it in at: & at:put:. If manual override is not used then the automatically > computed depth is too deep because of context access. > > Newspeak: > Integrate Ryan's newer absent receiver sends, which first apeared in > VMMaker.oscog-eem.919, abandoned because of Glue issues now resolved. Includes > nice refactoring of absent send argument marshalling into its own routine. > > LargeIntegersPlugin: > Remove/fix assumption of 32-bit digit length in normalization routines. > > -- > best, > Eliot >

Jan. 30, 2015