December 2016 - Pharo-users

Re: [Pharo-users] How to edit an element with Teapot

by Sven Van Caekenberghe

I meant section 11 of the Zinc HTTP Server chapter https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… > On 17 Dec 2016, at 11:56, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Chapter 11 : Scripting a REST Web Service with Zinc > > of the Enterprise book > >> On 17 Dec 2016, at 11:31, stepharong <stepharong(a)free.fr> wrote: >> >> Hi >> >> This is probably a stupid question but I dare to ask it. >> >> I have a tiny teapot application (based on the library example) and I would like to let the use add an item or edit an item. >> I do want to force the user to do it via the request path with a post or that way >> >> ZnClient new >> url: 'http://localhost:8080/books/1'; >> formAt: 'author' put: 'SquareBracketAssociates'; >> formAt: 'title' put: 'Pharo For The Enterprise'; put >> >> I know how to do it in Seaside but I feel spoiled because I do not know how to do it in plain html to serve it with Teapot. >> >> I noticed that in none of our chapters (Teapot, ZnApplication chapter, tinyblog-teapot, tinyblog-seaside) shows how to do it. >> >> >> -- >> Using Opera's mail client: http://www.opera.com/mail/ >> >

Dec. 17, 2016

Re: [Pharo-users] How to edit an element with Teapot

by Sven Van Caekenberghe

Chapter 11 : Scripting a REST Web Service with Zinc of the Enterprise book > On 17 Dec 2016, at 11:31, stepharong <stepharong(a)free.fr> wrote: > > Hi > > This is probably a stupid question but I dare to ask it. > > I have a tiny teapot application (based on the library example) and I would like to let the use add an item or edit an item. > I do want to force the user to do it via the request path with a post or that way > > ZnClient new > url: 'http://localhost:8080/books/1'; > formAt: 'author' put: 'SquareBracketAssociates'; > formAt: 'title' put: 'Pharo For The Enterprise'; put > > I know how to do it in Seaside but I feel spoiled because I do not know how to do it in plain html to serve it with Teapot. > > I noticed that in none of our chapters (Teapot, ZnApplication chapter, tinyblog-teapot, tinyblog-seaside) shows how to do it. > > > -- > Using Opera's mail client: http://www.opera.com/mail/ >

Dec. 17, 2016

How to edit an element with Teapot

by stepharong

Hi This is probably a stupid question but I dare to ask it. I have a tiny teapot application (based on the library example) and I would like to let the use add an item or edit an item. I do want to force the user to do it via the request path with a post or that way ZnClient new url: 'http://localhost:8080/books/1'; formAt: 'author' put: 'SquareBracketAssociates'; formAt: 'title' put: 'Pharo For The Enterprise'; put I know how to do it in Seaside but I feel spoiled because I do not know how to do it in plain html to serve it with Teapot. I noticed that in none of our chapters (Teapot, ZnApplication chapter, tinyblog-teapot, tinyblog-seaside) shows how to do it. -- Using Opera's mail client: http://www.opera.com/mail/

Dec. 17, 2016

Re: [Pharo-users] [Vm-dev] ptsd rage

by Ben Coman

On Sat, Dec 17, 2016 at 9:57 AM, Robert Withers <robert.w.withers(a)gmail.com> wrote: > > I need to apologize for all my dread behavior. Here is the reason, and I am > on service-connected disability. Current diagnosis is Complex PTSD. Sorry > about all my sturm und drang. > > http://www.ptsd.va.gov/public/problems/anger-and-trauma.asp > Sorry to hear you are suffering with that. Hopefully a useful treatment is not too far away... F.D.A. Agrees to New Trials for Ecstasy as Relief for PTSD Patients http://www.nytimes.com/2016/11/29/us/ptsd-mdma-ecstasy.html?_r=0 cheers -ben

Dec. 17, 2016

ptsd rage

by Robert Withers

