May 2017 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Ston feature idea?

by Cyril Ferlicot D.

On 17/05/2017 15:17, Sven Van Caekenberghe wrote: > > > OK. > > But don't go too far in writing actual code. I want to understand the use case at a high level (like how you started), then I can try to find how/if STON can do what you want. Right now, you are already too deep into a possible solution. > > If I have to give a really simple use case. Imagine an invoice. The invoice has the name of the customer and the currency used as a class. During the export of the invoice you do not want to export the currency as a class but as a String. So if I have an Invoice instance like this: username: 'user' currency: Currency[Euro] I want to transform the currency to a string during the export. (and keep the username as strings). Result: Invoice { #username : 'user', #currency : 'eur' } Instead of: Invoice { #username : 'user', #currency : Currency { #unit: 'Euro' } } Then during the import I want to transform the currency into a class again. (For example `Currency fromAbbreviation: stonInput`). -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

May 17, 2017

Re: [Pharo-users] Ston feature idea?

by Sven Van Caekenberghe

> On 17 May 2017, at 15:11, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > > On 17/05/2017 14:55, Sven Van Caekenberghe wrote: >> >> >> The use of #stonAllInstVarNames works in limiting what you write out (there is even a unit test based on STONTestUser3). >> >> But you seem to want to do something else, you want to write the others ones out in a different way. >> >> What I tried to explain is that that is generally not needed, if you customise the value of #variableToCustomise (that is one level deeper). This is what I did in the example. >> >> Since you can't or won't explain your use case better, I really can't help, can I ? >> >> > > I don't really have the time right now but later I'll try to write a > simple example. OK. But don't go too far in writing actual code. I want to understand the use case at a high level (like how you started), then I can try to find how/if STON can do what you want. Right now, you are already too deep into a possible solution. > -- > Cyril Ferlicot > https://ferlicot.fr > > http://www.synectique.eu > 2 rue Jacques PrÃ©vert 01, > 59650 Villeneuve d'ascq France >

May 17, 2017

Re: [Pharo-users] Ston feature idea?

by Cyril Ferlicot D.

On 17/05/2017 14:55, Sven Van Caekenberghe wrote: > > > The use of #stonAllInstVarNames works in limiting what you write out (there is even a unit test based on STONTestUser3). > > But you seem to want to do something else, you want to write the others ones out in a different way. > > What I tried to explain is that that is generally not needed, if you customise the value of #variableToCustomise (that is one level deeper). This is what I did in the example. > > Since you can't or won't explain your use case better, I really can't help, can I ? > > I don't really have the time right now but later I'll try to write a simple example. -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

May 17, 2017

Re: [Pharo-users] HiDPI

by phil＠highoctane.be

Ah, the @x2 and @x3 fun... https://developer.apple.com/ios/human-interface-guidelines/graphics/image-s… On Wed, May 17, 2017 at 2:48 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > But AFAIK what Tobias did was just to render per pixel essentially scaling > all UI 4 times. While the VM should be able to render per pixel, there > should be some abstraction that converts generic âpointsâ if the normal UI > to pixels used for rendering. So we can have the same UI as we had without > doing any changes, but something should know that each point on the retina > devices consists of 4 pixels, while on other devices it consists of 1 > pixel. This was done at some iteration of Block, maybe it can be done in a > different way. > > Uko > > P.S. yes, I know that you can increase the font to mitigate the scaled > down UI, but everything else (icons, margins, â¦) will stay the same size. > And this is the point of abstract points, to separate the concerns of UI > modeling from rendering. > > > > On 17 May 2017, at 11:18, Stephan Eggermont <stephan(a)stack.nl> wrote: > > > > Hi Tim, Steven > > > > No, it has nothing to do with Bloc. The necessary change was made by > Tobias in the squeak vm some time ago, but that was destabilizing the spur > vm at that time. I assume it is time to revisit it now the gc bugs seem to > be gone. > > > > Stephan > > > > > > > >

May 17, 2017

Re: [Pharo-users] Ston feature idea?

by Sven Van Caekenberghe

