February 2016 - Pharo-users

Re: [Pharo-users] GSOC 2016 we are done

by Jigyasa Grover

Good Luck -- View this message in context: http://forum.world.st/GSOC-2016-we-are-done-tp4879057p4879159.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 20, 2016

REEF examples

by recursive68＠gmail.com

Hi, I'm trying to use REEF but can only find a few limited examples which aren't helping really. Does anyone know for example how I would update a RETextField value when a REButton is clicked ? I found this example someone answered to a the query I had but it doesn't work: REForm subclass: #MyForm instanceVariableNames: 'textFieldContents' classVariableNames: '' poolDictionaries: '' category: 'ReefSample1-View'. textFieldContents ^textFieldContents textFieldContents: aString textFieldContents := aString initializeContents self add: (RETextField new on: #textFieldContents of: self). self add: (REButton new label: 'Try me!'; callback: [ self triggerThenDo: [ self inform: self textFieldContents ]]). All it does is generate a dialog box when the button is clicked. I don't know if inform: has usage since that was written. Thanks

Feb. 19, 2016

Re: [Pharo-users] GSOC 2016 we are done

by Tudor Girba

Amazing work! Thank you, Doru > On Feb 19, 2016, at 8:05 PM, Serge Stinckwich <Serge.Stinckwich(a)gmail.com> wrote: > > Dear all, > > the GSOC website is close now. Thank to the incredible work of Peter and Uko, > we were able to submitting our application for GSOC 2016. > Thank you all the people who provide insights and advices for the application. > > You can still update the topics list by providing pull requests on github: > https://github.com/pharo-project/pharo-project-proposals/blob/master/Topics… > > The 2016 Mentor Organizations will be announced on February 29, 2016 > on Google website: https://summerofcode.withgoogle.com/ > > Thank you. > Regards, > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ > -- www.tudorgirba.com www.feenk.com "The coherence of a trip is given by the clearness of the goal."

Feb. 19, 2016

GSOC 2016 we are done

by Serge Stinckwich

Dear all, the GSOC website is close now. Thank to the incredible work of Peter and Uko, we were able to submitting our application for GSOC 2016. Thank you all the people who provide insights and advices for the application. You can still update the topics list by providing pull requests on github: https://github.com/pharo-project/pharo-project-proposals/blob/master/Topics… The 2016 Mentor Organizations will be announced on February 29, 2016 on Google website: https://summerofcode.withgoogle.com/ Thank you. Regards, -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Feb. 19, 2016

Re: [Pharo-users] Using GTSpotter how do I find an implementor of #accept ?

by Paul DeBruicker

