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

Re: [Pharo-users] Pharo6 playground saving semantics and .changes?

by Offray Vladimir Luna CÃ¡rdenas

Hi, Tim, I have made a project, called Grafoscopio, that, in its core, is about saving playgrounds and embed them into bigger context/narratives. You can see more details and examples here: [1] http://mutabit.com/grafoscopio/index.en.html Still needs work to do, for example improving English documentation and discoverability, as Glenn suggested (Spanish page is better ranked in search engines), but maybe you find it interesting for what you're looking for. See the page at [1] and the examples, to see what is possible at the moment. Cheers, Offray Ps: I share Esteban's concern on privacy and autosave feature, despite of being useful, sometimes, for me and in the workshops. This behavior should be disabled by default and turn on on user demand. (Maybe a tool tip on first launch, like the one on anonymous metrics could help here too). On 29/06/17 15:55, Esteban A. Maringolo wrote: > Please allow me a little rant here... > > I still find disturbing the"autosave" feature without having the > option to explicitly save the contents in the filesystem as I did with > Workspaces. Sometimes I don't want the contents of a file/tab updated > by a criteria different than when to save the image, it is: my own > when I consider appropriate. > > It's not I want to disable Playground by complete which I find useful > when integrated with the inlined insector, but I want to keep the > behavior of saving and restoring the contents under my control. > > Privacywise I don't like the "history" of previous contents in the > Playground, the history it can be removed but it can't be disabled. I > can condense the changes file, but the Playground history remains. > > Regards! > > > Esteban A. Maringolo > > > 2017-06-29 17:12 GMT-03:00 Tim Mackinnon <tim(a)testit.works>: >> Cool - I was missing that insight. >> >> Tim >> >> Sent from my iPhone >> >>> On 29 Jun 2017, at 18:04, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>> One of the more hidden Playground features are named Pages. Double-click the page tab title and give it a name, it will then be saved automagically in pharo-local/play-stash (and auto saves on changes from then on). I use that all the time. >>> >>>> On 29 Jun 2017, at 16:45, Tim Mackinnon <tim(a)testit.works> wrote: >>>> >>>> Hi - I really like the playground metaphor, it really is such a nice way to experiment. >>>> >>>> However I've noticed that unlike older versions of Smalltalk, it seems that DoIt operations in playground don't end up in the .changes file anymore (which I guess is a mixed blessing when you want to recover). It seems that the new metaphor is that work you do is saved as a page and you can see versions of your page in the upper right menu? Well sort of - as I haven't quite understood when it saves or doesn't? Often I get duplicate looking pages in that menu and often I make a change and want to keep it but find it doesn't save and if I accidentally close my playground my changes in a page are lost? >>>> >>>> What are the semantics of page saving? >>>> >>>> An example - if you do a few gofer loads of utilities and the put a comment on the first line of the page (which gives it a nice title in the page dropdown), sometimes that comment will be saved other times not? >>>> >>>> I also think it might be nice to remove page versions to help tidy things up. I'm thinking of rolling my sleeves up on this idea - but wanted to understand the vision firsts >>>> >>>> Tim >>>> >>>> Sent from my iPhone >>>> >>>> >>>> Sent from my iPhone >>>> >>> >> >

June 29, 2017

Solved: ZdcPluginMissing: SSL/TLS plugin initailization failed (VM plugin missing ? OS libraries missing ?)

by Offray Vladimir Luna CÃ¡rdenas

Hi, Thanks Sven. This solves the problem. The issue was the 32 bit library. I don't know if this should be added as some kind of annotation or footnode to [1], because the chapter suposse a 32-bit Ubuntu Gnu/Linux deployment, but some of us are going to try similar stuff in similar environment, forgetting to install the 32 bits libraries. Anyway, if there is any room for this, I would be happy to make the edition with the respective pull request. [1] https://github.com/SquareBracketAssociates/EnterprisePharo/blob/master/WebA… Cheers, Offray Ps: Sorry to open a new thread. My mail was having some issues and didn't get updated threads.

June 29, 2017

Re: [Pharo-users] Pharo6 playground saving semantics and .changes?

by Esteban A. Maringolo

