March 2016 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Ideas of web services that I could script in a couple of lines?

by phil＠highoctane.be

Wonderful. You are my hero :-) Phil On Tue, Mar 15, 2016 at 5:14 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > On 14 Mar 2016, at 09:33, phil(a)highoctane.be wrote: > > > > 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. > > I added a class facade STONJSON to make this more explicit (with tests): > > === > Name: STON-Core-SvenVanCaekenberghe.70 > Author: SvenVanCaekenberghe > Time: 15 March 2016, 5:07:59.236863 pm > UUID: c990d2ab-a407-4935-b489-c55139fdd665 > Ancestors: STON-Core-SvenVanCaekenberghe.69 > > Improve class comments > > Add STONJSON facade class to make it more explicit that you can use STON > for simple JSON parsing and generation > > Add STONJSONTests to test JSON compatibility > === > Name: STON-Tests-SvenVanCaekenberghe.62 > Author: SvenVanCaekenberghe > Time: 15 March 2016, 5:08:19.634401 pm > UUID: 097090ae-a1ca-4401-86b0-07d7d446a9dc > Ancestors: STON-Tests-SvenVanCaekenberghe.61 > > Improve class comments > > Add STONJSON facade class to make it more explicit that you can use STON > for simple JSON parsing and generation > > Add STONJSONTests to test JSON compatibility > === > > > This is the STON class comment > > > === > STON implements serialization and materialization using the Smalltalk > Object Notation format. > > I am a class side facade offering a high level API to write and read > objects using STON. > > U s a g e > > Basic operations > > #toString: > #fromString: > > STON toString: DisplayScreen boundingBox. > STON fromString: > 'Rectangle{#origin:Point[0,0],#corner:Point[1920,1030]}'. > > STON toString: { DateAndTime now. Float pi. 1 to: 10 by: 2. 3 days }. > STON fromString: > '[DateAndTime[''2016-03-15T13:57:59.462422+01:00''],3.141592653589793,Interval{#start:1,#stop:10,#step:2},Duration{#nanos:0,#seconds:259200}]' > > You can also read from or write to streams > > #fromStream: > #put:onStream: > > There is also the option to do pretty printing (indenting, multi line > output) > > #toStringPretty: > #put:onStreamPretty: > > STON is more or less a superset of JSON and is backwards compatible with > JSON while parsing, and can be compatible with it while writing. The > important differences (and the whole reason why STON exists in the first > place) are > > - class information (except for lists (Array) and maps (Dictionary)) > - proper handling of shared and circular references > - more Smalltalk like syntax (Symbols with #, single qouted Strings, nil > instead of null) > - more defined special types (Date, Time, DataAndTime, ByteArray, Point) > > Parsing JSON is done using #fromString: or #fromStream: with the results > being composed of Arrays and Dictionaries. > > Writing objects as JSON is done using: > > #toJsonString[Pretty]: > #put:asJsonOnStream[Pretty]: > > Note that you can only write Arrays and Dictionaries ! > > For a much more sophisticated JSON parser/writer implementation, have a > look at NeoJSON. > > Like JSON, STON does not allow for comments. However, a preprocessor > option can skip C style comments before parsing. > > I also define some contants used in the implementation: the class used as > list, map and association, as well as the optional class name key (used > when reading objects using an unknown class). > > > I m p l e m e n t a t i o n > > The 2 key methods are > > #stonOn: > #fromSton: > > which work together with STONWriter and STONReader; read their class > comments for all configuration options (you can use the #reader and #writer > methods to avoid referring to these classes directly). > > Several methods are used to support and/or control the implementation > > #stonName - defines the external name for a class > #stonAllInstVarNames - defines which instance variable to write > #stonContainSubObjects - shortcut looking into objects for subobjects > #stonShouldWriteNilInstVars - option to skip writing nil valued instance > variables > > > S y n t a x > > value > primitive-value > object-value > reference > nil > primitive-value > number > true > false > symbol > string > object-value > object > map > list > object > classname map > classname list > reference > @ int-index-previous-object-value > map > {} > { members } > members > pair > pair , members > pair > string : value > symbol : value > number : value > list > [] > [ elements ] > elements > value > value , elements > string > '' > ' chars ' > chars > char > char chars > char > any-printable-ASCII-character- > except-'-"-or-\ > \' > \" > \\ > \/ > \b > \f > \n > \r > \t > \u four-hex-digits > symbol > # chars-limited > # ' chars ' > chars-limited > char-limited > char-limited chars-limited > char-limited > a-z A-Z 0-9 - _ . / > classname > uppercase-alpha-char alphanumeric-char > number > int > int frac > int exp > int frac exp > int > digit > digit1-9 digits > - digit > - digit1-9 digits > frac > . digits > exp > e digits > digits > digit > digit digits > e > e > e+ > e- > E > E+ > E- > === > > > And this is the STONJSON class comment > > > === > I am STONJSON, a class side facade to use STON as a simple JSON > parser/writer. > > STON is more or less a superset of JSON and is backwards compatible with > JSON while parsing, and can be compatible with it while writing. The > important differences (and the whole reason why STON exists in the first > place) are > > - class information (except for lists (Array) and maps (Dictionary)) > - proper handling of shared and circular references > - more Smalltalk like syntax (Symbols with #, single qouted Strings, nil > instead of null) > - more defined special types (Date, Time, DataAndTime, ByteArray, Point) > > Parsing JSON is done using > > #fromString: > #fromStream: > > with the results being composed of Arrays and Dictionaries. > > Writing objects as JSON is done using > > #toString[Pretty]: > #put:onStream[Pretty]: > > Note that you can only write Arrays and Dictionaries ! Shared and circular > references will be noted and signalled using an exception. > > E x a m p l e s > > STONJSON toString: { 1. -1. Float pi. true. 'JSON' }. > STONJSON fromString: '[1,-1,3.141592653589793,true,"JSON"]'. > > STONJSON toStringPretty: { #foo->1. #bar->2 } asDictionary. > STONJSON fromString: > '{"foo":1,"bar":2,"sub":{"a":true,"b":false},"flags":[1,8,32]}'. > > For a much more sophisticated JSON parser/writer implementation, have a > look at NeoJSON. > === > > > What would be a good way to do that? I wonder. > > Maybe we need some kind of central registry, maybe. > > Because the main goal would be to able to switch one implementation for > another, but that would only work if their interfaces and behaviour match. > Now, different implementations might share some API, but certainly will > differ in other places, because they each offer different features. > > Sven > > > > > >

