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

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

by stepharo

Doru is it the title: 'References' that is used to represent #references? I do not get it, I have ot guess. Showing people the implementation does not automatically explain. The help is missing some text (no idea if this is correct). " Each Extensions methods (e.g. spotterCompositionFor:) defines the category tags that you can type in the input field Point #traits? Point #composing traits? For the people loving implementation detail, the title of the listProcessor is used as categories. " Stef Le 22/2/16 10:24, Tudor Girba a Ã©crit : > Hi, > > Indeed, this is a problem: > https://pharo.fogbugz.com/f/cases/17668/Spotter-should-allow-filtering-cate… > > Now, I enhanced the category matching to ignore the whitespace. So, now you can say: > #Classinstancevariables > > Another option would be to change the names of categories to have underscore instead of space. Like this: > #Class_instance_variables > > What do you think? > > Cheers, > Doru > > >> On Feb 21, 2016, at 7:22 PM, stepharo <stepharo(a)free.fr> wrote: >> >> 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." >>> >>> >>> >> > -- > www.tudorgirba.com > www.feenk.com > > "Quality cannot be an afterthought." > > >

Feb. 23, 2016

Re: [Pharo-dev] MetaclassTest>>testMetaclassAndTraitClassRespectsPolymorphismRules

by stepharo

