- Pharo-dev - lists.pharo.org

Morphic Core dependencies
by stepharo July 24, 2014

July 24, 2014

Hi pavel this is related to your interrogations about system window Gofer it smalltalkhubUser: 'BaptisteQuide' project: 'PackageDependenciesAnalysis'; configuration; loadStable

3 4

ConfigurationOfMorphicCore
by Pavel Krivanek July 24, 2014

July 24, 2014

Hi, in latest update we integrated several patches needed for proper working of ConfiguratonOfMorphicCore. This simple configuration loads Morphic-Core package into the minimal image and initializes it so the result is a small standalone Morphic subset. But some issues that I would like to discuss with the community left: SystemWindows support ============================ SystemWindow is quite complex morph that requires many of other morph classes including text morphs, theming support etc. But in several situations the system windows play special role and the Morphic core classes need to be aware of them. So we have several options: - (current) do not have SystemWindow & co. in the image but let basic support of them. That will produce some unimplemented calls - create very simple SystemWindow superclass that will be part of the Morphic-Core but will not have look and possibilities of real SystemWindow - include SystemWindow and supporting classes Tools ============================ The current image generated by this configuraton will crash as soon as you try to press some keyboard button. The reason is in the method Morph>># handleKeystroke. This method contains this code to support Keymapping Smalltalk tools shortcuts handleKeystroke: anEvent inMorph: self. The #tools message is part of Tool-Base package and need to be there because it uses lazy evaluation that creates a ToolRegistry instance. Because Tool-Base is not loaded in the minimal nor Morphic-Core image, it raises DNU Solutions: - introduce some safer form like Smalltalk withToolsDo: [:tools | ...]. In this case it will not be able to look if the class variable "Tools" is nil (because of lazy evaluation) but it will need to do some ugly check of presence of ToolRegistry class or something similar. In this case we will produce more unimplemented calls (on several places in the image because withToolsDo: may be handy in other cases too) - something different :) Cheers, -- Pavel

4 7

[Pharo4] Weekend Project 1: Cleanup Low-Level animation code
by Marcus Denker July 24, 2014

July 24, 2014

Hi, Now with holidays comingâ¦ maybe someone wants to do a small Pharo related Project with impact on the future? Here is suggestion 1. Context: cleanup graphics. (so e.g. one could replace the canvas later). Details ====== Morphic has some very arcane code for animating moving morphs around that bypasses layers. DisplayObject has these methods: follow:while: follow:while:bitsBehind:startingLoc: slideFrom:to:nSteps:delay: slideWithFirstFrom:to:nSteps:delay: displayOnPort:at:rule: They are used by morphic for some not really important animation that for sure can be directly done by moving the morphs as morphs around. Bypassing and directly using low level (not even Canvas level) functionality is for sure not needed. On the Morph level the users are: slideBackToFormerSituation: vanishAfterSlidingTo:event: animationForMoveSuccess: What to do? -> rewrite the morphic level code to just move the morphs around. -> delete all the code from DisplayObject -> review âGrafPortâ usage, as this might have been the last client. Marcus

2 2

On my way to vacation
by Stephan Eggermont July 24, 2014

July 24, 2014

I drive past Lille, and would be interested in spending an afternoon the 29. doing some pair programming (and the evening preferably with some beer and a good diner). Would need to find a place to sleep for us (wife and 2 boys of 5 & 7) though. Stephan

2 1

Re: [Pharo-dev] Komitter in 30852?
by Stephan Eggermont July 24, 2014

July 24, 2014

Marcus wrote >https://pharo.fogbugz.com/f/cases/13539/receiver-of-NodeModel-is-Nil > >There is even a fix, but it needs to be reviewed and back ported. Thanks, I somehow missed that. I was a bit annoyed that I had just yesterday answered a question about closing lots of inspectors and then ran into the situation myself... Thierry wrote: >can you describe how you get it? I immediately had errors on 4.0 >when writing this fix (https://pharo.fogbugz.com/f/cases/13539/receiver-of-NodeModel-is-Nil) but it wasn't reproduced on 3.0. Open a fresh 30852 with 355 (Mac Mavericks 10.9.4). Open a Nautilus browser, create class Bla in category Bla. Open Komitter, 6 MNUs Close MNUs and Komitter add a class Blah in category Bla Open Komitter, 10 MNUs I tried it originally on an image that took over a minute to produce the MNUs... Stephan

