- Pharo-users - lists.pharo.org

Re: [Pharo-users] FYI: HTTP mocking lib (alpha) at https://lolg.it/herby/znock

by Stephane Ducasse

This cool. Because I wanted to use that in one test with a project with my son. What is the license? Where is the code? On Tue, Jan 30, 2018 at 11:31 PM, Herbert VojÄÃk <herby(a)mailbox.sk> wrote: > Hi! > > I started with a rudimentary HTTP mocking lib (adding features as needed) > inspired by nock, but using the existing ZnClient / ZnRequest / ZnResponse > api for mocking. > > Atm the feature are very basic (no filtering, matching only by host and > scheme), but there it is for the interested. > > Usage: > > setUp > "other stuff" > Znock default intercept > > tearDown > "other stuff" > Znock default verify > > testFooBar > 'https://foo.bar' znock > url: '/api/v0/info'; > get; > ok: (ZnEntity json: self sampleInfoResponse). > "code that should get https://foo.bar/api/v0/info" > > The setUp starts and cleans the mocker; the test case sets up the > expectation that GET https://foo.bar/api/v0/info will occur and defines the > response; tearDown checks that that GET actually appeared and fails if not. > > DNU w/ whitelisting is used to reply certain ZnClient messages to set up the > expectation, ZnResponse class messages to create the response and ZnResponse > messages to fill it further. > > So you can > > 'foo.bar' znock > https; > url: '/api/v0/info'; > get; > notModified. > > if you like it this way or > > 'foo.bar' znock > url: '/api/v0/info'; > get; > notModified. > > to allow both http and https; eventually > > 'foo.bar/api/v0/info' znock > get; > notModified. > > if you want it shorter; mocking multiple req/res pair should work (not > tested), as in > > 'foo.bar' znock > url: '/api/v0/info'; > get; > notModified; > url: '/api/v0/last'; > get; > ok: (ZnEntity textCRLF: 'herby'). > > Both must appear (in any order) for verify to be happy. > > Herby >

Jan. 31, 2018

Re: [Pharo-users] is OSSubProcess working in Pharo 6.1?

by Stephane Ducasse

Thanks I really do not know how to debug it. Because I can load pillar code on my machine. On Tue, Jan 30, 2018 at 11:47 PM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > Hi Stef, > > On 30 January 2018 at 23:13, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> Hi >> >> in pillar 70 we have >> baseline: spec >> <baseline> >> spec >> for: #common >> do: [ spec blessing: #baseline. >> spec repository: 'http://smalltalkhub.com/mc/Pier/Pillar/main/'. >> spec >> baseline: 'OSSubprocess' >> with: [ spec >> repository: 'github://marianopeck/OSSubprocess:v0.2.5/repository' ]; >> baseline: 'Mustache' >> with: [ spec >> repository: 'github://noha/mustache:v1.0/repository' ]; >> project: 'Cocoon' >> >> but travis reports this: >> >> >> Fetched -> OSSubprocess-cypress.1 --- >> github://marianopeck/OSSubprocess:v0.2.5/repository [1d56f81:v0.2.5] >> --- github://marianopeck/OSSubprocess:v0.2.5/repository >> Fetched -> OSSubprocess-Tests-cypress.1 --- >> github://marianopeck/OSSubprocess:v0.2.5/repository [1d56f81:v0.2.5] >> --- github://marianopeck/OSSubprocess:v0.2.5/repository >> ...RETRY >> ...RETRYMessageNotUnderstood: receiver of "withSqueakLineEndings" is nil >> UndefinedObject(Object)>>doesNotUnderstand: #withSqueakLineEndings >> MCFileTreeStCypressReader>>addClassAndMethodDefinitionsFromEntry: >> >> and I do not get why? >> >> Stef >> > > I use the following to load OSSubProcess in Pharo 7.0 32 bit: > > Metacello new > configuration: 'OSSubprocess'; > repository: 'github://marianopeck/OSSubprocess:master/repository'; > version: #stable; > load. > > > i.e. just replace the "v0.2.5" with "master". > > HTH, > Alistair >

Jan. 31, 2018

Re: [Pharo-users] is OSSubProcess working in Pharo 6.1?

by Alistair Grant