May be I got wrong what you say. But we should not link metaclass or TApplyingOnClassSide on Ston. Le 20/2/16 12:34, Henrik Nergaard a Ã©crit : > Ah, test testMetaclass. Somehow I only read testClass.... > > Moving those two methods from Metaclass to TApplyingOnClassSide should make the test happy. > > Best regards, > Henrik > > -----Original Message----- > From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Sven Van Caekenberghe > Sent: Saturday, February 20, 2016 11:58 AM > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Subject: Re: [Pharo-dev] MetaclassTest>>testMetaclassAndTraitClassRespectsPolymorphismRules > > If I add (in #50591) my methods to the exception set in the middle, the test is green > > self > assert: > (Metaclass localSelectors difference: ClassTrait localSelectors) > = > {#externalTypeAlias:. > #baseClass. > #basicLocalSelectors:. > #basicLocalSelectors. > #classClass. > #isClass. > #stonName. "<<<" > #stonOn:. "<<<" > #environment. > #fileOutOn:. > #fileOutOn:initializing:. > #postCopy. > #traitComposition. > #traitComposition:. > #veryDeepCopyWith:} asSet. > > I don't know about the other failures. > >> On 20 Feb 2016, at 11:37, Henrik Nergaard <henrik.nergaard(a)uia.no> wrote: >> >> The issue should be unrelated: >> >> https://pharo.fogbugz.com/f/cases/17616/CI-Server-Failing-tests-related-to-… >> >> Best regards, >> Henrik >> >> -----Original Message----- >> From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Sven Van Caekenberghe >> Sent: Saturday, February 20, 2016 11:05 AM >> To: Pharo Development List <pharo-dev(a)lists.pharo.org> >> Subject: [Pharo-dev] MetaclassTest>>testMetaclassAndTraitClassRespectsPolymorphismRules >> >> 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 >> >> > > >

Feb. 23, 2016

Re: [Pharo-dev] [ANN] Pharo on Travis-CI

by stepharo

https://pharoweekly.wordpress.com :) Le 21/2/16 22:36, Fabio Niephaus a Ã©crit : > Hello everyone, > > I haven't had the time to officially announce it here, but some of you > have already used or > contributed to this: > > Pharo is officially supported on Travis-CI <http://travis-ci.org/>! > This means you can finally set "language: smalltalk" in > your /.travis.yml/ in order to run tests for your GitHub-hosted Pharo > projects on Travis-CI. > > Peter has put together a blog post [1] that should get you started. > For more information see [2]. > If you have any bug reports or feature requests, please file an issue > at [3]. > > Many thanks to Dale, Peter, Esteban and everyone else who contributed > to smalltalkCI so far! > > Happy testing! > > Fabio (HPI student and smalltalkCI maintainer) > > > [1] > http://peteruhnak.com/blog/2016/02/15/testing-pharo-projects-with-travis/ > <https://github.com/hpi-swa/smalltalkCI#features> > [2] https://github.com/hpi-swa/smalltalkCI#how-to-use > <https://github.com/hpi-swa/smalltalkCI#how-to-use> > [3] https://github.com/hpi-swa/smalltalkCI/issues > <https://github.com/hpi-swa/smalltalkCI/issues>

Feb. 23, 2016

Re: [Pharo-dev] [ANN] Pharo on Travis-CI

by stepharo

Super cool Thanks for your effort! Le 21/2/16 22:36, Fabio Niephaus a Ã©crit : > Hello everyone, > > I haven't had the time to officially announce it here, but some of you > have already used or > contributed to this: > > Pharo is officially supported on Travis-CI <http://travis-ci.org/>! > This means you can finally set "language: smalltalk" in > your /.travis.yml/ in order to run tests for your GitHub-hosted Pharo > projects on Travis-CI. > > Peter has put together a blog post [1] that should get you started. > For more information see [2]. > If you have any bug reports or feature requests, please file an issue > at [3]. > > Many thanks to Dale, Peter, Esteban and everyone else who contributed > to smalltalkCI so far! > > Happy testing! > > Fabio (HPI student and smalltalkCI maintainer) > > > [1] > http://peteruhnak.com/blog/2016/02/15/testing-pharo-projects-with-travis/ > <https://github.com/hpi-swa/smalltalkCI#features> > [2] https://github.com/hpi-swa/smalltalkCI#how-to-use > <https://github.com/hpi-swa/smalltalkCI#how-to-use> > [3] https://github.com/hpi-swa/smalltalkCI/issues > <https://github.com/hpi-swa/smalltalkCI/issues>

Feb. 23, 2016

Re: [Pharo-dev] Hackathon IoT. I used Pharo.

by stepharo

When? I would like to attend Le 22/2/16 17:22, Serge Stinckwich a Ã©crit : > On Mon, Feb 22, 2016 at 3:07 PM, philippe.back(a)highoctane.be > <philippe.back(a)gmail.com> wrote: >> LoRa stuff with sensors etc. Integrated REST apis for that in Pharo. >> >> I'll do a writeup on my blog. >> >> Lots of opportunities for Pharo in that space. > Yes, I think so. > I would like to push Pharo in this area in the future, especially with > LoRa sensors. We will organize a meeting for wireless sensors for > environmental surveillance in May. > are you interested to present something around Pharo ? > > Regards,

Feb. 23, 2016

Re: [Pharo-dev] Hackathon IoT. I used Pharo.

by stepharo

I'm interested too because we Rmod wants to check Pharo as a IoT platform in the future Le 22/2/16 15:07, philippe.back(a)highoctane.be a Ã©crit : > > LoRa stuff with sensors etc. Integrated REST apis for that in Pharo. > > I'll do a writeup on my blog. > > Lots of opportunities for Pharo in that space. > > Phil > > On Feb 22, 2016 2:49 PM, "Serge Stinckwich" > <serge.stinckwich(a)gmail.com <mailto:serge.stinckwich@gmail.com>> wrote: > > Great ! What did you exactly, I'm interested by details ;-) > > 2016-02-22 14:42 GMT+01:00 phil(a)highoctane.be > <mailto:phil@highoctane.be> <phil(a)highoctane.be > <mailto:phil@highoctane.be>>: > > > http://geeko.lesoir.be/2016/02/22/hackapost-un-hackathon-sur-les-applis-iot… > > > > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ >

Feb. 23, 2016

Re: [Pharo-dev] [ANN] Pharo on Travis-CI

by Serge Stinckwich

Great ! You should do the announce on pharo-users also. Regards, On Sun, Feb 21, 2016 at 10:36 PM, Fabio Niephaus <lists(a)fniephaus.com> wrote: > Hello everyone, > > I haven't had the time to officially announce it here, but some of you have > already used or > contributed to this: > > Pharo is officially supported on Travis-CI! This means you can finally set > "language: smalltalk" in > your .travis.yml in order to run tests for your GitHub-hosted Pharo projects > on Travis-CI. > > Peter has put together a blog post [1] that should get you started. For more > information see [2]. > If you have any bug reports or feature requests, please file an issue at > [3]. > > Many thanks to Dale, Peter, Esteban and everyone else who contributed to > smalltalkCI so far! > > Happy testing! > > Fabio (HPI student and smalltalkCI maintainer) > > > [1] > http://peteruhnak.com/blog/2016/02/15/testing-pharo-projects-with-travis/ > [2] https://github.com/hpi-swa/smalltalkCI#how-to-use > [3] https://github.com/hpi-swa/smalltalkCI/issues -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Feb. 23, 2016

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

by Eliot Miranda

Hi Nicolai, there is a hairy script that moves methods around the hierarchy. IIRC Float is renamed to BoxedFloat64, then a new Float is introduced, then BoxedFloat64 made to inherit from it. It's likely that the last step of this script, which replaces the methodClassAssociations in the moved methods (makes those BoxedFloat64 methods that used to be Float or maybe vice verse) with the right association, didn't work. I don't know how the Pharo 5 image is built. If it is incremental then just write a script to fix the associations. But if the image is produced by a bootstrap you'll need to track down the script that creates the revised Float hierarchy and fix it to work properly in Pharo. _,,,^..^,,,_ (phone) > On Feb 18, 2016, at 2:47 AM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > 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. 23, 2016

Re: [Pharo-dev] Hackathon IoT. I used Pharo.

by Stephan Eggermont

On 22/02/16 15:07, philippe.back(a)highoctane.be wrote: > LoRa stuff with sensors etc. Integrated REST apis for that in Pharo. > > I'll do a writeup on my blog. Please do. LoRa looks very interesting. Stephan

Feb. 22, 2016

Re: [Pharo-dev] [ANN] Pharo on Travis-CI

by Peter UhnÃ¡k

+1000 Great work! On Sun, Feb 21, 2016 at 10:36 PM, Fabio Niephaus <lists(a)fniephaus.com> wrote: > Hello everyone, > > I haven't had the time to officially announce it here, but some of you > have already used or > contributed to this: > > Pharo is officially supported on Travis-CI <http://travis-ci.org/>! This > means you can finally set "language: smalltalk" in > your *.travis.yml* in order to run tests for your GitHub-hosted Pharo > projects on Travis-CI. > > Peter has put together a blog post [1] that should get you started. For > more information see [2]. > If you have any bug reports or feature requests, please file an issue at > [3]. > > Many thanks to Dale, Peter, Esteban and everyone else who contributed to > smalltalkCI so far! > > Happy testing! > > Fabio (HPI student and smalltalkCI maintainer) > > > [1] > http://peteruhnak.com/blog/2016/02/15/testing-pharo-projects-with-travis/ > <https://github.com/hpi-swa/smalltalkCI#features> > [2] https://github.com/hpi-swa/smalltalkCI#how-to-use > [3] https://github.com/hpi-swa/smalltalkCI/issues >

Feb. 22, 2016