September 2017 - Pharo-users

Re: [Pharo-users] About encoding

by Stephane Ducasse

> Any chance you can point me to the original file ? No they removed it May be I could try to convert it to utf-8 (I do not know how to do it) > The file is indeed in Latin1 encoded, but GitHub serves it as UTF-8 (it did not change the contents, but the meta data). Ok I see the problem > > The default encoder option only works when the server says nothing, it does not override what the server says. Ah ok. > The only way to read it, is by reading it binary (which basically ignores the meta data) and then convert it manually: > > (ZnCharacterEncoder latin1 decodeBytes: > (ZnClient new > beBinary; > get: 'https://raw.githubusercontent.com/SquareBracketAssociates/LearningOOPWithPh…')) lines. > > But this is very ugly. > > Best convert the original file to UTF-8 before uploading to GitHub. OK I will try to leanr how to do it. > > Sven > > >

Sept. 26, 2017

Re: [Pharo-users] Usability issues with Calypso

by Stephane Ducasse

In fact I'm not sure that continuing to use the * is not a good idea. On Sun, Sep 24, 2017 at 2:46 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Hi Sean > > 2017-09-23 19:57 GMT+02:00 Sean P. DeNigris <sean(a)clipperadams.com>: >> >> Stephane Ducasse-3 wrote >> > Calypso is still an enfant and this is >> > IMPORTANT that people tell what >> > they do not like so that we can improve. >> >> A few more impressions now that I've been using Calypso as my default >> browser: >> - Overall really enjoying it! >> - When browsing a class from its own package, and then adding an extension >> protocol via '*...' in "New protocol" context menu, the dialog closes >> without objection, but then the new protocol doesn't seem to exist. I had >> to >> create a dummy protocol and then DND the methods into the >> package-to-be-extended. > > > In Calypso you should not create protocols with star. In method editor > status bar there is explicit checkbox "extension" to specify external > package for the method. > We should move away from star convention and work directly with packages. > Calypso gives you the tools for this. > > But I will add special notification when user creates new protocol with > star. I think it will help "old" Pharo users to adopt. > https://github.com/dionisiydk/Calypso/issues/96 > >> >> - When Calypso is set to be the default browser, it would be helpful if >> the >> World menu item changed from "Calypso Browser" to "Nautilus" >> - Lack of word wrapping is becoming teeeeeeedious >> >> >> >> ----- >> Cheers, >> Sean >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >

Sept. 26, 2017

Re: [Pharo-users] About encoding

by Sven Van Caekenberghe

> On 26 Sep 2017, at 17:25, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Hi sven > > the web site I was using remove the file for my book. > So I copied the file on github. > When I open the file with texmate it tells that the encoding is western-latin1 > but when I try to load it as follow I get an UTF-8 illegal error. > > | lines | > lines := (ZnDefaultCharacterEncoder > value: ZnCharacterEncoder latin1 > during: [ > ZnClient new > get: 'https://raw.githubusercontent.com/SquareBracketAssociates/LearningOOPWithPh…' > ]) lines. > > Do you have any idea? > > Tx > > Stef Any chance you can point me to the original file ? The file is indeed in Latin1 encoded, but GitHub serves it as UTF-8 (it did not change the contents, but the meta data). The default encoder option only works when the server says nothing, it does not override what the server says. The only way to read it, is by reading it binary (which basically ignores the meta data) and then convert it manually: (ZnCharacterEncoder latin1 decodeBytes: (ZnClient new beBinary; get: 'https://raw.githubusercontent.com/SquareBracketAssociates/LearningOOPWithPh…')) lines. But this is very ugly. Best convert the original file to UTF-8 before uploading to GitHub. Sven

Sept. 26, 2017

About encoding

by Stephane Ducasse

Hi sven the web site I was using remove the file for my book. So I copied the file on github. When I open the file with texmate it tells that the encoding is western-latin1 but when I try to load it as follow I get an UTF-8 illegal error. | lines | lines := (ZnDefaultCharacterEncoder value: ZnCharacterEncoder latin1 during: [ ZnClient new get: 'https://raw.githubusercontent.com/SquareBracketAssociates/LearningOOPWithPh…' ]) lines. Do you have any idea? Tx Stef

Sept. 26, 2017

Re: [Pharo-users] Force headless mode

by ClÃ©ment Bera

