- Pharo-users - lists.pharo.org

Re: [Pharo-users] STON shouldn't care about shared references in JSON mode

by Peter UhnÃ¡k

Ah sorry, I'm blind. Yes, ideally it should throw up an error in case of recursive. And I see that NeoJSON runs into infinite cycle, so I guess this should be addressed there too. On Tue, Mar 27, 2018 at 6:41 PM, Herbert VojÄÃk <herby(a)mailbox.sk> wrote: > > > Peter UhnÃ¡k wrote: > >> Hi Sven, >> >> shouldn't it be set to #ignore by default for JSON then? Or is there a >> use case where it makes sense to have something else for JSON? >> > > To keep STON practices / assumptions while using JSON to hold the data > where STON is not supported yet, maybe? IIRC STON is positioning itself as > JSON superset; but maybe only syntactic superset, while semantically it can > be a bit different (so STONize to more low-level, JSON, syntax via STON; > JSONize faithfully to JSON semantics using NeoJSON; but maybe I am just > making things up). > > Herbert: I am not talking about (infinitely) recursive references, but >> > > I know; Sven explicitly asked what to do with cycles in that case, though. > > referencing the same object, e.g. >> >> >> Peter >> >> On Tue, Mar 27, 2018 at 6:08 PM, Herbert VojÄÃk <herby(a)mailbox.sk >> <mailto:herby@mailbox.sk>> wrote: >> >> >> >> Sven Van Caekenberghe wrote: >> >> Hi Peter, >> >> Both cases will pass using this expression: >> >> String streamContents: [ :out | >> STON jsonWriter >> referencePolicy: #ignore; >> on: out; >> nextPut: d ]. >> >> The problem is what to do with cycles. >> >> >> Be faithful to what JSON.stringify does in JS. See attachment. :-) >> >> Herby >> >> >> Sven >> >> On 27 Mar 2018, at 17:43, Peter UhnÃ¡k<i.uhnak(a)gmail.com >> <mailto:i.uhnak@gmail.com>> wrote: >> >> Hi, >> >> I don't think this should throw an error when I am producing >> JSON. >> >> ``` >> d := { >> 'a' -> #(). >> 'b' -> #(). >> } asDictionary. >> >> STON toJsonString: d. >> ``` >> >> dtto this >> >> ``` >> a := {'hm'}. >> >> d := { >> 'a' -> a. >> 'b' -> a. >> } asDictionary. >> >> STON toJsonString: d. >> ``` >> >> Maybe I should forgo using STON>>toJson* out of laziness (it >> is preinstalled) and always go for NeoJSON? >> >> Peter >> >> >> >> >> >

March 27, 2018

Re: [Pharo-users] STON shouldn't care about shared references in JSON mode

by Herbert VojÄÃk

Peter UhnÃ¡k wrote: > Hi Sven, > > shouldn't it be set to #ignore by default for JSON then? Or is there a > use case where it makes sense to have something else for JSON? To keep STON practices / assumptions while using JSON to hold the data where STON is not supported yet, maybe? IIRC STON is positioning itself as JSON superset; but maybe only syntactic superset, while semantically it can be a bit different (so STONize to more low-level, JSON, syntax via STON; JSONize faithfully to JSON semantics using NeoJSON; but maybe I am just making things up). > Herbert: I am not talking about (infinitely) recursive references, but I know; Sven explicitly asked what to do with cycles in that case, though. > referencing the same object, e.g. > > > Peter > > On Tue, Mar 27, 2018 at 6:08 PM, Herbert VojÄÃk <herby(a)mailbox.sk > <mailto:herby@mailbox.sk>> wrote: > > > > Sven Van Caekenberghe wrote: > > Hi Peter, > > Both cases will pass using this expression: > > String streamContents: [ :out | > STON jsonWriter > referencePolicy: #ignore; > on: out; > nextPut: d ]. > > The problem is what to do with cycles. > > > Be faithful to what JSON.stringify does in JS. See attachment. :-) > > Herby > > > Sven > > On 27 Mar 2018, at 17:43, Peter UhnÃ¡k<i.uhnak(a)gmail.com > <mailto:i.uhnak@gmail.com>> wrote: > > Hi, > > I don't think this should throw an error when I am producing > JSON. > > ``` > d := { > 'a' -> #(). > 'b' -> #(). > } asDictionary. > > STON toJsonString: d. > ``` > > dtto this > > ``` > a := {'hm'}. > > d := { > 'a' -> a. > 'b' -> a. > } asDictionary. > > STON toJsonString: d. > ``` > > Maybe I should forgo using STON>>toJson* out of laziness (it > is preinstalled) and always go for NeoJSON? > > Peter > > > >

