March 2024 - Pharo-users - lists.pharo.org

Re: Books about Pharo

by Offray Vladimir Luna CÃ¡rdenas

On the next iteration for Microdown you may find Djot [1] interesting, as it is also trying to be familiar to Markdown users, while fixing the several of its shortcomings and making parsers easier to build, by having a clearer non-ambiguous syntax, that doesn't require look ahead mechanisms. I think that Djot may share the Microdow design principles stated at [2] regarding [2a] familiarity to Markdown [2b] Small uniform core and [2c] extensibility. Umm... I wonder, given that one of the selling points of Djot is the easiness of implementing parsers, how difficult could be to implement a Djot parser and connect it to the Pillar infrastructure? Following the idea quoted at the beginning blog post at [3] trying to " to create a light markup syntax that keeps what is good about Markdown, while revising some of the features that have led to bloat and complexity" and finding the sweet spot between popular options and added value, without being tied by popularity or the past, is a worth exploration. It help us, as a community, to reach the people where they are. Even more considering how Markdown is a popular but clumsy standard de facto (<flame> kind of the Git/GitHub of the light Markup languages,Â promoted greatly by its GitHub usage </flame>). In my case, given the constrains in computer labs where installing Pandoc can be cumbersome, using Markdeep has been an important time saver, even if we need to fork[4] its main repository to document publicly its possibilities and shortcomings. A natively fully supported and well defined light format in Pharo, like Microdown or Djot, could help us a lot in our documentation workflows, given our limited resources[^a]. And, because of the shared design sensibilities behind both formats, I would like to have Microdown more inspired in Djot than in "wild Markdown". The efforts in having a "popular alike" format totally supported in the image are greatly appreciated. Cheers, Offray == Links and footnotes [1] https://djot.net/ [2] https://rmod-files.lille.inria.fr/Team/Texts/Papers/Duca20a-Microdown-IWST.… [3] https://www.jonashietala.se/blog/2024/02/02/blogging_in_djot_instead_of_mar… [4] https://github.com/ruidajo/markdeep/ [^a]: I'm half of the population of the two active Smalltalkers/Pharoers in my country, working in the language part time. We need to cleverly combine resources with a low complexity/expressivity ratio, that's where our combination of tools like Pharo/GT, Fossil, Markdeep, Pandoc comes from. On 27/03/24 2:48, stephane ducasse wrote: > I released yesterday the version 9.0.1 of pillar for Pharo 11. > And I will restart a new iteration on Microdown. > - better support for math > - introducing > > and more as time allows. > > S > >> On 27 Mar 2024, at 01:25, Offray Vladimir Luna CÃ¡rdenas >> <offray.luna(a)mutabit.com> wrote: >> >> Pretty cool! >> >> One of my ideas with Grafoscopio was to be able to read interactive >> documentation inside Pharo, which was obtained in a pretty primitive >> way. Now I have moved to Lepiter as a GUI of our documentation >> workflows and Markdeep as a default format for storage and web >> rendering. But seeing the advances in Microdown and its interactive >> viewer is pretty inspiring. I hope to check some Pharo books >> prepackaged with upcoming releases. >> >> Keep the good work, >> >> Offray >> >> On 14/03/24 9:40, stephane ducasse wrote: >>> Hi Richard >>> >>> I did not see your original post because I messed up with my account. >>> But thanks for your email :) >>> >>> Now the cool stuff if that we can also read the books from within Pharo. >>> We should improve the Microdown renderer and suddenly we will get >>> shiny cool >>> documentation. >>> >>> S >>> >>> >>> >>>> This is a new thread because it's not limited to any specific topic. >>>> >>>> If you have questions about Pharo, especially "how do I do <this> in >>>> Pharo", you can always ask in this mailing list. Â You can, if you like >>>> playing Russian Roulette, ask a Large Language Model "AI". >>>> >>>> But there is an amazing resource you should really trye. >>>> >>>> books.pharo.org >>>> >>>> Did you ever wonder where the manual for Pharo was? >>>> That's where. Â The site lists a bunch of Pharo books and booklets, >>>> all of which have free PDFs except for two of the books. >>>> In particular, you'll always want the most recent edition of >>>> "Pharo by Example" handy. >>>> >>>> These books are really useful. Â They are written by people know know >>>> their material thoroughly and do a good job of explaining it. Â If you >>>> want to make any serious use of Pharo, or even to have more happiness >>>> than headaches just playing with it, you owe it to yourself to get the >>>> free PDFs Â What do we owe the authors? Â Well, if you're not trying to >>>> make one pension support four people, you owe them the purchase of >>>> some of the books. Â Me, I'm giving them thanks, praise, and a >>>> heartfelt recommendation. >>>> >>>> Seriously, these books represent a HUGE amount of work and "you are a >>>> fool to yourself and a burden to others" if you don't take advantage >>>> of this great resource. > > StÃ©phane Ducasse > http://stephane.ducasse.free.fr > 06 30 93 66 73 > > "If you knew today was your lastÂ day on earth, what wouldÂ youÂ do > differently? ....ESPECIALLYÂ if, by doing somethingÂ different,Â today > mightÂ notÂ be your last dayÂ on earth.â CalvinÂ & Hobbes > > > > >