Hi Stef, On 30 January 2018 at 23:13, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi > > in pillar 70 we have > baseline: spec > <baseline> > spec > for: #common > do: [ spec blessing: #baseline. > spec repository: 'http://smalltalkhub.com/mc/Pier/Pillar/main/'. > spec > baseline: 'OSSubprocess' > with: [ spec > repository: 'github://marianopeck/OSSubprocess:v0.2.5/repository' ]; > baseline: 'Mustache' > with: [ spec > repository: 'github://noha/mustache:v1.0/repository' ]; > project: 'Cocoon' > > but travis reports this: > > > Fetched -> OSSubprocess-cypress.1 --- > github://marianopeck/OSSubprocess:v0.2.5/repository [1d56f81:v0.2.5] > --- github://marianopeck/OSSubprocess:v0.2.5/repository > Fetched -> OSSubprocess-Tests-cypress.1 --- > github://marianopeck/OSSubprocess:v0.2.5/repository [1d56f81:v0.2.5] > --- github://marianopeck/OSSubprocess:v0.2.5/repository > ...RETRY > ...RETRYMessageNotUnderstood: receiver of "withSqueakLineEndings" is nil > UndefinedObject(Object)>>doesNotUnderstand: #withSqueakLineEndings > MCFileTreeStCypressReader>>addClassAndMethodDefinitionsFromEntry: > > and I do not get why? > > Stef > I use the following to load OSSubProcess in Pharo 7.0 32 bit: Metacello new configuration: 'OSSubprocess'; repository: 'github://marianopeck/OSSubprocess:master/repository'; version: #stable; load. i.e. just replace the "v0.2.5" with "master". HTH, Alistair

Jan. 30, 2018

Re: [Pharo-users] FYI: HTTP mocking lib (alpha) at https://lolg.it/herby/znock

by Herbert VojÄÃk

Herbert VojÄÃk wrote: > Hi! > > I started with a rudimentary HTTP mocking lib (adding features as > needed) inspired by nock, but using the existing ZnClient / ZnRequest / > ZnResponse api for mocking. > > Atm the feature are very basic (no filtering, matching only by host and > scheme), but there it is for the interested. > > Usage: > > setUp > "other stuff" > Znock default intercept > > tearDown > "other stuff" > Znock default verify > > testFooBar > 'https://foo.bar' znock > url: '/api/v0/info'; > get; > ok: (ZnEntity json: self sampleInfoResponse). > "code that should get https://foo.bar/api/v0/info" > > The setUp starts and cleans the mocker; the test case sets up the > expectation that GET https://foo.bar/api/v0/info will occur and defines > the response; tearDown checks that that GET actually appeared and fails > if not. > > DNU w/ whitelisting is used to reply certain ZnClient messages to set up s/reply/replay/ > the expectation, ZnResponse class messages to create the response and > ZnResponse messages to fill it further. > > So you can > > 'foo.bar' znock > https; > url: '/api/v0/info'; > get; > notModified. > > if you like it this way or > > 'foo.bar' znock > url: '/api/v0/info'; > get; > notModified. > > to allow both http and https; eventually > > 'foo.bar/api/v0/info' znock > get; > notModified. > > if you want it shorter; mocking multiple req/res pair should work (not > tested), as in > > 'foo.bar' znock > url: '/api/v0/info'; > get; > notModified; > url: '/api/v0/last'; > get; > ok: (ZnEntity textCRLF: 'herby'). > > Both must appear (in any order) for verify to be happy. > > Herby >

Jan. 30, 2018

Re: [Pharo-users] FYI: HTTP mocking lib (alpha) at https://lolg.it/herby/znock

by Herbert VojÄÃk

Herbert VojÄÃk wrote: > Hi! > > I started with a rudimentary HTTP mocking lib (adding features as > needed) inspired by nock, but using the existing ZnClient / ZnRequest / > ZnResponse api for mocking. Credits: Uses Mocketry's `ZnClient new stub will: ...` to set up mocked client; thanks Denis Kudriashov. Herby > Atm the feature are very basic (no filtering, matching only by host and > scheme), but there it is for the interested. > > Usage: > > setUp > "other stuff" > Znock default intercept > > tearDown > "other stuff" > Znock default verify > > testFooBar > 'https://foo.bar' znock > url: '/api/v0/info'; > get; > ok: (ZnEntity json: self sampleInfoResponse). > "code that should get https://foo.bar/api/v0/info" > > The setUp starts and cleans the mocker; the test case sets up the > expectation that GET https://foo.bar/api/v0/info will occur and defines > the response; tearDown checks that that GET actually appeared and fails > if not. > > DNU w/ whitelisting is used to reply certain ZnClient messages to set up > the expectation, ZnResponse class messages to create the response and > ZnResponse messages to fill it further. > > So you can > > 'foo.bar' znock > https; > url: '/api/v0/info'; > get; > notModified. > > if you like it this way or > > 'foo.bar' znock > url: '/api/v0/info'; > get; > notModified. > > to allow both http and https; eventually > > 'foo.bar/api/v0/info' znock > get; > notModified. > > if you want it shorter; mocking multiple req/res pair should work (not > tested), as in > > 'foo.bar' znock > url: '/api/v0/info'; > get; > notModified; > url: '/api/v0/last'; > get; > ok: (ZnEntity textCRLF: 'herby'). > > Both must appear (in any order) for verify to be happy. > > Herby >

