- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Bloc] Do we want <return: #Point> or <return: Point>
by Esteban Lorenzano Feb. 23, 2016

Feb. 23, 2016

> On 23 Feb 2016, at 13:20, Alain Plantec via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > > From: Alain Plantec <alain.plantec(a)yahoo.com> > Subject: Re: [Pharo-dev] [Bloc] Do we want <return: #Point> or <return: Point> > Date: 23 February 2016 at 13:19:34 GMT+1 > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > > > Hello Doru, > >> On 23 Feb 2016, at 10:33, Tudor Girba <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>> wrote: >> >> Hi, >> >> At the moment, it is used for documentation purposes in Bloc. It is part of the effort of Alex to document Bloc thoroughly. I think it is an interesting idea, in that we would have a significant case study for that can be used later as optional types information to improve static tool support. And it does not hurt at the moment. >> >> What do you think? > > Experimenting optional types is a good idea. We could have Tools to dynamically check them. > What about a separate typing model that could be used to add/remove the types annotations ? > Also, I wonder if Bloc is the good package to experiment optional types. Maybe it is not stable enough. > Cheers > Alain please, please, please keep the scope of those experiments aside the main effort who is to have Block/Brick running as soon as possible. Esteban ps: â¦ optional typesâ¦ at the end, we will realise Gilad was right all this time :) > > >> >> Cheers, >> Doru >> >> >>> On Feb 23, 2016, at 10:25 AM, Alain Plantec via Pharo-dev <pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org>> wrote: >>> >>> >>> From: Alain Plantec <alain.plantec(a)yahoo.com <mailto:alain.plantec@yahoo.com>> >>> Subject: Re: [Pharo-dev] [Bloc] Do we want <return: #Point> or <return: Point> >>> Date: February 23, 2016 at 10:23:33 AM GMT+1 >>> To: Pharo Development List <pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org>> >>> >>> >>> I donât like it too. >>> Alain >>> >>>> Le 23 fÃ©vr. 2016 Ã 09:50, Nicolai Hess <nicolaihess(a)gmail.com <mailto:nicolaihess@gmail.com>> a Ã©crit : >>>> >>>> >>>> >>>> 2016-02-23 9:47 GMT+01:00 stepharo <stepharo(a)free.fr <mailto:stepharo@free.fr>>: >>>> Hi >>>> >>>> I saw that something <return: #Point> or <return: Point> >>>> I do not know why but I have the impression that <return: #Point> is better. >>>> Because we may have code not present and still want to load the code. >>>> >>>> I would like to know for what this is used. >>>> I don't like it. >>>> >>>> >>>> Stef >>>> >>>> >>> >>> >>> >> >> -- >> www.tudorgirba.com <http://www.tudorgirba.com/> >> www.feenk.com <http://www.feenk.com/> >> >> "We are all great at making mistakes." > > >

3 3

[pharo-project/pharo-core]
by GitHub Feb. 23, 2016

Feb. 23, 2016

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

1 0

[pharo-project/pharo-core] d37c12: 50602
by GitHub Feb. 23, 2016

Feb. 23, 2016

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: d37c124b9367ad904de724a5db0f27ca34be93fa https://github.com/pharo-project/pharo-core/commit/d37c124b9367ad904de724a5… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-02-23 (Tue, 23 Feb 2016) Changed paths: M ConfigurationOfSessionManager.package/ConfigurationOfSessionManager.class/instance/symbolic versions/stable_.st A ConfigurationOfSessionManager.package/ConfigurationOfSessionManager.class/instance/versions/version13_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50601.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50602.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50601.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50602.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A System-SessionManager-Tests.package/SessionManagerRegistrationTest.class/instance/tests/testGivenARegisteredClassHandlerShouldHasRegisteredReturnsTrue.st A System-SessionManager-Tests.package/SessionManagerRegistrationTest.class/instance/tests/testGivenUnknonwnHandledIdShouldHasRegisteredReturnsFalse.st A System-SessionManager.package/SessionManager.class/instance/registration/hasRegistered_.st A System-SessionManager.package/SessionManager.class/instance/registration/registerUserClassNamed_.st A System-SessionManager.package/SessionManager.class/instance/registration/registerUserClassNamed_atPriority_.st Log Message: ----------- 50602 17680 SessionManager 1.3 https://pharo.fogbugz.com/f/cases/17680 http://files.pharo.org/image/50/50602.zip

