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

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

by eftomi

Todd, this is great, I didn't know that you are working on ActiveRecord. BTW, I have some minor additions to SQLServerPlatform (support for National Language Character Set) and OraclePlatform (Decimal data type) - is there a central git repository for Glorp so that I could PR to? Thanks and best wishes, Tomaz -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Jan. 20, 2020

Re: [Pharo-users] Willow documentation

by TomaÅ¾ Turk

Dear Gabriel, Yes, I followed the steps from the blog - my code is here: https://github.com/eftomi/willow-tryout/blob/master/Poskusi-Willow/ToDoAppl…. Maybe I misunderstood something. Many thanks for additional explanations about Willow coding. Best wishes, Tomaz ------ Original Message ------ From: "Gabriel Cotelli" <g.cotelli(a)gmail.com> To: "TomaÅ¾ Turk" <tomaz.turk(a)ef.uni-lj.si>; "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org> Sent: 20.1.2020 12:49:37 Subject: Re: [Pharo-users] Willow documentation >Hi Tomas, >Comments inline. > >On Sun, Jan 19, 2020 at 2:59 PM TomaÅ¾ Turk <tomaz.turk(a)ef.uni-lj.si> >wrote: >>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: >> >I will check because this looks like a problem in the online version of >the jquery library. You've got this error following just the tutorial >steps? >> >>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 > >There are two operations modes for the component supplier. >If your application will be online on the open internet you can use >Bootstrap4ComponentSupplier online, and this will get the required JS >libraries from the official CDNs. >The second option is to self-serve the libraries (this case is more >common for applications that will run in a closed environment like a >company intranet, or a heavy regulated environment where the access to >open resources on the internet are probably forbidden or require a lot >of bureaucracy and approvals). > >> >>My question is - is there a better documentation available for Willow? >>It's quite hard to study all bits and pieces from scratch. > >The doc available is the one in the repo under /docs, the blog posts >and the sample applications in Willow-Playground. If you have some >ideas on missing docs or parts of the documentation that can be >improved please fill an issue in >https://github.com/ba-st/Willow/issues >> >>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 >>:-) > >Mixing standard Seaside rendering with Willow components it's Ok. The >rule to follow here is: >if the component will need some kind of interaction from the user, a >Willow component will suit your needs better. Usually this gets >initialized once in the component containing it and then it's rendered >many times. In this way you can access the component state easily.for >elements that are more like presentation parts and will not have any >state nor interactions associated it's perfectly Ok to use standard >Seaside rendering. The exception here is in the case of containers >(divs, spans, etc) that you want to get replaced dynamically, for that >cases it's better to use GenericContainerWebView or >PhrasingContainerWebView. >Since some versions Willow extended standard Seaside facilities so you >can use the command-like interface with standard Seaside brushes. Take >a look at WATagBrush Willow extensions. So you can do something like: >html > div > with: [ html text:'Hi!'] > applying: [:container | container addClass bootstrap backgroundInfo] > Where the block in applying: allows the same command-like interface >available for components. > >> >>Best wishes, >>Tomaz >> >> >Regards, >Gabriel

Jan. 20, 2020

Re: [Pharo-users] [ANN] Pharo 8.0 Released!

by Esteban Lorenzano

