- Pharo-users - lists.pharo.org

Re: [Pharo-users] Where do I find a Pillar syntax summary?

by Alistair Grant

On Wed, Aug 23, 2017 at 09:11:47PM +0200, H. Hirzel wrote: > Thanks, it is useful. > Date is 24 June 2014. > Not sure if it is the latest version for what I have now in Pharo 6. > > --Hannes True, but it only covers the basic text mark-up and I don't think that has changed recently. Anyway, I haven't found anything wrong with it in Pharo 6 & 7 (admittedly, with only basic pillar usage). Cheers, Alistair > On 8/23/17, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > How about: > > > > http://pillarhub.pharocloud.com/hub/pillarhub/pillarcheatsheet > > > > Cheers, > > Alistair

Aug. 23, 2017

Re: [Pharo-users] new chapter on double dispatch for new book :)

by Herby VojÄÃk

Maybe in general sumWithFoo: => addSelfToFoo: to make clues clearer. Herby

Aug. 23, 2017

Re: [Pharo-users] new chapter on double dispatch for new book :)

by Herby VojÄÃk

Stephane Ducasse wrote: > feedback is welcome > Good reading 2.4 "is to explicit type check" - "is to explicitly type check", or - "is to do explicit type check" s/we will haveother/we will have other/ s/distabilizing/destabilizing/ "In fact we just to tell the receiver ,,," something's missing or is extra here s/a die or an handle/a die or a handle/ Figure 2.1 I find the diagram strange on the first look. The solid arrow pointing to the notes is the cause. I am used to see notes connected with dashed line without a tip, an in UML. 2.6 Addition is commutative, so it should not bother form implementation PoV, but it seems strange to see: The previous method ô is definitively what we want to do when we have two dice. So let us rename it as ô£ô¯ôô²ô°ôªôôô°ôô so that we can invoke it later. ôô°ô ô¼ô¼ ô£ô¯ôô²ô°ôªôôô°ôô ôôô°ô ô« ôô°ôô©ôôôôô ôôô» ôôôôô°ôô ô£ôôô§ô ôôôôô°ôô ôôô°ôô ôôô¯ôô£ôôô§ (eh? why pillar makes non copy-paste friendly pdfs?!) back to the point, to see renaming + to sumWithDie: and keep the order, and later do the magic and say "We just tell the argument (which can be a die or a die handle) that we want to add to it an die.". Mind is twisted when trying to grasp it as things are flipped. Much better would be to say "So let us rename it as ô£ô¯ôô²ô°ôªôôô°ôô so that we can invoke it later but let us switch the roles while doing it" and make the DD method with roles switched (self added second). Then the "We just tell the argument (...) that we want to add to it an die." clicks much better (I would use "add itself to a die" in the end). s/Easy, no./Easy, isn't it?/ "It is easy, isnât?" - remove, too much of the same near each other s/we simply creates a new die handle/we simply create a new die handle/ s/add all the die of the previous/add all the dice of the previous/ DieHandle >> sumWithDie: - also do reverse order and change the description to be on par 2.7 s/the receiver is a die handle/the receiver of + is a die handle/ With DD, things go there and back, better be explicit. s/to add a die handle this time/to add itself to a die handle this time/ "We know what is to add two die handles" something is missing or extra here We rename ... as ... => We rename ... as ... while switching roles. and reflect it in code "Remember that sending back a new message to the argument is the key aspect. Why? Because we kick in a new message lookup and dispatch." Not sure if this helps or confuses. Probably find better form. s/final behavior just have to/final behavior we just have to/ s/withWithHandle:/sumWithHandle:/ Note: Die >> sumWithHandle: is in correct order, need no switching. 2.8 maybe s/trivial to understand deeply/trivial to deeply understand/ maybe s/it requires time to digest it/it requires time to digest/ maybe s/method based on the argument too/method based on the argument/ s/we step badk/we step back/ s/applied twice the Donât ask, tell principle/applied the Donât ask, tell principle twice/ s/First the message ô plus selects/First the message ô selects/ s/selecting the correct method either W or Q/selecting either the correct method W or the correct method Q/ s/the receiver and the argument of a messages/the receiver and the argument of a + message/