+1 At this point I just keep a Workspace open to type what I'm looking for in and hit cmd+m or n or N or B. Instead of shift+end I hit opt+tab to find the Workspace. Not as convenient as shift+Enter but the problems in outlined in this message are gone. Its probably possible to remap shift+enter to open/surface the Workspace for me. I don't use a Playground for that because there is something weird sometimes when text is highlighted and deleted. You can find yourself in a situation where there is a one char wide space highlighted and everything you type goes into that space. I like to think I've always understood Doru's point that Spotter is a tool for finding objects. The code lookup/open browser functionality is secondary to the designed intent. stepharo wrote > I still do not get why a tool like spotter does not focus first one > working on the key scenarios we all want: > - sender > - implementor > - open a class > - class refs > > Because this is what we do 95% of the time. > > Le 11/6/15 09:38, Nicolai Hess a Ã©crit : >> >> >> 2015-06-11 7:05 GMT+02:00 Paul DeBruicker < > pdebruic@ > > > <mailto: > pdebruic@ > >>: >> >> Hi Doru, >> >> By "the old version of Spotter" I meant whatever was in Pharo 3 >> that would >> produce a list of search results with exact matches at the top >> when I'd hit >> shift+enter and then type e.g. 'accept.' Sorry to have said >> "Pharo 4" & >> been unnecessarily confusing. >> >> >> I miss spotlight for this fast accurate search too. >> It is much easier to type a message (like accept) and hit enter and >> you get a MessageList/Browser with that result. >> Instead, in spotter, you have to >> - scroll through the list of all other search results (like classes) >> - dive in the list of all implementors >> - scroll again >> and no easy way to open a message list with all implementors. >> >> But: >> It is MUCH easier to configure or extent Spotter >> (if you understand the badly documented concepts behind). >> >> Spotter is not a perfect replacement for Spotlight, but spotlight >> wasn't perfect/accurate too. >> For example, search for String and you got all possible classes or >> methods with String in its name but NOT the class String itself, >> (not even if you scroll down, because the search result includes >> only 100 entries). >> There are often symbols in the resultlist that aren't messages >> at all and if you select that result you get >> "There are no imiplementors of ..." this annoyed me a lot. >> I fixed some of the problems with spotlight but doing this >> for spottter is much cleaner and easier. >> >> >> >> I'm just going to use 'accept' for this example but why show the >> mixed list >> of 637 implementors of accept* and not lead with "accept". Why was >> it >> decided that inexact matches to the typed input be privileged >> above exact >> matches in the new tool? Is it a bad Levenshtein distance >> algorithm or >> something? >> >> >> "Why was it decided that ..." >> no decision, it was implemented successive to catch up with old >> spotlight. >> missing features were added afterwards (like search for globals and >> class vars) >> any missing feauter ? -> open an issue ( and or contribute a fix) >> >> >> >> >> Thanks for helping me figure it out >> >> >> Paul >> >> >> >> >> >> Tudor Girba-2 wrote >> > Hi, >> > >> > What do you mean by the old version of Spotter? >> > >> > Just in case: you should know that Spotter is made to be >> extensible. This >> > means that if you want to play with your own way of searching >> for objects, >> > you can just do it. Let me know if you to try and if you need >> help in this >> > direction. >> > >> > Cheers, >> > Doru >> > >> > >> > >> > On Wed, Jun 10, 2015 at 9:10 PM, Paul DeBruicker < >> >> > pdebruic@ >> >> > > wrote: >> > >> >> >> >> Is there any way to change back to the old version of Spotter >> in Pharo 4? >> >> >> >> >> >> >> >> >> >> >> >> Nicolai Hess wrote >> >> > 2015-06-10 16:24 GMT+02:00 Paul DeBruicker < >> >> >> >> > pdebruic@ >> >> >> >> > >: >> >> > >> >> >> So by default the search tool is only guaranteed to return >> an exact >> >> term >> >> >> match if there are only less than 5 non-exact match results? >> >> >> >> >> >> >> >> > Yes >> >> > >> >> > >> >> > >> >> > >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> Nicolai Hess wrote >> >> >> > 2015-06-10 7:39 GMT+02:00 Paul DeBruicker < >> >> >> >> >> >> > pdebruic@ >> >> >> >> >> >> > >: >> >> >> > >> >> >> >> when I hit shift+enter and type 'accept' I get things >> that are not >> >> >> >> #accept, e.g. #accept: and AbstractAcceptor. >> >> >> >> >> >> >> >> If I add a space after accept it doesn't help. >> >> >> >> >> >> >> >> >> >> >> >> What do I not understand? >> >> >> >> >> >> >> > >> >> >> > the result list is not sorted and the result list is built >> by all >> >> >> methods >> >> >> > having the query string as part >> >> >> > of its selector name. >> >> >> > >> >> >> > Yes this can be improved and it is not difficult, for >> example you >> >> can >> >> >> add >> >> >> > this method to >> >> >> > >> >> >> > GTFilterImplementor>>applyFilterWithQuery >> >> >> > super applyFilterWithQuery. >> >> >> > items sort: [ :a :b | (self itemFilterNameFor: a) size >> < (self >> >> >> > itemFilterNameFor: b) size ] >> >> >> > >> >> >> > this will sort the result list by the size of the selector >> name. So, >> >> if >> >> >> > there is a perfect match, >> >> >> > it will be listed first. >> >> >> > (BUT only in the implementors category if you "dive-in", >> not in the >> >> >> > 5-elements-result-preview-list). >> >> >> > >> >> >> > Maybe there is a better way without sorting. (We can modify >> >> >> > applyFilterWithQuery for the implementors >> >> >> > filter, to put perfect matches at the begining of the list). >> >> >> > >> >> >> > But all this is not easy to discover. Spotter classes make >> some >> >> heavy >> >> >> use >> >> >> > of delegation, many operations >> >> >> > are split and delgated to subclasses (GOOD!) >> >> >> > many classes aren't documented (BAD!) and this makes it >> really >> >> >> difficult >> >> >> > to >> >> >> > catch how all this is supposed to work together. >> >> >> > >> >> >> > >> >> >> > nicolai >> >> >> > >> >> >> > >> >> >> > >> >> >> > >> >> >> >> >> >> >> >> >> >> >> >> Thanks >> >> >> >> >> >> >> >> >> >> >> >> Paul >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> View this message in context: >> >> >> >> >> >> >> http://forum.world.st/Using-GTSpotter-how-do-I-find-an-implementor-of-accep… >> >> >> Sent from the Pharo Smalltalk Users mailing list archive at >> >> Nabble.com. >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> View this message in context: >> >> >> >> http://forum.world.st/Using-GTSpotter-how-do-I-find-an-implementor-of-accep… >> >> Sent from the Pharo Smalltalk Users mailing list archive at >> Nabble.com. >> >> >> >> >> > >> > >> > -- >> > www.tudorgirba.com <http://www.tudorgirba.com> >> > >> > "Every thing has its own flow" >> >> >> >> >> >> -- >> View this message in context: >> >> http://forum.world.st/Using-GTSpotter-how-do-I-find-an-implementor-of-accep… >> Sent from the Pharo Smalltalk Users mailing list archive at >> Nabble.com. >> >> -- View this message in context: http://forum.world.st/Using-GTSpotter-how-do-I-find-an-implementor-of-accep… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 19, 2016