March 31, 2024

# This week (13/2024) on the Pharo Issue Tracker

by Marcus Denker

# Fixes - Adapt #getVolumeInfo:into:size: for StWin32Info to strict FFI #729 https://github.com/pharo-spec/NewTools/pull/729 - Take the selector into account in #AdditionalMethodState>>#analogousCodeTo: #16302 https://github.com/pharo-project/pharo/pull/16302 - Add override for #drawPolygon:fillStyle:borderWidth:borderColor: on ScalingCanvas to avoid conversion of the second argument to a Color #16304 https://github.com/pharo-project/pharo/pull/16305 - Make #contentsMenu: on WorldMorph use the FormSet for each of the icons #16317 https://github.com/pharo-project/pharo/pull/16317 - Change â./$0â to â$0â in recursive retry command in script âgetPharoVM.shâ #16337 https://github.com/pharo-project/pharo/pull/16337 - ZnHeaders does not understand isNotEmpty #16339 https://github.com/pharo-project/pharo/pull/16339 - Move archival of â*.xmlâ and â*.fuelâ files in âJenkinsfileâ to the âfinallyâ block #16341 https://github.com/pharo-project/pharo/pull/16341 - remaining morphic dialogs: aligning the default option to right #16352 https://github.com/pharo-project/pharo/pull/16352 # Tools - fixes #16315 dependency browser layout feels wrong #16343 https://github.com/pharo-project/pharo/pull/16343 - enable / disable syntax highlight in code presenter of critics browser. #727 https://github.com/pharo-spec/NewTools/pull/727 # Cleanup - Remove StWindowsExtensionsTest #728 https://github.com/pharo-spec/NewTools/pull/728 - Remove #createTab from ClyBrowserToolMorph #16318 https://github.com/pharo-project/pharo/pull/16318 - Remove old backward compatibility code from FFILibrary #16349 https://github.com/pharo-project/pharo/pull/16349

March 29, 2024

Re: Books about Pharo

by stephane ducasse

I released yesterday the version 9.0.1 of pillar for Pharo 11. And I will restart a new iteration on Microdown. - better support for math - introducing > and more as time allows. S > On 27 Mar 2024, at 01:25, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: > > Pretty cool! > > One of my ideas with Grafoscopio was to be able to read interactive documentation inside Pharo, which was obtained in a pretty primitive way. Now I have moved to Lepiter as a GUI of our documentation workflows and Markdeep as a default format for storage and web rendering. But seeing the advances in Microdown and its interactive viewer is pretty inspiring. I hope to check some Pharo books prepackaged with upcoming releases. > > Keep the good work, > > Offray > > On 14/03/24 9:40, stephane ducasse wrote: >> Hi Richard >> >> I did not see your original post because I messed up with my account. >> But thanks for your email :) >> >> Now the cool stuff if that we can also read the books from within Pharo. >> We should improve the Microdown renderer and suddenly we will get shiny cool >> documentation. >> >> S >> >> >> >>> This is a new thread because it's not limited to any specific topic. >>> >>> If you have questions about Pharo, especially "how do I do <this> in >>> Pharo", you can always ask in this mailing list. You can, if you like >>> playing Russian Roulette, ask a Large Language Model "AI". >>> >>> But there is an amazing resource you should really trye. >>> >>> books.pharo.org >>> >>> Did you ever wonder where the manual for Pharo was? >>> That's where. The site lists a bunch of Pharo books and booklets, >>> all of which have free PDFs except for two of the books. >>> In particular, you'll always want the most recent edition of >>> "Pharo by Example" handy. >>> >>> These books are really useful. They are written by people know know >>> their material thoroughly and do a good job of explaining it. If you >>> want to make any serious use of Pharo, or even to have more happiness >>> than headaches just playing with it, you owe it to yourself to get the >>> free PDFs What do we owe the authors? Well, if you're not trying to >>> make one pension support four people, you owe them the purchase of >>> some of the books. Me, I'm giving them thanks, praise, and a >>> heartfelt recommendation. >>> >>> Seriously, these books represent a HUGE amount of work and "you are a >>> fool to yourself and a burden to others" if you don't take advantage >>> of this great resource. StÃ©phane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes

