November 2018 - Pharo-users

Re: [Pharo-users] Tracking method in and out with MetaLinks

by Manuel Leuenberger

Awesome! I am looking forward to it. Cheers, Manuel > On 23 Nov 2018, at 14:59, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > >> On 23 Nov 2018, at 13:40, Manuel Leuenberger <leuenberger(a)inf.unibe.ch> wrote: >> >> Hi, >> >> I stumbled upon another MetaLink scenario that I am unsure how to implement. I want to track method invocations, with receiver, arguments, selector, and return value (maybe even signaled exception). I can track the method input with a MetaLink installed on an RBMethodNode like this: >> >> MetaLink new >> metaObject: [ :c | Transcript show: c receiver; show: c method selector; show: c arguments; cr ]; >> selector: #value:; >> arguments: #(context). >> >> and for returns with a MetaLink on RBReturnNodes like this: >> >> MetaLink new >> metaObject: [ :v | Transcript show: v; cr ]; >> selector: #value:; >> arguments: #(value) >> >> The problem is though, that not all methods have explicit returns, and some mix explicit returns and self returns. I tried installed an #after MetaLink on a RBMethodNode, but this fails in many cases. Is there any way that I can instrument a method and track receiver, selector, arguments, and returned value (even if self) at the same time? >> > > I am working now on making the #after work so that one can get with #value the return of the methodâ¦ > > I now have a version where it works for Message Sends correctly *and* were #after on Method works better (the compilation errors should be fixed). > > But #value for #after on Method needs some more workâ¦ soon! > > I will commit this intermediate step now. > > Marcus

Nov. 23, 2018

Re: [Pharo-users] Tracking method in and out with MetaLinks

by Marcus Denker

> On 23 Nov 2018, at 13:40, Manuel Leuenberger <leuenberger(a)inf.unibe.ch> wrote: > > Hi, > > I stumbled upon another MetaLink scenario that I am unsure how to implement. I want to track method invocations, with receiver, arguments, selector, and return value (maybe even signaled exception). I can track the method input with a MetaLink installed on an RBMethodNode like this: > > MetaLink new > metaObject: [ :c | Transcript show: c receiver; show: c method selector; show: c arguments; cr ]; > selector: #value:; > arguments: #(context). > > and for returns with a MetaLink on RBReturnNodes like this: > > MetaLink new > metaObject: [ :v | Transcript show: v; cr ]; > selector: #value:; > arguments: #(value) > > The problem is though, that not all methods have explicit returns, and some mix explicit returns and self returns. I tried installed an #after MetaLink on a RBMethodNode, but this fails in many cases. Is there any way that I can instrument a method and track receiver, selector, arguments, and returned value (even if self) at the same time? > I am working now on making the #after work so that one can get with #value the return of the methodâ¦ I now have a version where it works for Message Sends correctly *and* were #after on Method works better (the compilation errors should be fixed). But #value for #after on Method needs some more workâ¦ soon! I will commit this intermediate step now. Marcus

Nov. 23, 2018

Re: [Pharo-users] can't debug TinyBlog in the Pharo MOOC

by Cyril Ferlicot

On Fri, Nov 23, 2018 at 1:25 PM iu136 via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > You were right Esteban, finally I fixed it by manually executing the code > below at Playground: > > | repository | > repository := VOMongoRepository database: 'tinyblog'. > repository enableSingleton . > > Even thought I was putting the above code at initialize method of TBMBlog, > but I don't know why its never get executed! Hi, Class initialisation methods are executed at loading. If you write the method the first time it will not execute it by default. > Thank you very much for your help! > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > -- Cyril Ferlicot https://ferlicot.fr

Nov. 23, 2018

Tracking method in and out with MetaLinks

by Manuel Leuenberger

Hi, I stumbled upon another MetaLink scenario that I am unsure how to implement. I want to track method invocations, with receiver, arguments, selector, and return value (maybe even signaled exception). I can track the method input with a MetaLink installed on an RBMethodNode like this: MetaLink new metaObject: [ :c | Transcript show: c receiver; show: c method selector; show: c arguments; cr ]; selector: #value:; arguments: #(context). and for returns with a MetaLink on RBReturnNodes like this: MetaLink new metaObject: [ :v | Transcript show: v; cr ]; selector: #value:; arguments: #(value) The problem is though, that not all methods have explicit returns, and some mix explicit returns and self returns. I tried installed an #after MetaLink on a RBMethodNode, but this fails in many cases. Is there any way that I can instrument a method and track receiver, selector, arguments, and returned value (even if self) at the same time? Cheers, Manuel

