February 2016 - Pharo-dev - lists.pharo.org

Yet again, wrong tempvars in debuggers context variables list

by Nicolai Hess

This is not an issue with GTDebugger, but the way opal generates the tempvar index or the way, debuggerMap tries to access the context vars 17660 <https://pharo.fogbugz.com/f/cases/17660/wrong-tempvar-values-in-debugger> wrong tempvar values in debugger This is a really special case, I wasn't able yet to create an easier example for reproducing this bug: - put a self haltOnce in RAbstractClass>>#directlyDefinesLocalMethod: - enable halt once - select any other method in Nautilus and choose "Rename method (all)" from method panes context menu - enter a new name and push "OK" -> the debugger pops up in method directlyDefinesLocalMethod: - select the first "allClassesDo:" context from top of the stack -> the debugger shows that we are in the evalBlock context The "seen" variable is a Set, but if you look at the "Variables"-pane, it is shown as a block (this is actually the parameter aBlock)

Feb. 20, 2016

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

by Stephan Eggermont

On 20-02-16 11:49, Damien Cassou wrote: > 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 use PharoLauncher all the time, on Mac and Linux. When fixing an issue, it provides an easy way to get the latest image, make a change or review a slice, or test a metacello configuration I use company project images, pharo-contribution (seaside, qcmagritte) and moose (petitdelphi) CI images Stephan

Feb. 20, 2016

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

by Cyril Ferlicot D.

Le 20/02/2016 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 > Hi, Myself and some people from Synectique use it to download and manage images from Pharo, Moose and Synectique's CI. -- Cyril

Feb. 20, 2016

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

by Cyril Ferlicot D.

Le 20/02/2016 11:46, Damien Cassou a Ã©crit : > For my CV, I need to know who is using the stuff I'm doing. If you use > Pillar, could you please tell me in which context (e.g., which company, > open-source project) and what you use it for (e.g., what kind of > document)? > > I don't need long paragraphs, just give me the keywords please. > Hi, I use it to write reports (internship report, or practical work report) for my faculty. -- Cyril

Feb. 20, 2016

Re: [Pharo-dev] GTSpotter, the 95% case

by stepharo

Sven I'm not against spotter. This is why I will try to do a video assuming that all the bugs are fixed. Now if I have 30 min to do a videos I do not have 5 days to understand how to use and try spotter because when I have few moments to program I need something fully working. Stef Le 20/2/16 11:26, Sven Van Caekenberghe a Ã©crit : >> On 20 Feb 2016, at 11:06, stepharo <stepharo(a)free.fr> wrote: >> >> Tx sven >> I will see if I use this scenario for a video to explain my friend Spotter. >> If you have scenario that I can blindly follow I'm eager to try to produce a video. > Yes, that would be good. > > But even better would be if one starts to use it a bit in day to day routine, only then do you really feel it, and then we can iterate and try to improve (I must say that I learned new stuff while writing this mail ;-) > > There should be something like on OS X > System Preferences > Trackpad where you have animations and videos explaining thing in the same UI (not jumping to something else). > > At least, there should be a cookbook explaining really well, high level, for beginners, how to use Spotter (but things have to be stable). > >>> Hi, >>> >>> >>> This is in the latest #50591, BTW. >>> >>> Starting with the 3rd one, searching for classes, that has been working well since day one and has benefited from general improvements. >>> >>> 'zncl' gives me ZnClient immediately. >>> >>> Yes, you have to learn how to dive into a result to expand it, but that is not often needed in this case. >>> >>> 'readstream', then first arrow (or cmd-shit-right), then 'co' gives me ZnCodePointReadStream and ZnEncodeReadStream. >>> >>> In both cases, just typing enter browses the class, which is what I want. >>> >>> Both implementers and senders do work well today, you just have to figure out how (learnability is an issue, but not everything can be obvious in this world). >>> >>> 'get: #i' but also, 'get:' + cmd-m gives you all implementors of #get: and spotter automatically expands from a limited set of 5 matches to 100 >> How do I get to see all of them and not just the 100 first. >> When I click on the arrow I get the same list 100/127 but not all > Yes, that is true, 100 is probably some arbitrary limit > > In the past there was just one limit for all categories, maybe it is different now, it could be much large or infinite in some cases > > The idea is to keep refining the search (like I described below) > >>> Enable preview (click outer arrow, or cmd-p) and you see the implementors right there >>> >>> Now, dive in (first arrow or cmd-shit-right), and type 'zn' and I can see ZnClient>>#get: >>> >>> Type enter to open the method in a browser >>> >>> Similar approach for senders, using #s and cmd-n >>> >>> 'join: #s'but also, 'join:' + cmd-n gives you all senders of #join: and spotter automatically expands >>> >>> Enable preview (click outer arrow, or cmd-p) and you see the implementors right there >>> >>> Now, dive in (first arrow or cmd-shit-right), and type 'zn' and I can see ZnDefaultServerDelegate>>#welcomePageCss >>> >>> Type enter to open the method in a browser >>> >>> Class references, I don't know how to do that, but I can't see why it would not fit and it would be a good addition. >>> >>> Spotter adds to the other ways of doing these 4 actions, the old one still work, as does command-click (one of my favourites). >>> >>> Sven >>> >>> PS: I don't wan to narrow down the discussion to just these 4 cases, Spotter and GT are about way more than just this, you can search for many, many things (for example, type 'json' and you can install 3 packages from the catalog), and you can extend these tools yourself. I also know that things must improve further. > >

Feb. 20, 2016

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

by Tudor Girba

Writing: - documentation - blog posts - a potential book Doru > On Feb 20, 2016, at 11:46 AM, Damien Cassou <damien.cassou(a)inria.fr> wrote: > > For my CV, I need to know who is using the stuff I'm doing. If you use > Pillar, could you please tell me in which context (e.g., which company, > open-source project) and what you use it for (e.g., what kind of > document)? > > I don't need long paragraphs, just give me the keywords please. > > -- > 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 "There are no old things, there are only old ways of looking at them."

Feb. 20, 2016

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

by phil＠highoctane.be

Writing documentation for http://pharo.org/success/CableExpertise * administration book * development guidelines book * devops book * training manual On Sat, Feb 20, 2016 at 11:46 AM, Damien Cassou <damien.cassou(a)inria.fr> wrote: > For my CV, I need to know who is using the stuff I'm doing. If you use > Pillar, could you please tell me in which context (e.g., which company, > open-source project) and what you use it for (e.g., what kind of > document)? > > I don't need long paragraphs, just give me the keywords please. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." --Winston Churchill > >

Feb. 20, 2016

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

by phil＠highoctane.be

I use it on Ubuntu Linux for starting images that run some tools I use to generate other languages template-based code. On Sat, Feb 20, 2016 at 11:49 AM, Damien Cassou <damien.cassou(a)inria.fr> wrote: > 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 > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." --Winston Churchill > >

Feb. 20, 2016

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

by Tudor Girba

Hi, I meant to say, that the help is not complete. We only added it as fast as possible to the UI so that you are not disturbed when taking screenshots. The help contents will follow. Cheers, Doru > On Feb 20, 2016, at 2:34 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > 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." > -- www.tudorgirba.com www.feenk.com "Every now and then stop and ask yourself if the war you're fighting is the right one."

Feb. 20, 2016

Re: [Pharo-dev] Other spotter questions

by Tudor Girba

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. 20, 2016