March 27, 2024

Re: Books about Pharo

by Offray Vladimir Luna CÃ¡rdenas

Pretty cool! One of my ideas with Grafoscopio was to be able to read interactive documentation inside Pharo, which was obtained in a pretty primitive way. Now I have moved to Lepiter as a GUI of our documentation workflows and Markdeep as a default format for storage and web rendering. But seeing the advances in Microdown and its interactive viewer is pretty inspiring. I hope to check some Pharo books prepackaged with upcoming releases. Keep the good work, Offray On 14/03/24 9:40, stephane ducasse wrote: > Hi Richard > > I did not see your original post because I messed up with my account. > But thanks for your email :) > > Now the cool stuff if that we can also read the books from within Pharo. > We should improve the Microdown renderer and suddenly we will get shiny cool > documentation. > > S > > > >> This is a new thread because it's not limited to any specific topic. >> >> If you have questions about Pharo, especially "how do I do <this> in >> Pharo", you can always ask in this mailing list. You can, if you like >> playing Russian Roulette, ask a Large Language Model "AI". >> >> But there is an amazing resource you should really trye. >> >> books.pharo.org >> >> Did you ever wonder where the manual for Pharo was? >> That's where. The site lists a bunch of Pharo books and booklets, >> all of which have free PDFs except for two of the books. >> In particular, you'll always want the most recent edition of >> "Pharo by Example" handy. >> >> These books are really useful. They are written by people know know >> their material thoroughly and do a good job of explaining it. If you >> want to make any serious use of Pharo, or even to have more happiness >> than headaches just playing with it, you owe it to yourself to get the >> free PDFs What do we owe the authors? Well, if you're not trying to >> make one pension support four people, you owe them the purchase of >> some of the books. Me, I'm giving them thanks, praise, and a >> heartfelt recommendation. >> >> Seriously, these books represent a HUGE amount of work and "you are a >> fool to yourself and a burden to others" if you don't take advantage >> of this great resource.

March 27, 2024

This week (12/2024) on the Pharo Issue Tracker

by Marcus Denker

# Features - Adding tests for debug points + integrating debug points to Calypso Browser #16268 https://github.com/pharo-project/pharo/pull/16268 - add uFFI convenience methods #16320 https://github.com/pharo-project/pharo/pull/16320 # Fixes - 16321-Method-with-an-highlighted-warning-or-error-is-kept-when-deleting-the-offending-text #16322 https://github.com/pharo-project/pharo/pull/16322 - Protect with a mutex the transcript update #16311 https://github.com/pharo-project/pharo/pull/16311 - 15841-ZeroDivide-when-selecting-idea11-icons #16309 https://github.com/pharo-project/pharo/pull/16309 - 14700-Shortcut-text-is-not-displayed-correctly-on-a-Mac #16307 https://github.com/pharo-project/pharo/pull/16307 - Fix parsing twice per keystroke in Calypso #16306 https://github.com/pharo-project/pharo/pull/16306 - NativeBrowserOpenVisitor requires typing for strict FFI #16325 https://github.com/pharo-project/pharo/pull/16325 - 15564-No-menubar-in-Mac-OS-Sonoma #16297 https://github.com/pharo-project/pharo/pull/16297 - Refactor RubTextSegmentMorph to support use of a FormSet #16323 https://github.com/pharo-project/pharo/pull/16323 - Make #taskbarButtonMenu: on SystemWindow and MorphicNativeWindow use the FormSet for each of the icons #16296 https://github.com/pharo-project/pharo/pull/16296 - Make #initializeFor: on TaskbarItemMorph use the FormSet for the icon #16316 https://github.com/pharo-project/pharo/pull/16316 - 16332-Bug-in-Transcript #16334 https://github.com/pharo-project/pharo/pull/16334 - Change #transformBy:clippingTo:during:smoothing: on FormCanvas to use BitBlt combination rule 34 instead of 24 #16303 https://github.com/pharo-project/pharo/pull/16303 - remove wrong name #16331 https://github.com/pharo-project/pharo/pull/16331/files - Add pre-filling the name text presenter in file dialogs #717 https://github.com/pharo-spec/NewTools/pull/717 - Allowing to use Texts as HelpText of Presenters #1529 https://github.com/pharo-spec/Spec/pull/1529 # Tools - fix-critics-browser-issue #724 https://github.com/pharo-spec/NewTools/pull/724 - Fixing Version Browser Presenter #721 https://github.com/pharo-spec/NewTools/pull/721 - Showing CMD character in OSX in Spotter #720 https://github.com/pharo-spec/NewTools/pull/720 - Improvements to the Scopes Editor and integration with Pharo #718 https://github.com/pharo-spec/NewTools/pull/718 # Breakpoints - Debug Point Browser integration #697 https://github.com/pharo-spec/NewTools/pull/697 # Refactoring Engine - 16326-Realize-class-menu-option-throws-error-on-any-class #16333 https://github.com/pharo-project/pharo/pull/16333 - Makes user defined scopes available in Refactoring User Interfaces #15918 https://github.com/pharo-project/pharo/pull/15918 - Fix: remove extract method transformation from UI #16301 https://github.com/pharo-project/pharo/pull/16301