Links to upvote: https://www.reddit.com/r/programming/comments/erd65s/pharo_80_the_immersive… https://news.ycombinator.com/item?id=22098604 :) > On 20 Jan 2020, at 14:23, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Dear World and dynamic language lovers: > The time has come for Pharo 8.0 <https://pharo.org/>! > Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback. > > Here are the key highlights of this release: > > The 64-bit version has become the recommended version for Windows as it was for Unix and OSX. > Iceberg, the git client for Pharo, reached its version 1.6.5 with several improvements and bugfixes. > Calypso, Pharoâs system browser has new and better refactoring integrations and AST-based suggestions for class definitions. > The unified foreign function interface (UnifiedFFI) has been improved with more support for literal objects, better type coercions, and more documentation. > Several speed improvements in code searches and compilation. > > In addition, this version includes several previews of new tools such as the Spec2 GUI framework with native widget integration and the new DrTests test analysis tool and opens the door for the upcoming headless VMs for servers and non-blocking FFI. > These are just the more prominent highlights, but the details are just as important. We have closed a massive amount of issues: 2805 issues! > A comprehensive changelog can be found at https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo80Change… <https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo60Change…>). > While the technical improvements are significant, still the most impressive fact is that the new code that got in the main Pharo 8.0 image was contributed by more than 100 people. > Pharo is more than code. It is an exciting project involving energetic people. We thank all the contributors to this release: > Serge Stinckwich, Myroslava Romaniuk, Hilaire Fernandes, Alexandre Bergel, David Bajger, Sean DeNigris, Theodore Moen, Dayne Guerra Calle, Juraj Kubelka, Max Leske, Santiago Jose Dandois, Alistair Grant, Sabine Mana, Chia Yu, Stephan Eggermont, Milton Mamani, Pavel Krivanek, Ben Coman, Marcus Denker, Pierre Misse, Christophe Demarey, Allex Oliveira, Andreina Cota, Theo Rogliano, ClÃ©ment Dutriez, Quentin Ducasse, Cyril Ferlicot, Cameron Bierwagen, Marek Niepieklo, Clotilde Toullec, Esteban Lorenzano, Vincent Blondeau, Danil Osipchuk, Eiichiro Ito, Noury Bouraqadi, Oleksandr Zaytsev, Jason Riggs, Alain Plantec, Kasper Osterbye, Leonardo Cecchi, Chi Huynh, Santiago Bragagnolo, Antonio Pierro, Pablo Tesone, Tim Mackinnon, Wesley Duerksen, Wilfred Hughes, John Brant, Evelyn Cusi Lopez, Manuel Leuenberger, Thomas Dupriez, Norbert Hartl, Torsten Bergmann, Gabriel Omar Cotelli, Carlo Teixeira, Guille Polito, Torsten Bergman, Damien Pollet, Holger Hans Peter Freyther, Julio Ripoll, Carolina Hernandez Phillips, Julien Delplanque, Hugo Lasnier, James Foster, Will Hensel, Erik Stel, Sven Van Caekenberghe, MartÃn Dias, Tomohiro Oda, Konrad Hinsen, SeÌbastien Roccaserra, StÃ©phane Ducasse, Denis Kudriashov, Ellis Harris, Steven Costiou > (If you contributed with Pharo 8.0 development in any way and we missed your name, please send us a mail and we will add you). > Enjoy! > The Pharo Team > Try Pharo: http://pharo.org/download <https://pharo.org/download> > Learn Pharo: http://pharo.org/documentation <https://pharo.org/documentation> > > If you cannot see this, follow this link: http://pharo.org/news/pharo8.0-released <http://pharo.org/news/pharo8.0-released>

Jan. 20, 2020

[ANN] Pharo 8.0 Released!

by Esteban Lorenzano

