December 2021 - Pharo-users

Re: Pharo9 GLORP + MySQL

by laszlo.szolnoki＠gmail.com

Iâm halfway through the documentation and made some tests. I am very impressed by ReStore so far, to say the least. Feels like a Christmas present :) Thank you, Sir. Laszlo

Dec. 24, 2021

Re: Pharo-WebView

by Russ Whaley

I tried to run the commands in terminal in MacOS... it didn't even (nor did I) understand 'go' so we were both stymied at step one (lol). I'll pick it up again after the holidays and give it another try with my full attention. Happy Holidays, Russ On Thu, Dec 23, 2021 at 1:06 PM <tomazz.turk(a)gmail.com> wrote: > @Todd, @Russ, yes, with Gtk3 it's a bit harder than I expected. > > Gtk3 has a main message loop gtk_main() which, as it is being used in the webview > library <https://github.com/webview/webview> that I chose, blocks Pharo > completely while webview window is active. On Windows, the webview window > in general works without engaging the main message loop, but windows > implementation doesn't rely on Gtk3 but on Edge. > > On Linux, I firstly tried to put this webview library into a separate > thread (a worker with headless image), however in this kind of setup the > callbacks from the library cannot reach Pharo main thread. I solved this by > exposing two additional Gtk3 functions in webview library, > gtk_events_pending() and gtk_main_iteration() which enabled the > construction of main event loop in Pharo that I run on the Idle Process > priority level so that it doesn't take 100% of the processor time, like > this: > > proc := [[ true ] > > whileTrue: [ > > (wv ffiEventsPending = 1) ifTrue: > > [wv ffiRunIteration]. > > Processor yield. > > ]] forkAt: Processor lowestPriority. > > So I don't need to run the webview library in separate thread, which is a > bit simpler, and the callbacks work as they should. Now I just have to > create some signaling so that Pharo will know if the user closes the > webview window, and check if two Pharo classes that I already have (WebView > and WebViewCallback) will suffice for these additional complications. > > If anybody has a better idea for main loop implementation, I'm opened to > suggestions :-) > > The webview library that I chose uses Cocoa on MacOS, so no Gtk3 there. I > hope that it will not be too difficult and that the above "one thread > approach" will be OK for MacOS, too. Gtk3 was quite challenging, I was also > considering to drop whis webview library and use gtk-bindings for Pharo > directly, however then I would not be consistent also for Edge and Cocoa > (in using one "umbrella" library). As far as I know, the webview general > intention is to use the native GUI technology as much as possible. > > Best wishes, > Tomaz > -- Russ Whaley whaley.russ(a)gmail.com

Dec. 23, 2021

Re: Pharo9 GLORP + MySQL

by Todd Blanchard

Load the glorp target from the MySQL repository. > On Dec 22, 2021, at 1:33 PM, laszlo.szolnoki(a)gmail.com wrote: > > Hi, Iâm new to the Pharo users mailing list and to Pharo in general, too. > > My goal is to make a CRUD web application using Seaside, Magritte, GLORP and MariaDB (MySQL-like RDBMS). > > I already test-drove GLORP with PostgreSQL-P3, with success. > > But I need MariaDB because it implements SQL:2011 (which Postgres lacks currently) thus enabling the use of system-versioned and bi-temporal tables. > > Currently I donât need GLORP to handle any of the SQL:2011 features as the versioning would be invisible to the web app, it is needed only for auditing purposes. > > I tried to make the system work be installing the MySQL driver into a fresh Pharo9 image: > > Metacello new repository: 'github://pharo-rdbms/Pharo-MySQL'; baseline: 'MySQL'; load Since the package 'MySQL-Glorp' didn't load, I installed it manually from github. (Sorry but I'm noob to work with baselines, Iceberg, Monticello and such.) Then loaded GLORP: Metacello new repository: 'github://pharo-rdbms/glorp'; baseline: 'Glorp'; load. Then I tried to do everything in a similar manner to how I did it with P3: login := Login new database: MySQLPlatform new; username: 'root'; password: '****'; host: '<my host>'; port: '3306'; databaseName: 'test'. accessor := DatabaseAccessor forLogin: login. accessor login. accessor isLoggedIn. >>> true Yay, very nice. Then: session := GlorpBookDescriptorSystem sessionForLogin: login. *GlorpBookDescriptorSystem is subclass of DescriptorSystem. It comes from the demo from pharobooks with an example on how to use GLORP with P3. It contains the demo class models, descriptors and table definitions. And finally: session login. >>> Instance of MySQLDriver did not understand #queryEncoding :( Any hints appreciated. > >