Aug. 23, 2017

Re: [Pharo-users] Where do I find a Pillar syntax summary?

by H. Hirzel

Thanks, it is useful. Date is 24 June 2014. Not sure if it is the latest version for what I have now in Pharo 6. --Hannes On 8/23/17, Alistair Grant <akgrant0710(a)gmail.com> wrote: > How about: > > http://pillarhub.pharocloud.com/hub/pillarhub/pillarcheatsheet > > Cheers, > Alistair > > > On 23 August 2017 at 20:22, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> Found the (incomplete) list on the last slide of >> >> http://esug.org/data/ESUG2015/4%20thursday/1600-1630%20Pilar/Pillar.pdf >> >> so far. >> >> HH >> >> >> >> On 8/22/17, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >>> Cyril >>> I imagine that you refer to link ref with *@...* >>> Yes we should probably produce a stylesheet. >>> >>> Now I'm busy finishing the new lecture. >>> >>> Since we could not reproduce the Pillar image for Pharo 40 (because of >>> a bug in metacello) luc >>> pushed the Pharo mooc to Pharo 50. >>> >>> Luc created a makefile producer from the pillar.conf and friday we will >>> do a day with damien on having the new makefile on all the booklets + >>> travis. >>> So that I can have one way to do things for all the project. >>> I want to deprecate all the postBuild.sh creation in all the projects. >>> >>> But lecture first >>> >>> Stef >>> >>> On Tue, Aug 22, 2017 at 12:56 PM, Cyril Ferlicot D. >>> <cyril.ferlicot(a)gmail.com> wrote: >>>> Le 22/08/2017 Ã 09:25, H. Hirzel a Ã©crit : >>>>> Hello >>>>> >>>>> There is a tutorial for the Pillar document writing system [1]. The >>>>> Pharo 6 catalog entry shows that the Pillar syntax goes back to the >>>>> Pier CMS syntax of Lukas Renggli [2]. >>>>> >>>>> There is a syntax summary for the Pier CMS >>>>> >>>>> http://www.piercms.com/doc/syntax [3] >>>>> >>>>> I assume that most this still applies for Pillar? >>>>> But I can imagine that there have here been updates / changes / >>>>> extensions. >>>>> >>>>> I am looking for a Pillar syntax summary ("cheat sheet"). >>>>> Is this available somewhere? >>>>> >>>>> Kind regards >>>>> >>>>> Hannes >>>>> >>>>> >>>> >>>> Hi! >>>> >>>> For everything before 2015 there is this one: >>>> >>>> https://www.cheatography.com/benjaminvanryseghem/cheat-sheets/pillar/ >>>> >>>> But everything added after 2015 there is none :( Also there was a >>>> change >>>> of syntax on the links but I don't remember which one. The correct >>>> syntax should be in the PDF you referenced in [1]. >>>> >>>> I'll add an issue to the Pillar repo to create such a sheet but I will >>>> not have the time to do it. (At least not now) >>>> >>>>> >>>>> >>>>> [1] >>>>> https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… >>>>> >>>>> [2] Pharo 6.1 catalog entry for Pillar >>>>> >>>>> Pillar is a wiki-like syntax, its document model, a parser for it, and >>>>> a set of exporters (e.g., HTML, LaTeX, Markdown...). Pillar is >>>>> primarily used as the wiki syntax behind the *Pier >>>>> CMS>http://piercms.com*. Pillar is also being used to write books: >>>>> e.g., *the Enterprise Pharo book>http://books.pharo.org/*. >>>>> >>>>> The original creator of Pillar (formerly known as ''the syntax behind >>>>> the Pier CMS'') is Lukas Renggli. Nevertheless, *Damien >>>>> Cassou>damien.cassou(a)inria.fr* is now the maintainer. The website is >>>>> at *http://www.smalltalkhub.com/#!/~Pier/Pillar*. Issues should be >>>>> reported to *https://github.com/pillar-markup/pillar/issues* >>>>> >>>>> >>>>> [3] http://wiki.squeak.org/squeak/3700 has some information about >>>>> Pier. >>>>> It refers to a Smallwiki mailing list which is active. >>>>> >>>>> https://www.list.inf.unibe.ch/pipermail/smallwiki/ >>>>> >>>>> e.g. >>>>> https://www.list.inf.unibe.ch/pipermail/smallwiki/2016-November/008051.html >>>>> with an announcment 'Pier3 with latest Pillar' >>>>> >>>> >>>> >>>> -- >>>> Cyril Ferlicot >>>> https://ferlicot.fr >>>> >>>> http://www.synectique.eu >>>> 2 rue Jacques PrÃ©vert 01, >>>> 59650 Villeneuve d'ascq France >>>> >>> >>> >> > >