March 15, 2016

Re: [Pharo-users] Ideas of web services that I could script in a couple of lines?

by Sven Van Caekenberghe

> On 14 Mar 2016, at 09:33, phil(a)highoctane.be wrote: > > 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. I added a class facade STONJSON to make this more explicit (with tests): === Name: STON-Core-SvenVanCaekenberghe.70 Author: SvenVanCaekenberghe Time: 15 March 2016, 5:07:59.236863 pm UUID: c990d2ab-a407-4935-b489-c55139fdd665 Ancestors: STON-Core-SvenVanCaekenberghe.69 Improve class comments Add STONJSON facade class to make it more explicit that you can use STON for simple JSON parsing and generation Add STONJSONTests to test JSON compatibility === Name: STON-Tests-SvenVanCaekenberghe.62 Author: SvenVanCaekenberghe Time: 15 March 2016, 5:08:19.634401 pm UUID: 097090ae-a1ca-4401-86b0-07d7d446a9dc Ancestors: STON-Tests-SvenVanCaekenberghe.61 Improve class comments Add STONJSON facade class to make it more explicit that you can use STON for simple JSON parsing and generation Add STONJSONTests to test JSON compatibility === This is the STON class comment === STON implements serialization and materialization using the Smalltalk Object Notation format. I am a class side facade offering a high level API to write and read objects using STON. U s a g e Basic operations #toString: #fromString: STON toString: DisplayScreen boundingBox. STON fromString: 'Rectangle{#origin:Point[0,0],#corner:Point[1920,1030]}'. STON toString: { DateAndTime now. Float pi. 1 to: 10 by: 2. 3 days }. STON fromString: '[DateAndTime[''2016-03-15T13:57:59.462422+01:00''],3.141592653589793,Interval{#start:1,#stop:10,#step:2},Duration{#nanos:0,#seconds:259200}]' You can also read from or write to streams #fromStream: #put:onStream: There is also the option to do pretty printing (indenting, multi line output) #toStringPretty: #put:onStreamPretty: STON is more or less a superset of JSON and is backwards compatible with JSON while parsing, and can be compatible with it while writing. The important differences (and the whole reason why STON exists in the first place) are - class information (except for lists (Array) and maps (Dictionary)) - proper handling of shared and circular references - more Smalltalk like syntax (Symbols with #, single qouted Strings, nil instead of null) - more defined special types (Date, Time, DataAndTime, ByteArray, Point) Parsing JSON is done using #fromString: or #fromStream: with the results being composed of Arrays and Dictionaries. Writing objects as JSON is done using: #toJsonString[Pretty]: #put:asJsonOnStream[Pretty]: Note that you can only write Arrays and Dictionaries ! For a much more sophisticated JSON parser/writer implementation, have a look at NeoJSON. Like JSON, STON does not allow for comments. However, a preprocessor option can skip C style comments before parsing. I also define some contants used in the implementation: the class used as list, map and association, as well as the optional class name key (used when reading objects using an unknown class). I m p l e m e n t a t i o n The 2 key methods are #stonOn: #fromSton: which work together with STONWriter and STONReader; read their class comments for all configuration options (you can use the #reader and #writer methods to avoid referring to these classes directly). Several methods are used to support and/or control the implementation #stonName - defines the external name for a class #stonAllInstVarNames - defines which instance variable to write #stonContainSubObjects - shortcut looking into objects for subobjects #stonShouldWriteNilInstVars - option to skip writing nil valued instance variables S y n t a x value primitive-value object-value reference nil primitive-value number true false symbol string object-value object map list object classname map classname list reference @ int-index-previous-object-value map {} { members } members pair pair , members pair string : value symbol : value number : value list [] [ elements ] elements value value , elements string '' ' chars ' chars char char chars char any-printable-ASCII-character- except-'-"-or-\ \' \" \\ \/ \b \f \n \r \t \u four-hex-digits symbol # chars-limited # ' chars ' chars-limited char-limited char-limited chars-limited char-limited a-z A-Z 0-9 - _ . / classname uppercase-alpha-char alphanumeric-char number int int frac int exp int frac exp int digit digit1-9 digits - digit - digit1-9 digits frac . digits exp e digits digits digit digit digits e e e+ e- E E+ E- === And this is the STONJSON class comment === I am STONJSON, a class side facade to use STON as a simple JSON parser/writer. STON is more or less a superset of JSON and is backwards compatible with JSON while parsing, and can be compatible with it while writing. The important differences (and the whole reason why STON exists in the first place) are - class information (except for lists (Array) and maps (Dictionary)) - proper handling of shared and circular references - more Smalltalk like syntax (Symbols with #, single qouted Strings, nil instead of null) - more defined special types (Date, Time, DataAndTime, ByteArray, Point) Parsing JSON is done using #fromString: #fromStream: with the results being composed of Arrays and Dictionaries. Writing objects as JSON is done using #toString[Pretty]: #put:onStream[Pretty]: Note that you can only write Arrays and Dictionaries ! Shared and circular references will be noted and signalled using an exception. E x a m p l e s STONJSON toString: { 1. -1. Float pi. true. 'JSON' }. STONJSON fromString: '[1,-1,3.141592653589793,true,"JSON"]'. STONJSON toStringPretty: { #foo->1. #bar->2 } asDictionary. STONJSON fromString: '{"foo":1,"bar":2,"sub":{"a":true,"b":false},"flags":[1,8,32]}'. For a much more sophisticated JSON parser/writer implementation, have a look at NeoJSON. === > What would be a good way to do that? I wonder. Maybe we need some kind of central registry, maybe. Because the main goal would be to able to switch one implementation for another, but that would only work if their interfaces and behaviour match. Now, different implementations might share some API, but certainly will differ in other places, because they each offer different features. Sven