Or write a script that obfuscate the code. Not so hard to do. On Tue, Sep 26, 2017 at 5:13 PM, Christophe Demarey < christophe.demarey(a)inria.fr> wrote: > Hi > > What about deploying a minimal image without UI ? > But, as you probably know, headless mode does not prevent to dump the code. > > Christophe > ----- Cyril Ferlicot <cyril.ferlicot(a)gmail.com> a Ã©crit : > > Hi, > > > > At Synectique we are working on the deployment of a web application > > and we would like to force the headless mode. We tried to just > > override the method SmalltalkImage>>#isHeadless to return true all the > > time be it is not enough because the image is still opened. It is > > probabaly the vm that open the window. > > > > I know we can add some arguments to the command line to open the image > > as headless but we want to forbid the user to launch the image without > > headless to protect the code. > > > > Is this possible? Do you have some pointers? > > > > Thanks in advance. > > > > -- > > Cyril Ferlicot > > https://ferlicot.fr > > > > http://www.synectique.eu > > 2 rue Jacques PrÃ©vert 01, > > 59650 Villeneuve d'ascq France > > > > >

Sept. 26, 2017

ReÂ : Force headless mode

by Christophe Demarey

Hi What about deploying a minimal image without UI ? But, as you probably know, headless mode does not prevent to dump the code. Christophe ----- Cyril Ferlicot <cyril.ferlicot(a)gmail.com> a Ã©critÂ : > Hi, > > At Synectique we are working on the deployment of a web application > and we would like to force the headless mode. We tried to just > override the method SmalltalkImage>>#isHeadless to return true all the > time be it is not enough because the image is still opened. It is > probabaly the vm that open the window. > > I know we can add some arguments to the command line to open the image > as headless but we want to forbid the user to launch the image without > headless to protect the code. > > Is this possible? Do you have some pointers? > > Thanks in advance. > > -- > Cyril Ferlicot > https://ferlicot.fr > > http://www.synectique.eu > 2 rue Jacques PrÃ©vert 01, > 59650 Villeneuve d'ascq France >

Sept. 26, 2017

Force headless mode

by Cyril Ferlicot

Hi, At Synectique we are working on the deployment of a web application and we would like to force the headless mode. We tried to just override the method SmalltalkImage>>#isHeadless to return true all the time be it is not enough because the image is still opened. It is probabaly the vm that open the window. I know we can add some arguments to the command line to open the image as headless but we want to forbid the user to launch the image without headless to protect the code. Is this possible? Do you have some pointers? Thanks in advance. -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Sept. 26, 2017

Re: [Pharo-users] Need help with NeoJSON reader definition

by Sven Van Caekenberghe