Please allow me a little rant here... I still find disturbing the"autosave" feature without having the option to explicitly save the contents in the filesystem as I did with Workspaces. Sometimes I don't want the contents of a file/tab updated by a criteria different than when to save the image, it is: my own when I consider appropriate. It's not I want to disable Playground by complete which I find useful when integrated with the inlined insector, but I want to keep the behavior of saving and restoring the contents under my control. Privacywise I don't like the "history" of previous contents in the Playground, the history it can be removed but it can't be disabled. I can condense the changes file, but the Playground history remains. Regards! Esteban A. Maringolo 2017-06-29 17:12 GMT-03:00 Tim Mackinnon <tim(a)testit.works>: > Cool - I was missing that insight. > > Tim > > Sent from my iPhone > >> On 29 Jun 2017, at 18:04, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> One of the more hidden Playground features are named Pages. Double-click the page tab title and give it a name, it will then be saved automagically in pharo-local/play-stash (and auto saves on changes from then on). I use that all the time. >> >>> On 29 Jun 2017, at 16:45, Tim Mackinnon <tim(a)testit.works> wrote: >>> >>> Hi - I really like the playground metaphor, it really is such a nice way to experiment. >>> >>> However I've noticed that unlike older versions of Smalltalk, it seems that DoIt operations in playground don't end up in the .changes file anymore (which I guess is a mixed blessing when you want to recover). It seems that the new metaphor is that work you do is saved as a page and you can see versions of your page in the upper right menu? Well sort of - as I haven't quite understood when it saves or doesn't? Often I get duplicate looking pages in that menu and often I make a change and want to keep it but find it doesn't save and if I accidentally close my playground my changes in a page are lost? >>> >>> What are the semantics of page saving? >>> >>> An example - if you do a few gofer loads of utilities and the put a comment on the first line of the page (which gives it a nice title in the page dropdown), sometimes that comment will be saved other times not? >>> >>> I also think it might be nice to remove page versions to help tidy things up. I'm thinking of rolling my sleeves up on this idea - but wanted to understand the vision firsts >>> >>> Tim >>> >>> Sent from my iPhone >>> >>> >>> Sent from my iPhone >>> >> >> > >

June 29, 2017

Re: [Pharo-users] Pharo6 playground saving semantics and .changes?

by Tim Mackinnon

Cool - I was missing that insight. Tim Sent from my iPhone > On 29 Jun 2017, at 18:04, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > One of the more hidden Playground features are named Pages. Double-click the page tab title and give it a name, it will then be saved automagically in pharo-local/play-stash (and auto saves on changes from then on). I use that all the time. > >> On 29 Jun 2017, at 16:45, Tim Mackinnon <tim(a)testit.works> wrote: >> >> Hi - I really like the playground metaphor, it really is such a nice way to experiment. >> >> However I've noticed that unlike older versions of Smalltalk, it seems that DoIt operations in playground don't end up in the .changes file anymore (which I guess is a mixed blessing when you want to recover). It seems that the new metaphor is that work you do is saved as a page and you can see versions of your page in the upper right menu? Well sort of - as I haven't quite understood when it saves or doesn't? Often I get duplicate looking pages in that menu and often I make a change and want to keep it but find it doesn't save and if I accidentally close my playground my changes in a page are lost? >> >> What are the semantics of page saving? >> >> An example - if you do a few gofer loads of utilities and the put a comment on the first line of the page (which gives it a nice title in the page dropdown), sometimes that comment will be saved other times not? >> >> I also think it might be nice to remove page versions to help tidy things up. I'm thinking of rolling my sleeves up on this idea - but wanted to understand the vision firsts >> >> Tim >> >> Sent from my iPhone >> >> >> Sent from my iPhone >> > >

June 29, 2017

[ANN] An evening with Pharo and the ESP32 microcontroller

by Ben Coman

Nothing too dramatic, but for a hardware hackathon I'm attending I wanted some online material I could expose to people to who hadn't heard of Pharo before. Maybe some Pharo regulars might also find it of interest. All comments welcome. http://blog.openinworld.com/2017/06/evening-with-pharo-esp32/ cheers -ben

June 29, 2017

Re: [Pharo-users] Question about writeStream

by Guillermo Polito

