June 2015 - Pharo-users - lists.pharo.org

Re: [Pharo-users] ZnClient and percent characters

by Jimmie Houchin

I am not an expert on URIs or encoding. However, this is a requirement of the API I am using and I am required to submit an encoded URI with %2C and no commas. As far as commas needing to be escaped, it seems from other sources that they should be. From https://www.ietf.org/rfc/rfc2396.txt The plus "+", dollar "$", and comma "," characters have been added to those in the "reserved" set, since they are treated as reserved within the query component. States that commas are reserved within the query component. http://stackoverflow.com/questions/8828702/why-is-the-comma-url-encoded Regardless of what is or is not required, I do need the ability to have a query string with commas encoded as %2C in order to satisfy and use the API which states. fields: Optional An URL encoded (%2C) comma separated list of instrument fields that are to be returned in the response. The instrument field will be returned regardless of the input to this query parameter. Please see the Response Parameters section below for a list of valid values. Which will look like this or something similar. fields=displayName%2Cinstrument%2Cpip Thanks. Jimmie On 06/10/2015 03:27 PM, Norbert Hartl wrote: > That's because the comma does not need to be escaped in the query part of the uri. > > Norbert > >> Am 10.06.2015 um 22:00 schrieb Jimmie Houchin <jlhouchin(a)gmail.com>: >> >> On 06/10/2015 10:32 AM, Sven Van Caekenberghe wrote: >>>> On 10 Jun 2015, at 17:24, David <stormbyte(a)gmail.com> wrote: >>>> >>>> El Wed, 10 Jun 2015 10:14:37 -0500 >>>> Jimmie Houchin <jlhouchin(a)gmail.com> >>>> escribiÃ³: >>>>> Hello, >>>>> >>>>> I am attempting to use ZnClient to request data. The request requires >>>>> a %2C (comma) delimited string as part of the query. Below is a >>>>> snippet. >>>>> >>>>> znClient >>>>> addPath: '/v1/instruments'; >>>>> queryAt: 'fields' putAll: 'displayName%2Cinstrument%2Cpip'; >>>>> get ; >>>>> contents) >>>>> >>>>> The string 'displayName%2Cinstrument%2Cpip' >>>>> is being converted to 'displayName%252Cinstrument%252Cpip' >>>>> which causes the request to fail. >>>>> >>>>> The query needs to be >>>>> fields=displayName%2Cinstrument%2Cpip >>>>> >>>>> I have not found how to do this correctly. >>>>> Any help greatly appreciated. >>>>> >>>>> Thanks. >>>>> >>>>> Jimmie >>>>> >>>>> >>>> Maybe a silly thing, but since %2C = , ... Did you tried already to >>>> make itself encode that? Like >>>> znClient >>>> addPath: '/v1/instruments'; >>>> queryAt: 'fields' putAll: 'displayName,instrument,pip'; >>>> get ; >>>> contents) >>>> >>>> I suspect it is using encoding internally, that is why % is also >>>> encoded if you try to put it. >>>> >>>> I hope that works >>> Not silly and no need to suspect, but absolutely correct ! >>> >>> Sven >> My apologies for not having full disclosure. >> >> Pharo 4, new image, freshly installed Zinc stable version. >> Xubuntu 15.04 >> >> >> >> That is what I thought would happen and what I tried first. But it is not being encoded from what I can find. >> >> Inspect this in a workspace/playground. >> >> ZnClient new >> https; >> host: 'google.com'; >> addPath: '/commaTest'; >> queryAt: 'fields' put: 'displayName,instrument,pip'; >> yourself >> >> View the request / requestLine / uri. The commas are still present in the URI. >> So I tried encoding myself and get the other error. >> >> Of course Google won't understand this and in this snippet won't receive it. >> >> And please let me know if I am doing something wrong. >> >> Any help greatly appreciated. >> >> Jimmie >> >> >> >

June 10, 2015

Re: [Pharo-users] World lastKeystroke and openInWorld: aPasteUpMorph

by Alain Plantec

> >> >> Hence, my question: Is lastKeystroke broken, or how is it meant to be used now? >> >> Second problem: In older versions of pharo this would work: >> >> f := PasteUpMorph new openInWorld. >> b := EllipseMorph new. >> b openInWorld: f. >> >> But with Pharo 3.0/4.0 the last line raises an error: >> >> MessageNotUnderstood: PasteUpMorph>>startSteppingSubmorphsOf > > also broken > another issue to open :) Quick fix to make it work: just move startSteppingSubmorphsOf: from WorldMorph to PasteUpMorph. Cheers Alain

June 10, 2015

Re: [Pharo-users] World lastKeystroke and openInWorld: aPasteUpMorph

by Alain Plantec