March 15, 2016

Re: [Pharo-users] Ideas of web services that I could script in a couple of lines?

by Sven Van Caekenberghe

> On 14 Mar 2016, at 07:25, stepharo <stepharo(a)free.fr> wrote: > > >>> On 13 Mar 2016, at 22:42, Henrik Nergaard <henrik.nergaard(a)uia.no> wrote: >>> >>> Correct, I used that for the example since it is by default in the Image . >> And that is a pity, IMHO, it sneaked in, while others have asked for NeoJSON to be included in the past ;-) > > Sven is STON able to replace MCFileTreeJsonParser > if so can you open a bug entry and we kill it. You know my point of view of such parsers.... https://pharo.fogbugz.com/f/cases/17822/Use-STON-for-JSON-parsing-in-MC-Fil… > Stef >> >> Anyway, STON, which is also part of the base image can parse JSON just as well. >> >> STON fromString: '[42, {"JSON":true}, -1.5]'. >> >> You can also generate JSON. >> >> STON toJsonStringPretty: { 42. { 'JSON'->true } asDictionary. -1.5 }. >> >> STON toJsonString: { 42. { 'JSON'->true } asDictionary. -1.5 }. >> >>> Best regards, >>> Henrik >>> >>> -----Original Message----- >>> From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of stepharo >>> Sent: Sunday, March 13, 2016 10:34 PM >>> To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> >>> Subject: Re: [Pharo-users] Ideas of web services that I could script in a couple of lines? >>> >>> Henrik >>> >>> do you use MCFileTreeJsonParser >>> just because this was just the JSON parser you got at hand? >>> >>> Stef >>> >>> Le 13/3/16 22:24, Henrik Nergaard a Ã©crit : >>>> Accessing the Nominatim service: http://wiki.openstreetmap.org/wiki/Nominatim . >>>> >>>> http://ws.stfx.eu/ATBXE2DN83CW >>>> >>>> Best regards, >>>> Henrik >>>> >>>> -----Original Message----- >>>> From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of stepharo >>>> Sent: Sunday, March 13, 2016 9:52 PM >>>> To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> >>>> Subject: [Pharo-users] Ideas of web services that I could script in a couple of lines? >>>> >>>> Hi hernan and others >>>> >>>> I'm looking for ideas of simple services capital, dictionaries.... >>>> forecast that I could access using Zinc in a couple of lines. >>>> >>>> This is for challenges that I'm writing for the mooc. >>>> Stef >>>> >>>> >>>> >>> >> >> > >