Re: [Pharo-users] Using GTSpotter how do I find an implementor of #accept ?

by Peter UhnÃ¡k

On Fri, Feb 19, 2016 at 5:38 PM, stepharo <stepharo(a)free.fr> wrote: > I still do not get why a tool like spotter does not focus first one > working on the key scenarios we all want: > - sender > - implementor > - open a class > - class refs > > Because this is what we do 95% of the time. > Spotter has statistics so it would be interesting what they say, because for me the key scenarios is: * find a method/implementor * find a class Finding senders or class refs is so much easier from Nautilusâ¦ just a keypress and no need to type name.

Feb. 19, 2016

Re: [Pharo-users] Using GTSpotter how do I find an implementor of #accept ?

by stepharo

I still do not get why a tool like spotter does not focus first one working on the key scenarios we all want: - sender - implementor - open a class - class refs Because this is what we do 95% of the time. Le 11/6/15 09:38, Nicolai Hess a Ã©crit : > > > 2015-06-11 7:05 GMT+02:00 Paul DeBruicker <pdebruic(a)gmail.com > <mailto:pdebruic@gmail.com>>: > > Hi Doru, > > By "the old version of Spotter" I meant whatever was in Pharo 3 > that would > produce a list of search results with exact matches at the top > when I'd hit > shift+enter and then type e.g. 'accept.' Sorry to have said > "Pharo 4" & > been unnecessarily confusing. > > > I miss spotlight for this fast accurate search too. > It is much easier to type a message (like accept) and hit enter and > you get a MessageList/Browser with that result. > Instead, in spotter, you have to > - scroll through the list of all other search results (like classes) > - dive in the list of all implementors > - scroll again > and no easy way to open a message list with all implementors. > > But: > It is MUCH easier to configure or extent Spotter > (if you understand the badly documented concepts behind). > > Spotter is not a perfect replacement for Spotlight, but spotlight > wasn't perfect/accurate too. > For example, search for String and you got all possible classes or > methods with String in its name but NOT the class String itself, > (not even if you scroll down, because the search result includes > only 100 entries). > There are often symbols in the resultlist that aren't messages > at all and if you select that result you get > "There are no imiplementors of ..." this annoyed me a lot. > I fixed some of the problems with spotlight but doing this > for spottter is much cleaner and easier. > > > > I'm just going to use 'accept' for this example but why show the > mixed list > of 637 implementors of accept* and not lead with "accept". Why was it > decided that inexact matches to the typed input be privileged > above exact > matches in the new tool? Is it a bad Levenshtein distance > algorithm or > something? > > > "Why was it decided that ..." > no decision, it was implemented successive to catch up with old spotlight. > missing features were added afterwards (like search for globals and > class vars) > any missing feauter ? -> open an issue ( and or contribute a fix) > > > > > Thanks for helping me figure it out > > > Paul > > > > > > Tudor Girba-2 wrote > > Hi, > > > > What do you mean by the old version of Spotter? > > > > Just in case: you should know that Spotter is made to be > extensible. This > > means that if you want to play with your own way of searching > for objects, > > you can just do it. Let me know if you to try and if you need > help in this > > direction. > > > > Cheers, > > Doru > > > > > > > > On Wed, Jun 10, 2015 at 9:10 PM, Paul DeBruicker < > > > pdebruic@ > > > > wrote: > > > >> > >> Is there any way to change back to the old version of Spotter > in Pharo 4? > >> > >> > >> > >> > >> > >> Nicolai Hess wrote > >> > 2015-06-10 16:24 GMT+02:00 Paul DeBruicker < > >> > >> > pdebruic@ > >> > >> > >: > >> > > >> >> So by default the search tool is only guaranteed to return > an exact > >> term > >> >> match if there are only less than 5 non-exact match results? > >> >> > >> >> > >> > Yes > >> > > >> > > >> > > >> > > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> Nicolai Hess wrote > >> >> > 2015-06-10 7:39 GMT+02:00 Paul DeBruicker < > >> >> > >> >> > pdebruic@ > >> >> > >> >> > >: > >> >> > > >> >> >> when I hit shift+enter and type 'accept' I get things > that are not > >> >> >> #accept, e.g. #accept: and AbstractAcceptor. > >> >> >> > >> >> >> If I add a space after accept it doesn't help. > >> >> >> > >> >> >> > >> >> >> What do I not understand? > >> >> >> > >> >> > > >> >> > the result list is not sorted and the result list is built > by all > >> >> methods > >> >> > having the query string as part > >> >> > of its selector name. > >> >> > > >> >> > Yes this can be improved and it is not difficult, for > example you > >> can > >> >> add > >> >> > this method to > >> >> > > >> >> > GTFilterImplementor>>applyFilterWithQuery > >> >> > super applyFilterWithQuery. > >> >> > items sort: [ :a :b | (self itemFilterNameFor: a) size > < (self > >> >> > itemFilterNameFor: b) size ] > >> >> > > >> >> > this will sort the result list by the size of the selector > name. So, > >> if > >> >> > there is a perfect match, > >> >> > it will be listed first. > >> >> > (BUT only in the implementors category if you "dive-in", > not in the > >> >> > 5-elements-result-preview-list). > >> >> > > >> >> > Maybe there is a better way without sorting. (We can modify > >> >> > applyFilterWithQuery for the implementors > >> >> > filter, to put perfect matches at the begining of the list). > >> >> > > >> >> > But all this is not easy to discover. Spotter classes make > some > >> heavy > >> >> use > >> >> > of delegation, many operations > >> >> > are split and delgated to subclasses (GOOD!) > >> >> > many classes aren't documented (BAD!) and this makes it really > >> >> difficult > >> >> > to > >> >> > catch how all this is supposed to work together. > >> >> > > >> >> > > >> >> > nicolai > >> >> > > >> >> > > >> >> > > >> >> > > >> >> >> > >> >> >> > >> >> >> Thanks > >> >> >> > >> >> >> > >> >> >> Paul > >> >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > >> >> -- > >> >> View this message in context: > >> >> > >> > http://forum.world.st/Using-GTSpotter-how-do-I-find-an-implementor-of-accep… > >> >> Sent from the Pharo Smalltalk Users mailing list archive at > >> Nabble.com. > >> >> > >> >> > >> > >> > >> > >> > >> > >> -- > >> View this message in context: > >> > http://forum.world.st/Using-GTSpotter-how-do-I-find-an-implementor-of-accep… > >> Sent from the Pharo Smalltalk Users mailing list archive at > Nabble.com. > >> > >> > > > > > > -- > > www.tudorgirba.com <http://www.tudorgirba.com> > > > > "Every thing has its own flow" > > > > > > -- > View this message in context: > http://forum.world.st/Using-GTSpotter-how-do-I-find-an-implementor-of-accep… > Sent from the Pharo Smalltalk Users mailing list archive at > Nabble.com. > >