Jan. 30, 2018

FYI: HTTP mocking lib (alpha) at https://lolg.it/herby/znock

by Herbert VojÄÃk

Hi! I started with a rudimentary HTTP mocking lib (adding features as needed) inspired by nock, but using the existing ZnClient / ZnRequest / ZnResponse api for mocking. Atm the feature are very basic (no filtering, matching only by host and scheme), but there it is for the interested. Usage: setUp "other stuff" Znock default intercept tearDown "other stuff" Znock default verify testFooBar 'https://foo.bar' znock url: '/api/v0/info'; get; ok: (ZnEntity json: self sampleInfoResponse). "code that should get https://foo.bar/api/v0/info" The setUp starts and cleans the mocker; the test case sets up the expectation that GET https://foo.bar/api/v0/info will occur and defines the response; tearDown checks that that GET actually appeared and fails if not. DNU w/ whitelisting is used to reply certain ZnClient messages to set up the expectation, ZnResponse class messages to create the response and ZnResponse messages to fill it further. So you can 'foo.bar' znock https; url: '/api/v0/info'; get; notModified. if you like it this way or 'foo.bar' znock url: '/api/v0/info'; get; notModified. to allow both http and https; eventually 'foo.bar/api/v0/info' znock get; notModified. if you want it shorter; mocking multiple req/res pair should work (not tested), as in 'foo.bar' znock url: '/api/v0/info'; get; notModified; url: '/api/v0/last'; get; ok: (ZnEntity textCRLF: 'herby'). Both must appear (in any order) for verify to be happy. Herby

Jan. 30, 2018

is OSSubProcess working in Pharo 6.1?

by Stephane Ducasse

Hi in pillar 70 we have baseline: spec <baseline> spec for: #common do: [ spec blessing: #baseline. spec repository: 'http://smalltalkhub.com/mc/Pier/Pillar/main/'. spec baseline: 'OSSubprocess' with: [ spec repository: 'github://marianopeck/OSSubprocess:v0.2.5/repository' ]; baseline: 'Mustache' with: [ spec repository: 'github://noha/mustache:v1.0/repository' ]; project: 'Cocoon' but travis reports this: Fetched -> OSSubprocess-cypress.1 --- github://marianopeck/OSSubprocess:v0.2.5/repository [1d56f81:v0.2.5] --- github://marianopeck/OSSubprocess:v0.2.5/repository Fetched -> OSSubprocess-Tests-cypress.1 --- github://marianopeck/OSSubprocess:v0.2.5/repository [1d56f81:v0.2.5] --- github://marianopeck/OSSubprocess:v0.2.5/repository ...RETRY ...RETRYMessageNotUnderstood: receiver of "withSqueakLineEndings" is nil UndefinedObject(Object)>>doesNotUnderstand: #withSqueakLineEndings MCFileTreeStCypressReader>>addClassAndMethodDefinitionsFromEntry: and I do not get why? Stef

Jan. 30, 2018

Re: [Pharo-users] Sending notifications from Pharo to your Mobile via Pushover.net

by Markus Stumptner