March 27, 2018

Re: [Pharo-users] fuel docs shows the same content twice

by Peter UhnÃ¡k

In fact this is problem on every page: it shows the Getting Started on the top, and then continues with the actual content of the page, e.g. https://rmod.inria.fr/web/software/Fuel/Version1.9/Documentation/Globals?_s… On Tue, Mar 27, 2018 at 6:29 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > Hi, > > not sure where to report this, but in this page of fuel docs > > https://rmod.inria.fr/web/software/Fuel/Version1.9/ > Documentation/GettingStarted?_s=gnS5amSI-7GcDf_k&_k=4e8w5tCS4RRm35p7&_n&18 > > all the chapters are twice there > > Basic examples > ... > FileStream > ... > Compressing > ... > Showing a progress bar > ... > Basic examples > ... > FileStream > ... > Compressing > ... > Showing a progress bar > ... > > Peter >

March 27, 2018

Re: [Pharo-users] STON shouldn't care about shared references in JSON mode

by Peter UhnÃ¡k

Hi Sven, shouldn't it be set to #ignore by default for JSON then? Or is there a use case where it makes sense to have something else for JSON? Herbert: I am not talking about (infinitely) recursive references, but referencing the same object, e.g. Peter On Tue, Mar 27, 2018 at 6:08 PM, Herbert VojÄÃk <herby(a)mailbox.sk> wrote: > > > Sven Van Caekenberghe wrote: > >> Hi Peter, >> >> Both cases will pass using this expression: >> >> String streamContents: [ :out | >> STON jsonWriter >> referencePolicy: #ignore; >> on: out; >> nextPut: d ]. >> >> The problem is what to do with cycles. >> > > Be faithful to what JSON.stringify does in JS. See attachment. :-) > > Herby > > > Sven >> >> On 27 Mar 2018, at 17:43, Peter UhnÃ¡k<i.uhnak(a)gmail.com> wrote: >>> >>> Hi, >>> >>> I don't think this should throw an error when I am producing JSON. >>> >>> ``` >>> d := { >>> 'a' -> #(). >>> 'b' -> #(). >>> } asDictionary. >>> >>> STON toJsonString: d. >>> ``` >>> >>> dtto this >>> >>> ``` >>> a := {'hm'}. >>> >>> d := { >>> 'a' -> a. >>> 'b' -> a. >>> } asDictionary. >>> >>> STON toJsonString: d. >>> ``` >>> >>> Maybe I should forgo using STON>>toJson* out of laziness (it is >>> preinstalled) and always go for NeoJSON? >>> >>> Peter >>> >> >> >>

March 27, 2018

fuel docs shows the same content twice

by Peter UhnÃ¡k

Hi, not sure where to report this, but in this page of fuel docs https://rmod.inria.fr/web/software/Fuel/Version1.9/Documentation/GettingSta… all the chapters are twice there Basic examples ... FileStream ... Compressing ... Showing a progress bar ... Basic examples ... FileStream ... Compressing ... Showing a progress bar ... Peter

March 27, 2018

Re: [Pharo-users] STON shouldn't care about shared references in JSON mode

by Herbert VojÄÃk

