On Tue, Mar 15, 2016 at 6:08 PM, stepharo <steph...@free.fr> wrote: > > > Le 14/3/16 09:33, p...@highoctane.be a écrit : > > JSON is so pervasive that a base Pharo image should have things named > after it. > STON is supercool but there is no JSON name in it, that's an issue for me. > > > Since STON can read and emit JSON I do not get the problem? >
Discoverability. See Sven other mail. > > > What would be a good way to do that? I wonder. > > In the same vein, in Angular, consuming webservices that have a "proper" > REST API (if there is such a thing, but still, this is nice) is easy with > Restangular ( <https://github.com/mgonto/restangular> > https://github.com/mgonto/restangular). Not having such a thing has > costed me much time during hackathons, during which competition using it > was wrapping webservices at the speed of light while I was plodding along. > > Is there such a thing in Pharo? > > Seaside REST > No: this is for exposing endpoints, not consuming them. See Restangular. > Teapot > No: same. I use SeasideREST and Teapot BTW. > > > Phil > > On Mon, Mar 14, 2016 at 8:44 AM, stepharo <steph...@free.fr> wrote: > >> ((STON fromString: ( >> ZnEasy >> get: 'http://api.geonames.org/countryInfoJSON' >> username: 'demo' >> password: '') contents) at: #geonames) collect: [ : d | d at: >> #capital ] >> >> With STON :) >> >> >> > >