Aug. 23, 2017

Re: [Pharo-users] Where do I find a Pillar syntax summary?

by Alistair Grant

How about: http://pillarhub.pharocloud.com/hub/pillarhub/pillarcheatsheet Cheers, Alistair On 23 August 2017 at 20:22, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > Found the (incomplete) list on the last slide of > > http://esug.org/data/ESUG2015/4%20thursday/1600-1630%20Pilar/Pillar.pdf > > so far. > > HH > > > > On 8/22/17, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> Cyril >> I imagine that you refer to link ref with *@...* >> Yes we should probably produce a stylesheet. >> >> Now I'm busy finishing the new lecture. >> >> Since we could not reproduce the Pillar image for Pharo 40 (because of >> a bug in metacello) luc >> pushed the Pharo mooc to Pharo 50. >> >> Luc created a makefile producer from the pillar.conf and friday we will >> do a day with damien on having the new makefile on all the booklets + >> travis. >> So that I can have one way to do things for all the project. >> I want to deprecate all the postBuild.sh creation in all the projects. >> >> But lecture first >> >> Stef >> >> On Tue, Aug 22, 2017 at 12:56 PM, Cyril Ferlicot D. >> <cyril.ferlicot(a)gmail.com> wrote: >>> Le 22/08/2017 Ã 09:25, H. Hirzel a Ã©crit : >>>> Hello >>>> >>>> There is a tutorial for the Pillar document writing system [1]. The >>>> Pharo 6 catalog entry shows that the Pillar syntax goes back to the >>>> Pier CMS syntax of Lukas Renggli [2]. >>>> >>>> There is a syntax summary for the Pier CMS >>>> >>>> http://www.piercms.com/doc/syntax [3] >>>> >>>> I assume that most this still applies for Pillar? >>>> But I can imagine that there have here been updates / changes / >>>> extensions. >>>> >>>> I am looking for a Pillar syntax summary ("cheat sheet"). >>>> Is this available somewhere? >>>> >>>> Kind regards >>>> >>>> Hannes >>>> >>>> >>> >>> Hi! >>> >>> For everything before 2015 there is this one: >>> >>> https://www.cheatography.com/benjaminvanryseghem/cheat-sheets/pillar/ >>> >>> But everything added after 2015 there is none :( Also there was a change >>> of syntax on the links but I don't remember which one. The correct >>> syntax should be in the PDF you referenced in [1]. >>> >>> I'll add an issue to the Pillar repo to create such a sheet but I will >>> not have the time to do it. (At least not now) >>> >>>> >>>> >>>> [1] >>>> https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… >>>> >>>> [2] Pharo 6.1 catalog entry for Pillar >>>> >>>> Pillar is a wiki-like syntax, its document model, a parser for it, and >>>> a set of exporters (e.g., HTML, LaTeX, Markdown...). Pillar is >>>> primarily used as the wiki syntax behind the *Pier >>>> CMS>http://piercms.com*. Pillar is also being used to write books: >>>> e.g., *the Enterprise Pharo book>http://books.pharo.org/*. >>>> >>>> The original creator of Pillar (formerly known as ''the syntax behind >>>> the Pier CMS'') is Lukas Renggli. Nevertheless, *Damien >>>> Cassou>damien.cassou(a)inria.fr* is now the maintainer. The website is >>>> at *http://www.smalltalkhub.com/#!/~Pier/Pillar*. Issues should be >>>> reported to *https://github.com/pillar-markup/pillar/issues* >>>> >>>> >>>> [3] http://wiki.squeak.org/squeak/3700 has some information about Pier. >>>> It refers to a Smallwiki mailing list which is active. >>>> >>>> https://www.list.inf.unibe.ch/pipermail/smallwiki/ >>>> >>>> e.g. >>>> https://www.list.inf.unibe.ch/pipermail/smallwiki/2016-November/008051.html >>>> with an announcment 'Pier3 with latest Pillar' >>>> >>> >>> >>> -- >>> Cyril Ferlicot >>> https://ferlicot.fr >>> >>> http://www.synectique.eu >>> 2 rue Jacques PrÃ©vert 01, >>> 59650 Villeneuve d'ascq France >>> >> >> >