Sven Van Caekenberghe wrote: > Hi Peter, > > Both cases will pass using this expression: > > String streamContents: [ :out | > STON jsonWriter > referencePolicy: #ignore; > on: out; > nextPut: d ]. > > The problem is what to do with cycles. Be faithful to what JSON.stringify does in JS. See attachment. :-) Herby > Sven > >> On 27 Mar 2018, at 17:43, Peter UhnÃ¡k<i.uhnak(a)gmail.com> wrote: >> >> Hi, >> >> I don't think this should throw an error when I am producing JSON. >> >> ``` >> d := { >> 'a' -> #(). >> 'b' -> #(). >> } asDictionary. >> >> STON toJsonString: d. >> ``` >> >> dtto this >> >> ``` >> a := {'hm'}. >> >> d := { >> 'a' -> a. >> 'b' -> a. >> } asDictionary. >> >> STON toJsonString: d. >> ``` >> >> Maybe I should forgo using STON>>toJson* out of laziness (it is preinstalled) and always go for NeoJSON? >> >> Peter > >

March 27, 2018

Re: [Pharo-users] STON shouldn't care about shared references in JSON mode

by Sven Van Caekenberghe

Hi Peter, Both cases will pass using this expression: String streamContents: [ :out | STON jsonWriter referencePolicy: #ignore; on: out; nextPut: d ]. The problem is what to do with cycles. Sven > On 27 Mar 2018, at 17:43, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Hi, > > I don't think this should throw an error when I am producing JSON. > > ``` > d := { > 'a' -> #(). > 'b' -> #(). > } asDictionary. > > STON toJsonString: d. > ``` > > dtto this > > ``` > a := {'hm'}. > > d := { > 'a' -> a. > 'b' -> a. > } asDictionary. > > STON toJsonString: d. > ``` > > Maybe I should forgo using STON>>toJson* out of laziness (it is preinstalled) and always go for NeoJSON? > > Peter

March 27, 2018

RTLegendBuilder onDemand doesn't popup in html

by Andrei Stebakov

Just wanted to report that when I add a legend to RTView, it works as expected when I ispect the view. When I export it to HTML, it shows the node, but neither mouse clicking nor hovering bring up the popup. Could you take a look?

March 27, 2018

STON shouldn't care about shared references in JSON mode

by Peter UhnÃ¡k

Hi, I don't think this should throw an error when I am producing JSON. ``` d := { 'a' -> #(). 'b' -> #(). } asDictionary. STON toJsonString: d. ``` dtto this ``` a := {'hm'}. d := { 'a' -> a. 'b' -> a. } asDictionary. STON toJsonString: d. ``` Maybe I should forgo using STON>>toJson* out of laziness (it is preinstalled) and always go for NeoJSON? Peter

March 27, 2018

Re: [Pharo-users] Looking for small boards and tiny computers which can run Pharo

by Marcus Denker

Hi, There are other interesting tiny boards that should fit well with Pharo-IOT (we should of course: https://www.raspberrypi.org/products/raspberry-pi-zero/ <https://www.raspberrypi.org/products/raspberry-pi-zero/> but then, there are many and it should be relatively easy to get running there: beaglebone pocket: https://beagleboard.org/pocket <https://beagleboard.org/pocket> Nanpi Duo: http://www.friendlyarm.com/index.php?route=product/product&path=69&product_… <http://www.friendlyarm.com/index.php?route=product/product&path=69&product_…> CHIP https://getchip.com/pages/chippro or industrial platforms like http://www.variscite.com/variscite-products <http://www.variscite.com/variscite-products> > On 23 Mar 2018, at 20:18, Steven Costiou <steven.costiou(a)kloum.io> wrote: > > Hi, > > thanks for the links :) > > Yes i am still working on this topic, however i chose to focus on Raaspbery Pi. It is quite handy to have an embedded linux to experiment things. I do not have a public page on my projects at the moment, but there is the Pharo-iot github project that gather work of the community on the subject (https://github.com/pharo-iot) <https://github.com/pharo-iot)> > Did you manage to launch Pharo on the Teensy boards? > > Steven. > > Le 2018-03-23 08:47, Jonathan van Alteren a Ã©crit : > >> Hi Steven, >> >> I found your message and was wondering if you're still working on this. >> I did some IoT stuff with the little Teensy 3.2 boards, which I find very >> convenient to use. The new 3.6 board has more memory (1Mb flash and 256Kb >> RAM). >> >> See info and seller here: >> - https://www.pjrc.com/teensy/techspecs.html <https://www.pjrc.com/teensy/techspecs.html> >> - https://www.antratek.com/boards/arduino-compatible/teensy <https://www.antratek.com/boards/arduino-compatible/teensy> >> >> Can I follow your progress anywhere? >> >> Kind regards, >> Jonathan >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> >

March 27, 2018