Hi Joachim, Have a look at this new example: === Name: Neo-JSON-Tests-SvenVanCaekenberghe.43 Author: SvenVanCaekenberghe Time: 26 September 2017, 2:14:01.71055 pm UUID: f40af758-7816-0d00-89cd-641e08d6220e Ancestors: Neo-JSON-Tests-SvenVanCaekenberghe.42 Add #testVirtualTransferObject as another mapping example === NeoJSONMappingTests>>#testVirtualTransferObject | data customMapping extraJson json result | data := NeoJSONObject new data: { 1@1. 2@2 }. extraJson := '{"foo":1,"data":[{"x":1,"y":1},{"x":2,"y":2,"z":-1}]}'. "The idea here is that we are not interested in the top level object just in its data property, which should be of a specific type, hence we create a virtual transfer object" customMapping := [ :mapper | mapper for: Point do: [ :mapping | mapping mapInstVars: #(x y) ]; for: #ArrayOfPoints customDo: [ :mapping | mapping listOfElementSchema: Point ]; for: #TransferObject do: [ :mapping | mapping subjectClass: NeoJSONObject. (mapping mapAccessor: #data) valueSchema: #ArrayOfPoints ]; yourself ]. "By using NeoJSONObject accessors (#data & #data:) are translated to generic #at:[put:] messages. A longer alternative is (mapping mapProperty: #data getter: [ :obj | obj at: #data ] setter: [ :obj :x | obj at: #data put: x]) valueSchema: #ArrayOfPoints where the blocks give you the flexibility to use a plain Dictionary for example" result := (customMapping value: (NeoJSONReader on: extraJson readStream)) nextAs: #TransferObject. self assert: result equals: data. json := String streamContents: [ :out | (customMapping value: (NeoJSONWriter on: out)) nextPut: data as: #TransferObject ]. result := (customMapping value: (NeoJSONReader on: json readStream)) nextAs: #TransferObject. self assert: result equals: data Does this help ? Sven > On 26 Sep 2017, at 12:01, jtuchel(a)objektfabrik.de wrote: > > I probably need to send a bit more info. > > My latest attempt was this: > > mapper := NeoJSONReader new. > > mapper for: #RootObject customDo: [:mapping | mapping mapWithValueSchema: #TransferMessage]. > > mapper > > for: #TransferMessage > > do: [:mapping | > > (mapping mapInstVar: 'Data' to: 'Data') listOfElementSchema: SomeExistingSmalltalkClass]. > > > which results in > > Symbol does not understand allInstVarNames > > Please note there is no class named #TransferMessage in my Image. This works for things like #ArrayOfPoints in the examples on the NeoJSON git page and it also works in some of my other JSON mappings in different contexts. > > I guess this is because I cannot map to instvars if there is no class/object to store values into... > So do I really need to implement an otherwise useless Smalltalk class just to have something to map the outermost {} object to? > > I also tried variations of for:customDo: for the mapping of the #TransferMessage and had no success so far. > > Any ideas? > > > Joachim > > > Am 26.09.17 um 08:29 schrieb jtuchel(a)objektfabrik.de: >> Hi there, >> >> >> I am having a hard time configuring a NeoJSONReader for a JSON file like this: >> >> { >> "Paging": { someStuff >> }, >> "ErrorMessage": null, >> "ErrorCode": 0, >> "Data": [ >> {object1}, >> >> {object2} >> >> ] >> >> } >> >> >> Where I want to ignore everything but the list named "Data". (Of course I'll have to take a look at ErrorMessages later, but one step after the other...). >> >> I've tried several combinations of mappers and always end up with NoeJSON parsing Exceptions. I semm unable to see the obvious. >> >> In The end I just want to only use the contents of the Data list and map each entry in there to some smalltalk object. I was successful with other structures and lists, but this time I am unable to see the forest among all those trees. >> >> Any hints? >> >> >> Joachim >> >> >> >> >> > > -- > ----------------------------------------------------------------------- > Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de > Fliederweg 1 http://www.objektfabrik.de > D-71640 Ludwigsburg http://joachimtuchel.wordpress.com > Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1 > >

Sept. 26, 2017

Re: [Pharo-users] Testing a Unicode Character's Category

by Prof. Andrew P. Black

Hi Richard, Normally I agree with you, and prefer boolean methods inCatagoryCc: aChar isCategorySm: aChar to categoryOf: aChar == #Cc categoryOf: aChar == #Sm In this particular case, though, the category codes are part of the Unicode Standard, so perhaps exposing them isnât so bad. Moreover, there is meaning encoded into the symbols â for example, all the letter categories start with L. So one could write an isLetter test like this Character >> isLetter ^ (Unicode categoryOf: self) first == $L rather than Character >> isLetter Unicode inCategoryLl ifTrue: [ ^ true ]. Unicode inCategoryLm ifTrue: [ ^ true ]. Unicode inCategoryLo ifTrue: [ ^ true ]. Unicode inCategoryLt ifTrue: [ ^ true ]. Unicode inCategoryLu ifTrue: [ ^ true ]. ^ false There is still the disadvantage that a typo in the Category name (typing #L1, for example, when one means #Ll) is likely to go undetected. Andrew

Sept. 26, 2017

Re: [Pharo-users] NeoJSON and polymorphism

by Sven Van Caekenberghe