March 25, 2024

Re: [Pharo-dev] "The Classification Model" â New blog post on all: objects all: theTime

by Koen De Hondt

Hi Tim, This is a good place to discuss. I did not add comment functionality to my blog because I do not want people to spam the site with stuff that is not related to the content, and I do not want to moderate the comments. Sending me messages is fine too, but here everyone can read along. You have understood correctly, but I consider it a virtual classification rather than a computed classification because the classification does not depend on user input. Atlas has an âAllMethodsClassificationâ that holds items for all methods of a class. It is used for instance methods and class methods, depending on the âsourceâ of the classification, either a class or a metaclass. Suppose you implement a new classification, letâs say âAllInstanceMethodsAndClassMethodsClassificationâ, that holds items for all instance methods and class methods of a class, then you are all set. All items and classifications have a display name, which is shown in the UI. However, the display name depends on the context. If it is clear from the context that #example is a class method, then displaying âexampleâ is fine. However, when the context is more general, like any manual classification that can hold anything, displaying âMy class>>#exampleâ would be more appropriate. So just implementing a new kind of classification would not be enough for your use case. Therefore I would also implement a dedicated view on that classification so that the list in the view can indicate whether a method is an instance or a class method, together with the protocol it belongs to. An alternative to what you propose, and a better solution in my opinion, is to have two views side by side, so that instance and class methods are not mixed. That simplifies the implementation, certainly because Atlas has both views, and composing your own browser is possible. That is certainly a topic for a future post. Thank you for your questions. I welcome all feedback, as it will shape Atlas. Ciao, Koen > On 19 Mar 2024, at 17:30, Tim Mackinnon <tim(a)testit.works> wrote: > > Hi Koen - is there any particular place you would like us to feedback on the posts? Is here useful, or some other location? > > I like the concepts you are introducing (I need to take to read your PHD - so good to have the link in there) - but the devil is in the detail of course. > > If I have understood correctly - the idea of computed classifications give rise to the flexibility we all crave? So in my previous comment - when designing a new class and trying to work out its protocol, in particular how to instantiate it vs. update it - its very inconvenient to have to flip between class and instance method definitions - a much flatter view of a Class has both instance AND class methods that I can see together is more efficient to work with in that initial design phase vs later when stabilised the more traditional - a Class name has Class and Instance definition, a Class definition has class methods, an Instance definition has instance methods (apologies if terminology isn't quite right - typing this in a hurry on a break). > > But does the classification model handle the above? To flatten instance and class methods into a single sorted list (discriminated in some manner - like one being bold or having some prefix) and also allowing you to add to add new items to that list and provide that discrimination sounds like it might not fit that classification model? Or maybe it does? I guess we do currently allow methods to have categories and we can view multiple categories in a list. I guess I'm curious how it hangs together to model non-trivial examples? And maybe this is the next blog post? > > Thanks for surfacing the ideas. > > Tim > > On Mon, 18 Mar 2024, at 5:51 PM, Koen De Hondt wrote: >> Dear Pharo users and developers, >> >> Last week I told you about a new blog post that outlined the objectives of the Atlas browser. It was the first post of a series. >> If you liked it, I invite you to read the next post <https://all-objects-all-the-time.st/#/blog/posts/7>. It describes the Classification Model, which is the foundation of Atlas. >> >> Happy reading! >> >> Ciao, >> Koen

