January 2019 - Pharo-users - lists.pharo.org

Search in settings borwser

by Hilaire

Hi, In latest P7 with GToolkit loaded, when performing a search in the settings browser I have an error "#name sent to nil". Anyone notice the same problem? Btw, in the settings browser I don't find anymore the option to remove the critic pane in the class browser? Hilaire -- Dr. Geo http://drgeo.eu

Jan. 13, 2019

[ANN] News channel for our Discord Server

by Dimitris Chloupis

I am happy to annoyance a new channel in our Discord Server , #news News is a read only channel (members cannot post there only admins) that I intended to act as a newspaper of short that you can read with your morning coffee to get all the latest news in the Pharo land. The rules of the channel are very simple, 1) Only admins can post there. Its not a dicussion channel, all other relevant channels can be used for discussing the Pharo news. We already have tons of them. 2) every post must be no more than 2 lines, similarly to twitter, this is for headlines not for entire articles 3) every post must contain a link for more info 4) every post must mention the author that the news concern 5) least news must always be related to Pharo, it can be anything (article, project, update etc) 6) last but not least I am always open to suggestions in case something escapes my attention If you have not done so make sure you join our Discord server following this link https://discord.gg/QewZMZa You wont be getting only news but a very active community always willing to help you with any questions and problems you may have, real time. All people are welcomed :)

Jan. 12, 2019

Re: [Pharo-users] [Seaside] [ANN] MaterialDesignLite v2.0.0

by Sven Van Caekenberghe

