- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] How was BoxedFloat64 integrated into the image ?

by Yuriy Tymchuk

Hi, I can add it, but can you give me a bit of context? Are we talking about references to BoxedFloat64 class? Cheers. Uko > On 18 Feb 2016, at 13:55, Ben Coman <btc(a)openinworld.com> wrote: > > On Thu, Feb 18, 2016 at 8:52 PM, Nicolas Cellier > <nicolas.cellier.aka.nice(a)gmail.com> wrote: >> Beware, most client code should only refer to the visible faÃ§ade Float and >> its API. >> BoxedFloat64 is an implementation detail and is VM dependent. >> We don't want client code to be VM dependent, do we? >> I hope those references to BoxedFloat64 are rare. > > Should there be a Quality Assistant rule for this? > cheers -ben > >> >> 2016-02-18 11:47 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: >>> >>> Because we have compiled methods with BoxedFloat64 associations in the >>> methods literals, but the source code still shows only "Float". >>> >>> 17638 Browsing calls on BoxedFloat64 shows methods with reference to >>> BoxedFloat64 in the code >>> >>> >>> >> >

Feb. 21, 2016

Re: [Pharo-dev] Who is using Pharo Launcher and for what

by stepharo

All the time to organise my 1000 images :) Le 20/2/16 11:49, Damien Cassou a Ã©crit : > For my CV, I need to know who is using the stuff I'm doing. If you use > the Pharo Launcher, could you please tell me in which context (e.g., > which company, open-source project) and what you use it for (e.g., > download from CI, standard Pharo)? > > I don't need long paragraphs, just give me the keywords please. > > Thanks >

Feb. 21, 2016

Re: [Pharo-dev] Other spotter questions

by stepharo

Thanks. You see been a bug "spotter" is absolutely not fun even if people may think it is. I always have the impression that my flat is full of boxes and that I have to jump over them to move. Stef Le 20/2/16 14:36, Tudor Girba a Ã©crit : > This is a regression. > > I opened a bug: > https://pharo.fogbugz.com/f/cases/17658/Spotter-in-place-category-expansion… > > Doru > > >> On Feb 20, 2016, at 2:30 PM, stepharo <stepharo(a)free.fr> wrote: >> >> So >> >> I type >> >> Point #references >> >> spotter shows me 51/46 >> >> I press show all and I get 46/46 class references >> >> I do not understand why >> >> when I type >> >> get: #implementors >> spotter shows me 100/172 >> >> when I press the arrow I get >> 100/172 >> >> So how do I get the 72 that are missing. >> >> Stef >> >> >> >> > -- > www.tudorgirba.com > www.feenk.com > > "We cannot reach the flow of things unless we let go." > > > > > >

Feb. 21, 2016

Re: [Pharo-dev] Why the GTSpotter help does not explain all the categories

by stepharo

Thanks but it does not really help understanding. At least I do not get it at all. I have no idea how from Class instance variables I should type something meaningfull. I could get it for Examples, Implementors, Senders because there is only one word. Le 20/2/16 14:34, Tudor Girba a Ã©crit : > We added the mechanism and created a kind of an API entry for documenting all entries within the image. This was one of your request: to know what are all the different searches possible :). > > Doru > > >> On Feb 20, 2016, at 2:26 PM, stepharo <stepharo(a)free.fr> wrote: >> >> 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:) >> >> >> > -- > www.tudorgirba.com > www.feenk.com > > "Reasonable is what we are accustomed with." > > >

Feb. 21, 2016

Re: [Pharo-dev] double selection in the debugger is confusing

by stepharo

Here this is terribly confusing because we could think that the execution will go inside the true block but no in reality it is jumping right after. So we must remove this selection of matching terms. Stef Le 21/2/16 19:04, stepharo a Ã©crit : > 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

Feb. 21, 2016

double selection in the debugger is confusing

by stepharo

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

Feb. 21, 2016

in 50596 protocol icons are lost

by stepharo

Hi guys I noticed that when I look at the protocols with Pharo5.0 Latest update: #50596 that the icons are damaged. Stef

Feb. 21, 2016

cannot use shortcut in text pane of MC

by stepharo

Hi guillermo I do not know if this is the one you fixed but in Pharo5.0 Latest update: #50596 I cannot type the name of class and browse it in a MC textpane. Stef

Feb. 21, 2016

Re: [Pharo-dev] Looking for class

by Eliot Miranda

Hi Doru > On Feb 20, 2016, at 12:53 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Again, as I said, we have a problem with finding a performant solution for order. If anyone would like to have a look, it would be useful. What does one need other than exact matches come first followed by sorted inexact matches? Works very well with find class dialogs at least. As one types more the relevant results float to the top. > Cheers, > Doru > > >> On Feb 20, 2016, at 9:46 PM, Damien Cassou <damien.cassou(a)inria.fr> wrote: >> >> I've just tried to use to spotter to get the code of the #class method. I typed 'class' and Spotter showed a lot of methods but the method I was looking for was not in the top. In the Emacs equivalent of Spotter (helm), closest and exact matches are shown first. I guess helm uses a notion of distance to order results. In helm, I could have typed "class$" to get only methods ending with "class". >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Success is the ability to go from one failure to another without >> losing enthusiasm." --Winston Churchill > > -- > www.tudorgirba.com > www.feenk.com > > "Presenting is storytelling." > >

Feb. 21, 2016

Re: [Pharo-dev] adding custom tabs to bottom of gtDebugger

by Ben Coman

Thanks. Some examples I found useful were * Date>>gtInspectorDetailsIn: * GTInspector>>gtInspectorExtensionsIn: cheers -ben On Sun, Feb 21, 2016 at 4:53 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > The tabs from the inspector are defined through inspector extensions. > > So, you should have a method annotated with gtInspectorPresentationOrder: in your OwnedLockBadRelease. > > Let me know if you need more help. > > Cheers, > Doru > > >> On Feb 21, 2016, at 9:35 AM, Ben Coman <btc(a)openInWorld.com> wrote: >> >> With... >> Error subclass: #OwnedLockBadRelease >> instanceVariableNames: 'lockOwner perpetrator' >> classVariableNames: '' >> package: 'Kernel-Processes' >> >> In playground when I do... >> | error | >> (error := OwnedLockBadRelease new) signal >> then in the debugger select the 'error' tempvar, >> the [Raw] tab is too busy, so I'd like a custom [Error] tab >> showing only my two instance variables. >> >> I've managed to get a tab to show up by implementing... >> OwnedLockBadRelease>>gtDebuggerEvaluatorIn: composite >> super gtDebuggerEvaluatorIn: composite. >> (GTObjectVariablesBrowser new evaluatorIn: composite) >> title: 'Error Tab To Do' >> but I can't find how to add variables. >> >> Tips please? >> cheers -ben >> > > -- > www.tudorgirba.com > www.feenk.com > > "It's not how it is, it is how we see it." > >

Feb. 21, 2016