March 19, 2024

Re: [Pharo-dev] "The Classification Model" â New blog post on all: objects all: theTime

by Tim Mackinnon

Hi Koen - is there any particular place you would like us to feedback on the posts? Is here useful, or some other location? I like the concepts you are introducing (I need to take to read your PHD - so good to have the link in there) - but the devil is in the detail of course. If I have understood correctly - the idea of computed classifications give rise to the flexibility we all crave? So in my previous comment - when designing a new class and trying to work out its protocol, in particular how to instantiate it vs. update it - its very inconvenient to have to flip between class and instance method definitions - a much flatter view of a Class has both instance AND class methods that I can see together is more efficient to work with in that initial design phase vs later when stabilised the more traditional - a Class name has Class and Instance definition, a Class definition has class methods, an Instance definition has instance methods (apologies if terminology isn't quite right - typing this in a hurry on a break). But does the classification model handle the above? To flatten instance and class methods into a single sorted list (discriminated in some manner - like one being bold or having some prefix) and also allowing you to add to add new items to that list and provide that discrimination sounds like it might not fit that classification model? Or maybe it does? I guess we do currently allow methods to have categories and we can view multiple categories in a list. I guess I'm curious how it hangs together to model non-trivial examples? And maybe this is the next blog post? Thanks for surfacing the ideas. Tim On Mon, 18 Mar 2024, at 5:51 PM, Koen De Hondt wrote: > Dear Pharo users and developers, > > Last week I told you about a new blog post that outlined the objectives of the Atlas browser. It was the first post of a series. > If you liked it, I invite you to read the next post <https://all-objects-all-the-time.st/#/blog/posts/7>. It describes the Classification Model, which is the foundation of Atlas. > > Happy reading! > > Ciao, > Koen

March 19, 2024

Re: [Pharo-dev] "The Classification Model" â New blog post on all: objects all: theTime

by Noury Bouraqadi

It sounds promising. I want it now ;-) Noury On Mar 18 2024, at 6:51 pm, Koen De Hondt <koen(a)all-objects-all-the-time.st> wrote: > Dear Pharo users and developers, > > Last week I told you about a new blog post that outlined the objectives of the Atlas browser. It was the first post of a series. > If you liked it, I invite you to read the next post (https://all-objects-all-the-time.st/#/blog/posts/7) It describes the Classification Model, which is the foundation of Atlas. > > Happy reading! > > Ciao, > Koen >

March 19, 2024

UKSTUG Meeting - Maximiliano Tabacman: Electronic Roleplaying Assistant - 27 March 2024

by Giovanni Corriga

In this presentation, Maximiliano Tabacman will be presenting the main features, abstractions and design decisions behind ERA, the Electronic Roleplaying Assistant ( https://preview.drivethrurpg.com/en/product/137825/ERA-for-Rolemaster ). ERA is currently being used to create characters and manage the adventures of many gaming groups across the world, supporting Navigator RPG, Against the Darkmaster, Rolemaster Classic, Rolemaster Fantasy and Rolemaster Unified. We will review how Pharo allows creating a deployed version that runs locally in Linux, Mac and Windows, while Digital Ocean and Auth0 allow running an online server with different user roles. https://pharo.org/success/RolPlayingAssistant.html We will also mention how ERA makes use of the different frameworks developed and maintained by the Buenos Aires Smalltalk group, hosted at Github. Maximiliano Tabacman ( https://www.linkedin.com/in/maximiliano-tabacman-9aa4b817b/ ) is a long time Smalltalker with a Phd from the University of Buenos Aires. He is a Software architect at Mercap, executive secretary at FAST and creator of ERA. This will be an online meeting from home. If you'd like to join us, please sign up in advance on the meeting's Meetup page ( https://www.meetup.com/ukstug/events/299364517/ ) to receive the meeting details. Donât forget to bring your laptop and drinks!

March 19, 2024

"The Classification Model" â New blog post on all: objects all: theTime

by Koen De Hondt

Dear Pharo users and developers, Last week I told you about a new blog post that outlined the objectives of the Atlas browser. It was the first post of a series. If you liked it, I invite you to read the next post <https://all-objects-all-the-time.st/#/blog/posts/7>. It describes the Classification Model, which is the foundation of Atlas. Happy reading! Ciao, Koen

March 18, 2024