> On 17 May 2017, at 14:38, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > > On 17/05/2017 14:22, Sven Van Caekenberghe wrote: >> >> Of course that does not work, it is your job to do something similar that fits your use case. You certainly do not have to cache everything. >> >> On the other had, if you only serialise part of an object, or just one reference (id, url, name) like in the example, how will you recreate the rest, unless you have access to it ? And that is what your version of #fromId: should do. >> >> I can't understand how your 'to export from an image and to load from another' can possibly work, unless there is some other way of sharing the data. >> >> But I probably don't understand you, I known nothing about Moose models. >> > > What I would like to know is if there is a simple way to customize the > export of only one or two of the variables. And let the other variables > be exported as usual. The use of #stonAllInstVarNames works in limiting what you write out (there is even a unit test based on STONTestUser3). But you seem to want to do something else, you want to write the others ones out in a different way. What I tried to explain is that that is generally not needed, if you customise the value of #variableToCustomise (that is one level deeper). This is what I did in the example. Since you can't or won't explain your use case better, I really can't help, can I ? > I think I can do something like (I did not test but the spirit is here): > > myObject class>>stonAllInstVarNames > ^ super stonAllInstVarNames \ { #variableToCustomise } > > > myObject>>stonOn: stonWriter > > stonWriter writeObject: self streamMap: [ :dictionary | > self class stonAllInstVarNames do: [ :each | > (self instVarNamed: each) > ifNotNil: [ :value | dictionary at: each asSymbol put: value ] > ifNil: [ self stonShouldWriteNilInstVars ifTrue: [ > dictionary at: each asSymbol put: nil ] ] ]. > dictionary at: #variableToCustomize put: (self instVarNamed: > #variableToCustomize) asString. ] > > > myObject class>>fromSton: stonReader > > | obj | > obj := super fromSton: stonReader. > obj variableToCustomize: (UUID fromString: obj variableToCustomize) > ^ obj > > But this imply to rewrite inside #stonOn: a part of the code used in the > super stonOn: and I don't really like this in general. > > So I wanted to know if there was a hook to customize certain variables > while exporting the other as usual. > > -- > Cyril Ferlicot > https://ferlicot.fr > > http://www.synectique.eu > 2 rue Jacques PrÃ©vert 01, > 59650 Villeneuve d'ascq France >

May 17, 2017

Re: [Pharo-users] HiDPI

by Yuriy Tymchuk

But AFAIK what Tobias did was just to render per pixel essentially scaling all UI 4 times. While the VM should be able to render per pixel, there should be some abstraction that converts generic âpointsâ if the normal UI to pixels used for rendering. So we can have the same UI as we had without doing any changes, but something should know that each point on the retina devices consists of 4 pixels, while on other devices it consists of 1 pixel. This was done at some iteration of Block, maybe it can be done in a different way. Uko P.S. yes, I know that you can increase the font to mitigate the scaled down UI, but everything else (icons, margins, â¦) will stay the same size. And this is the point of abstract points, to separate the concerns of UI modeling from rendering. > On 17 May 2017, at 11:18, Stephan Eggermont <stephan(a)stack.nl> wrote: > > Hi Tim, Steven > > No, it has nothing to do with Bloc. The necessary change was made by Tobias in the squeak vm some time ago, but that was destabilizing the spur vm at that time. I assume it is time to revisit it now the gc bugs seem to be gone. > > Stephan > >

May 17, 2017

Re: [Pharo-users] Ston feature idea?

by Cyril Ferlicot D.

On 17/05/2017 14:22, Sven Van Caekenberghe wrote: > > Of course that does not work, it is your job to do something similar that fits your use case. You certainly do not have to cache everything. > > On the other had, if you only serialise part of an object, or just one reference (id, url, name) like in the example, how will you recreate the rest, unless you have access to it ? And that is what your version of #fromId: should do. > > I can't understand how your 'to export from an image and to load from another' can possibly work, unless there is some other way of sharing the data. > > But I probably don't understand you, I known nothing about Moose models. > What I would like to know is if there is a simple way to customize the export of only one or two of the variables. And let the other variables be exported as usual. I think I can do something like (I did not test but the spirit is here): myObject class>>stonAllInstVarNames ^ super stonAllInstVarNames \ { #variableToCustomise } myObject>>stonOn: stonWriter stonWriter writeObject: self streamMap: [ :dictionary | self class stonAllInstVarNames do: [ :each | (self instVarNamed: each) ifNotNil: [ :value | dictionary at: each asSymbol put: value ] ifNil: [ self stonShouldWriteNilInstVars ifTrue: [ dictionary at: each asSymbol put: nil ] ] ]. dictionary at: #variableToCustomize put: (self instVarNamed: #variableToCustomize) asString. ] myObject class>>fromSton: stonReader | obj | obj := super fromSton: stonReader. obj variableToCustomize: (UUID fromString: obj variableToCustomize) ^ obj But this imply to rewrite inside #stonOn: a part of the code used in the super stonOn: and I don't really like this in general. So I wanted to know if there was a hook to customize certain variables while exporting the other as usual. -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

