February 2019 - Pharo-users

How to test a new Iceberg baseline?

by Tim Mackinnon

How does one go about testing an Iceberg/metacello baseline? Two parts to this actually - I want to check one under my control - and am wondering if there is a lint checker or some way to tell me what it will load (without having to check it in and try. Or if you do this - can you test loading from a branch? Similarly - if I want to try improving a baseline in another project - is there an easy way to do this (in this case, I canât really check it in - or I suppose I can fork all the dependencies and put them all in branches - but then how do convince each part of the chain to load from my forkâ¦ this sounds like a world of pain). So any tips? Tim

Feb. 22, 2019

Re: [Pharo-users] Interval form: x to: y when x > y - or how to count down...

by Konrad Hinsen

On 22/02/2019 15:57, Tim Mackinnon wrote: > I've just been caught out with Intervals - why can't you do: > 5 to: 1 do: [ :i | Transcript show: i printString] (eg a negative interval)? > > if you want to iterate down a series of numbers do you really have to do: > 5 to: 1 by: -1 do: [â¦ > > I always assumed that if x > y the step was automatically -1 (but its not). Expectations are obviously personal, but as far as I am concerned, I'd expect to see the behavior that Pharo implements. If you don't specify by:, you get a default value of 1. That's much simpler than a default value depending on the bounds of the interval. Konrad.

Feb. 22, 2019

Interval form: x to: y when x > y - or how to count down...

by Tim Mackinnon

I've just been caught out with Intervals - why can't you do: 5 to: 1 do: [ :i | Transcript show: i printString] (eg a negative interval)? if you want to iterate down a series of numbers do you really have to do: 5 to: 1 by: -1 do: [â¦ I always assumed that if x > y the step was automatically -1 (but its not). I asked on Discord - and someone pointed out that if you use variables it could be ambiguous - but is it really? I donât know if other smalltalks do it this way (I vaguely recall Dolphin going down, but not sure). Either way the Interval comment should mention this - and Iâll correct it when I get the wisdom of the crowd here. Tim

Feb. 22, 2019

What does the Package and Sub-Package comment do?

by Tim Mackinnon

Hi - I notice that you can sort of put comments on packages - but Iâm not sure if this is working or if its supposed to work? When I type something it seems to create and extra Manifest tag, and then the comment that I type seems to be the same for the package and all of its sub tags? Is this a work in progress? Should Calypso even show a comment for the tags (or is it read only for them - as its the parent). Iâm just not clear on what it does, and whether I can programmatically add stuff to it or not? (I was thinking for exercism to store exercise information there - but maybe I will stick to the test class comment) Tim

Feb. 22, 2019

Re: [Pharo-users] Embedding object properties in NeoJSON mappings

by Esteban Maringolo

Hi, El vie., 22 feb. 2019 a las 7:55, Sven Van Caekenberghe (<sven(a)stfx.eu>) escribiÃ³: > > On 22 Feb 2019, at 02:05, Esteban Maringolo <emaringolo(a)gmail.com> wrote: > > Am I stretching it too much? :) > > Yes, this is out of the scope of NeoJSON. > > As you know, JSON is strictly limited and kept simple, by design. > Things people do to shoehorn objects, classes, types, ids, collections, references, etc on to it are exactly that, hacks on top. > There are many ways to try to do any of this. I though so. :) > What you are doing now, a two pass approach, is what I would do too: first use NeoJSON > to get a standard structure (maybe use NeoJSONObject for simplicity), > next do some extra work - and vice versa. > Note that Pharo itself might lack some meta info to describe a mapping by itself > (collections have no element types for example), so a good mapping is always > necessary to go to a statically typed model. > > There is a reason STON exists, it is one answer to this problem. Thanks, I'll look into it to see if I can adapt it to my needs. Regards,

Feb. 22, 2019

Re: [Pharo-users] Pharo Object Serialization

by BrunoBB

Peter, Yes i already read those posts. Maybe i will try and see but i highly doubt i will use it in production. Back in the old days i used it a lot with Dolphin Smalltalk, David Jorisek provided good support then. regards, bruno -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Feb. 22, 2019

Re: [Pharo-users] Streams for FileReference in Pharo 7

by Sven Van Caekenberghe

https://github.com/pharo-project/pharo/pull/2695 > On 18 Feb 2019, at 16:52, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > OK, I that is what I expected. > I will study this again and make a PR with better comments and tests. > >> On 18 Feb 2019, at 16:32, ducasse <stepharo(a)netcourrier.com> wrote: >> >>> >>> >>> I have been thinking a bit more about this, and I have a lot of problems with >>> >>> Integer>>#putOn: aStream >>> aStream isBinary >>> ifTrue: [ self asByteArray do: [ :each | aStream nextPut: each ] ] >>> ifFalse: [ self asString putOn: aStream ] >>> >>> I think we should simply remove this method. It is ugly and wrong. >> >> I agree >> >>> #<< should simply be a shortcut for either #nextPut: and #nextPutAll: and nothing more. >>> >>> The following two are OK for me: >>> >>> String streamContents: [ :out | out << 'Hello' << $! ]. >>> ByteArray streamContents: [ :out | out << #[ 1 2 3 ] << 4 ]. >>> >>> But the following most definitively not: >>> >>> (ByteArray streamContents: [ :out | out << 16rFF << 16rFF11 << 16rFFFF22 << 16rFFFFFF33 ]) hex. >>> >>> When you write out an integer, you have to decide its size, that can never depend on the magnitude (because there is no way to read this back unless there is additional bracketing). >>> >>> Also, printing to a stream should be (very) efficient. Making copies of objects just for conversion purposes should be avoided. >> >> yes. >> >>> >>> I think that if we remove Integer>>#putOn: I could live with >>> >>> ZnEncodedStream>>#<< anObject >>> anObject putOn: self >> >> Yes :) >> and remove the ugly one? Yes >> >>> >>> The other solution is to define #<< as strictly the same as #nextPutAll: and remove all #putOn: implementors. >>> >>> Sven >

Feb. 22, 2019

Re: [Pharo-users] Pharo Object Serialization

by PBKResearch

Bruno OmniBase was ported to Pharo 6+ in Jun 2018. The original porting work was done by Esteban Lorenzano, but he pointed out that, as a non-user, he is not in a position to provide any support. It was used to a small extent by me, and much more by Matias Maretto. The repo is at https://github.com/estebanlm/OmniBase. There were a couple of tweaks needed to get it fully working; I don't know whether they were incorporated in the repo version. I haven't really used it much - my project got overtaken by other work. I think Matias used it more. You can see the whole story if you search for the subject 'OmniBase for Pharo 6' in this forum. HTH Peter Kenny -----Original Message----- From: Pharo-users <pharo-users-bounces(a)lists.pharo.org> On Behalf Of BrunoBB Sent: 22 February 2019 03:05 To: pharo-users(a)lists.pharo.org Subject: [Pharo-users] Pharo Object Serialization Hi, Which are the options for serialize objects in Pharo ? I know there is Fuel (https://rmod.inria.fr/web/software/Fuel) OmniBase is not supported any more. OmniBase was pretty cool even transactional !!! What are you using ? (of course there is GemStone/S but i was not able to convince my client yet :) regards, bruno -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Feb. 22, 2019

Iliad & disbled JS

by Siemen Baader

Hi, has support for disabled JavaScript been removed from Iliad? When I do $ curl http://localhost:9999/examples/counters I get [...] <h1>0</h1><a href="javascript:{}" onclick="iliad.evaluateAction("/examples/counters?_session=e333771f-db3e-0d00-bc9a-e623066cc382&_action=10073&_state=bb37771f");">++</a> [...] So it works only with JS enabled. It would be nice to be able to make requests from non-JS-capable clients such as ZnEasy for testing purposes. Can I re-enable it? -- Siemen

Feb. 22, 2019

Re: [Pharo-users] Embedding object properties in NeoJSON mappings

by Sven Van Caekenberghe

Hi, > On 22 Feb 2019, at 02:05, Esteban Maringolo <emaringolo(a)gmail.com> wrote: > > Hi all (again), > > As part of writing the port (and adaptation to use Zinc and NeoJSON), > a CouchDB JSON-REST API, now I find something I don't know how to > solve using NeoJSON mappings. > > All objects you store in CouchDB at a particular URI are saved as > "Documents", so if you save a dictionary with keys "name", "height", > "c" to "/people/1234" , when you query "people/1234" you get the keys > of the saved dictionary PLUS to extra keys called _id and _rev. > > Then when you query (GET) back the document you get a JSON like this: > {"_id": ..., "_rev": ..., "name": ..., "height":...,} > > My Idea is that I can wrap any object serializable as JSON within > aDocument, but then if I define CouchDocument class>>#neoJsonMapping: > mapper as: > > mapper for: self do: [ :mapping | > mapping mapAccessor: #id to: '_id'. > mapping mapAccessor: #revision to: '_rev'. > mapping mapAccessor: #class to: '_class' > ]. > > I have no way to "flatten"/"merge" anObject within aDocument. > > I would expect something like > > mapper for: self do: [ :mapping | > mapping mapAccessor: #id to: '_id'. > mapping mapAccessor: #revision to: '_rev'. > mapping mapAccessor: #class to: '_class' > mapping embed: [:object | object whatToEmbed] > ]. > > Of course this is awkward, because if I need to read it back, the > "extraction" of the embeded properties needs to know which belongs to > which and more importantly , what to instantiate! > > Of course I can do it manually without using NeoJSON (It's already > being done [1]) , but I like when different libraries things fit > naturally together :) > > > Am I stretching it too much? :) Yes, this is out of the scope of NeoJSON. As you know, JSON is strictly limited and kept simple, by design. Things people do to shoehorn objects, classes, types, ids, collections, references, etc on to it are exactly that, hacks on top. There are many ways to try to do any of this. What you are doing now, a two pass approach, is what I would do too: first use NeoJSON to get a standard structure (maybe use NeoJSONObject for simplicity), next do some extra work - and vice versa. Note that Pharo itself might lack some meta info to describe a mapping by itself (collections have no element types for example), so a good mapping is always necessary to go to a statically typed model. There is a reason STON exists, it is one answer to this problem. Sven > Regards, > > > [1] Currently the writing is done manually and the refresh (which is > also a GET) does the following: > > CouchDocument>>#refresh > " Update this Document to the latest revision " > | response | > response := self information. "response is a Dictionary" > revision := response at: '_rev'. > object := response couchToObject. > ^response > > And here happens the magic, it searchs for a "_class" key which if > present will use to instantiate the object "wrapped" by the document. > > Dictionary>>couchToObject > | class object | > self removeKey: '_id' ifAbsent: []. > self removeKey: '_rev' ifAbsent: []. > self keysAndValuesDo: [:key :value | self at: key put: value couchToObject]. > class := (self at: '_class' ifAbsent: [^self]) asSymbol asClass. > object := class basicNew. > object jsonInstanceVariableNames keysAndValuesDo: [:index :key | > self at: key ifPresent: [:value | object instVarAt: index put: value]]. > ^object > > #jsonInstanceVariableNames is another level of "mapping" here, that > defined what to map from the Document response. > > > Esteban A. Maringolo >

Feb. 22, 2019