- Pharo-users - lists.pharo.org

Re: [Pharo-users] Glorp + P3 + SQLite
by Pierce Ng Oct. 22, 2019

Oct. 22, 2019

On Sat, Oct 19, 2019 at 01:26:10AM -0700, Todd Blanchard via Pharo-users wrote: > I loaded GLORP+P3 without issue. > Trying to load SQLite3 - it also wants to load GLORP which complains of conflict. Todd, to load SQLite3 only: Metacello new repository: 'github://astares/Pharo-UDBC/src'; baseline: 'UDBC'; load: 'SQLite' Pierce

2 1

Moving pharo
by Kasper Ãsterbye Oct. 22, 2019

Oct. 22, 2019

Today is a big day for some in Denmark. We are moving an old landmark lighthouse 80m inland. https://media.scribblelive.com/2019/10/22/72511d80-c9c1-4a19-b8d8-eec2cad61… I have the feeling it is not that different from moving Pharo. A lot of people working, and progress is slow but steady. About 40sec into it, you see the whole lighthouse. Best, Kasper

1 0

Pillar in-image rendering as RichText
by Kasper Ãsterbye Oct. 22, 2019

Oct. 22, 2019

Cheers, Rendering the Pillar markup inside the Pharo image This is work in (early) progress, but I think it is far enough for a "technology preview". <https://github.com/kasperosterbye/PillarRichTextRender/blob/master/README.m…>Goal of the project The goal of the project is to be able to do better in-image documentation. To do this, I am working on several fronts: 1. Rendering more pillar, expecially I would like to get a solution for tables. 2. Rendering github markdown in addition to pillar markdown. This will allow me to pull markdown from git and display it in-image. 3. Giving the "help-system" some love. 4. In-image tools for writing markdown - a markdown editor 5. A design for keeping the mark-down texts seamlessly outside of the image Reg. 1., I can only figure out how to transform a morphic table into an image, and then add that image to the text (not included atm as I find it so ugly a solution). Any other ideas are greatly appreciated. Reg. 2. I am nearly done on this one, at least for the easy aspects (headers, lists, emphasis, code-blocks). Reg 3 and 4. Only loose ideas atm. <https://github.com/kasperosterbye/PillarRichTextRender/blob/master/README.m…>Trying it out Load it using Metacello: Metacello new baseline: 'PillarRichTextRender'; repository: 'github://kasperosterbye/PillarRichTextRender'; load. At the moment it will load the whole of Pillar, but I hope to fix that soon. Once loaded, the class PRRichTextComposer has some examples on the class side.

4 6

String concatenation vs. Stream
by Kasper Ãsterbye Oct. 21, 2019

Oct. 21, 2019

This is an old one, and I knew of cause that one should not use #, when you can use streams instead. But that is was this bad to use #, came as a surprise I must say <https://gist.github.com/kasperosterbye/d8c9bd518fba68289c9f129d553ad6b6> Best, Kasper

7 11

[ANN] HeySql v1.1
by Petter Oct. 21, 2019

Oct. 21, 2019

Hi, I have just released HeySql, version 1.1 - a database orm for Postgresql. - Support for migrations - Generation of migration templates based on classes - Models can now be subclassed - Updated license to MIT - Updated docs - Some minor stuff https://github.com/pegesund/heysql Petter -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

2 2

PharoADO
by eftomi Oct. 21, 2019

Oct. 21, 2019

Dear all, A working prototype of PharoADO is now available at https://github.com/eftomi/pharo-ado. I'd be glad if you can find the time to test it and report your observations to this list or on the GitHub. PRs are welcome and much needed :-) Firstly, I would like to focus on various database data types. When using ADOClient and ADORecordset, the availability of data types heavily depends from PharoWin32/PharoCOM packages, so we have to update both repositories :-) The PharoADO package is not huge after all, since ActiveX Data Objects itself is an abstraction layer and provides much of the needed functionalities by itself. Best wishes, Tomaz -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

4 6

Strategy for investigating test failures
by PBKResearch Oct. 20, 2019

Oct. 20, 2019