Nov. 23, 2018

[ANN] Next Pharo Sprint: Nov 30

by Marcus Denker

We will organize a Pharo sprint / Moose dojo Nov 30, starting at 10:00am. (Local Time Paris). Goals of this sprint: â¢ Pharo 7 issues Remote Sprint: Remotely, you can join us on Discord. During the sprint, we synchronize local and remote Pharo sprinters: http://pharo.org/contribute-events Known Local Sprint meetings Lille/France: It will be at the Inria Lille, Building B, third floor (RMoD offices). As the building is not open to the public, please contact us before if you plan to come https://association.pharo.org/event-2973626

Nov. 23, 2018

Re: can't debug TinyBlog in the Pharo MOOC

by iu136

> Which again, should means you never executed initializeLocalhostMongoDB > method. > Can you try doing: > > TBBlock initializeLocalhostMongoDB. > > Esteban You were right Esteban, finally I fixed it by manually executing the code below at Playground: | repository | repository := VOMongoRepository database: 'tinyblog'. repository enableSingleton . Even thought I was putting the above code at initialize method of TBMBlog, but I don't know why its never get executed! Thank you very much for your help! -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Nov. 23, 2018

Re: [Pharo-users] can't debug TinyBlog in the Pharo MOOC

by Esteban Lorenzano

> On 22 Nov 2018, at 21:48, iu136 via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > > From: iu136 <iu136(a)yahoo.com> > Subject: Re: can't debug TinyBlog in the Pharo MOOC > Date: 22 November 2018 at 21:48:52 CET > To: pharo-users(a)lists.pharo.org > > > EstebanLM wrote >> Hi, >> >> You are missing to initialise the Voyage repository. >> I donât know how is explained in the Mooc, but you will probably need to >> do something like: >> >> VOMemoryRepository new enableSingleton. >> >> Cheers, >> Esteban > > Hi Esteban. > > actually I'm using an External Mongo database and in the MOOC the > initialization of Voyage Mongo repository, is done like: > > TBBlog class >> initializeLocalhostMongoDB > | repository | > repository := VOMongoRepository database: 'tinyblog'. > repository enableSingleton. > > TBBlog class >> reset > self initializeLocalhostMongoDB > > and in my code I'm doing exactly like above. but interestingly when I wanted > to reset the cache of Voyage by: > VORepository current reset > > again I've got another Error saying: "MessageNotUnderstood: receiver of > "reset" is nillâ. Which again, should means you never executed initializeLocalhostMongoDB method. Can you try doing: TBBlock initializeLocalhostMongoDB. Esteban > > thanks anyway! > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > > >

Nov. 23, 2018

Re: [Pharo-users] [ANN] JSON schema implementation

by Esteban Maringolo