Great stuff! On 30/01/2018 6:10, Sven Van Caekenberghe wrote: > Hi, > > Just a little snippet I wanted to share. Pushover > (https://pushover.net) is a general service that delivers > notifications to iOS, Android and desktop devices via an API (and an > email gateway as well). It is really easy to get started with. > > This is how you do it from Pharo: > > ZnClient new > Â systemPolicy; > Â url: 'https://api.pushover.net/1/messages.json'; > Â accept: ZnMimeType applicationJson; > Â contentReader: [ :entity | NeoJSONObject fromString: entity contents ]; > Â contentWriter: [ :object | ZnEntity json: object asString ]; > Â contents: (NeoJSONObject new > Â Â Â Â Â Â Â Â token: 'ax4o55o6g5imb1a6st3m9x34hqu44z'; > Â Â Â Â Â Â Â Â user: 'uv2fovx3f9sp3rgssrupvjgvdo8quw'; > Â Â Â Â Â Â Â Â title: 'Test 3'; > Â Â Â Â Â Â Â Â message: ('This is a test @ {1} by {2}.' format: { > Â Â Â Â Â Â Â Â Â Â Â Â Â Â DateAndTime now. SystemVersion current })); > Â post. > > It will look like this on your mobile device (just seconds later): > > > Nothing special, but pretty handy. > > Sven > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > > >

Jan. 30, 2018

Re: [Pharo-users] New booklets organisation and new booklet

by Ben Coman

On 30 January 2018 at 15:54, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Now I wonder if it makes sense to have all the docs of drGeo here. I > can do it but I'm thinking about it. > May be I could create another category. Perhaps a category named "Applications" or "Libraries" cheers -ben > I "read" your handbook and I > do not think that it should be listed among the pharo books. > Now what I would love to have is a handbook: Pharo for the Data > Journalist. Do you have something like that? > > Stef > > On Mon, Jan 29, 2018 at 1:35 AM, Offray Vladimir Luna CÃ¡rdenas > <offray.luna(a)mutabit.com> wrote: >> Hi, >> >> Nice to see this collection organized in this way with more targeted reading >> audiences. >> >> The DrGeo PDFs are linked in the page Phil pointed to: >> >> English: https://launchpadlibrarian.net/300141633/drgeo-english.pdf >> French: https://launchpadlibrarian.net/322576649/drgeo.pdf >> >> You could add several books which are made with Grafoscopio: >> >> The User Manual (pdf): >> http://mutabit.com/repos.fossil/grafoscopio/doc/tip/Docs/En/Books/Manual/ma… >> Manual de Periodismo de datos (The Data Driven Journalist Handbook) >> >> PDF: http://mutabit.com/repos.fossil/mapeda/uv/mapeda.pdf >> Epub: http://mutabit.com/repos.fossil/mapeda/uv/mapeda.epub >> Repo: http://mutabit.com/repos.fossil/mapeda/ >> >> Pasos para una Biblioteca Digital de BogotÃ¡ (Steps towards the Bogota >> Digital Library): >> >> PDF: >> http://mutabit.com/repos.fossil/dataweek/uv/Artefactos/BibliotecaDigitalBog… >> Repo: >> http://mutabit.com/repos.fossil/dataweek/doc/tip/Artefactos/BibliotecaDigit… >> >> We are just starting, but I think that the local community will be producing >> a good collection of digital publications, mainly books and booklets, >> powered by Grafoscopio, and done easily in a multiplatform and portable >> setup (Windows, Linux, Mac). We plan to follow a similar approach to GitBook >> [1] and LeanPub [2], and we have made some contacts with some publishers, >> authors and translators who would like to have a Open Reproducible >> Publishing Light Environment. Once we have more work done we will build our >> own books and booklets collection, so, may be we can showcase this work in >> some "powered by Pharo" publishing examples. >> >> [1] https://www.gitbook.com/ >> [2] https://leanpub.com/ >> >> I know there is a very vocal opposition in this community about using >> anything but Pillar for documentation, but I think that showing that there >> is a strong support for writing complex documents, using Pharo powered tools >> and playing well with others, can be a strong point of advocacy about what >> is possible within this ecosystem, tech and community for a wider audience >> beyond programmers, like kids, school teachers, journalist, hacktivist, >> librarians, and so on. >> >> Cheers, >> >> Offray >> >> >> On 28/01/18 16:44, Stephane Ducasse wrote: >> >> If hilaire send me a pdf I will add them. I did not about them. >> >> Stef >> >> On Sun, Jan 28, 2018 at 11:55 AM, phil(a)highoctane.be <phil(a)highoctane.be> >> wrote: >> >> Looks nice. >> >> We should also put the books of Dr Geo in there but maybe they are GPL. >> >> But at least a link to http://www.drgeo.eu/help would be nice. >> >> Phil >> >> On Sun, Jan 28, 2018 at 10:47 AM, Esteban Lorenzano <estebanlm(a)gmail.com> >> wrote: >> >> +1 >> >> On 27 Jan 2018, at 20:55, Stephane Ducasse <stepharo.self(a)gmail.com> >> wrote: >> >> Hi >> >> We reorganised the books.pharo.org web site to make the distinction >> between technology and teaching oriented booklet. >> We will have specific covers soon and print available on lulu. >> >> In addition we got the new booklet from C. Bera that explains Call >> Stack Management. >> >> http://books.pharo.org >> >> Stef >> >> >> >> >> >

Jan. 30, 2018

Techtalk starting: Genetic Algorithms

by Marcus Denker

TechTalk is starting now. Link is: https://www.youtube.com/watch?v=ZB1U259wPaA Pharo TechTalk: Genetic Algorithms https://association.pharo.org/event-2757884

Jan. 30, 2018