Hello Markus, > With older versions of pharo I was glad that my pupils could track keystrokes so easily by evaluating > > World lastKeystroke. > > With Pharo3.0/4.0 this only returns '<down>' independently of any keys I'm typing. > > f := PasteUpMorph new openInWorld. > f takeKeyBoardFocus. > f lastKeystroke. > > Is returning the empty string. this lastKeystroke suff seems broken please, open an issue > > Hence, my question: Is lastKeystroke broken, or how is it meant to be used now? > > Second problem: In older versions of pharo this would work: > > f := PasteUpMorph new openInWorld. > b := EllipseMorph new. > b openInWorld: f. > > But with Pharo 3.0/4.0 the last line raises an error: > > MessageNotUnderstood: PasteUpMorph>>startSteppingSubmorphsOf also broken another issue to open :) > > With > > f := WorldMorph new openInWorld. > b := EllipseMorph new. > b openInWorld: f. > > pharo freezes. Yes, I dont think that you can open a world in the root world. Cheers Alain > > So: How is openInWorld: meant to be used? > > Markus > >

June 10, 2015

Re: [Pharo-users] World lastKeystroke and openInWorld: aPasteUpMorph

by Johan Fabry

Hi Markus, this is probably not how it should be done, but to get the last keystroke I have been doing the following: World activeHand instVarNamed: #lastKeyScanCode If you find a cleaner way Iâd be grateful if you can share it. > On Jun 10, 2015, at 18:50, Markus Schlager <m.slg(a)gmx.de> wrote: > > Hi, > > I'm using pharo to teach smalltalk as first 'real' programming language at school. With older versions of pharo I was glad that my pupils could track keystrokes so easily by evaluating > > World lastKeystroke. > > With Pharo3.0/4.0 this only returns '<down>' independently of any keys I'm typing. > > f := PasteUpMorph new openInWorld. > f takeKeyBoardFocus. > f lastKeystroke. > > Is returning the empty string. > > Hence, my question: Is lastKeystroke broken, or how is it meant to be used now? > > Second problem: In older versions of pharo this would work: > > f := PasteUpMorph new openInWorld. > b := EllipseMorph new. > b openInWorld: f. > > But with Pharo 3.0/4.0 the last line raises an error: > > MessageNotUnderstood: PasteUpMorph>>startSteppingSubmorphsOf > > With > > f := WorldMorph new openInWorld. > b := EllipseMorph new. > b openInWorld: f. > > pharo freezes. > > So: How is openInWorld: meant to be used? > > Markus > > > ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

June 10, 2015

World lastKeystroke and openInWorld: aPasteUpMorph

by Markus Schlager

Hi, I'm using pharo to teach smalltalk as first 'real' programming language at school. With older versions of pharo I was glad that my pupils could track keystrokes so easily by evaluating World lastKeystroke. With Pharo3.0/4.0 this only returns '<down>' independently of any keys I'm typing. f := PasteUpMorph new openInWorld. f takeKeyBoardFocus. f lastKeystroke. Is returning the empty string. Hence, my question: Is lastKeystroke broken, or how is it meant to be used now? Second problem: In older versions of pharo this would work: f := PasteUpMorph new openInWorld. b := EllipseMorph new. b openInWorld: f. But with Pharo 3.0/4.0 the last line raises an error: MessageNotUnderstood: PasteUpMorph>>startSteppingSubmorphsOf With f := WorldMorph new openInWorld. b := EllipseMorph new. b openInWorld: f. pharo freezes. So: How is openInWorld: meant to be used? Markus

June 10, 2015

Re: [Pharo-users] ZnClient and percent characters

by Norbert Hartl

That's because the comma does not need to be escaped in the query part of the uri. Norbert > Am 10.06.2015 um 22:00 schrieb Jimmie Houchin <jlhouchin(a)gmail.com>: > > On 06/10/2015 10:32 AM, Sven Van Caekenberghe wrote: >>> On 10 Jun 2015, at 17:24, David <stormbyte(a)gmail.com> wrote: >>> >>> El Wed, 10 Jun 2015 10:14:37 -0500 >>> Jimmie Houchin <jlhouchin(a)gmail.com> >>> escribiÃ³: >>>> Hello, >>>> >>>> I am attempting to use ZnClient to request data. The request requires >>>> a %2C (comma) delimited string as part of the query. Below is a >>>> snippet. >>>> >>>> znClient >>>> addPath: '/v1/instruments'; >>>> queryAt: 'fields' putAll: 'displayName%2Cinstrument%2Cpip'; >>>> get ; >>>> contents) >>>> >>>> The string 'displayName%2Cinstrument%2Cpip' >>>> is being converted to 'displayName%252Cinstrument%252Cpip' >>>> which causes the request to fail. >>>> >>>> The query needs to be >>>> fields=displayName%2Cinstrument%2Cpip >>>> >>>> I have not found how to do this correctly. >>>> Any help greatly appreciated. >>>> >>>> Thanks. >>>> >>>> Jimmie >>>> >>>> >>> Maybe a silly thing, but since %2C = , ... Did you tried already to >>> make itself encode that? Like >>> znClient >>> addPath: '/v1/instruments'; >>> queryAt: 'fields' putAll: 'displayName,instrument,pip'; >>> get ; >>> contents) >>> >>> I suspect it is using encoding internally, that is why % is also >>> encoded if you try to put it. >>> >>> I hope that works >> Not silly and no need to suspect, but absolutely correct ! >> >> Sven > > My apologies for not having full disclosure. > > Pharo 4, new image, freshly installed Zinc stable version. > Xubuntu 15.04 > > > > That is what I thought would happen and what I tried first. But it is not being encoded from what I can find. > > Inspect this in a workspace/playground. > > ZnClient new > https; > host: 'google.com'; > addPath: '/commaTest'; > queryAt: 'fields' put: 'displayName,instrument,pip'; > yourself > > View the request / requestLine / uri. The commas are still present in the URI. > So I tried encoding myself and get the other error. > > Of course Google won't understand this and in this snippet won't receive it. > > And please let me know if I am doing something wrong. > > Any help greatly appreciated. > > Jimmie > > >