In fact the question comes from the fact that they are not polymorphic and you should know if you're manipulating a closable stream or not... Maybe a solution is indeed to use #writeStreamDo:, that should behave well even for in-memory, collection streams, no? On Thu, Jun 29, 2017 at 4:58 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > On 29 Jun 2017, at 16:07, JÃ©rÃ©mie Regnault <jeremie.regnault(a)outlook.com> > wrote: > > > > Hi, > > > > I am writing tests with streams, and I noticed that a stream opened on a > > string doesn't close, but FileStreams do close. Is it normal ? > > How do you mean that ? That FileStreams close automatically ? > > That is indeed the case, that they are closed as a finalization action > (i.e. when they become garbage), but that I consider that a fail safe > thing, not something you should rely on. They should be properly closed, > like #readStreamDo: and #writeStreamDo: do. > > Streams over collections such as Strings do not need closing, as there is > no opening either. But general stream code better does. > > > -- > > JÃ©rÃ©mie Regnault > > > > > -- Guille Polito Research Engineer French National Center for Scientific Research - *http://www.cnrs.fr* <http://www.cnrs.fr> *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

June 29, 2017

Re: [Pharo-users] Pharo on the SqueakJS virtual machine

by Pavel Krivanek

If I understand it well, for a local copy we need: clone repository: git clone git@github.com:ccrraaiigg/ccrraaiigg.github.io.git inside the clone to run a webserver, e.g.: python -m SimpleHTTPServer 9090 then go to: http://localhost:9090/pharo/squeakjspharo.html -- Pavel 2017-06-29 18:56 GMT+02:00 Craig Latta <craig(a)blackpagedigital.com>: > > Well, that didn't take as long as I thought. :) Probably due to > progress Bert made since we looked at it at ESUG 2016. > > For more details, see https://tinyurl.com/y727fz4a > (thiscontext.com) Let the bugfixing begin. :) > > > thanks again, > > -C > > -- > Craig Latta > Black Page Digital > Amsterdam :: San Francisco > craig(a)blackpagedigital.com > +31 6 2757 7177 (SMS ok) > + 1 415 287 3547 (no SMS) > >

June 29, 2017

Re: [Pharo-users] Pharo on the SqueakJS virtual machine

by Sven Van Caekenberghe

> On 29 Jun 2017, at 19:14, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > WOW!!! +10 > Thank you all very much for this effort. > > -- Pavel > > > > 2017-06-29 18:56 GMT+02:00 Craig Latta <craig(a)blackpagedigital.com>: > > Well, that didn't take as long as I thought. :) Probably due to > progress Bert made since we looked at it at ESUG 2016. > > For more details, see https://tinyurl.com/y727fz4a > (thiscontext.com) Let the bugfixing begin. :) > > > thanks again, > > -C > > -- > Craig Latta > Black Page Digital > Amsterdam :: San Francisco > craig(a)blackpagedigital.com > +31 6 2757 7177 (SMS ok) > + 1 415 287 3547 (no SMS) > >

June 29, 2017

Re: [Pharo-users] Pharo on the SqueakJS virtual machine

by Pavel Krivanek

WOW!!! Thank you all very much for this effort. -- Pavel 2017-06-29 18:56 GMT+02:00 Craig Latta <craig(a)blackpagedigital.com>: > > Well, that didn't take as long as I thought. :) Probably due to > progress Bert made since we looked at it at ESUG 2016. > > For more details, see https://tinyurl.com/y727fz4a > (thiscontext.com) Let the bugfixing begin. :) > > > thanks again, > > -C > > -- > Craig Latta > Black Page Digital > Amsterdam :: San Francisco > craig(a)blackpagedigital.com > +31 6 2757 7177 (SMS ok) > + 1 415 287 3547 (no SMS) > >

June 29, 2017

Re: [Pharo-users] Pharo on the SqueakJS virtual machine

by Craig Latta

Well, that didn't take as long as I thought. :) Probably due to progress Bert made since we looked at it at ESUG 2016. For more details, see https://tinyurl.com/y727fz4a (thiscontext.com) Let the bugfixing begin. :) thanks again, -C -- Craig Latta Black Page Digital Amsterdam :: San Francisco craig(a)blackpagedigital.com +31 6 2757 7177 (SMS ok) + 1 415 287 3547 (no SMS)

June 29, 2017