1 0

[pharo-project/pharo-core] a1da99: 50599
by GitHub Feb. 23, 2016

Feb. 23, 2016

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: a1da9931b80887c0b2bc1cca1150487b56df3dd5 https://github.com/pharo-project/pharo-core/commit/a1da9931b80887c0b2bc1cca… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-02-22 (Mon, 22 Feb 2016) Changed paths: M ConfigurationOfSessionManager.package/ConfigurationOfSessionManager.class/instance/symbolic versions/stable_.st A ConfigurationOfSessionManager.package/ConfigurationOfSessionManager.class/instance/versions/version12_.st M Deprecated50.package/extension/SmalltalkImage/instance/addDeferredStartupAction_.st M Deprecated50.package/extension/SmalltalkImage/instance/addToShutDownList_.st M Deprecated50.package/extension/SmalltalkImage/instance/addToStartUpList_.st M Deprecated50.package/extension/SmalltalkImage/instance/add_toList_after_.st M Deprecated50.package/extension/SmalltalkImage/instance/add_toList_before_.st M Kernel.package/Class.class/instance/subclass creation/immediateByteSubclass_instanceVariableNames_classVariableNames_package_.st M Kernel.package/DelayScheduler.class/instance/class initialization/initialize.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50598.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50599.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50598.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50599.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Traits.package/TClass.class/instance/subclass creation - immediate/immediateSubclass_instanceVariableNames_classVariableNames_package_.st M Traits.package/TClass.class/instance/subclass creation - variableWord/variableWordSubclass_instanceVariableNames_classVariableNames_package_.st M Traits.package/Trait.class/instance/subclass creation/immediateByteSubclass_instanceVariableNames_classVariableNames_package_.st Log Message: ----------- 50599 ConfigurationOfSessionManager http://files.pharo.org/image/50/50599.zip

4 3

double selection in the debugger is confusing
by stepharo Feb. 23, 2016

Feb. 23, 2016

Hi guy we should disable the double selection when we click on a stack element because we get selection in frame and in fill and this is confusing because the PC is represented by the filled one. Stef

3 5

TxText architecture question
by Stephan Eggermont Feb. 23, 2016

Feb. 23, 2016

In the TxText model, a text consists of a double-linked list of spans, containing the text content and its attributes. I wonder how to efficiently map a hierarchical text model (like that of Pillar) to that. Stephan

1 0

Why the GTSpotter help does not explain all the categories
by stepharo Feb. 23, 2016

Feb. 23, 2016

