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

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

Dec. 13, 2022

Re: Using ZnResponse>>#redirect: to pass an error message

by vinref＠gmail.com

Hi again Unfortunately the solution I came up with above is vulnerable to cross-site scripting attack (XSS). The solution takes the parameter passed in from the url and shows it to the user. An attacker can insert a script and send the link to a user for instance. Please do not do this. You can mitigate the XSS attack with CSP (https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-…) but it can be tricky to get right. Back to square one. Vince

Dec. 13, 2022

Re: Using ZnResponse>>#redirect: to pass an error message

by vinref＠gmail.com

Hi To answer my own question, I passed the error message as a parameter in the url: ``` [ self insertNewUser. ``` ``` ZnResponse redirect: self request url ] on: TbDbError do: [ :err | | url | ``` ``` url := (ZnUrl fromString: 'error/db_error/') ``` ``` queryAt: 'msg' put: err messageText; ``` ``` yourself. ``` ``` ZnResponse redirect: url ] ``` Vince

Dec. 13, 2022

Using ZnResponse>>#redirect: to pass an error message

by vinref＠gmail.com

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

Dec. 13, 2022

[ANN] docker-pharo-runtime v10.0.1-2022-12-12 [v10.0.1 [2022-12-12]] released!

by Buenos Aires Smalltalk

Dec. 12, 2022

[ANN] docker-pharo-vm v9.0.21-2022.12.12 [v9.0.21 [2022-12-12]] released!

by Buenos Aires Smalltalk

Dec. 12, 2022

Re: Pharo VM Release - v9.0.21

by Norbert Hartl

Thanks Pablo for the new vm but as well for the update notification. This is super valuable. Norbert > Am 12.12.2022 um 14:30 schrieb tesonep(a)gmail.com: > > 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 <http://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 <mailto:tesonep@gmail.com>

Dec. 12, 2022

Re: [Pharo-dev] Pharo VM Release - v9.0.21

by Guillermo Polito

Thanks Pablo!!! > El 12 dic. 2022, a las 14:30, tesonep(a)gmail.com escribiÃ³: > > 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 <http://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 <mailto:tesonep@gmail.com>

Dec. 12, 2022

Pharo VM Release - v9.0.21

by tesonep＠gmail.com

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

Dec. 12, 2022

Re: Pharo dark window buttons

by Sebastian Jordan Montano

Hello, Currently, the colors are defined in instance side methods inside the theme class or instance side. So, to change the color you need to redefine that method. But the problem is that I don't know with method specifically defines the color of the windows collapse. So, I can't help you in that aspect. Cordialement, Sebastian Jordan ----- Mail original ----- > De: "pierre misse-chanabier" <pierre.misse-chanabier(a)inria.fr> > Ã: "pharo-users" <pharo-users(a)lists.pharo.org> > Cc: "Sebastian Jordan Montano" <sebastian.jordan(a)inria.fr> > EnvoyÃ©: Jeudi 1 DÃ©cembre 2022 06:01:02 > Objet: Re: [Pharo-users] Pharo dark window buttons > Hi, > > I think I saw a setting once for that, but it has been years. > However, you can edit the Theme directly. > The dark theme is defined in PharoDarkTheme. > > Sebastian (in copy of this mail) has recently started to look at the > themes and will probably change them slightly soon. > He might be able to be more precise than I am. > If you could tell him what has fit for you, or PR your changes so other > visually impaired people could see them better, that'd be great (I'm one > of them, and that back on dark grey is... complicated). > > One last thing, if you're working on a PharoLightTheme release (like > Pharo 11) it might be an update issue. > Most components update properly upon changing from light to dark theme. > However some don't. > For example for a while, class comment were black on grey, which was > impossible for me to read. > > Pierre > > On 11/30/2022 10:17 PM, pumps-moats.0i--- via Pharo-users wrote: >> >> 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

Dec. 2, 2022