I need to apologize for all my dread behavior. Here is the reason, and I am on service-connected disability. Current diagnosis is Complex PTSD. Sorry about all my sturm und drang. http://www.ptsd.va.gov/public/problems/anger-and-trauma.asp Sincerely, Robert

Dec. 17, 2016

Re: [Pharo-users] NeoJSON

by stepharong

> Strange. > > In Neo-JSON-Core-SvenVanCaekenberghe.37 in the class comment of > NeoJSONMapper last paragraph before the examples. sure I just meant that it was not visible enough. We should add for example XXX >> neoJsonMapping: aMapper aMapper for: self do: [ :mapping | mapping mapInstVars: #(#title #kind #hasDoc #grade #stars #isCollectorEdition #paidPrice #language #zone)] > >> Now do you have an idea why I got this other missing class mapping for >> bytestring? > > You must have done something wrong ;-) > > NeoJSONWriter toString: { 'string'. #symbol. 1. Float pi }. > > '["string","symbol",1,3.141592653589793]' I do not think so because my objects totally stupid. So this is why I was surprised. here are two exampleKlonoa <sampleInstance> ^ self new title: 'Klonoa'; ps2; threeStar; grade: '(16/15)'; paidPrice: 1 exampleWildArm <sampleInstance> ^ self new title: 'Wild Arm'; ps2; threeStar; grade: '(16/15)'; paidPrice: 1 only strings, numbers and symbols. this ByteString looked strange. > >> Stef >> >> On Fri, 16 Dec 2016 15:25:40 +0100, Sven Van Caekenberghe >> <sven(a)stfx.eu> wrote: >> >>> >>>> On 16 Dec 2016, at 15:23, stepharong <stepharong(a)free.fr> wrote: >>>> >>>> Ok I see. >>>> >>>> I was doing >>>> >>>> GameCollection >> neoJsonOn: neoJSONWriter >>>> >>>> neoJSONWriter >>>> writeObject: games >>>> >>>> >>>> GameItem >> neoJsonOn: neoJSONWriter >>>> self class instanceVariables >>>> do: [ :each | >>>> neoJSONWriter writeObject: (self instVarNamed: each) ] >>>> >>>> >>>> Now it did not work because byteString is not covered and I found >>>> that strange. >>>> >>>> I will use your solution. >>>> >>>> I read the section 5 before so there is something missing there. >>>> I will see how I can add an example. >>>> >>>> May be we should improve the class comment of mapper stating this >>>> class methods. >>> >>> It is right there, in NeoJSONMapper's class comment >>> >>> ... >>> A mapping can be specified explicitely on a mapper, or can be resolved >>> using the #neoJsonMapping: class method. >>> ... >>> >>> This is the superclass of both NeoJSONReader and NeoJSONWriter. >>> >>> But we should add it to the book chapter too. >>> >>>> Stef >>> >> >> >> -- >> Using Opera's mail client: http://www.opera.com/mail/ > -- Using Opera's mail client: http://www.opera.com/mail/

Dec. 16, 2016

Re: [Pharo-users] NeoJSON

by Sven Van Caekenberghe

> On 16 Dec 2016, at 15:47, stepharong <stepharong(a)free.fr> wrote: > > Ok it works :) Good. > And I read the class comment but I do not see it. Strange. In Neo-JSON-Core-SvenVanCaekenberghe.37 in the class comment of NeoJSONMapper last paragraph before the examples. > Now do you have an idea why I got this other missing class mapping for bytestring? You must have done something wrong ;-) NeoJSONWriter toString: { 'string'. #symbol. 1. Float pi }. '["string","symbol",1,3.141592653589793]' > Stef > > On Fri, 16 Dec 2016 15:25:40 +0100, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> >>> On 16 Dec 2016, at 15:23, stepharong <stepharong(a)free.fr> wrote: >>> >>> Ok I see. >>> >>> I was doing >>> >>> GameCollection >> neoJsonOn: neoJSONWriter >>> >>> neoJSONWriter >>> writeObject: games >>> >>> >>> GameItem >> neoJsonOn: neoJSONWriter >>> self class instanceVariables >>> do: [ :each | >>> neoJSONWriter writeObject: (self instVarNamed: each) ] >>> >>> >>> Now it did not work because byteString is not covered and I found that strange. >>> >>> I will use your solution. >>> >>> I read the section 5 before so there is something missing there. >>> I will see how I can add an example. >>> >>> May be we should improve the class comment of mapper stating this class methods. >> >> It is right there, in NeoJSONMapper's class comment >> >> ... >> A mapping can be specified explicitely on a mapper, or can be resolved using the #neoJsonMapping: class method. >> ... >> >> This is the superclass of both NeoJSONReader and NeoJSONWriter. >> >> But we should add it to the book chapter too. >> >>> Stef >> > > > -- > Using Opera's mail client: http://www.opera.com/mail/

Dec. 16, 2016

Re: [Pharo-users] NeoJSON

by stepharong

Ok it works :) And I read the class comment but I do not see it. Now do you have an idea why I got this other missing class mapping for bytestring? Stef On Fri, 16 Dec 2016 15:25:40 +0100, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> On 16 Dec 2016, at 15:23, stepharong <stepharong(a)free.fr> wrote: >> >> Ok I see. >> >> I was doing >> >> GameCollection >> neoJsonOn: neoJSONWriter >> >> neoJSONWriter >> writeObject: games >> >> >> GameItem >> neoJsonOn: neoJSONWriter >> self class instanceVariables >> do: [ :each | >> neoJSONWriter writeObject: (self instVarNamed: each) ] >> >> >> Now it did not work because byteString is not covered and I found that >> strange. >> >> I will use your solution. >> >> I read the section 5 before so there is something missing there. >> I will see how I can add an example. >> >> May be we should improve the class comment of mapper stating this class >> methods. > > It is right there, in NeoJSONMapper's class comment > > ... > A mapping can be specified explicitely on a mapper, or can be resolved > using the #neoJsonMapping: class method. > ... > > This is the superclass of both NeoJSONReader and NeoJSONWriter. > > But we should add it to the book chapter too. > >> Stef > -- Using Opera's mail client: http://www.opera.com/mail/