Feb. 19, 2016

Re: [Pharo-users] Line end convention in method source

by Norbert Hartl

I didn't think about danger because it is a short term hack that will go away soon. I was just wondering because I think it is a bug. I now compile storeString into the method which generates an ordered collection. Norbert > Am 19.02.2016 um 10:46 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > But I think it is a bit dangerous to rely on a specific EOL convention being maintained in method source code. Although I agree that it should not touch the contents of constants. > > You could do something (inefficient) like > > ^ String lf join: 'one > two > three' lines > > I've done this before (to get CRLF). > >> On 19 Feb 2016, at 10:32, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> Hi, >> >> This is strangeâ¦ do you have a way to re-create it? >> >> it looks like a bug (or a non-wanted side effect) to me... >>> On 17 Feb 2016, at 09:56, Norbert Hartl <norbert(a)hartl.name> wrote: >>> >>> I had a strange effect using a method as storage. I had a list of strings that I compiled into a method. The strings were delimited by Character lf. I created this on a Mac. Saving the source and opening the same code on a linux machine changed the line endings from lf to cr. >>> IMHO this is a bug because I think that the content of a method should be unchanged in that case. Or are there any other reasons why this is the way it is? >>> >>> thanks, >>> >>> Norbert >>> >>> >> >> > >

