- Pharo-users - lists.pharo.org

Re: [Pharo-users] Generate class hierarchy from JSON Schema

by Todd Blanchard

I have some work around building class hierarchies from database schema - specifically a Rails style Active Record schema. It is a bit of a work in progress and is intended to be folded into Glorp but you can see where I am at https://github.com/pharo-db/glorp/blob/13-Drive-DescriptorSystem-creation-e… <https://github.com/pharo-db/glorp/blob/13-Drive-DescriptorSystem-creation-e…> Maybe it helps? > On Jan 18, 2020, at 12:20 AM, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > > Hi there, > > anyone has experience about generating a class hierarchy from a JSON Schema ? Code available somewhere ? > > Thank you. > > -- > Serge Stinckwich > Int. Research Unit on Modelling/Simulation of Complex Systems (UMMISCO) > Sorbonne University (SU) > French National Research Institute for Sustainable Development (IRD) > University of YaoundÃ© I, Cameroon > "Programs must be written for people to read, and only incidentally for machines to execute." > https://twitter.com/SergeStinckwich <https://twitter.com/SergeStinckwich>

Jan. 19, 2020

Willow documentation

by TomaÅ¾ Turk

Dear all, I'm trying out Willow which looks very interesting, however I'm struggling with simple examples ... I basically follow the blogs (here <https://medium.com/mercap-tech-blog/willow-introduction-d498e198dd4a>). I loaded Willow with Bootstrap and prepared the To-Do app as described in blog series. This works OK, however when I try to do something more, like button := AsynchronicButtonWebView labeled: 'Now it''s time to click'. button onTrigger executeOnClient: [ :canvas | canvas javascript alert: 'You just clicked a button' ] the browser's javascript gives no response, and its console reports some errors: It looks like problems with libraries. I checked the examples in WillowPlayground (which works OK, BTW), and found out that some basic things are way richer than described in the blogs. For instance, component supplier is not just componentSupplierForApplication ^ Bootstrap4ComponentSupplier online as in the blog, but: componentSupplierForApplication ^ BootstrapComponentSupplier withBootstrapLibrary: (self deploymentMode libraryFor: Bootstrap3MetadataLibrary) withoutOptionalTheme selectLibrary: ((self deploymentMode libraryFor: BootstrapSelectLibrary) using: self language) datepickerLibrary: ((self deploymentMode libraryFor: BootstrapDatepickerLibrary) using: self language) typeaheadLibrary: (self deploymentMode libraryFor: BootstrapTypeaheadLibrary) new My question is - is there a better documentation available for Willow? It's quite hard to study all bits and pieces from scratch. The second question is about the suggested "architecture" or design pattern that should be followed when using Willow. The blog mixes Seaside components (e.g. #PendingTask as a subclass of WAPainter) that engages Seaside rendering elements (e.g. html paragraph:) on one hand, with the components supplier's components (e.g. singleLineTextField ...) implemented directly in the Willow Application on the other hand. This probably isn't the way things should be done :-) Best wishes, Tomaz

Jan. 19, 2020

Re: [Pharo-users] Pharo display bug

by Norbert Hartl

Didnât you know pharo has a website? Did you have trouble finding the âReporting issuesâ section on the website? What went wrong with you and the available information? Norbert > Am 18.01.2020 um 19:16 schrieb Richard Kenneth Eng <horrido.hobbies(a)gmail.com>: > > ï»¿ > I don't know how to report Pharo bugs, so I'll just mention that the Pharo IDE isn't displaying code properly. For example: > > <image.png> > > > Look at "map cellAt: ". The 'A' and 't" are mashed together. > > Another example: > > <image.png> > > > Look at ":cellA:cellB | cellA energy ". It's not displaying the space between "cellA" and "energy". > > This is more than just a display bug because how the hell are you supposed to edit this code??? > > Richard

Jan. 19, 2020

Re: [Pharo-users] Pharo display bug

by horrido

Thanks! Works perfectly. Torsten Bergmann wrote > This is a known issue with FreeType - it happens in some images and in > next automatically > built image it is gone. See all details in: > > https://github.com/pharo-project/pharo/issues/2336 > > Workaround: > > Just go to the WorldMenu Pharo -> Settings (to open the SettingsBrowser) > -> Appearance -> Switch the "Use Free Type" checkbox twice and fonts will > be OK again > > Thx > T. > > > >> Gesendet: Samstag, 18. Januar 2020 um 19:29 Uhr >> Von: "tbrunz" < > wild.ideas@ > > >> An: > pharo-users@.pharo >> Betreff: Re: [Pharo-users] Pharo display bug >> >> Richard, >> >> It's pretty easy. Surf to the 'issues' page of the Pharo repo, which is >> in >> the 'pharo-project' organization in GitHub: >> >> https://github.com/pharo-project/pharo/issues >> >> Click the bright green "New issue" button, then describe away... >> >> -Ted >> >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >> -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Jan. 18, 2020

Re: [Pharo-users] Pharo display bug

by Tim Mackinnon

I find that pressing save fixes it (itâs a cache corruption thing and very annoying - but itâs been hard to fix). Itâs certainly improved since the last round of fixes but I still get it, and some things loaded in your image seem to trigger it more frequently (mirage was one of them) Tim Sent from my iPhone > On 18 Jan 2020, at 18:48, Torsten Bergmann <astares(a)gmx.de> wrote: > > This is a known issue with FreeType - it happens in some images and in next automatically > built image it is gone. See all details in: > > https://github.com/pharo-project/pharo/issues/2336 > > Workaround: > > Just go to the WorldMenu Pharo -> Settings (to open the SettingsBrowser) > -> Appearance -> Switch the "Use Free Type" checkbox twice and fonts will be OK again > > Thx > T. > > > >> Gesendet: Samstag, 18. Januar 2020 um 19:29 Uhr >> Von: "tbrunz" <wild.ideas(a)gmail.com> >> An: pharo-users(a)lists.pharo.org >> Betreff: Re: [Pharo-users] Pharo display bug >> >> Richard, >> >> It's pretty easy. Surf to the 'issues' page of the Pharo repo, which is in >> the 'pharo-project' organization in GitHub: >> >> https://github.com/pharo-project/pharo/issues >> >> Click the bright green "New issue" button, then describe away... >> >> -Ted >> >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >> >

Jan. 18, 2020

Re: [Pharo-users] Pharo display bug

by Torsten Bergmann

This is a known issue with FreeType - it happens in some images and in next automatically built image it is gone. See all details in: https://github.com/pharo-project/pharo/issues/2336 Workaround: Just go to the WorldMenu Pharo -> Settings (to open the SettingsBrowser) -> Appearance -> Switch the "Use Free Type" checkbox twice and fonts will be OK again Thx T. > Gesendet: Samstag, 18. Januar 2020 um 19:29 Uhr > Von: "tbrunz" <wild.ideas(a)gmail.com> > An: pharo-users(a)lists.pharo.org > Betreff: Re: [Pharo-users] Pharo display bug > > Richard, > > It's pretty easy. Surf to the 'issues' page of the Pharo repo, which is in > the 'pharo-project' organization in GitHub: > > https://github.com/pharo-project/pharo/issues > > Click the bright green "New issue" button, then describe away... > > -Ted > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >

Jan. 18, 2020

Re: [Pharo-users] Pharo display bug

by tbrunz

Richard, It's pretty easy. Surf to the 'issues' page of the Pharo repo, which is in the 'pharo-project' organization in GitHub: https://github.com/pharo-project/pharo/issues Click the bright green "New issue" button, then describe away... -Ted -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Jan. 18, 2020

Pharo display bug

by Richard Kenneth Eng

I don't know how to report Pharo bugs, so I'll just mention that the Pharo IDE isn't displaying code properly. For example: [image: image.png] Look at "map cellAt: ". The 'A' and 't" are mashed together. Another example: [image: image.png] Look at ":cellA:cellB | cellA energy ". It's not displaying the space between "cellA" and "energy". This is more than just a display bug because how the hell are you supposed to edit this code??? Richard

Jan. 18, 2020

Re: [Pharo-users] Generate class hierarchy from JSON Schema

by Eric Gade

Serge I would also be interested in seeing what you come up with. On Sat, Jan 18, 2020 at 3:56 AM <serge.stinckwich(a)gmail.com> wrote: > Great work ! I will have a look. > > I want to be able to generate JSON files following a JSON Schema with a > high level API. So my idea was to generate automatically from JSON Schema > the class hierarchy but a runtime model might be enough maybe. > > Regards, > > Sent from my iPhone > > On 18 Jan 2020, at 09:28, Norbert Hartl <norbert(a)hartl.name> wrote: > > ï»¿We have > > https://github.com/zweidenker/JSONSchema > > which is an implementation of basic stuff in JSON schema. But it does not > compile classes it just creates a runtime model. To be honest I never > understood why we make the effort to compile classes for parsed model. The > runtime model works usually pretty well. The only reason I can see is that > it is easier to store somewhere. > > If you like our code and you miss things, we are eager to add the stuff we > not had (yet) reason to do so. > > Norbert > > Am 18.01.2020 um 09:20 schrieb Serge Stinckwich < > serge.stinckwich(a)gmail.com>: > > Hi there, > > anyone has experience about generating a class hierarchy from a JSON > Schema ? Code available somewhere ? > > Thank you. > > -- > Serge Stinckwic > h > > Int. Research Unit > on Modelling/Simulation of Complex Systems (UMMISCO) > Sorbonne University > (SU) > French National Research Institute for Sustainable Development (IRD) > U > niversity of YaoundÃ© I, Cameroon > "Programs must be written for people to read, and only incidentally for > machines to execute." > https://twitter.com/SergeStinckwich > > > -- Eric

Jan. 18, 2020

Re: [Pharo-users] Latest Pharo Update

by horrido

Reinstalling Pharo from scratch fixes it. Somehow, the automatic update is broken. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Jan. 18, 2020