May 17, 2017

Re: [Pharo-users] Ston feature idea?

by Sven Van Caekenberghe

> On 17 May 2017, at 14:15, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > > On 17/05/2017 13:46, Sven Van Caekenberghe wrote: >> >>> On 17 May 2017, at 12:44, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>> Hi Cyril, >>> >>> This can be done quite easily in STON, I will make you a small example and add it to the unit tests. >> >> === >> Name: STON-Tests-SvenVanCaekenberghe.79 >> Author: SvenVanCaekenberghe >> Time: 17 May 2017, 1:43:03.944446 pm >> UUID: fb472e87-180c-0d00-b559-fec60aee7555 >> Ancestors: STON-Tests-SvenVanCaekenberghe.78 >> >> Add STONWriteReadTests>>#testKnownObjects as an example of how to serialize only an ID and resolve that ID upon materialization >> >> Add STONTestKnownObject with custom #stonOn: and class side #fromSton: >> === >> >> You basically (over)write 2 methods, instance side >> >> "protocol: ston-core" >> stonOn: stonWriter >> "We only write out our id" >> >> stonWriter writeObject: self listSingleton: self id asString >> >> and class side >> >> "protocol: ston-core" >> fromSton: stonReader >> ^ self fromId: stonReader parseListSingleton >> >> The #fromId: methods retrieves an existing instance. >> >> HTH, >> >> Sven >> >> >> > Hi Sven, > > I do not want to keep all the KnowObjects in the memory. One of the goal > is to export from an image and to load from another. > > The following does not work: > > | obj string| > obj := STONTestKnownObject new description: 'something else'; yourself. > string := STON toStringPretty: obj. > STONTestKnownObject resetKnownObjects. > self assert: (STON fromString: string) description = 'something else' Of course that does not work, it is your job to do something similar that fits your use case. You certainly do not have to cache everything. On the other had, if you only serialise part of an object, or just one reference (id, url, name) like in the example, how will you recreate the rest, unless you have access to it ? And that is what your version of #fromId: should do. I can't understand how your 'to export from an image and to load from another' can possibly work, unless there is some other way of sharing the data. But I probably don't understand you, I known nothing about Moose models. > What is the simple may to customize only one or two variable(s)? > -- > Cyril Ferlicot > https://ferlicot.fr > > http://www.synectique.eu > 2 rue Jacques PrÃ©vert 01, > 59650 Villeneuve d'ascq France >

May 17, 2017

Re: [Pharo-users] Ston feature idea?

by Cyril Ferlicot D.

On 17/05/2017 13:46, Sven Van Caekenberghe wrote: > >> On 17 May 2017, at 12:44, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> Hi Cyril, >> >> This can be done quite easily in STON, I will make you a small example and add it to the unit tests. > > === > Name: STON-Tests-SvenVanCaekenberghe.79 > Author: SvenVanCaekenberghe > Time: 17 May 2017, 1:43:03.944446 pm > UUID: fb472e87-180c-0d00-b559-fec60aee7555 > Ancestors: STON-Tests-SvenVanCaekenberghe.78 > > Add STONWriteReadTests>>#testKnownObjects as an example of how to serialize only an ID and resolve that ID upon materialization > > Add STONTestKnownObject with custom #stonOn: and class side #fromSton: > === > > You basically (over)write 2 methods, instance side > > "protocol: ston-core" > stonOn: stonWriter > "We only write out our id" > > stonWriter writeObject: self listSingleton: self id asString > > and class side > > "protocol: ston-core" > fromSton: stonReader > ^ self fromId: stonReader parseListSingleton > > The #fromId: methods retrieves an existing instance. > > HTH, > > Sven > > > Hi Sven, I do not want to keep all the KnowObjects in the memory. One of the goal is to export from an image and to load from another. The following does not work: | obj string| obj := STONTestKnownObject new description: 'something else'; yourself. string := STON toStringPretty: obj. STONTestKnownObject resetKnownObjects. self assert: (STON fromString: string) description = 'something else' What is the simple may to customize only one or two variable(s)? -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

May 17, 2017

Re: [Pharo-users] Ston feature idea?

by Cyril Ferlicot D.

On 17/05/2017 13:14, Peter Uhnak wrote: > Just curious... why don't you use MSE? > Because what we want to export is not composed only of entities describes by Fame. We only reference some of them sometimes. > Peter > -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

May 17, 2017