Aug. 23, 2017

Brea wiki software

by H. Hirzel

On 8/23/17, Offray <offray.luna(a)mutabit.com> wrote: > Hi, > > On the Teapot + Mustache integration, Hannes, you may want to see my early > prototype: > > http://smalltalkhub.com/#!/~Offray/Brea > > At some point, it will contain distributed wiki, backed by Fossil, now that > we're thinking in empower community driven wiki like documentation. > > Offray Hi Offray I found Name: Brea-OffrayLuna.8 Author: OffrayLuna Time: 1 June 2017, 4:18:20.860411 pm There is no test to show me how to use it and I none of the class comments of the 4 classes gives enough clues. Interesting method so far routes "I define how the website behaves accordingly to particular routes." self server serveStatic: 'demo' from: '/opt/gig/'; GET: 'members/test' -> [ :req | BreaMember new renderTestUserAsHtml ]; GET: 'members/add' -> [ :req | BreaMember new htmlInput ]; POST: 'members/summit' -> [ :req | self processNewMember: req ] May I ask you to give a few hints how to start it? Is it possible to use it without Fossil, just with image persistence? Regards Hannes

Aug. 23, 2017

Re: [Pharo-users] Where do I find a Pillar syntax summary?

by H. Hirzel

Found the (incomplete) list on the last slide of http://esug.org/data/ESUG2015/4%20thursday/1600-1630%20Pilar/Pillar.pdf so far. HH On 8/22/17, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Cyril > I imagine that you refer to link ref with *@...* > Yes we should probably produce a stylesheet. > > Now I'm busy finishing the new lecture. > > Since we could not reproduce the Pillar image for Pharo 40 (because of > a bug in metacello) luc > pushed the Pharo mooc to Pharo 50. > > Luc created a makefile producer from the pillar.conf and friday we will > do a day with damien on having the new makefile on all the booklets + > travis. > So that I can have one way to do things for all the project. > I want to deprecate all the postBuild.sh creation in all the projects. > > But lecture first > > Stef > > On Tue, Aug 22, 2017 at 12:56 PM, Cyril Ferlicot D. > <cyril.ferlicot(a)gmail.com> wrote: >> Le 22/08/2017 Ã 09:25, H. Hirzel a Ã©crit : >>> Hello >>> >>> There is a tutorial for the Pillar document writing system [1]. The >>> Pharo 6 catalog entry shows that the Pillar syntax goes back to the >>> Pier CMS syntax of Lukas Renggli [2]. >>> >>> There is a syntax summary for the Pier CMS >>> >>> http://www.piercms.com/doc/syntax [3] >>> >>> I assume that most this still applies for Pillar? >>> But I can imagine that there have here been updates / changes / >>> extensions. >>> >>> I am looking for a Pillar syntax summary ("cheat sheet"). >>> Is this available somewhere? >>> >>> Kind regards >>> >>> Hannes >>> >>> >> >> Hi! >> >> For everything before 2015 there is this one: >> >> https://www.cheatography.com/benjaminvanryseghem/cheat-sheets/pillar/ >> >> But everything added after 2015 there is none :( Also there was a change >> of syntax on the links but I don't remember which one. The correct >> syntax should be in the PDF you referenced in [1]. >> >> I'll add an issue to the Pillar repo to create such a sheet but I will >> not have the time to do it. (At least not now) >> >>> >>> >>> [1] >>> https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… >>> >>> [2] Pharo 6.1 catalog entry for Pillar >>> >>> Pillar is a wiki-like syntax, its document model, a parser for it, and >>> a set of exporters (e.g., HTML, LaTeX, Markdown...). Pillar is >>> primarily used as the wiki syntax behind the *Pier >>> CMS>http://piercms.com*. Pillar is also being used to write books: >>> e.g., *the Enterprise Pharo book>http://books.pharo.org/*. >>> >>> The original creator of Pillar (formerly known as ''the syntax behind >>> the Pier CMS'') is Lukas Renggli. Nevertheless, *Damien >>> Cassou>damien.cassou(a)inria.fr* is now the maintainer. The website is >>> at *http://www.smalltalkhub.com/#!/~Pier/Pillar*. Issues should be >>> reported to *https://github.com/pillar-markup/pillar/issues* >>> >>> >>> [3] http://wiki.squeak.org/squeak/3700 has some information about Pier. >>> It refers to a Smallwiki mailing list which is active. >>> >>> https://www.list.inf.unibe.ch/pipermail/smallwiki/ >>> >>> e.g. >>> https://www.list.inf.unibe.ch/pipermail/smallwiki/2016-November/008051.html >>> with an announcment 'Pier3 with latest Pillar' >>> >> >> >> -- >> Cyril Ferlicot >> https://ferlicot.fr >> >> http://www.synectique.eu >> 2 rue Jacques PrÃ©vert 01, >> 59650 Villeneuve d'ascq France >> > >