March 15, 2016

Re: [Pharo-users] Beginner's question on morphs

by Markus Stumptner

Thanks! Extremely useful answers. Cheers Markus

March 15, 2016

[Mongo] Creating MongoTimeStamp

by Martin Dias

Hi, This email is related to Mongo project [1]. As MongoDb documentation [2] states: "BSON has a special timestamp type for *internal* MongoDB use and is not > associated with the regular Datetype. Timestamp values are a 64 bit value > where: > - the first 32 bits are a time_t value (seconds since the Unix epoch) > - the second 32 bits are an incrementing ordinal for operations within a > given second." Now, our Mongo bindings [1] convert this MongoDb's internal type to Pharo's TimeStamp (i.e. the subclass of DateAndTime) with two problems: - it's a wrong: the 2 parts of 32 bits are converted as 64 bits of milliseconds - it produces a warning in latest Pharo [3]: TimeStamp has been removed so extension methods cannot be installed. That's why I'm creating MongoTimeStamp, and changing BSON marshaling from: BSON>>nextTimestamp ^self nextDateAndTime asTimeStamp to: BSON>>nextTimestamp ^MongoTimeStamp value: self nextInt64 (similar for writing). This solution was idea of Esteban and Norbert, and discussed in the issue tracker of Voyage [3]. Mongo talk team, please tell me if you don't agree. Regards, Martin 1. http://smalltalkhub.com/#!/~MongoTalkTeam/mongotalk 2: https://docs.mongodb.org/manual/reference/bson-types/#timestamps 3: https://github.com/estebanlm/voyage/issues/11

