- Pharo-dev - lists.pharo.org

smalltalkhub.com down?
by Nicolai Hess Dec. 1, 2013

Dec. 1, 2013

smalltalkhub.com is not accessible from mcbrowser. (Is it right, that the smalltalkhub.com shows the same

1 0

Athens-Cairo is part of Pharo?
by Bernardo Ezequiel Contreras Nov. 30, 2013

Nov. 30, 2013

Hi all, There's a deprecated method in Athens-Cairo. method: AthensCairoSurface>>#createLinearGradient:origin:corner: category: #paints package: RGPackage(Athens-Cairo) Should i move it to Deprecated package? https://pharo.fogbugz.com/f/cases/11668/Move-all-deprecated-method-to-Depre… Thanks. -- Bernardo E.C. Sent from a cheap desktop computer in South America.

3 4

Nautilus unload...
by StÃ©phane Ducasse Nov. 30, 2013

Nov. 30, 2013

Hi esteban I'm looking for a change due to the TreePackage introduction. Before I could simply do something like the following to unload Nautilus Smalltalk tools remove: #browser. Smalltalk tools register: Browser as: #browser. (MCWorkingCopy forPackage: (MCPackage named: 'NautilusRefactoring')) unload. "OK" #Nautilus asClass cleanUp. KMRepository reset. KMPragmaKeymapBuilder release. #NautilusUI asClass allSubInstances do: [ :inst | SystemAnnouncer uniqueInstance unsubscribe: inst]. Smalltalk garbageCollect. (MCWorkingCopy forPackage: (MCPackage named: 'NautilusCommon')) unload. (MCWorkingCopy forPackage: (MCPackage named: 'Nautilus')) unload. And now if does not work anymore. I get some TreePackage around. Apparently I get a weakMessageSend on classRemoved: and this message refers to an obsoletePackageTreeNautilus class. buildGroupManagerFor: anInstance | holder | holder := GroupHolder new. (holder addADynamicClassGroupSilentlyNamed: 'Most Viewed Classes' block: [ anInstance recentClassesElements ]) removable: false. (holder addADynamicClassGroupSilentlyNamed: 'Last Modified Classes' block: [ self lastModifiedClasses ]) removable: false. (holder addADynamicGroupSilentlyNamed: 'Work' block: [ {} ]) removable: true; isFillable: true. ^ holder Do you have any idea? A registration mechanism? from which I forgot to unregister. Stef

5 17

groupManager
by StÃ©phane Ducasse Nov. 30, 2013

Nov. 30, 2013

Hi I'm trying to understand the goal of groupManager. I do not understand that GroupManager current groups does not return the current groups. Even when I add a group. Stef

2 3

Commit rights to pharo30inbox
by Nicolai Hess Nov. 30, 2013

Nov. 30, 2013

hi I want to contribute to pharo and would like to have commit rights to pharo30inbox. username : NicolaiHess regards Nicolai

2 1

[pharo-project/pharo-core]
by GitHub Nov. 30, 2013

Nov. 30, 2013

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

1 0

[pharo-project/pharo-core] 45e604: 30613
by GitHub Nov. 30, 2013

Nov. 30, 2013

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 45e60499b534bbf8a9fbe5d5ac0db89a2528f75e https://github.com/pharo-project/pharo-core/commit/45e60499b534bbf8a9fbe5d5… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-11-30 (Sat, 30 Nov 2013) Changed paths: A ClassOrganizer-Core.package/AllProtocol.class/instance/accessing/name_.st M ClassOrganizer-Core.package/AllProtocol.class/instance/testing/canBeRemoved.st A ClassOrganizer-Core.package/AllProtocol.class/instance/testing/canBeRenamed.st A ClassOrganizer-Core.package/ClassOrganization.class/instance/accessing/protocolNamed_.st M ClassOrganizer-Core.package/ClassOrganization.class/instance/backward compatibility/renameCategory_toBe_.st M ClassOrganizer-Core.package/ClassOrganization.class/instance/testing/isEmptyCategoryNamed_.st M ClassOrganizer-Core.package/Protocol.class/instance/accessing/name_.st A ClassOrganizer-Core.package/Protocol.class/instance/testing/canBeRenamed.st R ClassOrganizer-Core.package/ProtocolOrganizer.class/instance/accessing/getProtocolNamed_.st A ClassOrganizer-Core.package/ProtocolOrganizer.class/instance/accessing/protocolNamed_.st A ClassOrganizer-Core.package/ProtocolOrganizer.class/instance/accessing/protocolNamed_ifAbsent_.st M ClassOrganizer-Core.package/ProtocolOrganizer.class/instance/accessing/renameProtocol_into_.st M ClassOrganizer-Core.package/ProtocolOrganizer.class/instance/backward compatibility/methodsInProtocolNamed_.st M ClassOrganizer-Core.package/ProtocolOrganizer.class/instance/private/moveMethodsFrom_to_.st M ClassOrganizer-Core.package/ProtocolOrganizer.class/instance/protocol - removing/removeProtocolNamed_.st R Compiler.package/Compiler.class/instance/public - decompiler/decompile_in_.st R Compiler.package/Compiler.class/instance/public - decompiler/decompile_in_method_.st A Deprecated30.package/extension/Compiler/instance/decompile_in_.st A Deprecated30.package/extension/Compiler/instance/decompile_in_method_.st A Keymapping-KeyCombinations.package/extension/MacOSPlatform/instance/defaultModifier.st A Keymapping-KeyCombinations.package/extension/OSPlatform/instance/defaultModifier.st A Keymapping-KeyCombinations.package/extension/UnixPlatform/instance/defaultModifier.st A Keymapping-KeyCombinations.package/extension/Win32Platform/instance/defaultModifier.st R Morphic-Base.package/MenuMorph.class/class/utilities/inform_.st A Nautilus.package/PackageTreeNautilusUI.class/instance/accessing/selectedProtocol.st A Nautilus.package/PackageTreeNautilusUI.class/instance/menus behavior/renameCategory.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script268.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30613.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Spec-Core.package/MenuGroupModel.class/instance/protocol-building/fromSpec_.st M Spec-Core.package/MenuItemModel.class/instance/initialize/initialize.st A Spec-Core.package/MenuItemModel.class/instance/protocol-building/fromSpec_.st M Spec-Core.package/MenuItemModel.class/instance/protocol/icon_.st A Spec-Core.package/MenuModel.class/instance/protocol-building/addAllFromPragma_target_.st A Spec-Core.package/MenuModel.class/instance/protocol-building/fromSpec_.st A Spec-Core.package/extension/PluggableMenuItemSpec/instance/addToMenuGroupModel_.st A Spec-Core.package/extension/PluggableMenuItemSpec/instance/addToMenuItemModel_.st A Spec-Core.package/extension/PluggableMenuSpec/instance/addToMenuModel_.st A Spec-MorphicAdapters.package/MorphicMenuItemAdapter.class/instance/as yet unclassified /shortcutFromString.st A Spec-MorphicAdapters.package/MorphicMenuItemAdapter.class/instance/private/defaultModifierShortcut.st M Spec-MorphicAdapters.package/MorphicMenuItemAdapter.class/instance/widget API/shortcutText.st M Spec-Tools.package/ChangeSorterApplication.class/instance/menu/changeSetMenu1_shifted_.st M System-Support.package/SystemNavigation.class/instance/packages/removeAllButPackages_.st Log Message: ----------- 30613 12291 Improvement in menus https://pharo.fogbugz.com/f/cases/12291 11994 Remove MenuMorph inform: https://pharo.fogbugz.com/f/cases/11994 12303 Rename category in TabModel to Deprecated30 https://pharo.fogbugz.com/f/cases/12303 12302 Move Compiler deprecated methods to Deprecated30 package again https://pharo.fogbugz.com/f/cases/12302 11439 Renaming --all-- protocol should not be possible https://pharo.fogbugz.com/f/cases/11439 http://files.pharo.org/image/30/30613.zip

1 0

Added shop page
by phil＠highoctane.be Nov. 30, 2013

Nov. 30, 2013

While I was at it, I added a shop page with the goodies. That way it will not stay in the mailing list depths forever. http://www.pharo-project.org/community/shop If that's a problem, I can remove the page. Phil

4 6

Coordinates problem with Athens and Morphic while coding Hyperion
by kilon alios Nov. 30, 2013

Nov. 30, 2013

So I have found some strange problems with my vector editor , Hyperion. Hyperion is a Morph openInWindow. Code can be found in the class side of Hyperion>>open. The coordinate system when detecting events (mouseOver, mouseUp and mouseDown events of the Hyperion instance) looks like it takes to account also beyond the morph as coordinates as a result events happening at the top right edge of the morph where Hyperion is rendered is 6@30( which is the size of the window's title bar plus its borders). Thats ok, I have taken these offsets to account when computing the position of the mouse. I guess it uses the global coordinated and not the local coordinates of the morph. I am adding a button to control the edit mode of a line, when in edit mode handles for line's control points are shown and those handles can be dragged around to control the shape of the line , when off edit mode, the line will be able to be drag around (not implemented yet). My problem is that when I add that button as morph to the existing morph of Hyperion in 0@0 , it actually appears in 0@30 in local coordinated of the Hyperion moprh which in global coordinates it 6@60 ( 0@0 + 6@30 + 0@30 = 6@60). Why is that ? I have no clue why I am getting an offset of 0@30 in local coordinates of the Hyperion morph. here is the picture showing a) how it looks like b) the code that set the position c) transcript showing mouse coordinates when clicked in the top left corner of Hyperion morph Hyperion coordinates problem.JPG<https://docs.google.com/file/d/0B1L74rM985aqVTZleHlmb3RmbWs/edit?usp=drive_…> if anyone wants to try the code himself the repo is here http://www.smalltalkhub.com/#!/~kilon/Hyperion To sum up, to place that button on top left, I will have to position it 0@(-30) which for me makes no sense at all. Please note that everything is rendered with Athens. Maybe I have messed up the code myself somewhere but I have looked it again and again I cant find a problem with my code.