> On 25 Sep 2017, at 17:14, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: > > Hi Sven, > > thank you! > > In the NeoJSON repository, you likely want to merge Neo-JSON-Core-SvenVanCaekenberghe.43 and 44. And the same for the test cases. I did, thanks ! >> On Sep 24, 2017, at 06:05, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> Hi Juraj, >> >> This would be a simpler form of the type/class tags that are often used in JSON encoding. Since there are many ways to do this, there cannot be one solution. NeoJSON mapping was not designed to cover these cases. Nor is JSON meant to do this. STON is one (rather elegant if I may say so) answer to this problem. Your example would be encoded as >> >> [ >> PngAttachement { #url:'http://example.com/random-name.txt', #fileName:'chapter-one.txt' }, >> TxtAttachement { #url:'http://example.com/random-name.png', #fileName:'image.png' } >> ] > > About STON usage, I wonder how it works in terms of a data structure evolution. Currently I use JSON format to store a data permanently. The data are supposed to be accesible for a long time (years). I am pretty sure that the protocol will evolve and we will end up with several JSON versions. I think that having different JSON mapping schemes will allow to map old JSON versions to a latest object structure (or to several different versions if necessary). > > For the example above, think of the scenario that PngAttachment does not exist anymore. In a simple scenario there could be an ImageAttachment class instead with the same instance variables. In a more complex scenario, there could be a AttachmentTwo { #type: AttachmentTwoType { â¦ instances â¦ }, #path: AttachmentTwoPath { â¦ instances â¦ } }. > > I can use JSON mappings that transform the old JSON version to the new class structure. I am not sure if STON is that flexible. > What do you think? Do I miss something? STON has no options for more than one mapping (the 'system' one). Schema evolution is always a hard problem, using temporary structures seems the simplest solution. The STON specification has not changed significantly since I first wrote it years ago. The implementation and the number of cases handled has though. >> Still, the question of how to do this kind of dynamic decoding is an interesting challenge. Please update to the following commits: >> >> === >> Name: Neo-JSON-Core-SvenVanCaekenberghe.44 >> Author: SvenVanCaekenberghe >> Time: 22 September 2017, 3:24:51.679449 pm >> UUID: f1ebeade-2816-0d00-a04c-ae370e598362 >> Ancestors: Neo-JSON-Core-SvenVanCaekenberghe.42 >> >> Implement some missing code in NeoJSONCustomMapping (the writing part of #listOfElementSchema: #listOfType:andElementSchema: #mapWithValueSchema:) >> >> Add NeoJSONStreamingWriter>>#writeElementAs: >> >> Add NeoJSONMappingTests>>#testDynamicTyping as an example >> === >> Name: Neo-JSON-Tests-SvenVanCaekenberghe.41 >> Author: SvenVanCaekenberghe >> Time: 22 September 2017, 3:25:09.881494 pm >> UUID: a9a900e0-2816-0d00-a04d-a6fb0e598362 >> Ancestors: Neo-JSON-Tests-SvenVanCaekenberghe.39 >> >> Implement some missing code in NeoJSONCustomMapping (the writing part of #listOfElementSchema: #listOfType:andElementSchema: #mapWithValueSchema:) >> >> Add NeoJSONStreamingWriter>>#writeElementAs: >> >> Add NeoJSONMappingTests>>#testDynamicTyping as an example >> === >> >> Now you can do as follows: >> >> NeoJSONMappingTests>>#testDynamicTyping >> | data customMapping json result | >> data := Array with: #foo->1 with: #(foo 2). >> "The idea is to map a key value combination as either a classic association or a simple pair, >> using key & value properties as well as a type property to distinguish between the two" >> customMapping := [ :mapper | >> mapper >> for: #AssocOrPair customDo: [ :mapping | >> mapping >> encoder: [ :x | >> x isArray >> ifTrue: [ { #type->#pair. #key->x first. #value->x second } asDictionary ] >> ifFalse: [ { #type->#assoc. #key->x key. #value->x value } asDictionary ] ]; >> decoder: [ :x | >> (x at: #type) = #pair >> ifTrue: [ Array with: (x at: #key) with: (x at: #value) ] >> ifFalse: [ (x at: #key) -> (x at: #value)] ] ]; >> for: #ArrayOfAssocOrPair customDo: [ :mapping | >> mapping listOfType: Array andElementSchema: #AssocOrPair ]; >> yourself ]. >> json := String streamContents: [ :out | >> (customMapping value: (NeoJSONWriter on: out)) nextPut: data as: #ArrayOfAssocOrPair ]. >> result := (customMapping value: (NeoJSONReader on: json readStream)) nextAs: #ArrayOfAssocOrPair. >> self assert: result equals: data >> >> Everything is virtual (not implemented as methods on actual classes) which makes the example self contained and non intrusive, but not very elegant, nor object oriented or extendable. Also, it is not as efficient as NeoJSON mapping was designed for, since it creates intermediate structures. > > Nice example. If #decoder: and #encoder: are used, is it still possible to use inner mappings? For example in my previous example, one instance variable is a ZnUrl instance that is stored as a String. Can I say âuse ZnUrl mapping in for this intermediate structureâ? Well, I understand that I can hard code it directly in the the #decoder: and #encoder: messages using #asZnUrl and #asString messages. I am thinking about a more complicated structures that involves more mapping definitions. Yes, other mappings should be respected. Sven > Thanks! > Juraj > >> >> HTH, >> >> Sven >> >>> On 21 Sep 2017, at 22:07, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: >>> >>> Hi, >>> >>> By studying the NeoJSON book chapter (Pharo Enterprise), I do not understand how to modify the following example: >>> >>> -=-=-=-=-=-=-=- >>> "Let us say that we have an Attachment class..." >>> >>> Object subclass: #Attachment >>> instanceVariableNames: 'url fileName' >>> classVariableNames: '' >>> package: 'NeoJSON-Use-Case'. >>> >>> "...with url: and fileName: methods." >>> Attachment compile: 'url: anObject', String cr, String tab, 'url := anObject' classified: 'accessing'. >>> Attachment compile: 'fileName: anObject', String cr, String tab, 'fileName := anObject' classified: 'accessing'. >>> >>> "Let's create a collection of two instances:" >>> collectionOne := { >>> Attachment new >>> url: 'http://example.com/random-name.txt' asZnUrl; >>> fileName: 'chapter-one.txt' >>> yourself. >>> Attachment new >>> url: 'http://example.com/random-name.png' asZnUrl; >>> fileName: 'image.png'; >>> yourself. >>> }. >>> >>> "And let's map it to a JSON structure:" >>> String streamContents: [ :aStream | >>> (NeoJSONWriter on: aStream) >>> for: #CollectionOfAttachments customDo: [ :mapping | >>> mapping listOfElementSchema: Attachment ]; >>> mapAllInstVarsFor: Attachment; >>> for: ZnUrl customDo: [ :mapping | >>> mapping encoder: [ :aZnUrl | >>> aZnUrl asString ] ]; >>> nextPut: collectionOne as: #CollectionOfAttachments. >>> ]. >>> >>> "And read the JSON structure:" >>> (NeoJSONReader on: '[{"url":"http://example.com/random-name.txt","fileName":"chapter-one.txt"},{"url":"http://example.com/random-name.png","fileName":"image.png"}]' readStream) >>> for: #CollectionOfAttachments customDo: [ :mapping | >>> mapping listOfElementSchema: Attachment ]; >>> for: Attachment do: [ :mapping | >>> mapping mapInstVar: 'fileName'. >>> (mapping mapInstVar: 'url') valueSchema: ZnUrl ]; >>> for: ZnUrl customDo: [ :mapping | >>> mapping decoder: [ :string | >>> string asZnUrl ] ]; >>> nextAs: #CollectionOfAttachments. >>> >>> "=======================" >>> âThe previous example works perfectly, including the ZnUrl mapping (notice that url variables have ZnUrl instances). >>> >>> Now, let's say that we want to distinguish PNG and TXT attachments. >>> For that reason we will create two Attachment subclasses..." >>> >>> Attachment subclass: #PngAttachment >>> instanceVariableNames: '' >>> classVariableNames: '' >>> package: 'NeoJSON-Use-Case'. >>> >>> Attachment subclass: #TxtAttachment >>> instanceVariableNames: '' >>> classVariableNames: '' >>> package: 'NeoJSON-Use-Case'. >>> >>> "...with type methods that might be used in a new JSON structure:" >>> PngAttachment compile: 'type', String cr, String tab, '^ ''png''' classified: 'accessing'. >>> TxtAttachment compile: 'type', String cr, String tab, '^ ''txt''' classified: 'accessing'. >>> >>> "Let's create a collection with the PNG and TXT instances:" >>> collectionTwo := { >>> TxtAttachment new >>> url: 'http://example.com/random-name.txt' asZnUrl; >>> fileName: 'chapter-one.txt' >>> yourself. >>> PngAttachment new >>> url: 'http://example.com/random-name.png' asZnUrl; >>> fileName: 'image.png'; >>> yourself. >>> }. >>> >>> "How can I modify NeoJSONWriter and NeoJSONReader mappings? >>> >>> The JSON structure should (ideally) looks like this:" >>> >>> '[ >>> {âtypeâ:âtxtâ,"url":"http://example.com/random-name.txt","fileName":"chapter-one.txtâ}, >>> {âtypeâ:âpngâ,"url":"http://example.com/random-name.png","fileName":"image.pngâ} >>> ]' >>> -=-=-=-=-=-=-=- >>> >>> I would like to keep the mapping isolated (without defining neoJsonOn: methods). >>> >>> Thank you! >>> Juraj

Sept. 26, 2017