Congratulations (again), Cyril, for doing such a professional job in running this project. This is really one of the nicest projects I have seen, I am jealous. > On 10 Jan 2019, at 01:38, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > > Hello, > > Today I released the version v2.0.0 of MaterialDesignLite for Seaside. > (https://github.com/DuneSt/MaterialDesignLite/releases/tag/v2.0.0) > > This release does not brings much new features but it contains all > breaking changes that accumulated in the issue tracker. (That's why it's > a major release). > > The main changes are: > - Migration to Tonel (People using Gemstone might need to stick to v1.x.x) > - Removal of all deprecated classes and methods > - I added named URLs in the demo to be able to send links of pages or > example > - Addition of a Pagination widget as extension of MDL > (https://mdl.ferlicot.fr/mdl/Extensions/Pagination) > > A migration guide can be found here: > > https://github.com/DuneSt/MaterialDesignLite/blob/v2.0.0/resources/migratio… > > This release is tagged with v2.0.0 and I also introduced tags v2.x.x and > v2.0.x which are moving tags following patch and minor versions. > > Here is the full changelog of the release: > https://github.com/DuneSt/MaterialDesignLite/blob/v2.0.0/CHANGELOG.md > > If you have issues, need a new feature or have a comment on the project > feel free to open a issue: > > https://github.com/DuneSt/MaterialDesignLite/issues > > I also updated the demo: https://mdl.ferlicot.fr/ > > Have a nice day! > > -- > Cyril Ferlicot > https://ferlicot.fr > > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Jan. 11, 2019

Re: [Pharo-users] Status of Tabular

by Sven Van Caekenberghe

> On 11 Jan 2019, at 08:21, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > > Hi Sven > > The most recent discussion was November 2018 on Pharo-Dev ML > > Subject: Excel export with Tabular > > Repo now: https://github.com/VincentBlondeau/Tabular Wow, that is great, thank you all ! > --Hannes > > On 1/10/19, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> Hi, >> >> What is the status of Tabular (the Excel export package) ? >> There was some talk about recent additions, where are they ? >> There was some talk about moving this project to GitHub, has this been done >> ? >> >> Sven >> >> >> >

Jan. 11, 2019

Re: [Pharo-users] Status of Tabular

by H. Hirzel

Hi Sven The most recent discussion was November 2018 on Pharo-Dev ML Subject: Excel export with Tabular Repo now: https://github.com/VincentBlondeau/Tabular --Hannes On 1/10/19, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi, > > What is the status of Tabular (the Excel export package) ? > There was some talk about recent additions, where are they ? > There was some talk about moving this project to GitHub, has this been done > ? > > Sven > > >

Jan. 11, 2019

Re: [Pharo-users] NeoJSON Custom Mapping Question

by Eric Gade

Thanks Norbert, that's great. I won't be able to get back to this project for another week or two (some stuff has come up) but will let you know if I have any questions. On Thu, Jan 10, 2019 at 2:52 AM Norbert Hartl via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > Hi Eric, > > Iâm late to the game but Iâm interested to talk abd cooperate. I > implemented JSON schema [1] not long ago. This can also be used to add a > mapping from object to json. It has also a type key inside the json object. > I did it with an intermediate object. The JSONSchemaDefinition is a super > type of all JSON schema types meaning one json object containing all keys > of all types. I read the super type and then with a visitor > I explode this super type into concrete type objects. As you say on > writing I use the concrete objects. The asymmetry is also a bit tricky but > in the end the best approach so far. So if you like we can talk. I think > that it could be a good idea to think about how JSON Schema and JSON LD > could fit together. > > Norbert > > > [1] https://github.com/zweidenker/JSONSchema > > Am 09.01.2019 um 22:27 schrieb Eric Gade <eric.gade(a)gmail.com>: > > Hi Sven, thanks for the response. > > Unfortunately since I'm working with a standard here, there is always > going to be an explicit `"type": <foo>` attribute rather than having the > key itself be the name of the type. I guess I'll stick to the two-pass read > solution. But the writing solution can use the mapping so that saves a lot > of trouble! > > > On Wed, Jan 9, 2019 at 3:14 PM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> Eric, >> >> > On 9 Jan 2019, at 00:34, Eric Gade <eric.gade(a)gmail.com> wrote: >> > >> > Hey guys, >> > >> > I'm toying with the idea of a Pharo implementation of ActivityStreams ( >> https://www.w3.org/TR/activitystreams-core/#introduction) which is based >> on a subset of JSON called JSON-LD (for "linked data"). >> > >> > While I do not believe this would entail creating a whole JSON-LD >> implementation, I do have a question about how to implement >> reading/writing/mapping to and from the core set of object types in the >> specification. >> > >> > I am aware that giving any class #neoJsonMapping allows one to define >> the specifics of the mapping to and from objects of that class (I think >> this is super cool, by the way). The issue with ActivityStreams objects is >> that the "type" of object they represent is in the JSON itself as the >> property "type," for example: >> > >> > ``` >> > { >> > "@context": "https://www.w3.org/ns/activitystreams", >> > "name": "A simple note", >> > "type": "Note", >> > "id": "http://www.test.example/notes/1", >> > "content": "A simple note", >> > "replies": { >> > "type": "Collection", >> > "totalItems": 1, >> > "items": [ >> > { >> > "name": "A response to the note", >> > "type": "Note", >> > "content": "A response to the note", >> > "inReplyTo": "http://www.test.example/notes/1" >> > } >> > ] >> > } >> > } >> > ``` >> > >> > This refers to a top level ActivityStream object of type "Note" which >> we maybe want to parse into something like `ASNote`. >> > >> > My core question is this: how can we get a NeoJSONReader to determine >> which type of object to create by checking for a "type" property as soon as >> possible in the process? Because this property can show up in any order, we >> won't know what type of object to create until it is encountered. What is >> the best strategy there? >> > >> > Does the complexity suggest that we should simply parse incoming >> ActivityStream objects into the collection-and-dict default mapping and >> deal with creating the appropriate objects after that? In this case we >> could still use the custom mapping for the writing, which is not a problem >> since the "type" field will be associated with the class (ie, ASNote class >> >> #type will respond with 'Note' and we can go from there). >> > >> > Any thoughts or suggestions much appreciated! >> >> You describe the situation correctly: NeoJSON operates in 2 modes: >> >> (1) generating generic Arrays and Dictionaries (just like the spec) >> >> or >> >> (2) optionally mapping, stream based, directly, without intermediary >> representation, into domain instances (given a predefined static mapping) >> >> Using NeoJSONObject instead of Dictionary is just a convenience (it being >> a more JS like object). >> >> There is indeed another approach, using dynamic typing, that is not >> specifically supported in NeoJSON. >> >> As you remark yourself, that requires an intermediary representation, so >> one could just as well use option (1) and convert 'manually' in a second >> pass. >> >> That being said, it could/would be a nice addition to offer some support >> for this. Although there are multiple slightly different approaches. For >> example, there also is >> >> { >> "Point" : { "x" : 1, "y" : 2 } >> } >> >> Instead of >> >> { >> "_type" : "Point", >> "x" : 1, >> "y" : 2 >> } >> >> The key for the type/class can be different, the value can be anything, >> even 'com.java.graphics.Point'. >> >> Note also that typically, there are no collection types (and these would >> be way more complicated). >> >> Sven >> >> > -- >> > Eric >> >> >> > > -- > Eric > > -- Eric

Jan. 10, 2019

Status of XML Support's move to GitHub

by Sven Van Caekenberghe

Hi, What is the status of XML Support's move to GitHub ? Many people were pro, has anything been done ? It would be very nice. Sven

Jan. 10, 2019

Status of Tabular

by Sven Van Caekenberghe

Hi, What is the status of Tabular (the Excel export package) ? There was some talk about recent additions, where are they ? There was some talk about moving this project to GitHub, has this been done ? Sven

Jan. 10, 2019

Vote for the Pharo Mooc

by Alidra Abdelghani

Hi folks, You can now vote for the Mooc of the year on : http://r.news1.fun-mooc.fr/mk/cl/4hV61iNLo1hKaNwqtQNyMTHoEhJD-d6CY0tH22cxzh… Please vote for âProgrammation objet immersive en Pharo / Live Object Programming in Pharoâ the super fun and instructive mooc :) Abdelghani On 29 Dec 2018, at 3:41 am, Fun-Mooc <news(a)fun-mooc.fr> wrote: MOOC of the year 2019 : Votez pour le MOOC de votre choix ! <http://r.news1.fun-mooc.fr/mk/cl/diTkixS7LwpKWB2RmaotIs5wEXGmvvOY5P15P47ODM…> Le mois de janvier 2019 sera pour FUN, un mois riche en Ã©vÃ©nements. Notamment avec la cÃ©rÃ©mone des âMOOC of the yearâ qui aura lieu le 30 janvier prochain. Cet Ã©vÃ©nement est initiÃ© par âMy MOOCâ, plateforme qui rÃ©fÃ©rence plus de 10 000 MOOC, dont ceux diffusÃ©s par France UniversitÃ© NumÃ©rique. Les apprenants peuvent voter pour le MOOC de l'annÃ©e 2018 : votez pour un MOOC de FUN !

Jan. 10, 2019

Re: [Pharo-users] NeoJSON Custom Mapping Question

by Norbert Hartl

Hi Eric, Iâm late to the game but Iâm interested to talk abd cooperate. I implemented JSON schema [1] not long ago. This can also be used to add a mapping from object to json. It has also a type key inside the json object. I did it with an intermediate object. The JSONSchemaDefinition is a super type of all JSON schema types meaning one json object containing all keys of all types. I read the super type and then with a visitor I explode this super type into concrete type objects. As you say on writing I use the concrete objects. The asymmetry is also a bit tricky but in the end the best approach so far. So if you like we can talk. I think that it could be a good idea to think about how JSON Schema and JSON LD could fit together. Norbert [1] https://github.com/zweidenker/JSONSchema > Am 09.01.2019 um 22:27 schrieb Eric Gade <eric.gade(a)gmail.com>: > > Hi Sven, thanks for the response. > > Unfortunately since I'm working with a standard here, there is always going to be an explicit `"type": <foo>` attribute rather than having the key itself be the name of the type. I guess I'll stick to the two-pass read solution. But the writing solution can use the mapping so that saves a lot of trouble! > > >> On Wed, Jan 9, 2019 at 3:14 PM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> Eric, >> >> > On 9 Jan 2019, at 00:34, Eric Gade <eric.gade(a)gmail.com> wrote: >> > >> > Hey guys, >> > >> > I'm toying with the idea of a Pharo implementation of ActivityStreams (https://www.w3.org/TR/activitystreams-core/#introduction) which is based on a subset of JSON called JSON-LD (for "linked data"). >> > >> > While I do not believe this would entail creating a whole JSON-LD implementation, I do have a question about how to implement reading/writing/mapping to and from the core set of object types in the specification. >> > >> > I am aware that giving any class #neoJsonMapping allows one to define the specifics of the mapping to and from objects of that class (I think this is super cool, by the way). The issue with ActivityStreams objects is that the "type" of object they represent is in the JSON itself as the property "type," for example: >> > >> > ``` >> > { >> > "@context": "https://www.w3.org/ns/activitystreams", >> > "name": "A simple note", >> > "type": "Note", >> > "id": "http://www.test.example/notes/1", >> > "content": "A simple note", >> > "replies": { >> > "type": "Collection", >> > "totalItems": 1, >> > "items": [ >> > { >> > "name": "A response to the note", >> > "type": "Note", >> > "content": "A response to the note", >> > "inReplyTo": "http://www.test.example/notes/1" >> > } >> > ] >> > } >> > } >> > ``` >> > >> > This refers to a top level ActivityStream object of type "Note" which we maybe want to parse into something like `ASNote`. >> > >> > My core question is this: how can we get a NeoJSONReader to determine which type of object to create by checking for a "type" property as soon as possible in the process? Because this property can show up in any order, we won't know what type of object to create until it is encountered. What is the best strategy there? >> > >> > Does the complexity suggest that we should simply parse incoming ActivityStream objects into the collection-and-dict default mapping and deal with creating the appropriate objects after that? In this case we could still use the custom mapping for the writing, which is not a problem since the "type" field will be associated with the class (ie, ASNote class >> #type will respond with 'Note' and we can go from there). >> > >> > Any thoughts or suggestions much appreciated! >> >> You describe the situation correctly: NeoJSON operates in 2 modes: >> >> (1) generating generic Arrays and Dictionaries (just like the spec) >> >> or >> >> (2) optionally mapping, stream based, directly, without intermediary representation, into domain instances (given a predefined static mapping) >> >> Using NeoJSONObject instead of Dictionary is just a convenience (it being a more JS like object). >> >> There is indeed another approach, using dynamic typing, that is not specifically supported in NeoJSON. >> >> As you remark yourself, that requires an intermediary representation, so one could just as well use option (1) and convert 'manually' in a second pass. >> >> That being said, it could/would be a nice addition to offer some support for this. Although there are multiple slightly different approaches. For example, there also is >> >> { >> "Point" : { "x" : 1, "y" : 2 } >> } >> >> Instead of >> >> { >> "_type" : "Point", >> "x" : 1, >> "y" : 2 >> } >> >> The key for the type/class can be different, the value can be anything, even 'com.java.graphics.Point'. >> >> Note also that typically, there are no collection types (and these would be way more complicated). >> >> Sven >> >> > -- >> > Eric >> >> > > > -- > Eric

Jan. 10, 2019