March 15, 2016

Interleaving strings

by Andy Burnett

I have two strings, which are typically of different lengths, and I want to interleave them, i.e.: 'abcdefg' interleaveWith: '123' Would produce 'a1b2c3defg' I know how to write this procedurally, but I have been very impressed by what Sven shows in his Medium articles, so I wondered if there is any existing mechanism that would allow me to solve this elegantly? with:collection: almost does it, but the collections have to be the same size. Cheers Andy

March 15, 2016

Re: [Pharo-users] distributed peer2peer sharing app in Pharo

by cdegroot

A bit late - just got notified that this was discussed. I wrote most of the P2P code of that project; I'm not doing a lot of Smalltalk anymore, so the code is sort of orphaned, but I'd be more than willing to help advise people on how to use it. The conclusion that this library is specifically made to work under very adverse circumstances is correct. The project at hand, "Digital Society of the Past", was meant to create a P2P network of historians (amateur and professional) exchanging their archives through this package. So our main use case was people behind crappy cable connections :-). So if your focus is overlay networks with gossip-style protocols, I'd probably look at something like Hashicorp's Serf instead (link it in or port it); if you really want to do napster-style file sharing, this library may be a decent starting point. Hth, Cees (ping me preferably on my personal mail, casedeg at everyone's favorite email provider, Gmail, because I'm often way lax when it comes to catching up with mailing ists). -- View this message in context: http://forum.world.st/distributed-peer2peer-sharing-app-in-Pharo-tp4855144p… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

March 14, 2016

Re: [Pharo-users] Magritte Tutorial [Draft]

by stepharo

Thanks Pay attention this is a real draft Le 13/3/16 23:40, basilmir a Ã©crit : > Tried to access the link and it was dead. Apparently the name got reversed > along the way, walking the ci did the job. > > https://ci.inria.fr/pharo-contribution/view/Books/job/Magritte/lastSuccessf… > -- is not dead > > https://ci.inria.fr/pharo-contribution/view/Books/job/Magritte/lastSuccessf… > -- works > > > > -- > View this message in context: http://forum.world.st/Magritte-Tutorial-Draft-tp4866792p4884387.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

March 14, 2016

Re: [Pharo-users] Some info (was: How to access XML tag name?)

by stepharo

Le 14/3/16 08:47, monty a Ã©crit : > To handle character data (the "b" in "<a>b</a>"), use characters:. But know it's sent multiple times for an element if its character data is separated by other markup like '<a>b<c/>d</a>' (the new comment explains this). > > SAX parsing usually ends up needing a stack to track elements and their character data and is tedious but more efficient than DOM. Oh yes :) > > You can't use XPath without DOM, but there's XMLParserStAX, a newer alternative to XMLPullParser that supports building partial DOM trees. Like XMLPullParser, it treats the document as a stream of event (StAX) objects you can "pull" from using a stream protocol (next, peek, atEnd, and others), but it also has messages like nextNode to construct a DOM tree out of the next event(s). You can use XPath on that. Thanks I will continue my little experiment with Films and OPAX so that I get the feel. After I would like to see how I can build importers based on visitors on top of dom. Stef > >

March 14, 2016

Changing version of a dependency of a dependency

by Peter UhnÃ¡k

How do I change the loaded version of a dependency other dependency is loading? Imagine the following scenario: I have ProjectXXX that depends on ProjectYYY, and projectYYY depends on ProjectZZZ. Now normally all the dependencies are directed to the master branch. Now what I would like to do is to "lock" the version in BaselineOfXXX for both YYY and ZZZ. So when project XXX is loaded, then instead github://projectYYY:development, and github://projectZZZ:development will be loaded. Can I do that without changing the baseline of ProjectYYY? Thanks, Peter â

March 14, 2016