2 1

Refactor Nautilus
by Nicolai Hess July 24, 2014

July 24, 2014

If no one raises objections, I would like to start on refactor / cleanup nautilus code. This includes: renaming / recategorizing solve code critics shown in Critics Browser split classes (AbstractNautilusUI has 427 methods 24 instvars ) stronger separation between the browser model, browser state and browser UI. review event handling and UI updating (sometimes there is a difference between what the UI shows as selected and the selection the model(s) holds maybe: create one package pane widget for package and groups (therefore move all that package vs groups handling from nautilus ui to that widget) merge Nautilus and PackageTreeNautilus (I don't consider all of Nautilus bad code, it has well designed parts, it just has grown meanwhile...) How to update the code? Working with slices makes it easier to find changes that introduces new bugs. Otherwise it takes time to do it in such small steps and I don't know if those changes are reviewed at all. So, I would try to group the changes. 1. code critics 2. renameing/ simple refactoring 3. .... nicolai

5 5

Komitter in 30852?
by Stephan Eggermont July 24, 2014

July 24, 2014

Anyone tried Komitter recently in Pharo 3? I get about 4 to 6 debugger windows per change. Don't try on an image with lots of open changes... Stephan

4 3

[pharo-project/pharo-core]
by GitHub July 24, 2014

July 24, 2014

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

1 0

[pharo-project/pharo-core] 66a818: 40122
by GitHub July 24, 2014

July 24, 2014

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 66a8182c2a1b6f8de3417956bcf73e50e86fe2e6 https://github.com/pharo-project/pharo-core/commit/66a8182c2a1b6f8de3417956… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-07-24 (Thu, 24 Jul 2014) Changed paths: A Morphic-Base.package/TransformationMorph.class/instance/accessing/embeddedWindowOrNil.st R Morphic-Base.package/extension/PasteUpMorph/instance/windowsSatisfying_.st M Morphic-Core.package/HandMorph.class/instance/private events/generateMouseEvent_.st A Morphic-Core.package/Morph.class/instance/accessing/embeddedWindowOrNil.st A Morphic-Core.package/PasteUpMorph.class/instance/accessing/currentWindow.st A Morphic-Core.package/PasteUpMorph.class/instance/accessing/windowsSatisfying_.st A Morphic-Widgets-Windows.package/SystemWindow.class/instance/accessing/embeddedWindowOrNil.st M OpalCompiler-Core.package/OpalCompiler.class/instance/public access/compile.st R Polymorph-Widgets.package/extension/PasteUpMorph/instance/currentWindow.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script122.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40122.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40122 13675 safer windows enumeration https://pharo.fogbugz.com/f/cases/13675 13676 safer usage of KMBuffer in HandMorph >> #generateMouseEvent: https://pharo.fogbugz.com/f/cases/13676 13669 CompilerNotifying test failing on main build https://pharo.fogbugz.com/f/cases/13669 13674 safer access to top current window https://pharo.fogbugz.com/f/cases/13674 13667 Delete empty package System-Tools https://pharo.fogbugz.com/f/cases/13667 http://files.pharo.org/image/40/40122.zip

1 0

Package Dependencies Analysis : new features
by Baptiste Quide July 24, 2014

July 24, 2014

Hello Pharos Users, Since the first release of Package Dependencies Analysis, here is a summary of improvements : - tool is available in World Menu (Tools > Package Dependencies Browser) : choose your packages and browse dependencies. - add/remove packages into the analysis. - you can refresh the current analysis manually (for instance if you change a piece of code to remove/add dependency) - filter the packages displaying by name - button "find cycles" allows to find all cycles in the system where the selected packages in the tree are (it could take a while the first time you click) - contextual menu (right click) to browse scoped dependencies or find cycles among the selected packages in the tree Then, in the window displaying cycles among packages : - only dependencies among packages in the cycle are displaying (no outgoing dependencies) - packages appear by order (if you see aCycle : A, B, C, the cycle is A -> B -> C -> A) See more details : http://www.baptistequide.fr/packagedependencies.php Regards, Baptiste

2 4