Phil is simply pointing out that if someone will look for JSON, the first thing that person will try will be to type “JSON” in Spotter and expect to find something for it. So, now there is a class called STONJSON.
Cheers, Doru > On Mar 16, 2016, at 5:48 PM, stepharo <steph...@free.fr> wrote: > > >> >>> >>> 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). 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. > > I know you are busy but me too. > So what do you mean consuming them? > >> >> >> 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 :) >>> >>> >>> >> >> > -- www.tudorgirba.com www.feenk.com "There are no old things, there are only old ways of looking at them."