6 25

[Pharo-project] Suggestion about Phexample and StateSpecs(Mocketry) integration
by Denis Kudriashov Nov. 30, 2013

Nov. 30, 2013

Hello I think you read about Mocketry and know that It provides same "should syntax" DSL like project Phexample. There is problem between two projects. We both implement #should message in Object class. So when somebody want Phexample Mocketry become broken and vice versa. In the past I actually only read about Phexample tests reusage idea with #given message. And I didn't know that It provides "should syntax" too. Now I read about it and look at code (thank's Yuriy Tymchuk) and I have some suggestions about it. First few words about state of Mocketry project. Mocketry is not based on SSpec (I was google such wrong opinion). It is just implement SSpec idea about executable specifications and "should syntax". And specifications part with DSL was extracted from Mocketry to StateSpecs project. So Mocketry is only about mocks and behaviour specs. Idea of executable specifications is not about replacement "assert syntax" with "should syntax". It is about building reusable first class objects which can validate domain objects. For example there are EqualitySpec, ElementsCountSpec, ClassSpec. All this specs present "valid state" of objects. They know how to validate objects. State specs can be used in tests, UI and any other domain where you want put descriptions about what it mean "valid object". I start use StateSpecs in Presenty to build object editor. With specs I put requirements on model aspects. I am sure Magritte provides something similar in description objects. So StateSpecs solve very general problem: how to describe validation rules for objects and how to make such descriptions reusable. To make it convenient and readable StateSpecs provides two kind of DSL: - should syntax to immediately check object state - first class words to create spec instances with more readable way: Instance of: SomeClass, Equal to: #some, Containing item: arrayItem and others First option can be used in tests instead #assert: expressions. Last can be used in mock message arguments. StateSpecs provide very simple way to extend it DSL based on pragmas: Instance of: aClass <syntax: #(be an instance of:)> ^ClassSpec for: aClass Equal to: anObject <syntax: #(equal:)> <syntax: #(be equal:)> ^self return: (EqualitySpec pattern: anObject) Containing item: anObject <syntax: #(include:)> ^ElementContainmentSpec requiredElement: anObject And with this you can write: object should be an instance of: SomeClass object should equal: #some object should be equal: #some array should include: item. So with such approach both kind of DSL extended at one place. Ok. Now my main suggestion. Let's Phexample use StateSpecs for "should syntax". I can provide all "should protocol" of Phexample in StateSpecs. So it will be transparent for current users. It just few extra pragmas and classes in StateSpecs-DSL package. Maybe it is already done by Yuriy Tymchuk. With such integration both projects will just improved. What do you think? Best regards, Denis

6 19