Dec. 23, 2021

Re: Pharo-WebView

by tomazz.turk＠gmail.com

@Todd, @Russ, yes, with Gtk3 it's a bit harder than I expected. Gtk3 has a main message loop gtk_main() which, as it is being used in the [webview library](https://github.com/webview/webview) that I chose, blocks Pharo completely while webview window is active. On Windows, the webview window in general works without engaging the main message loop, but windows implementation doesn't rely on Gtk3 but on Edge. On Linux, I firstly tried to put this webview library into a separate thread (a worker with headless image), however in this kind of setup the callbacks from the library cannot reach Pharo main thread. I solved this by exposing two additional Gtk3 functions in webview library, gtk_events_pending() and gtk_main_iteration() which enabled the construction of main event loop in Pharo that I run on the Idle Process priority level so that it doesn't take 100% of the processor time, like this: `proc := [[ true ] ` ` whileTrue: [ ` ` (wv ffiEventsPending = 1) ifTrue: ` ` [wv ffiRunIteration]. ` ` Processor yield.` ` ]] forkAt: Processor lowestPriority.` So I don't need to run the webview library in separate thread, which is a bit simpler, and the callbacks work as they should. Now I just have to create some signaling so that Pharo will know if the user closes the webview window, and check if two Pharo classes that I already have (WebView and WebViewCallback) will suffice for these additional complications. If anybody has a better idea for main loop implementation, I'm opened to suggestions :-) The webview library that I chose uses Cocoa on MacOS, so no Gtk3 there. I hope that it will not be too difficult and that the above "one thread approach" will be OK for MacOS, too. Gtk3 was quite challenging, I was also considering to drop whis webview library and use gtk-bindings for Pharo directly, however then I would not be consistent also for Edge and Cocoa (in using one "umbrella" library). As far as I know, the webview general intention is to use the native GUI technology as much as possible. Best wishes,\ Tomaz

Dec. 23, 2021

Re: Pharo9 GLORP + MySQL

by John Aspinall

Hi - I canât help with your GLORP query but you may find ReStore a viable alternative, particularly if you're starting with a new database: https://github.com/rko281/ReStoreForPharo <https://github.com/rko281/ReStoreForPharo> Iâve just checked and the MySQL/MariaDB connector is working in both Pharo 9 and 10. Cheers. John Aspinall > On 22 Dec 2021, at 20:33, laszlo.szolnoki(a)gmail.com wrote: > > Hi, Iâm new to the Pharo users mailing list and to Pharo in general, too. > > My goal is to make a CRUD web application using Seaside, Magritte, GLORP and MariaDB (MySQL-like RDBMS). > > I already test-drove GLORP with PostgreSQL-P3, with success. > > But I need MariaDB because it implements SQL:2011 (which Postgres lacks currently) thus enabling the use of system-versioned and bi-temporal tables. > > Currently I donât need GLORP to handle any of the SQL:2011 features as the versioning would be invisible to the web app, it is needed only for auditing purposes. > > I tried to make the system work be installing the MySQL driver into a fresh Pharo9 image: > > Metacello new repository: 'github://pharo-rdbms/Pharo-MySQL'; baseline: 'MySQL'; load Since the package 'MySQL-Glorp' didn't load, I installed it manually from github. (Sorry but I'm noob to work with baselines, Iceberg, Monticello and such.) Then loaded GLORP: Metacello new repository: 'github://pharo-rdbms/glorp'; baseline: 'Glorp'; load. Then I tried to do everything in a similar manner to how I did it with P3: login := Login new database: MySQLPlatform new; username: 'root'; password: '****'; host: '<my host>'; port: '3306'; databaseName: 'test'. accessor := DatabaseAccessor forLogin: login. accessor login. accessor isLoggedIn. >>> true Yay, very nice. Then: session := GlorpBookDescriptorSystem sessionForLogin: login. *GlorpBookDescriptorSystem is subclass of DescriptorSystem. It comes from the demo from pharobooks with an example on how to use GLORP with P3. It contains the demo class models, descriptors and table definitions. And finally: session login. >>> Instance of MySQLDriver did not understand #queryEncoding :( Any hints appreciated. > >