Hi So I tried again to understand how spotter works and I looked at the help and I could not understand how I can find class references. I saw that but it does not show me how I can use it and I do not really want to understand how this is implemented. spotterReferenceFor: aStep <spotterOrder: 30> aStep listProcessor title: 'References'; allCandidates: [ (SystemNavigation default allReferencesTo: self binding) collect: #compiledMethod ]; itemName: [ :method | method gtDisplayString ]; filter: GTFilterSubstring To me this help is totally obscure. Spotter allows the developer to define custom search processors in different classes. These custom processors take effect when Spotter reaches an instance of the extended class. You can find below the list of extensions from this image. You can also browse this list by inspecting: GTSpotter spotterExtendingMethods Behavior - Class instance variables (spotterClassInstanceVariablesFor:) - Composing traits (spotterCompositionFor:) - Instance variables (spotterInstanceVariablesFor:) - QA Critics (spotterQACriticsFor:) - All subclasses (spotterSubclassesFor:) - All superclasses (spotterSuperclassesFor:) - Users (spotterTraitUsersFor:) - Special Slots (spotterUsedSlotsFor:) - Uses Traits (spotterUsedTraitsFor:) Class - Examples (gtSpotterGTExamplesFor:) - Class methods (spotterClassMethodsFor:) - Instance methods (spotterMethodsFor:) - References (spotterReferenceFor:) - Super class methods (spotterSuperClassMethodsFor:) - Super instance methods (spotterSuperMethodsFor:) ClassDescription - Package (spotterPackageFor:) Collection - spotterItemsFor: (spotterItemsFor:) CompiledMethod - Bytecode (spotterForBytecodesFor:) - Implementors (spotterForImplementorsFor:) - Senders (spotterForSendersFor:) - Class (spotterMethodClassFor:) - QA Critics (spotterQACriticsFor:) Dictionary - Keys (spotterForKeysFor:) FileReference - Directories (spotterForDirectoriesFor:) - Files (spotterForFilesFor:) - Directories (spotterForZipDirectoriesFor:) - Files (spotterForZipFilesFor:) GTExample - Example Dependencies (gtSpotterDependenciesFor:) - Example Dependents (gtSpotterDependentsFor:) - Example Provider (gtSpotterProviderFor:) - Example Source (gtSpotterSourceFor:) - Example Subjects (gtSpotterSubjectsFor:) GTExampleFinder - Examples (gtSpotterExamplesFor:) GTExampleFinder class - Examples (gtSpotterExamplesFor:) GTExampleOrganizer - Examples (gtSpotterGTExamplesFor:) GTExampleProxy - Example Dependencies (gtSpotterDependenciesFor:) - Example Dependents (gtSpotterDependentsFor:) GTInspector class - Extensions (spotterExtensionsFor:) GTSelectorImplementors - Implementors (spotterImplementorsFor:) - Senders (spotterSendersFor:) GTSpotter - Examples (gtSpotterExamplesFor:) - Catalog Projects (spotterCatalogProjectsFor:) - Clipboard History (spotterClipboardFor:) - Methods (spotterConcreteMethodFor:) - Dirty Monticello packages (spotterDirtyMonticelloPackagesFor:) - Playground cached pages (spotterForCachedPlaygroundPagesFor:) - Classes (spotterForClassesFor:) - Directories (spotterForDirectoriesFor:) - Calculator (spotterForExpressionsFor:) - Files (spotterForFilesFor:) - Global variables (spotterForGlobalVarsFor:) - Help topics (spotterForHelpTopicFor:) - Messages (spotterForMessagesFor:) - Metacello Configurations (spotterForMetacelloConfigurationsFor:) - Packages (spotterForPackagesFor:) - Pragmas (spotterForPragmasFor:) - References (spotterForReferencesFor:) - Monticello Repositories (spotterForRepositoriesFor:) - Senders (spotterForSendersFor:) - spotterForStashedPlaygroundPagesFor: (spotterForStashedPlaygroundPagesFor:) - History (spotterHistoryFor:) - Implementors (spotterImplementorsFor:) - ws.stfx.eu (spotterStfxFor:) - Menu (spotterWorldMenuFor:) GTSpotter class - Extensions (spotterExtensionsFor:) GTSpotterExceptionMock1 - mockProcessorFor: (mockProcessorFor:) GTSpotterExceptionMock2 - mockProcessorFor: (mockProcessorFor:) GTSpotterExceptionMock3 - mockProcessorFor: (mockProcessorFor:) GTSpotterExceptionMock4 - mockProcessorFor: (mockProcessorFor:) GTSpotterExceptionMock5 - mockProcessorFor: (mockProcessorFor:) GlobalVariable - Class (spotterClassFor:) - References (spotterForReferencesFor:) HelpTopic - Help contents (spotterForHelpTopicFor:) KMDispatcher - Keys (spotterForKeysFor:) MCPackage - Packages (spotterForPackageFor:) - Monticello Working Copy (spotterMonticelloWorkingCopyFor:) MCVersionInfo - Ancestors (spotterAncestorsFor:) MCWorkingCopy - All other repositories (spotterAllRepositoriesFor:) - Ancestors (spotterAncestorsFor:) - Monticello Package (spotterMonticelloPackageFor:) - Packages (spotterPackageFor:) - Package repositories (spotterPackageRepositoriesFor:) MenuItemMorph - spotterItemsFor: (spotterItemsFor:) MenuMorph - Items (spotterItemsFor:) MetacelloAbstractPackageSpec - Includes (spotterForIncludesFor:) - Requires (spotterForRequiresFor:) MetacelloProject - Versions (spotterForVersionsFor:) MetacelloVersion - Groups (spotterForGroupsFor:) - Packages (spotterForPackagesFor:) Morph - spotterForKeysFor: (spotterForKeysFor:) - Submorphs (spotterForSubmorphsFor:) PragmaType - Pragmas (spotterPragmasFor:) - Senders (spotterSendersFor:) RPackage - Classes (spotterClassesFor:) - Extension Methods (spotterExtensionMethodsFor:) - Monticello Package (spotterMonticelloPackageFor:) - Monticello Working Copy (spotterMonticelloWorkingCopyFor:) - Tags (spotterTagsFor:) RPackageTag - Classes (spotterClassesFor:) SettingNode - Children (spotterForSettingsFor:) SettingTree - Settings (spotterForSettingsFor:) Slot - Accesses (spotterAccessesFor:) Trait - Examples (gtSpotterGTExamplesFor:) - Class methods (spotterClassMethodsFor:) - Instance methods (spotterMethodsFor:) - References (spotterReferenceFor:) - Super class methods (spotterSuperClassMethodsFor:) - Super instance methods (spotterSuperMethodsFor:) TraitBehavior - Class instance variables (spotterClassInstanceVariablesFor:) - Composing traits (spotterCompositionFor:) - Instance variables (spotterInstanceVariablesFor:) - QA Critics (spotterQACriticsFor:) - All subclasses (spotterSubclassesFor:) - All superclasses (spotterSuperclassesFor:) - Users (spotterTraitUsersFor:) - Special Slots (spotterUsedSlotsFor:) - Uses Traits (spotterUsedTraitsFor:) TraitDescription - Package (spotterPackageFor:)

4 8

[Bloc] dispatcher vs shortcutHandler
by stepharo Feb. 23, 2016

Feb. 23, 2016

Hi what is the diff between kmDispatcher and shotcutHandler? Stef

1 0

[Bloc] Why space is weakly referenced?
by stepharo Feb. 23, 2016

Feb. 23, 2016

Just to understand space "Return space to which I belong. Direct reference boosts performance. Each element has weak reference to the current space which is set at creation moment. @see BlElement>>#basicSpace:" <return: #BlSpace> self assert: spaceReference isNotNil. ^ spaceReference ifNotNil: [ :sr | sr at: 1 ]

1 0

[Pharo-dev] MetaclassTest>>testMetaclassAndTraitClassRespectsPolymorphismRules
by Sven Van Caekenberghe Feb. 23, 2016

Feb. 23, 2016

Hi, I am trying to load a new version of STON in Pharo 5 https://pharo.fogbugz.com/f/cases/16893/Update-STON One of the tests that fails is MetaclassTest>>testMetaclassAndTraitClassRespectsPolymorphismRules More specifically, (Metaclass localSelectors difference: ClassTrait localSelectors) is no longer equal to the exceptions defined in the test because #stonName and #stonOn: were added to Metaclass What should I do ? Did I do something wrong ? Should I add to the exceptions defined in the test or should I add them to ClassTrait ? I think the first sounds the most correct. Thx, Sven

3 6