Aug. 23, 2017

Re: [Pharo-users] Parser failure on FFI pragmas declaration in Pharo 5

by bdurin

Hi Stef, Thank you for your explanations! About deprecation, I found it fast because I think FFI as a key component of a language. I imagine similar problems could happen when going from Morphic to its successor (Bloc?). Even with a stable API, I expect some code to explicitely depends on Morphic and break in the next GUI framework. I do not think this can be avoided. I am aware that maintenance is very costly and that it is always hard to be sure new users do not get caught in this kind of change. (As far as I understand the old MVC framework was kept quite long along with the at-the-time new Morphic to ensure smooth transition.) Note that I am not trying to claim that Pharo generally is bad or worse than another language. As a new user, my expectations were quite high after spending a few weeks learning the language, going through the MOOC, being able to tinker with the UI (looking at everything, modifying the World Menu, etc.), looking into the details of the bytecode and the VM. All of these worked very well and I still do think that Pharo is a great of software as I wrote in a previous question. Even when facing the UI problem in Pharo 5 due to old FFI syntax, I was able to hack into the code and get it work. In another language hitting an "internal" problem often is a dead end. I cannot tackle the problems I highlighted by myself. But with the help of someone who knows how to address them in the Pharo's way, I am willing to help. About dependencies and version, I knew of Metacello configurations when I wrote my first message and I was thinking of Pharo version (more precisely the versions of core packages and dependencies as opposed to other external packages that should be loaded on top of a freshly downloaded image). I did not know that Pharo version was in configurations. So I had a look at ConfigurationOfZeroMQ and maybe it keeps on being an exception but I did not find any dependency on Pharo version in it. However it declares a dependency on FFI version 1.4, which eventually is better than explicitely setting a dependency on a Pharo version. I also had a look at the "validate" class method and its comment that mentions "MetacelloMCVersionValidator". How is this validation mechanism triggered? I could work on it and modify the source code loader(s) so that instead of getting a syntax error in Pharo 6 I get an error or a critical warning from the validator. (I loaded the package by adding the corresponding repository in the Monticello browser and loading ZeroMQ and ConfigurationOfZeroMQ last versions.) I eventually found what you talked about. In ConfigurationOfFFI, "stable:" method lists the FFI versions that Pharo versions supports. The convention for versioning is not clear to me: old FFI is supposed to work up to Pharo 4 and the spec says FFI should be 1.7 to 1.9, which would mean that if a package needs version x, any version y>=x is ok, but from Pharo 5 (which requires FFI 1.10.1) it should fail, which would mean that version x should be matched exactly (or an interval should be defined). In Pharo 6 ConfigurationOfUnifiedFFI>>version_0_26_8 declares a dependency on FFI-Kernel âFFI-Kernel-EstebanLorenzano.45â, which I do not understand. Maybe here I can remove FFI dependencies. (Is this what you meant when saying you could have deprecated it but did not do it?) Besides ConfigurationOfFFI is not included in a freshly downloaded Pharo image (I checked for Pharo 5), I found a reference to it in ConfigurationOfUnifiedFFI (in the "ffi:" method) and manually added the corresponding repository (MetaRepoForPharo50) in Monticello browser and loaded the last version of ConfigurationOfFFI. So it seems that the info is not available by default. I had also a look at FFI-Kernel package (the object as found by running "RPackageOrganizer default packages select: [:p | p name = #'FFI-Kernelâ].") and could not find any version info. Is it correct that the version info of a package is only available through ConfigurationOf... and is not included in the package object? If I understand well, a way to correct the problem would be: - to ensure (or set it as an option for a start) that Metacello validation is triggered even when loading source code and let the user choose from an option whether it wants errors at loading stage or only warnings (and expect problems when running). - add all the ConfigurationOf that are in "Pharo/MetaRepoForPharo50/main" repository in the corresponding official image (maybe rather do this for Pharo60 which is still maintained) so that the validation gets all the needed info - as you mentioned in an earlier message ConfigurationOf for some "internal" packages (included in a freshly downloaded Pharo image) are missing, so add them, attribute them a version and set dependencies accordingly. (I can help, it is a good way to learn about the internals of the language.) Is it correct? (I can also work on the validator with some help.) About correcting the specific problem I had in Pharo 5. Esteban told me that it was not useful so I am confused now. About 0mq, I am not an expert of the (original) C library and of the python bindings. The library sets up sockets for communication between processes and even if you can serialize them apparently ZeroMQ is relatively brittle as regards initialization (and this is one of its flaws). The author of the ZeroMQ Pharo package was aware of the persistence problem and mentioned he could not solve it completely. This is not an easy problem apparently. About python bindings, they abstract initialization a bit and more importantly offer abstractions to process the messages through the sockets: integration with the async python 3 framework and with a popular event loop (python tornado library from Facebook) are offered. It is much easier to work with ZeroMQ this way as you do not have to care about low-level IO details. (I do not know how it is done in the python bindings but for example to listen to the socket either an event loop could take care of the regular polling of the sockets or one could set up a thread that listens to the socket through a blocking call.) The equivalent in Pharo might be to integrate ZeroMQ with the GUI event loop. (Not something I am able to do unfortunately.) Thanks, Bruno -- View this message in context: http://forum.world.st/Parser-failure-on-FFI-pragmas-declaration-in-Pharo-5-… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 23, 2017