Dec. 23, 2021

Re: Pharo-WebView

by Russ Whaley

Todd, me neither, but I am a bit worried about mentions of gtk, as I havenât been able to get that to work either :( On Fri, Dec 17, 2021 at 12:50 PM Todd Blanchard via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > Seems cool but I can't figure out how to build it as a library on MacOS. > > > On Dec 16, 2021, at 10:02 AM, TomaÅ¾ Turk <tomazz.turk(a)gmail.com> wrote: > > Dear all, > > Pharo-WebView package is now available on GitHub at > https://github.com/eftomi/Pharo-Webview. > > Pharo-WebView is a package which implements a binding to webview dll > library available at https://github.com/webview/webview in Pharo. Webview > allows you to show HTML user interfaces in a native window, inject > JavaScript code and HTML content into the window. It renders HTML > originating via web requests or as a direct input. > > I tested it on Windows 64 bit in Pharo 64, I plan to do that on Pharo 32 > and Linux, however I don't have access to Mac, so if anybody is interested, > I'd be grateful :-) > > Best wishes, > Tomaz > > > -- Russ Whaley whaley.russ(a)gmail.com

Dec. 22, 2021

Pharo9 GLORP + MySQL

by laszlo.szolnoki＠gmail.com

Hi, Iâm new to the Pharo users mailing list and to Pharo in general, too. My goal is to make a CRUD web application using Seaside, Magritte, GLORP and MariaDB (MySQL-like RDBMS). I already test-drove GLORP with PostgreSQL-P3, with success. But I need MariaDB because it implements SQL:2011 (which Postgres lacks currently) thus enabling the use of system-versioned and bi-temporal tables. Currently I donât need GLORP to handle any of the SQL:2011 features as the versioning would be invisible to the web app, it is needed only for auditing purposes. I tried to make the system work be installing the MySQL driver into a fresh Pharo9 image: Metacello new repository: 'github://pharo-rdbms/Pharo-MySQL'; baseline: 'MySQL'; load Since the package 'MySQL-Glorp' didn't load, I installed it manually from github. (Sorry but I'm noob to work with baselines, Iceberg, Monticello and such.) Then loaded GLORP: Metacello new repository: 'github://pharo-rdbms/glorp'; baseline: 'Glorp'; load. Then I tried to do everything in a similar manner to how I did it with P3: login := Login new database: MySQLPlatform new; username: 'root'; password: '\*\*\*\*'; host: '<my host>'; port: '3306'; databaseName: 'test'. accessor := DatabaseAccessor forLogin: login. accessor login. accessor isLoggedIn. >>> true Yay, very nice. Then: session := GlorpBookDescriptorSystem sessionForLogin: login. \*GlorpBookDescriptorSystem is subclass of DescriptorSystem. It comes from the demo from pharobooks with an example on how to use GLORP with P3. It contains the demo class models, descriptors and table definitions. And finally: session login. >>> Instance of MySQLDriver did not understand #queryEncoding \:( Any hints appreciated.

Dec. 22, 2021

Re: Pharo won't start on Ubuntu

by hedley.finger＠gmail.com

I tried finding all pharo locations: `hedster:/$ whereis pharo` `pharo: /usr/bin/pharo /usr/lib/x86_64-linux-gnu/pharo9.0 /snap/bin/pharo /snap/bin/pharo.getimage /snap/bin/pharo.cleanimage32 /snap/bin/pharo.getimage32 /snap/bin/pharo.cleanimage /snap/bin/pharo.config /snap/bin/pharo.ui /snap/bin/pharo.sqlite3` Hope this helps. Regards, Hedster

Dec. 22, 2021

Pharo won't start on Ubuntu

by hedley.finger＠gmail.com