June 10, 2015

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

by Tudor Girba

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(a)gmail.com> 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 "Every thing has its own flow"

June 10, 2015

Re: [Pharo-users] ZnClient and percent characters

by Jimmie Houchin

On 06/10/2015 10:32 AM, Sven Van Caekenberghe wrote: >> On 10 Jun 2015, at 17:24, David <stormbyte(a)gmail.com> wrote: >> >> El Wed, 10 Jun 2015 10:14:37 -0500 >> Jimmie Houchin <jlhouchin(a)gmail.com> >> escribiÃ³: >>> Hello, >>> >>> I am attempting to use ZnClient to request data. The request requires >>> a %2C (comma) delimited string as part of the query. Below is a >>> snippet. >>> >>> znClient >>> addPath: '/v1/instruments'; >>> queryAt: 'fields' putAll: 'displayName%2Cinstrument%2Cpip'; >>> get ; >>> contents) >>> >>> The string 'displayName%2Cinstrument%2Cpip' >>> is being converted to 'displayName%252Cinstrument%252Cpip' >>> which causes the request to fail. >>> >>> The query needs to be >>> fields=displayName%2Cinstrument%2Cpip >>> >>> I have not found how to do this correctly. >>> Any help greatly appreciated. >>> >>> Thanks. >>> >>> Jimmie >>> >>> >> Maybe a silly thing, but since %2C = , ... Did you tried already to >> make itself encode that? Like >> znClient >> addPath: '/v1/instruments'; >> queryAt: 'fields' putAll: 'displayName,instrument,pip'; >> get ; >> contents) >> >> I suspect it is using encoding internally, that is why % is also >> encoded if you try to put it. >> >> I hope that works > Not silly and no need to suspect, but absolutely correct ! > > Sven My apologies for not having full disclosure. Pharo 4, new image, freshly installed Zinc stable version. Xubuntu 15.04 That is what I thought would happen and what I tried first. But it is not being encoded from what I can find. Inspect this in a workspace/playground. ZnClient new https; host: 'google.com'; addPath: '/commaTest'; queryAt: 'fields' put: 'displayName,instrument,pip'; yourself View the request / requestLine / uri. The commas are still present in the URI. So I tried encoding myself and get the other error. Of course Google won't understand this and in this snippet won't receive it. And please let me know if I am doing something wrong. Any help greatly appreciated. Jimmie

June 10, 2015

Re: [Pharo-users] ZnClient and percent characters

by Jimmie Houchin

On 06/10/2015 10:32 AM, Sven Van Caekenberghe wrote: >> On 10 Jun 2015, at 17:24, David <stormbyte(a)gmail.com> wrote: >> >> El Wed, 10 Jun 2015 10:14:37 -0500 >> Jimmie Houchin <jlhouchin(a)gmail.com> >> escribiÃ³: >>> Hello, >>> >>> I am attempting to use ZnClient to request data. The request requires >>> a %2C (comma) delimited string as part of the query. Below is a >>> snippet. >>> >>> znClient >>> addPath: '/v1/instruments'; >>> queryAt: 'fields' putAll: 'displayName%2Cinstrument%2Cpip'; >>> get ; >>> contents) >>> >>> The string 'displayName%2Cinstrument%2Cpip' >>> is being converted to 'displayName%252Cinstrument%252Cpip' >>> which causes the request to fail. >>> >>> The query needs to be >>> fields=displayName%2Cinstrument%2Cpip >>> >>> I have not found how to do this correctly. >>> Any help greatly appreciated. >>> >>> Thanks. >>> >>> Jimmie >>> >>> >> Maybe a silly thing, but since %2C = , ... Did you tried already to >> make itself encode that? Like >> znClient >> addPath: '/v1/instruments'; >> queryAt: 'fields' putAll: 'displayName,instrument,pip'; >> get ; >> contents) >> >> I suspect it is using encoding internally, that is why % is also >> encoded if you try to put it. >> >> I hope that works > Not silly and no need to suspect, but absolutely correct ! > > Sven That is what I thought would happen and what I tried first. But it is not being encoded from what I can find. Inspect this in a workspace/playground. ZnClient new https; host: 'google.com'; addPath: '/commaTest'; queryAt: 'fields' put: 'displayName,instrument,pip'; yourself View the request / requestLine / uri. The commas are still present in the URI. So I tried encoding myself and get the other error. Of course Google won't understand this and in this snippet won't receive it. And please let me know if I am doing something wrong. Any help greatly appreciated. Jimmie

June 10, 2015

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

by Paul DeBruicker

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.

June 10, 2015