Re: [Pharo-users] Parser failure on FFI pragmas declaration in Pharo 5

by bdurin

Hi Marcus, I would be happy to contribute to your experiment. Let me know. Bruno -- View this message in context: http://forum.world.st/Parser-failure-on-FFI-pragmas-declaration-in-Pharo-5-… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 23, 2017

Re: [Pharo-users] Teapot and Mustache in Pharo 6?

by Offray

Hi, On the Teapot + Mustache integration, Hannes, you may want to see my early prototype: http://smalltalkhub.com/#!/~Offray/Brea At some point, it will contain distributed wiki, backed by Fossil, now that we're thinking in empower community driven wiki like documentation. Offray El 21 de agosto de 2017 10:52:47 GMT-05:00, "H. Hirzel" <hannes.hirzel(a)gmail.com> escribiÃ³: >Hello > >The TeaPot documentation [1] references Mustache [2] in the section > > 4.1. Response Transformers [3] > >There is an example for a JSON transformation but none for Mustache. > >Where do I find some information how to use Mustache together with >Teapot? > >Regards >Hannes > > > > >[1] >https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… > >[2] >https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… > > >[3] The responsibility of a response transformer is to convert the >output of the action block to HTML and to set the content-type of the >response. Some response transformers require external packages (e.g., >NeoJSON, STON, Mustache). > >[4] Adapted example > >TLWebserver teapot GET: '/jsonlist' -> #(1 2 3 4); output: #json. -- Enviado desde mi dispositivo Android con K-9 Mail. Por favor, disculpa mi brevedad.

Aug. 23, 2017