Dec. 16, 2016

Re: [Pharo-users] NeoJSON

by Sven Van Caekenberghe

> On 16 Dec 2016, at 15:23, stepharong <stepharong(a)free.fr> wrote: > > Ok I see. > > I was doing > > GameCollection >> neoJsonOn: neoJSONWriter > > neoJSONWriter > writeObject: games > > > GameItem >> neoJsonOn: neoJSONWriter > self class instanceVariables > do: [ :each | > neoJSONWriter writeObject: (self instVarNamed: each) ] > > > Now it did not work because byteString is not covered and I found that strange. > > I will use your solution. > > I read the section 5 before so there is something missing there. > I will see how I can add an example. > > May be we should improve the class comment of mapper stating this class methods. It is right there, in NeoJSONMapper's class comment ... A mapping can be specified explicitely on a mapper, or can be resolved using the #neoJsonMapping: class method. ... This is the superclass of both NeoJSONReader and NeoJSONWriter. But we should add it to the book chapter too. > Stef

Dec. 16, 2016

Re: [Pharo-users] NeoJSON

by stepharong

Ok I see. I was doing GameCollection >> neoJsonOn: neoJSONWriter neoJSONWriter writeObject: games GameItem >> neoJsonOn: neoJSONWriter self class instanceVariables do: [ :each | neoJSONWriter writeObject: (self instVarNamed: each) ] Now it did not work because byteString is not covered and I found that strange. I will use your solution. I read the section 5 before so there is something missing there. I will see how I can add an example. May be we should improve the class comment of mapper stating this class methods. Stef

Dec. 16, 2016