Pharo 9 (amd64) Ubuntu 20.04.3 LTS (Focal Fossa) I installed Pharo 9 by following the instructions for Xubuntu 20.04 at [OpenSuse Builder](https://bityl.co/ABlH "OpenSuse Builder"). Next I checked for a starter script: `hedster:~$ which pharo` `/usr/bin/pharo` Then I executed the script â¦ `hedster:~$ pharo` â¦ which did not start the Pharo GUI but produced a pile of error messages I donât understand. Iâm sorry to inflict this on you because it is rather long. See the CLI output below. Regards, Hedster --- `hedley-PC:~$ pharo` `Module not found.` `LGitLibrary(Object)>>error:` `LGitLibrary>>unixModuleName` `LGitLibrary(FFILibrary)>>unixLibraryName` `LGitLibrary(FFILibrary)>>unix64LibraryName` `Unix64Platform>>ffiLibraryName:` `LGitLibrary(FFILibrary)>>libraryName` `FFICalloutMethodBuilder>>libraryName` `FFICalloutMethodBuilder>>createFFICalloutLiteralFromSpec:` `FFICalloutMethodBuilder>>generateFFICallout:spec:` `[ :builder | self generateFFICallout: builder spec: functionSpec ] in FFICalloutMethodBuilder>>generateMethodFromSpec: in Block: [ :builder | self generateFFICallout: builder spec...etc...` `IRBuilder class>>buildIR:` `FFICalloutMethodBuilder>>generateMethodFromSpec:` `FFICalloutMethodBuilder>>generate` `FFICalloutMethodBuilder>>build:` `FFICalloutAPI>>function:library:` `LGitLibrary(Object)>>ffiCall:library:options:` `LGitLibrary(Object)>>ffiCall:library:` `LGitLibrary(Object)>>ffiCall:` `LGitLibrary>>libgit2_init` `[ self libgit2_init.` `self recordInitializationSuccess ] in LGitLibrary>>initializeLibGit2 in Block: [ self libgit2_init....` `BlockClosure>>on:do:` `LGitLibrary>>initializeLibGit2` `LGitLibrary class>>startUp:` `ClassSessionHandler>>startup:` `[ :each | each startup: isImageStarting ] in WorkingSession>>runStartup: in Block: [ :each | each startup: isImageStarting ]` `[ aBlock value: each ] in [ :each | ` `[ aBlock value: each ]` ` on: Exception` ` do: [ :error | self errorHandler handleError: error ] ] in WorkingSession>>runList:do: in Block: [ aBlock value: each ]` `BlockClosure>>on:do:` `[ :each | ` `[ aBlock value: each ]` ` on: Exception` ` do: [ :error | self errorHandler handleError: error ] ] in WorkingSession>>runList:do: in Block: [ :each | ...` `Array(SequenceableCollection)>>do:` `WorkingSession>>runList:do:` `Failed to find SDL2 library.` `SDL2 class(Object)>>error:` `SDL2 class>>findSDL2` `SDL2 class>>moduleName` `SDL2 class>>ffiLibraryName` `SDL2 class(Object)>>ffiLibrary` `SDL2 class(Object)>>ffiCall:` `SDL2 class>>setHint:value:` `SDL2 class>>initLibrary` `SDL2 class>>initEverything` `OSSDL2Driver>>initialize` `OSSDL2Driver class(Behavior)>>new` `OSWindowDriver class>>current` `OSWorldRenderer>>pickMostSuitableWindowDriver` `OSWorldRenderer>>doActivate` `OSWorldRenderer(AbstractWorldRenderer)>>activate` `WorldState>>worldRenderer:` `MorphicUIManager>>activate` `UIManager class>>default:` `UIManagerSessionHandler>>startup:` `[ :each | each startup: isImageStarting ] in WorkingSession>>runStartup: in Block: [ :each | each startup: isImageStarting ]` `[ aBlock value: each ] in [ :each | ` `[ aBlock value: each ]` ` on: Exception` ` do: [ :error | self errorHandler handleError: error ] ] in WorkingSession>>runList:do: in Block: [ aBlock value: each ]` `BlockClosure>>on:do:` `[ :each | ` `[ aBlock value: each ]` ` on: Exception` ` do: [ :error | self errorHandler handleError: error ] ] in WorkingSession>>runList:do: in Block: [ :each | ...` `Array(SequenceableCollection)>>do:` `WorkingSession>>runList:do:` `WorkingSession>>runStartup:` `WorkingSession>>start:` `SessionManager>>launchSnapshot:andQuit:` `[ isImageStarting := self launchSnapshot: save andQuit: quit.` `wait signal ] in SessionManager>>snapshot:andQuit: in Block: [ isImageStarting := self launchSnapshot: save and...etc...` `[ self value.` `Processor terminateActive ] in BlockClosure>>newProcess in Block: [ self value....` `Error: Failed to find SDL2 library.` `SDL2 class(Object)>>error:` `SDL2 class>>findSDL2` `SDL2 class>>moduleName` `SDL2 class>>ffiLibraryName` `SDL2 class(Object)>>ffiLibrary` `SDL2 class(Object)>>ffiCall:` `SDL2 class>>setHint:value:` `SDL2 class>>initLibrary` `SDL2 class>>initEverything` `OSSDL2Driver>>initialize` `OSSDL2Driver class(Behavior)>>new` `OSWindowDriver class>>current` `OSWorldRenderer>>pickMostSuitableWindowDriver` `OSWorldRenderer>>doActivate` `OSWorldRenderer(AbstractWorldRenderer)>>activate` `WorldState>>worldRenderer:` `MorphicUIManager>>activate` `UIManager class>>default:` `UIManagerSessionHandler>>startup:` `[ :each | each startup: isImageStarting ] in WorkingSession>>runStartup: in Block: [ :each | each startup: isImageStarting ]` `[ aBlock value: each ] in [ :each | ` `[ aBlock value: each ]` ` on: Exception` ` do: [ :error | self errorHandler handleError: error ] ] in WorkingSession>>runList:do: in Block: [ aBlock value: each ]` `BlockClosure>>on:do:` `[ :each | ` `[ aBlock value: each ]` ` on: Exception` ` do: [ :error | self errorHandler handleError: error ] ] in WorkingSession>>runList:do: in Block: [ :each | ...` `Array(SequenceableCollection)>>do:` `WorkingSession>>runList:do:` `WorkingSession>>runStartup:` `WorkingSession>>start:` `SessionManager>>launchSnapshot:andQuit:` `[ isImageStarting := self launchSnapshot: save andQuit: quit.` `wait signal ] in SessionManager>>snapshot:andQuit: in Block: [ isImageStarting := self launchSnapshot: save and...etc...` `[ self value.` `Processor terminateActive ] in BlockClosure>>newProcess in Block: [ self value....` `#renderer was sent to nil` `UndefinedObject(Object)>>doesNotUnderstand: #renderer` `UndefinedObject>>doesNotUnderstand: #renderer` `OSWorldRenderer>>osWindowRenderer` `OSWorldRenderer>>checkForNewScreenSize` `WorldState>>doOneCycleNowFor:` `WorldState>>doOneCycleFor:` `WorldMorph>>doOneCycle` `WorldMorph class>>doOneCycle` `[ [ WorldMorph doOneCycle.` `Processor yield.` `false ] whileFalse: [ ] ] in MorphicUIManager>>spawnNewProcess in Block: [ [ WorldMorph doOneCycle....` `[ self value.` `Processor terminateActive ] in BlockClosure>>newProcess in Block: [ self value....`

Dec. 22, 2021

Survey of Library Update and Breaking Changes

by Oleksandr Zaitsev

Hi everyone, Could you please take 5-10 minutes of your time to take part in our survey? We want to understand how developers deal with API breaking changes, what problems do they have when updating to the new version, etc. https://framaforms.org/library-update-how-to-manage-dependencies-on-the-evo… If you are also developing a library, framework, or microservice (anything that has an API, multiple versions, and some users other than yourself), please answer my second survey: https://framaforms.org/library-update-how-do-you-manage-changes-in-the-api-… This survey is also quick to answer (5-10 min). And this doesn't have to be a very big library. Even if you developed a small tool that some people use, I am really interested in your answers! If you are interested in the results of those two surveys, please specify your email address (last optional question) and I will send you the summary of our study. Thank you for your help, Oleksandr

Dec. 21, 2021