Dear World and dynamic language lovers: The time has come for Pharo 8.0 <https://pharo.org/>! Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback. Here are the key highlights of this release: The 64-bit version has become the recommended version for Windows as it was for Unix and OSX. Iceberg, the git client for Pharo, reached its version 1.6.5 with several improvements and bugfixes. Calypso, Pharoâs system browser has new and better refactoring integrations and AST-based suggestions for class definitions. The unified foreign function interface (UnifiedFFI) has been improved with more support for literal objects, better type coercions, and more documentation. Several speed improvements in code searches and compilation. In addition, this version includes several previews of new tools such as the Spec2 GUI framework with native widget integration and the new DrTests test analysis tool and opens the door for the upcoming headless VMs for servers and non-blocking FFI. These are just the more prominent highlights, but the details are just as important. We have closed a massive amount of issues: 2805 issues! A comprehensive changelog can be found at https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo80Change… <https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo60Change…>). While the technical improvements are significant, still the most impressive fact is that the new code that got in the main Pharo 8.0 image was contributed by more than 100 people. Pharo is more than code. It is an exciting project involving energetic people. We thank all the contributors to this release: Serge Stinckwich, Myroslava Romaniuk, Hilaire Fernandes, Alexandre Bergel, David Bajger, Sean DeNigris, Theodore Moen, Dayne Guerra Calle, Juraj Kubelka, Max Leske, Santiago Jose Dandois, Alistair Grant, Sabine Mana, Chia Yu, Stephan Eggermont, Milton Mamani, Pavel Krivanek, Ben Coman, Marcus Denker, Pierre Misse, Christophe Demarey, Allex Oliveira, Andreina Cota, Theo Rogliano, ClÃ©ment Dutriez, Quentin Ducasse, Cyril Ferlicot, Cameron Bierwagen, Marek Niepieklo, Clotilde Toullec, Esteban Lorenzano, Vincent Blondeau, Danil Osipchuk, Eiichiro Ito, Noury Bouraqadi, Oleksandr Zaytsev, Jason Riggs, Alain Plantec, Kasper Osterbye, Leonardo Cecchi, Chi Huynh, Santiago Bragagnolo, Antonio Pierro, Pablo Tesone, Tim Mackinnon, Wesley Duerksen, Wilfred Hughes, John Brant, Evelyn Cusi Lopez, Manuel Leuenberger, Thomas Dupriez, Norbert Hartl, Torsten Bergmann, Gabriel Omar Cotelli, Carlo Teixeira, Guille Polito, Torsten Bergman, Damien Pollet, Holger Hans Peter Freyther, Julio Ripoll, Carolina Hernandez Phillips, Julien Delplanque, Hugo Lasnier, James Foster, Will Hensel, Erik Stel, Sven Van Caekenberghe, MartÃn Dias, Tomohiro Oda, Konrad Hinsen, SeÌbastien Roccaserra, StÃ©phane Ducasse, Denis Kudriashov, Ellis Harris, Steven Costiou (If you contributed with Pharo 8.0 development in any way and we missed your name, please send us a mail and we will add you). Enjoy! The Pharo Team Try Pharo: http://pharo.org/download <https://pharo.org/download> Learn Pharo: http://pharo.org/documentation <https://pharo.org/documentation> If you cannot see this, follow this link: http://pharo.org/news/pharo8.0-released

Jan. 20, 2020

New Smalltalk Blog

by Richard Kenneth Eng

I've created a new Smalltalk blog <https://smalltalk.tech.blog/>. I've left Medium because of their pressure to put everyone behind a paywall. I've opened up the blog for third-party submissions. Anyone can email me an article submission and if I deem it appropriate, I will edit and publish it. Here's an example from Leandro Caniglia, President of FAST: Extending the Smalltalk Syntax <https://smalltalk.tech.blog/2020/01/20/extending-the-smalltalk-syntax/>. Articles should serve to showcase why Smalltalk is such a great language. If possible, an accompanying eye-catching feature image would be nice. (If you look at the other posts, you'll see images of a Maserati and a Tesla!) I would prefer the article submissions to be in LibreOffice format. It would make it easier for me to edit. Thanks, Richard

Jan. 20, 2020

Re: [Pharo-users] Pharo connect to PostgreSQL

by Sven Van Caekenberghe