Thank you Norbert and IID. Another brick in the bridge towards mainstream. :) Regards, El jue., 22 nov. 2018 a las 18:11, Sven Van Caekenberghe (<sven(a)stfx.eu>) escribiÃ³: > > Nice. Another piece of the puzzle. Thank you. > > > On 22 Nov 2018, at 17:56, Norbert Hartl <norbert(a)hartl.name> wrote: > > > > JSONSchema > > =========== > > > > This is an implementation of JSON Schema for the pharo language. It is used to define the structure and values of a JSON string and to validate it. The schema itself can be externalized for being consumed by a third party. > > > > I like to announce the availability of a JSON schema implementation for pharo. As part of my implementation of OpenAPI (which is to be released a bit later) I factored out the JSON schema part into its own repository because I think it is useful. I release it even it is not really finished. Code is mostly undocumented and a lot of features are missing from the full spec. I will improve it slowly and add features as I need them or they being requested > > > > Hope you like it! > > > > Norbert > > > > ==== > > > > The documentation so far (from https://github.com/zweidenker/JSONSchema) > > > > It can be loaded by downloading it in pharo via > > > > Metacello new > > repository: 'github://zweidenker/JSONSchema'; > > baseline: #JSONSchema; > > load > > > > Defining a schema > > ------------------------- > > > > These are the expression to create a schema model inside pharo. > > > > schema := { > > #name -> JSONSchema string. > > #dateAndTime -> (JSONSchema stringWithFormat: 'date-time'). > > #numberOfPets -> JSONSchema number } asJSONSchema. > > > > > > defines as schema that can parse the following JSON: > > > > jsonString := '{ > > "name" : "John Doe", > > "dateAndTime" : "1970-01-01T14:00:00", > > "numberOfPets" : 3 > > }'. > > > > Reading/Writing a value using a schema > > ------------------------------------------------------ > > > > To parse the value from JSON we only need to invoke: > > > > value := schema read: jsonString > > > > The object in value will have name as a string, dateAndTime as a DateAndTime object and numberOfPets as a SmallInteger object. > > > > The schema can also be used to write out the value as JSON. This is especially useful if we want to ensure that only valid JSON is written. For this invoke > > > > jsonString := schema write: value. > > > > Serialize/Materialize a schema > > ---------------------------------------- > > > > Addtionally to reading and writing objects a schema can be serialized to string. > > > > schemaString := NeoJSONWriter toStringPretty: schema. > > > > gives > > > > { > > "type" : "object", > > "properties" : { > > "name" : { > > "type" : "string" > > }, > > "numberOfPets" : { > > "type" : "number" > > }, > > "dateAndTime" : { > > "type" : "string", > > "format" : "date-time" > > } > > } > > } > > > > > > If we would get a schema as string we can instantiate by invoking > > > > schema := JSONSchema fromString: schemaString. > > > > Nested schemas > > ----------------------- > > > > Schemas can be nested in any depth. And it can be specified by using the literal Array syntax. > > > > schema := { > > #name -> JSONSchema string. > > #address -> { > > #street -> JSONSchema string. > > #number -> JSONSchema number > > } } asJSONSchema > > > > Constraints > > --------------- > > > > JSON Schema has a defined set of constraints that can be specified. E.g. for a number the inerval of the value can be specified by > > > > numberSchema := JSONSchema number. > > numberSchema interval > > minimum: 1; > > exclusiveMaximum: 100 > > > > constraining the number value to be greater or equal to 1 and smaller than 100. > > > >

Nov. 23, 2018

Re: [Pharo-users] [ANN] JSON schema implementation

by Francisco Ortiz PeÃ±aloza

This is great. Thanks! On Thu, 22 Nov 2018 at 18:10 Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Nice. Another piece of the puzzle. Thank you. > > > On 22 Nov 2018, at 17:56, Norbert Hartl <norbert(a)hartl.name> wrote: > > > > JSONSchema > > =========== > > > > This is an implementation of JSON Schema for the pharo language. It is > used to define the structure and values of a JSON string and to validate > it. The schema itself can be externalized for being consumed by a third > party. > > > > I like to announce the availability of a JSON schema implementation for > pharo. As part of my implementation of OpenAPI (which is to be released a > bit later) I factored out the JSON schema part into its own repository > because I think it is useful. I release it even it is not really finished. > Code is mostly undocumented and a lot of features are missing from the full > spec. I will improve it slowly and add features as I need them or they > being requested > > > > Hope you like it! > > > > Norbert > > > > ==== > > > > The documentation so far (from https://github.com/zweidenker/JSONSchema) > > > > It can be loaded by downloading it in pharo via > > > > Metacello new > > repository: 'github://zweidenker/JSONSchema'; > > baseline: #JSONSchema; > > load > > > > Defining a schema > > ------------------------- > > > > These are the expression to create a schema model inside pharo. > > > > schema := { > > #name -> JSONSchema string. > > #dateAndTime -> (JSONSchema stringWithFormat: 'date-time'). > > #numberOfPets -> JSONSchema number } asJSONSchema. > > > > > > defines as schema that can parse the following JSON: > > > > jsonString := '{ > > "name" : "John Doe", > > "dateAndTime" : "1970-01-01T14:00:00", > > "numberOfPets" : 3 > > }'. > > > > Reading/Writing a value using a schema > > ------------------------------------------------------ > > > > To parse the value from JSON we only need to invoke: > > > > value := schema read: jsonString > > > > The object in value will have name as a string, dateAndTime as a > DateAndTime object and numberOfPets as a SmallInteger object. > > > > The schema can also be used to write out the value as JSON. This is > especially useful if we want to ensure that only valid JSON is written. For > this invoke > > > > jsonString := schema write: value. > > > > Serialize/Materialize a schema > > ---------------------------------------- > > > > Addtionally to reading and writing objects a schema can be serialized to > string. > > > > schemaString := NeoJSONWriter toStringPretty: schema. > > > > gives > > > > { > > "type" : "object", > > "properties" : { > > "name" : { > > "type" : "string" > > }, > > "numberOfPets" : { > > "type" : "number" > > }, > > "dateAndTime" : { > > "type" : "string", > > "format" : "date-time" > > } > > } > > } > > > > > > If we would get a schema as string we can instantiate by invoking > > > > schema := JSONSchema fromString: schemaString. > > > > Nested schemas > > ----------------------- > > > > Schemas can be nested in any depth. And it can be specified by using the > literal Array syntax. > > > > schema := { > > #name -> JSONSchema string. > > #address -> { > > #street -> JSONSchema string. > > #number -> JSONSchema number > > } } asJSONSchema > > > > Constraints > > --------------- > > > > JSON Schema has a defined set of constraints that can be specified. E.g. > for a number the inerval of the value can be specified by > > > > numberSchema := JSONSchema number. > > numberSchema interval > > minimum: 1; > > exclusiveMaximum: 100 > > > > constraining the number value to be greater or equal to 1 and smaller > than 100. > > > > > -- Sent from the past

Nov. 22, 2018

Re: [Pharo-users] [ANN] JSON schema implementation

by Sven Van Caekenberghe

Nice. Another piece of the puzzle. Thank you. > On 22 Nov 2018, at 17:56, Norbert Hartl <norbert(a)hartl.name> wrote: > > JSONSchema > =========== > > This is an implementation of JSON Schema for the pharo language. It is used to define the structure and values of a JSON string and to validate it. The schema itself can be externalized for being consumed by a third party. > > I like to announce the availability of a JSON schema implementation for pharo. As part of my implementation of OpenAPI (which is to be released a bit later) I factored out the JSON schema part into its own repository because I think it is useful. I release it even it is not really finished. Code is mostly undocumented and a lot of features are missing from the full spec. I will improve it slowly and add features as I need them or they being requested > > Hope you like it! > > Norbert > > ==== > > The documentation so far (from https://github.com/zweidenker/JSONSchema) > > It can be loaded by downloading it in pharo via > > Metacello new > repository: 'github://zweidenker/JSONSchema'; > baseline: #JSONSchema; > load > > Defining a schema > ------------------------- > > These are the expression to create a schema model inside pharo. > > schema := { > #name -> JSONSchema string. > #dateAndTime -> (JSONSchema stringWithFormat: 'date-time'). > #numberOfPets -> JSONSchema number } asJSONSchema. > > > defines as schema that can parse the following JSON: > > jsonString := '{ > "name" : "John Doe", > "dateAndTime" : "1970-01-01T14:00:00", > "numberOfPets" : 3 > }'. > > Reading/Writing a value using a schema > ------------------------------------------------------ > > To parse the value from JSON we only need to invoke: > > value := schema read: jsonString > > The object in value will have name as a string, dateAndTime as a DateAndTime object and numberOfPets as a SmallInteger object. > > The schema can also be used to write out the value as JSON. This is especially useful if we want to ensure that only valid JSON is written. For this invoke > > jsonString := schema write: value. > > Serialize/Materialize a schema > ---------------------------------------- > > Addtionally to reading and writing objects a schema can be serialized to string. > > schemaString := NeoJSONWriter toStringPretty: schema. > > gives > > { > "type" : "object", > "properties" : { > "name" : { > "type" : "string" > }, > "numberOfPets" : { > "type" : "number" > }, > "dateAndTime" : { > "type" : "string", > "format" : "date-time" > } > } > } > > > If we would get a schema as string we can instantiate by invoking > > schema := JSONSchema fromString: schemaString. > > Nested schemas > ----------------------- > > Schemas can be nested in any depth. And it can be specified by using the literal Array syntax. > > schema := { > #name -> JSONSchema string. > #address -> { > #street -> JSONSchema string. > #number -> JSONSchema number > } } asJSONSchema > > Constraints > --------------- > > JSON Schema has a defined set of constraints that can be specified. E.g. for a number the inerval of the value can be specified by > > numberSchema := JSONSchema number. > numberSchema interval > minimum: 1; > exclusiveMaximum: 100 > > constraining the number value to be greater or equal to 1 and smaller than 100. >

Nov. 22, 2018