December 2022 - Pharo-users

Mardeep as a format to (re)publish and exchange Pharo powered data narratives, lesson and book(let)s
by Offray Vladimir Luna CÃ¡rdenas Dec. 15, 2022

Dec. 15, 2022

Hi, As I told in a previous message, we, at the Grafoscopio[1][1a][1b] community, are migrating some lessons learned since 2015 to the new capabilities available since last year via Lepiter[2]. And one of such lessons is the use of human friendly data formats for exchanging and publishing data narratives. [1] https://mutabit.com/grafoscopio/en.html [1a] https://mutabit.com/repos.fossil/grafoscopio/doc/tip/intro.md [1b] https://mutabit.com/repos.fossil/grafoscopio/doc/tip/readme.md.html [2] https://lepiter.io/feenk/introducing-lepiter--knowledge-management--e2p6apq… Originally, in Grafoscopio, we made this friendly format by embedding Markdown inside STON, as shown in the Grafoscopio Manual (PDF[3], source code [3a]) and now we are flipping the strategy: embedding STON metadata in Mardeep[4]/Markdown, which allows us to exchange and publish Pharo powered data narratives, lessons and book(let)s in a pretty light format as shown by the republication of the "PetitParser: Building Modular Parsers" chapter (18th )from the Deep into Pharo book[4]Â as a Markdeep data narrative[4a]. The chapter was rewritten in Lepiter and can be exported/imported to/from Markdeep, so new updates or learning notes can be created pretty easily[4b]. Because we combine this with Fossil SCM[5], it is also possible to have the history of the documents (look at [4a1][4b1]) in a self contained environment for collaborative publishing/writing that is easier to use, in comparison with Git based alternatives (as shown in our practices introducing this tools and workflows to non-programmers). [3] https://mutabit.com/repos.fossil/grafoscopio/uv/Docs/En/Books/Manual/manual… [3a] https://mutabit.com/repos.fossil/grafoscopio/file?name=Docs/En/Books/Manual… [4] http://files.pharo.org/books-pdfs/deep-into-pharo/2013-DeepIntoPharo-EN.pdf [4a] http://mutabit.com/repos.fossil/mutabit/doc/tip/wiki/en/petitparser-buildin… [4b] http://mutabit.com/repos.fossil/mutabit/doc/tip/wiki/en/petitparser-buildin… [4a1] http://mutabit.com/repos.fossil/mutabit/timeline?uf=1680c3899 [4b1] http://mutabit.com/repos.fossil/mutabit/finfo?name=wiki/en/petitparser-buil… [5] https://fossil-scm.org/ I like the results with so far with this light (re)publishing workflow based in Markdeep, despite some bugs, like subsection numbering done in Markdeep when combined with HTML divs[6] (a bug already reported to the author). For more detailed control of the output or the combination with HTML graphical libraries, like Apache Echarts, we're testing a similar strategy using Pandoc's Markdown with promising features. For example, we can have interactive snippets in the HTML exported document [6a]. [6] https://nitter.net/offrayLC/status/1585701931728740352#m [6a] https://twitter.com/offrayLC/status/1555229528355651586 Such light, human readable and diff friendly publishing and exchange formats are kind of a dehydrated data narrative for the web and/or the file-system than can be re-hydrated back into a full Pharo/GToolkit image for total interactivity/moldability and meanwhile you can tease the casual web reader/explorer with data stories and visualizations without s/he having the need to have Pharo/GToolkit in her/his machine. Cheers and thanks for the community and technologies that make this possible. I will be posting more advances as they come. Offray

2 1

Pharo VM Release - v9.0.21
by tesonep＠gmail.com Dec. 14, 2022

Dec. 14, 2022

Hello, I have released a new version of the Pharo VM for Pharo 9, Pharo 10 and Pharo 11. This VM is accessible right now from Zero-Conf, updating it in the Pharo Launcher or using the usual downloads (as described in pharo.org/download) This version includes a series of bug fixes and upgrades on the third-party libraries. Changelog: - Implementing High resolution clock for ARM64 (Used during profiling) - Updating third party libraries for all the graphic layer. - Fixing a performance regression on the allocation of opcodes and fix-ups. Cleaning only the ones that are going to be used. Like this, this version has the same speed than before when allocating in the stack. - Correctly handling the encoding of the command line arguments of the VM (Windows) - Allocating the opcodes and fixup structs only once and reusing them (Reducing risk of C Stack Overflow) Thanks a lot, and any doubt please let me know. Cheers, Pablo on behalf of the whole Pharo team. -- Pablo Tesone. tesonep(a)gmail.com

4 3

[Issue Tracker] Please check your issues
by Marcus Denker Dec. 14, 2022

Dec. 14, 2022

Hi, The issue tracker has a bit the problem that outdated issues are never cleaned - sometimes PRs are merged but the issue is not closed because it was never connected to the PR ( github sometimes just does not do it correctly ) - Duplicated reports, bug is fixed but the other issue was closed - Problem fixed due to other reasons Or your issue might have seen someone asking a question. People tend to just wait for an answer to those. Or maybe the issue has just not enough information for others to take action? Maybe you could submit a PR instead of just describing the change you think should be done? The best would be if everyone who opened an issue would check all the issues they submitted. you can just add a filter to https://github.com/pharo-project/pharo/issues, e.g. author:MarcusDenker shows you all that I submitted Marcus

1 0

Using ZnResponse>>#redirect: to pass an error message
by vinref＠gmail.com Dec. 13, 2022

Dec. 13, 2022

Hello I catch an error like this: ``` [ self insertNewUser. ``` ``` ZnResponse redirect: self request url ] on: TbDbError do: [ :err | | ent | ``` ``` ZnResponse redirect: '/error/db_error' ] ]. ``` I would like to pass ``` err messageText ``` to the page at: â/error/db_errorâ, to display to the user. I prefer not to cache it is a session or use a Js hack to do it. Does someone have a strategy for passing objects via a ZnResponse instance? I did try ``` ZnResponse redirect: aUrl entity: anEntity ``` but the entity is discarded by the time it gets to the page. Vince

1 2

[ANN] docker-pharo-runtime v10.0.1-2022-12-12 [v10.0.1 [2022-12-12]] released!
by Buenos Aires Smalltalk Dec. 12, 2022

Dec. 12, 2022

1 0

[ANN] docker-pharo-vm v9.0.21-2022.12.12 [v9.0.21 [2022-12-12]] released!
by Buenos Aires Smalltalk Dec. 12, 2022

Dec. 12, 2022

1 0

Pharo dark window buttons
by pumps-moats.0i＠icloud.com Dec. 2, 2022

Dec. 2, 2022

Pardon if this is a duplicate but, is there a way to change the themeâs color for the windows close/collapse buttons? They are too dark for me (black on dark grey background). Iâm somewhat visually impaired so the extra contrast would help. I looked at the settings/preferences and couldnât find anything there. Thank you. Regards Pete

3 2