[Pharo-users] Playground doesn't respect LF endings

Hi, when I paste a text into the playground with line endings containing just LF (unix-style), then navigation to beginning/end of a line instead jumps to the beginning/end of the text. (I guess it is hardcoded to CR only). Right now I have to execute `Clipboard clipboardText

Re: [Pharo-users] gtInspector override default select behavior

Perfect. Do you know if these methods are systematically documented anywhere? I feel like if I understood Glamour better these things might be more obvious, but I can never manage to infer the gtInspector calls from the Glamour docs. Thanks. -- View this message in context:

Re: [Pharo-users] Best Practices for Bundling Documentation

Ok, thanks. -- View this message in context: http://forum.world.st/Best-Practices-for-Bundling-Documentation-tp4958788p4959139.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Re: [Pharo-users] Problem with ThreadPool on os windows - no execution

Hi Sabine, There shouldn't be any differences between the platforms. Maybe I broke something in the update recently where I make the pool start/stop based on whether it has any jobs. You could try the older version that starts the pool on startup and report back if it works or not. Seems

Re: [Pharo-users] Best Practices for Bundling Documentation

Gracias, pronto lo reviso. -- View this message in context: http://forum.world.st/Best-Practices-for-Bundling-Documentation-tp4958788p4959140.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

[Pharo-users] Fetching https site content with Zinc

Hi there, I am trying to automate the fetching of a site content in Pharo. Basically, I want to fetch smart contract information from Etherscan. Here is an example URL: https://etherscan.io/address/0xbcff2d15c698d3874bc29aa170c89fd7a6146a4b#code I tried to use Zinc to fetch that, here is my code

Re: [Pharo-users] Fetching https site content with Zinc

Hi, Probably, the hashbang (#code) is causing the front end proxy to respond with a 400 error. It works if you do: ZnEasy get: 'https://etherscan.io/address/0xbcff2d15c698d3874bc29aa170c89fd7a6146a4b' However, I think there might be an specify REST API to get the Solidity code of that

Re: [Pharo-users] sharing context/variables between multiple playgrounds

I mentioned this a while back 2, less between different playground windows, but more when you drill down on a value in a playground and then want to use a value on the first pane. There was some discussion about this (Denis had some good ideas), and it seemed like a good idea but something to

Re: [Pharo-users] sharing context/variables between multiple playgrounds

In that cases I simply make them global. -- Pavel 2017-08-07 10:16 GMT+02:00 Peter Uhnak : > Hi, > > is there a way to share context/variables between multiple playgrounds? > > E.g. in Playground window 1 I declare > > ``` > factor := 70. > ``` > > and in Playground window 2

Re: [Pharo-users] gtInspector override default select behavior

Hi, On Mon, Aug 7, 2017 at 5:28 AM, Evan Donahue wrote: > Hello, > > I have a gtInspector extension a tree-structured object. By default, when > I click on one of the objects in the gtInspector, the inspector opens up > another inspector on that node (using the finder-style

[Pharo-users] sharing context/variables between multiple playgrounds

Hi, is there a way to share context/variables between multiple playgrounds? E.g. in Playground window 1 I declare ``` factor := 70. ``` and in Playground window 2 I do (without declaring `factor`) ``` 5 * factor. "-> 350" ``` Thanks, Peter

Re: [Pharo-users] Lazy-initialization patterns

Esteban A. Maringolo wrote > 2017-08-05 19:21 GMT-03:00 Peter Uhnak > i.uhnak@ > : > >> If I want to initialize the value in a separate method (typically for >> testing or reuse), then I prefer to avoid state mutation there and >> instead I return the result. >> >> MyClass>>#property >>

Re: [Pharo-users] sharing context/variables between multiple playgrounds

Hi, I have been thinking in a similar problem for Grafoscopio. In that way, we could have the same persistence among playgrounds in a similar way to Jupyter's persistence among code cells. My bet would be on using the playground bindings that you get when it is executed. In Grafoscopio's case,

Re: [Pharo-users] Lazy-initialization patterns

> On 7 Aug 2017, at 10:50, Henrik Sperre Johansen > wrote: > >>> MyClass>>#property >>>^ property ifNil: [ property := self createNewProperty ] >>> >>> MyClass>>createNewProperty >>>"I won't touch property instance variable here, just create a new