July 2018 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Monticello default repositories & Iceberg

by Sean P. DeNigris

Evan Donahue wrote > I see a "default local repository" and a "local cache directory" that > point to old obsolete paths > from years ago on my machine. Could this be the result of an obsolete startup script? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

July 28, 2018

Monticello default repositories & Iceberg

by Evan Donahue

I am using Pharo Launcher. Currently, if I create a new image and go to Settings > Software Configuration > Monticello, I see a "default local repository" and a "local cache directory" that point to old obsolete paths from years ago on my machine. As a result, I'm having trouble using iceberg through metacello, because it keeps looking for baselines in these old paths and crashing. What should those paths be for Pharo launcher? Does it use one default path for all images, or is there a way to tell it to change the default cache for each new image? Thanks, Evan

July 27, 2018

Re: [Pharo-users] Tracing Method Calls

by Steven Costiou

Hi, it may not be actively maintained but Phantom has recently been ported to Pharo 6/6.1 https://github.com/InesSosa95/PHANtom You could also use Reflectivity (look for MetaLink class), which should not be hard to understand if you are familiar with aspects (although that is not aspects). For example, if you wanted to trace the receivers and parameters of a method named #mWithArg1:withArg2:withArg3: in class C, you could do : |link| link := MetaLink new. link control: #before. link arguments: #(#receiver #arguments). link metaObject: YourMetaObject. link selector: #yourMethodWithArg1:andArg:. (C lookupSelector: #mWithArg1:withArg2:withArg3:) ast link: link YourMetaObject is here an object which will receive the yourMethodWithArg1:andArg: with as arguments the receiver of the method #mWithArg1:withArg2:withArg3: and its arguments as an array. It could be a block with 2 arguments, or any other object that you would use to implement your trace behavior. You have a number of reifications available that you can pass as arguments from the context, look for subclasses of RFReification. Steven. Le 2018-07-27 17:25, Arturo Zambrano a Ã©crit : > Hi all, > I have a piece of undocumented software that I need understand ... One thing I would like to do is to have a complete trace of method calls (receivers, parameters) for certain scenarios. > As an "aspects"guy, my first idea was to use Phantom, but it seems not active anymore. > > Could someone please point me to some tools that I could use for this? (using Pharo 6, 6.1 or 7) > > Thanks in advance > > Cheers > Arturo

July 27, 2018

Re: [Pharo-users] [Pharo-dev] [ANN] Pharo Git Thermite Release

by Arturo Zambrano

This sounds great! I need to use something like this now. I will make questions ;-) and provide feedback On Tue, Jul 17, 2018 at 10:28 PM Alexandre Bergel via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > It would be fantastic that people try it out. It is easy to use, and is > really a big improvement over the tool set we use. > > And getting feedback is important. > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On Jul 17, 2018, at 11:08 AM, Ronie Salgado <roniesalg(a)gmail.com> wrote: > > Hello, > > I am finally releasing an initial public version of Pharo Git Thermite, a > tool that I am developing as part of my master thesis for visualizing > Monticello and Git commits, for Pharo and Python: > > GitHub Page with sources/documentation/issue tracker: > https://github.com/ronsaldo/pharo-git-thermite > > Short video examples: > - Monticello Visualization; https://youtu.be/02CUHBmm-K8 > - GitHub pull request: https://youtu.be/f196btLfYxM > - Local git commit: https://youtu.be/LCHTiJ4nx3g > > Feedback form: > https://docs.google.com/forms/d/e/1FAIpQLSeir6VlE3bR78oRsNAp9eHLkUn2Q016wEl… > > Best regards, > Ronie > > <thermite-visualization.png> > > >

July 27, 2018

Tracing Method Calls

by Arturo Zambrano

Hi all, I have a piece of undocumented software that I need understand ... One thing I would like to do is to have a complete trace of method calls (receivers, parameters) for certain scenarios. As an "aspects"guy, my first idea was to use Phantom, but it seems not active anymore. Could someone please point me to some tools that I could use for this? (using Pharo 6, 6.1 or 7) Thanks in advance Cheers Arturo

July 27, 2018

Re: [Pharo-users] Working with urls that contain non latin characters

by Sven Van Caekenberghe

> On 27 Jul 2018, at 15:25, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Right, but that guess is wrong (check the resulting string). Actually, the encoding used is GBK, https://en.wikipedia.org/wiki/GBK_(character_encoding) This is a variable length encoding used in China. It is not currently implemented (but could be added). But even if we implemented it, it would not solve the current issue (we would not known that we had to use it).

July 27, 2018

Re: [Pharo-users] OmniBase for Pharo 6

by marco

Peter, yes, tested windows (10) and unix/linux (32-bit). It works, green light. With the 2010 "fix" at least the garbage collection will not work on any OS. The logic tries to lock the same file twice. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

July 27, 2018