Hello all I have done some experiments, and basically all the questions in my previous mail can be ignored. I think it is all a question of timing, which I sort of understand. Perhaps someone can clarify for me. All my previous tests involved running the whole test suite, to ensure the set-up and tear-down methods were run. As an experiment, I selected the one red method and clicked 'Run Tests'. After about 10 seconds, a halt appeared with the message 'Test took too long'. When I clicked 'Proceed', the green appeared almost immediately. I tried again several times with similar results, although the halt occurred at different places in the code. I went back to my old P6 version and tried running tests on the one method; each time, it ran to green in about 11-12 seconds. So back now to the P7 version; wondered if there is now a setting for permitted test duration. Eventually found it under 'System', default 10 secs. Changed to 15 secs, re-run red test, now comes up green. Re-run whole test suite, all green. So it all comes down to my ignorance of test settings. But Pharo is less than helpful; if you run the whole test suite, there is no way to distinguish a test which failed due to a wrong assertion from one which was terminated for taking too long - or did I miss something? Peter Kenny

3 5

Re: [Pharo-users] Glorp + P3 + SQLite
by HernÃ¡n Morales Durand Oct. 20, 2019

Oct. 20, 2019

Hi Todd, El sÃ¡b., 19 oct. 2019 a las 13:11, Todd Blanchard via Pharo-users (< pharo-users(a)lists.pharo.org>) escribiÃ³: > I should probably mention that I do not really have a great handle on how > package configurations work these days. > > Coming back to Smalltalk after a long time away. > > Welcome back! > Pointer to an explanation of how package configurations work would be > great. > > Have a look at: https://github.com/pharo-open-documentation/pharo-wiki/blob/master/General/… Cheers, HernÃ¡n

1 0

ESUG Videos
by Norbert Hartl Oct. 20, 2019

Oct. 20, 2019

It has been a while since ESUG took place in cologne. We are sorry for the delay in providing the videos of the talks but the end of summer was a busy time for the guy doing the videos and there is quite some material to post-process. Talk videos are prepared now and we start soon to upload them to the github channel at [1]. Additional to the talks we ordered a short image video for the conference so people get an impression what the event is like. As a teaser before the uploading starts we want to make the image video available to you https://zweidenker.de/en/esug-conference-2019/ <https://zweidenker.de/en/esug-conference-2019/> As soon as there are videos available Marcus will drop a note about it. Hope you like it! the ZWEIDENKER Team [1] https://www.youtube.com/channel/UCO-vBhaKVZf0al-ISMMPvRw <https://www.youtube.com/channel/UCO-vBhaKVZf0al-ISMMPvRw>

1 0

Strategy for investigating test failures
by PBKResearch Oct. 20, 2019

Oct. 20, 2019

Hello all I would be grateful for hints on strategy in investigating test failures on upgrade. It is an area in which I have no experience; I can see some brute force approaches, but I suspect there are cleverer ways to do it. I have OmniBase working successfully on Moose Suite 6.1 (Pharo 6.0, Latest update: #60541, 32-bit) on Windows 10. All the tests are green, and everything I have tried for my own data works well. To get a bit nearer to the state of the art, I tried to load OmniBase into a new 32-bit Pharo 7 image, created via Pharo Launcher a few days ago. I now have all tests green except one - named 'testBTreeKeyLocking'. Since I am working in single-user mode, I do not expect to need key locking, so I could go on without worrying about it. But I am left with a nagging worry, and I would like to find out what is wrong. The test method has altogether 8 assert/deny statements, so I do not know where to start. 1. Is there any obvious reason why the upgrade should make working code fail? Does P7 have a different compiler? If so, can I switch to an older compiler and see if it is that? (On P6 andP7, the code mentor complains that it should use 'assert:equals:' rather than 'assert:' and = , but that is true in all the other test methods.) 2. Is there any easy way in the test framework to work out which assert/deny has failed? 3. I could insert 'self halt' all over the place and use the debugger, or run the method in debug mode; would this be an approved way of doing it? The test suite creates and manipulates tiny databases; I am not sure whether there might be timing issues in stepping through the code. Any help or suggestions gratefully received. Peter Kenny

1 0