Feb. 19, 2016

Re: [Pharo-users] Line end convention in method source

by Peter UhnÃ¡k

Or be platform-independent and store it in an array, and retrieve on demand? MyStorage>>strings ^ #('string1' 'string2' 'string3' ...) MyStorage>>stringsSeparated ^ self stringsSeparatedBy: String lf MyStorage>>stringsSeparatedBy: aSeparator ^ self string joinUsing: aSeparator On Fri, Feb 19, 2016 at 10:46 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > But I think it is a bit dangerous to rely on a specific EOL convention > being maintained in method source code. Although I agree that it should not > touch the contents of constants. > > You could do something (inefficient) like > > ^ String lf join: 'one > two > three' lines > > I've done this before (to get CRLF). > > > On 19 Feb 2016, at 10:32, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > > Hi, > > > > This is strangeâ¦ do you have a way to re-create it? > > > > it looks like a bug (or a non-wanted side effect) to me... > >> On 17 Feb 2016, at 09:56, Norbert Hartl <norbert(a)hartl.name> wrote: > >> > >> I had a strange effect using a method as storage. I had a list of > strings that I compiled into a method. The strings were delimited by > Character lf. I created this on a Mac. Saving the source and opening the > same code on a linux machine changed the line endings from lf to cr. > >> IMHO this is a bug because I think that the content of a method should > be unchanged in that case. Or are there any other reasons why this is the > way it is? > >> > >> thanks, > >> > >> Norbert > >> > >> > > > > > > >

Feb. 19, 2016

Re: [Pharo-users] Line end convention in method source

by Sven Van Caekenberghe

But I think it is a bit dangerous to rely on a specific EOL convention being maintained in method source code. Although I agree that it should not touch the contents of constants. You could do something (inefficient) like ^ String lf join: 'one two three' lines I've done this before (to get CRLF). > On 19 Feb 2016, at 10:32, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > This is strangeâ¦ do you have a way to re-create it? > > it looks like a bug (or a non-wanted side effect) to me... >> On 17 Feb 2016, at 09:56, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> I had a strange effect using a method as storage. I had a list of strings that I compiled into a method. The strings were delimited by Character lf. I created this on a Mac. Saving the source and opening the same code on a linux machine changed the line endings from lf to cr. >> IMHO this is a bug because I think that the content of a method should be unchanged in that case. Or are there any other reasons why this is the way it is? >> >> thanks, >> >> Norbert >> >> > >

Feb. 19, 2016