Re: [Pharo-users] Working with urls that contain non latin characters

by Sven Van Caekenberghe

> On 27 Jul 2018, at 13:58, Ben Coman <btc(a)openinworld.com> wrote: > > On 27 July 2018 at 18:39, Offray Vladimir Luna CÃ¡rdenas > <offray.luna(a)mutabit.com> wrote: >> Hi, >> >> I was ready to show a friend the Pharo web capabilities with the >> classical "myString asUrl retrieveContents", but the friend gave me a >> url that contains non Latin characters[1] and then I got an >> ZnInvalidUTF8 error. >> >> [1] >> http://www.bidchance.com/freesearch.do?&filetype=&channel=&currentpage=1&se… >> >> How can I process web addresses in Pharo that contain non latin >> characters like the one in [1]? > > Just some blind digging... > > A few levels down the stack is a call equivalent to... > x := '%BF%A6%CA%B2'. > ZnPercentEncoder new decode: x. > which fails with the same error. > > In #decode we have... > bytes := #[191 166 202 178]. Correct (as it is not legal UTF-8) > and browsing around I discovered a useful method... > encoder := ZnCharacterEncoder detectEncoding: bytes > "==> a ZnSimplifiedByteEncoder('iso88591' strict)" > > now the following works... > (ZnPercentEncoder new characterEncoder: encoder ) decode: x. Right, but that guess is wrong (check the resulting string). Since we are talking about Chinese characters that are outside the allowed range for #iso88591 (#latin1), that is logical. Clearly, the original website http://www.bidchance.com knows the encoding ... Again, to my understanding, without further context, when %BF%A6%CA%B2 is encountered in the query part of a URL, it is first percent decoded, then UTF-8 decoded. That is what #asUrl assumes, and which leads to the error since that particular sequence, when interpreted like that, does not constitute a legal UTF-8 encoding. > So maybe that helps explain it, > but I don't know how to join the dots to make it work out of the box > with "asUrl retrieveContents" > > cheers -ben

July 27, 2018

Re: [Pharo-users] Working with urls that contain non latin characters

by Ben Coman

On 27 July 2018 at 18:39, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: > Hi, > > I was ready to show a friend the Pharo web capabilities with the > classical "myString asUrl retrieveContents", but the friend gave me a > url that contains non Latin characters[1] and then I got an > ZnInvalidUTF8 error. > > [1] > http://www.bidchance.com/freesearch.do?&filetype=&channel=&currentpage=1&se… > > How can I process web addresses in Pharo that contain non latin > characters like the one in [1]? Just some blind digging... A few levels down the stack is a call equivalent to... x := '%BF%A6%CA%B2'. ZnPercentEncoder new decode: x. which fails with the same error. In #decode we have... bytes := #[191 166 202 178]. and browsing around I discovered a useful method... encoder := ZnCharacterEncoder detectEncoding: bytes "==> a ZnSimplifiedByteEncoder('iso88591' strict)" now the following works... (ZnPercentEncoder new characterEncoder: encoder ) decode: x. So maybe that helps explain it, but I don't know how to join the dots to make it work out of the box with "asUrl retrieveContents" cheers -ben

July 27, 2018

Re: [Pharo-users] Working with urls that contain non latin characters

by Sven Van Caekenberghe

Hi Offray, > On 27 Jul 2018, at 12:39, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: > > Hi, > > I was ready to show a friend the Pharo web capabilities with the > classical "myString asUrl retrieveContents", but the friend gave me a > url that contains non Latin characters[1] and then I got an > ZnInvalidUTF8 error. > > [1] > http://www.bidchance.com/freesearch.do?&filetype=&channel=&currentpage=1&se… > > How can I process web addresses in Pharo that contain non latin > characters like the one in [1]? I am on holiday, so I cannot go too deep into this, but AFAIU the URL is wrong (or it assumes a specific context with a non-standard encoding). In a URL's query part, non-ASCII data is first UTF-8 encoded, then percent encoded (this is the modern way). I don't read Chinese, so it is hard to infer much from the original site, but I am assuming the search is for 'åä»', a city called Kashgar, https://en.wikipedia.org/wiki/Kashgar_(disambiguation). The string in question can be written as (to avoid copy/paste problems): String with: 21888 asCharacter with: 20160 asCharacter. The encoding in a URL has to be: ZnPercentEncoder new encode: (String with: 21888 asCharacter with: 20160 asCharacter). This gives us for example the following URL: 'https://www.google.com/search?q=%E5%96%80%E4%BB%80' asUrl. Which parses OK and contains the correct encoded string (decoded in the URL object): 'https://www.google.com/search?q=%E5%96%80%E4%BB%80' asUrl queryAt: #q. If you copy/paste that URL in your browser it should resolve to stuff about Kashgar. Obviously the website www.bidchance.com does something else (non-standard ?). HTH, Sven > Thanks, > > Offray

July 27, 2018