Hi, You are not saying which library/framework you are trying to use. One up to date option is P3, the "lean and mean PostgreSQL client for Pharo " [ https://github.com/svenvc/P3 ]. A connection to your database could then be specified using a URL. To test the connection: (P3Client url: 'psql://postgres:lucian@localhost:5432/mydb') in: [ :client | [ client isWorking ] ensure: [ client close ] ]. To do a query: (P3Client url: 'psql://postgres:lucian@localhost:5432/mydb') in: [ :client | [ (client query: 'SELECT * FROM some_table') recordsAsDictionaries ] ensure: [ client close ] ]. Of course, you first have to make sure external clients can connect to your db (try the psql command line client over TCP first). HTH, Sven Apart from https://postgresql.org, the following site is pretty good: https://www.postgresqltutorial.com. On macOS, I recommend https://postgresapp.com. > On 20 Jan 2020, at 12:37, Macmus via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > > From: Macmus <luci.barcan(a)yahoo.com> > Subject: Pharo connect to PostgreSQL > Date: 20 January 2020 at 12:37:13 GMT+1 > To: pharo-users(a)lists.pharo.org > > > I am trying to connect to a PostgreSQL database from Pharo but I keep getting > "SubscriptOutOfBounds: 11" error (I am a beginner). The server is started > and the database is working fine. What am I missing? > > > |connectionArguments connection resultSets resultSet rows firstRow| > > connectionArguments := PG3ConnectionArguments new > hostname: 'localhost'; > port: 5432; > username: 'postgres'; > password: 'lucian'; > databaseName: 'mydb' > yourself. > connection := connectionArguments newConnection. > > connection startup. > > resultSets := connection execute: 'select 3 + 4, now()'. > resultSet := resultSets first. > rows := resultSet rows. > firstRow := rows first. > firstRow at: 1. > firstRow at: 2. > > connection terminate. > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > > >

Jan. 20, 2020

Re: [Pharo-users] Willow documentation

by Gabriel Cotelli

Hi Tomas, Comments inline. On Sun, Jan 19, 2020 at 2:59 PM TomaÅ¾ Turk <tomaz.turk(a)ef.uni-lj.si> wrote: > 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: > > I will check because this looks like a problem in the online version of the jquery library. You've got this error following just the tutorial steps? > > 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 > There are two operations modes for the component supplier. 1. If your application will be online on the open internet you can use Bootstrap4ComponentSupplier online, and this will get the required JS libraries from the official CDNs. 2. The second option is to self-serve the libraries (this case is more common for applications that will run in a closed environment like a company intranet, or a heavy regulated environment where the access to open resources on the internet are probably forbidden or require a lot of bureaucracy and approvals). > > My question is - is there a better documentation available for Willow? > It's quite hard to study all bits and pieces from scratch. > The doc available is the one in the repo under /docs, the blog posts and the sample applications in Willow-Playground. If you have some ideas on missing docs or parts of the documentation that can be improved please fill an issue in https://github.com/ba-st/Willow/issues > > 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 :-) > Mixing standard Seaside rendering with Willow components it's Ok. The rule to follow here is: - if the component will need some kind of interaction from the user, a Willow component will suit your needs better. Usually this gets initialized once in the component containing it and then it's rendered many times. In this way you can access the component state easily. - for elements that are more like presentation parts and will not have any state nor interactions associated it's perfectly Ok to use standard Seaside rendering. The exception here is in the case of containers (divs, spans, etc) that you want to get replaced dynamically, for that cases it's better to use GenericContainerWebView or PhrasingContainerWebView. Since some versions Willow extended standard Seaside facilities so you can use the command-like interface with standard Seaside brushes. Take a look at WATagBrush Willow extensions. So you can do something like: html div with: [ html text: 'Hi!'] applying: [:container | container addClass bootstrap backgroundInfo] Where the block in applying: allows the same command-like interface available for components. > Best wishes, > Tomaz > > > Regards, Gabriel

Jan. 20, 2020

Pharo connect to PostgreSQL

by Macmus

I am trying to connect to a PostgreSQL database from Pharo but I keep getting "SubscriptOutOfBounds: 11" error (I am a beginner). The server is started and the database is working fine. What am I missing? |connectionArguments connection resultSets resultSet rows firstRow| connectionArguments := PG3ConnectionArguments new hostname: 'localhost'; port: 5432; username: 'postgres'; password: 'lucian'; databaseName: 'mydb' yourself. connection := connectionArguments newConnection. connection startup. resultSets := connection execute: 'select 3 + 4, now()'. resultSet := resultSets first. rows := resultSet rows. firstRow := rows first. firstRow at: 1. firstRow at: 2. connection terminate. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Jan. 20, 2020

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