April 2023 - Pharo-users - lists.pharo.org

Re: Porting from VW to Pharo

by Christian Haider

Yes, PDFtalk is the only example, because it was created to port that library. Any other uses are welcome. The project has been dormant for a year now because of other obligations, but I hope to resume soon. The documentation is, as Richard notes, in a suboptimal state. I think that the information is still accurate. Any help with this would be welcome, for example by asking questions or by criticizing concrete issues. Christian Von: Richard Sargent <richard.sargent(a)gemtalksystems.com> Gesendet: Donnerstag, 6. April 2023 17:55 An: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Betreff: [Pharo-users] Re: Porting from VW to Pharo The best(?) place to start is perhaps https://wiki.pdftalk.de/doku.php?id=smalltalktransform. The only examples are various ports of PDFtalk (from VisualWorks) to Pharo, Squeak, GemStone, and VAST. PDFtalk is quite complex and the porting rules are correspondingly complex. The Transform documentation does leave something to be desired. On Thu, Apr 6, 2023 at 8:22â¯AM Steffen MÃ¤rcker <merkste(a)web.de <mailto:merkste@web.de> > wrote: Hi! this topic pops up from time to time on the mailing list. I want to port a number of packages to Pharo. I remember "Shaping" asking this for porting PDFtalk. 1. Is the workflow still up to date or is there a new way of doing things? 2. From what I understand so far, I just need the following package from Store: - Smalltalk Transform Project 3. Is there a page that documents the process process in general? https://wiki.pdftalk.de/doku.php?id=setupvisualworks seems to be specific for PDFtalk like the thread on this list. Kind regards, Steffen

April 6, 2023

Re: Porting from VW to Pharo

by Richard Sargent

The best(?) place to start is perhaps https://wiki.pdftalk.de/doku.php?id=smalltalktransform. The only examples are various ports of PDFtalk (from VisualWorks) to Pharo, Squeak, GemStone, and VAST. PDFtalk is quite complex and the porting rules are correspondingly complex. The Transform documentation does leave something to be desired. On Thu, Apr 6, 2023 at 8:22â¯AM Steffen MÃ¤rcker <merkste(a)web.de> wrote: > Hi! > > this topic pops up from time to time on the mailing list. I want to port a > number of packages to Pharo. I remember "Shaping" asking this for porting > PDFtalk. > > 1. Is the workflow still up to date or is there a new way of doing things? > 2. From what I understand so far, I just need the following package from > Store: > - Smalltalk Transform Project > 3. Is there a page that documents the process process in general? > https://wiki.pdftalk.de/doku.php?id=setupvisualworks seems to be specific > for PDFtalk like the thread on this list. > > Kind regards, > Steffen >

April 6, 2023

Porting from VW to Pharo

by Steffen MÃ¤rcker

Hi! this topic pops up from time to time on the mailing list. I want to port a number of packages to Pharo. I remember "Shaping" asking this for porting PDFtalk. 1. Is the workflow still up to date or is there a new way of doing things? 2. From what I understand so far, I just need the following package from Store: - Smalltalk Transform Project 3. Is there a page that documents the process process in general? https://wiki.pdftalk.de/doku.php?id=setupvisualworks seems to be specific for PDFtalk like the thread on this list. Kind regards, Steffen

April 6, 2023

Re: A blog on graph algorithms library of Pharo

by Steffen MÃ¤rcker

Hi Goutham, thanks for sharing that post. Looks interesting, indeed! Best, Steffen Guillermo Polito schrieb am Mittwoch, 5. April 2023 10:03:28 (+02:00): Hi Goutham! Thanks for the post! I like the concrete examples. I did not find them in the repo, I think pushing the examples as comments or executable code in the relevant classes is a great first PR ;) G El 4 abr. 2023, a las 18:29, DK Goutham <dkgoutham1806(a)gmail.com> escribiÃ³: Dear Pharo Users, Here's a blog on pharo-ai/graph-algorithms library. This acts as a primer for people new to this library and discusses the flow and architecture of the library. The motive of this blog is to introduce people to the amazing graph library of Pharo and give them enough confidence to contribute to this library. Link: https://medium.com/@dkgoutham1806/graph-algorithms-in-pharo-7d12af0be060 Happy reading! Thank you, Goutham -- Gesendet mit Vivaldi Mail. Laden Sie Vivaldi kostenlos von vivaldi.com herunter.

April 6, 2023

Block evaluation with n+1 arguments

by Steffen MÃ¤rcker

Hi! I want to evaluate a block an argument 'arg1' and additional n arguments given in an array 'args'. The following code does the trick: block valueWithArguments: (Array with: arg1) , args. Is there a way to do this without the overhead of creating a new Array? (How) Can I add additional #value:value:[...] methods to BlockClosure that evaluate the block with n arguments directly without falling back to #valueWithArguments: ? If yes, what's the maximum? Cheers! Steffen

April 6, 2023

Pharo 11 release soon: Please check Issue Tracker

by Marcus Denker

Hi, Pharo11 us now frozen for a while, it seems we are on a good way to release soon. This is always a good time to clean up the issue tracker. Please check especially the issues you opend https://github.com/pharo-project/pharo/issues Github often fails to close the isssue even though it is correctly set as to be closed in the PR. And often bugs are fixed due to a duplicate issue tracker entry or as part of other work. As we do not timeout issues anymore, we rely on everyone to help to keep this in a somewhat sane stateâ¦ Marcus

April 5, 2023

Re: A blog on graph algorithms library of Pharo

by Richard O'Keefe

Warmest congratulations to the author(s) of this library. It's a lot of work, and it's available to the Pharo community. It doesn't suit my graph-processing needs, but that doesn't stop me appreciating the contribution. On Wed, 5 Apr 2023 at 04:29, DK Goutham <dkgoutham1806(a)gmail.com> wrote: > Dear Pharo Users, > > Here's a blog on *pharo-ai/graph-algorithms* library. This acts as a > primer for people new to this library and discusses the flow and > architecture of the library. The motive of this blog is to introduce > people to the amazing graph library of Pharo and give them enough > confidence to contribute to this library. > > Link: > https://medium.com/@dkgoutham1806/graph-algorithms-in-pharo-7d12af0be060 > > Happy reading! > > Thank you, > Goutham >

April 5, 2023

Re: A blog on graph algorithms library of Pharo

by Guillermo Polito

Hi Goutham! Thanks for the post! I like the concrete examples. I did not find them in the repo, I think pushing the examples as comments or executable code in the relevant classes is a great first PR ;) G > El 4 abr. 2023, a las 18:29, DK Goutham <dkgoutham1806(a)gmail.com> escribiÃ³: > > Dear Pharo Users, > > Here's a blog on pharo-ai/graph-algorithms library. This acts as a primer for people new to this library and discusses the flow and architecture of the library. The motive of this blog is to introduce people to the amazing graph library of Pharo and give them enough confidence to contribute to this library. > > Link: https://medium.com/@dkgoutham1806/graph-algorithms-in-pharo-7d12af0be060 <https://medium.com/@dkgoutham1806/graph-algorithms-in-pharo-7d12af0be060> > > Happy reading! > > Thank you, > Goutham

April 5, 2023

A blog on graph algorithms library of Pharo

by DK Goutham

Dear Pharo Users, Here's a blog on *pharo-ai/graph-algorithms* library. This acts as a primer for people new to this library and discusses the flow and architecture of the library. The motive of this blog is to introduce people to the amazing graph library of Pharo and give them enough confidence to contribute to this library. Link: https://medium.com/@dkgoutham1806/graph-algorithms-in-pharo-7d12af0be060 Happy reading! Thank you, Goutham

April 4, 2023

Re: This week (13/2023) on the Pharo Issue Tracker

by Norbert Hartl

It is just incredible what happens in one week in the pharo community. This is really great! Thank you all for your efforts! Norbert > Am 31.03.2023 um 12:18 schrieb Marcus Denker <marcus.denker(a)inria.fr>: > > We again merged ~60 PRs. > > Pharo11 got some bugfixes and last improvements. > > In Pharo12, we continue the compiler refactoring and the cleanup of ClassOrganizer. > > > Pharo11 > ======= > > > Last Improvements > ================= > > - Add a way to know the real processor architecture #13124 > https://github.com/pharo-project/pharo/pull/13124 > > - remove end line characters in returned value of processorArchitecture #13155 > https://github.com/pharo-project/pharo/pull/13155 > > - Removing unused instance variable topContext in DebugContext #13179 > https://github.com/pharo-project/pharo/pull/13179 > > - Add inspector extensions for Chronology #499 > https://github.com/pharo-spec/NewTools/pull/499 > > - More inspector extensions #497 > https://github.com/pharo-spec/NewTools/pull/497 > > > Fixes > ===== > > - 13181-DeprecationPerformedNotification-Automatic-deprecation-code-rewrite #13182 > https://github.com/pharo-project/pharo/pull/13182 > > - implement #selectedClassOrMetaClass in MCTool to return nil #13167 > https://github.com/pharo-project/pharo/pull/13167 > > - 13141-timesRepeat-does-not-work-on-nested-loops #13154 > https://github.com/pharo-project/pharo/pull/13154 > > - 13122 rbparser cutting tokens in stepBar [Pharo11] #13129 > https://github.com/pharo-project/pharo/pull/13129 > > - fixing the code update bug after compiling a missing method with the unfiltered stack #491 > https://github.com/pharo-spec/NewTools/pull/491 > > - Categorizing uncategorized classes in new tools debugger tests #500 > https://github.com/pharo-spec/NewTools/pull/500 > > - SpCodeInteractionModel>>#notify: Avoid crashing #1363 > https://github.com/pharo-spec/Spec/pull/1363 > > - SpDropListExampleTest does not opens Playgorunds anymore #1359 > https://github.com/pharo-spec/Spec/pull/1359 > > > Pharo12 > ======= > > Speed > ===== > > - speedup-testNoShadowedVariablesInMethods #13170 > https://github.com/pharo-project/pharo/pull/13170 > > - Speed up #assertCollection:hasSameElements: in case they are equals. #13144 > https://github.com/pharo-project/pharo/pull/13144 > > > ClassOrganizer Cleanup > ====================== > > - Inline extensions of protocol organizer #13194 > https://github.com/pharo-project/pharo/pull/13194 > > - ChangeRecord: rename category into protocol #13188 > https://github.com/pharo-project/pharo/pull/13188 > > - Inline some protocol organizer behavior #13191 > https://github.com/pharo-project/pharo/pull/13191 > > - remove commentSourcePointer from ClassOrganization #13176 > https://github.com/pharo-project/pharo/pull/13176 > > - Set-CommentSourcepointer-ClassDescription #13171 > https://github.com/pharo-project/pharo/pull/13171 > > - Update behaviour of #protocolNamed: #13173 > https://github.com/pharo-project/pharo/pull/13173 > > - Simplify and deprecate ClassDescription>>allProtocolsUpTo: #13160 > https://github.com/pharo-project/pharo/pull/13160 > > - ProtocolOrganizer cleanings #13169 > https://github.com/pharo-project/pharo/pull/13169 > > - ClassComments-Via-Class #13168 > https://github.com/pharo-project/pharo/pull/13168 > > - Rename #nullCategory into #nullProtocolName #13157 > https://github.com/pharo-project/pharo/pull/13157 > > > Compiler Cleanup > ================ > > - Remove RBInstanceVariableNode crufts #13199 > https://github.com/pharo-project/pharo/pull/13199 > > - Faulty code: Make OCUndeclaredVariableWarning a little less special #13186 > https://github.com/pharo-project/pharo/pull/13186 > > - Compiler source code is String #13184 > https://github.com/pharo-project/pharo/pull/13184 > > - Factorize recompile:from: #13180 > https://github.com/pharo-project/pharo/pull/13180 > > - OpalCompiler gain install #13152 > https://github.com/pharo-project/pharo/pull/13152 > > - Faulty code: improve code error descriptions #13174 > https://github.com/pharo-project/pharo/pull/13174 > > - Faulty code: make OCASTSemanticAnalyzer (almost) faulty only #13165 > https://github.com/pharo-project/pharo/pull/13165 > > - CodeImport - stop requestor madness #13162 > https://github.com/pharo-project/pharo/pull/13162 > > - Faulty code - signal mainly CodeError #13164 > https://github.com/pharo-project/pharo/pull/13164 > > - Faulty code improve scanner on error tokens #13135 > https://github.com/pharo-project/pharo/pull/13135 > > - Faulty code: introduce invalid variables #13148 > https://github.com/pharo-project/pharo/pull/13148 > > - CodeSnippet: can update itself thaks to metaprogramming and code transformation #13127 > https://github.com/pharo-project/pharo/pull/13127 > > - Faulty code: cleanup CodeError #13163 > https://github.com/pharo-project/pharo/pull/13163 > > - Faulty code: improve shadowing policy and implementation #13132 > https://github.com/pharo-project/pharo/pull/13132 > > - Faulty code: improve error on unexpected block parameter #13133 > https://github.com/pharo-project/pharo/pull/13133 > > - 13122 rbparser cutting tokens in stepBar [Pharo12] #13130 > https://github.com/pharo-project/pharo/pull/13130 > > > > Refactoring Engine > ================== > > - Refactorings clean up #13131 > https://github.com/pharo-project/pharo/pull/13131 > > - Refactoring push down method command to use driver #13099 > https://github.com/pharo-project/pharo/pull/13099 > > - Remove duplicated mocking #13151 > https://github.com/pharo-project/pharo/pull/13151 > > Improvements > ============= > > - Improve announcements printing #13178 > https://github.com/pharo-project/pharo/pull/13178 > > - Clean copying methods of ClassDescription #13159 > https://github.com/pharo-project/pharo/pull/13159 > > - More explicit error message for slot usage in bootstrap #13145 > https://github.com/pharo-project/pharo/pull/13145 > > - move bootstrap/src into main src #13016 > https://github.com/pharo-project/pharo/pull/13016 > > Cleanups > ======== > > - OSPlatformTest should be in System-Platforms-Tests #13192 > https://github.com/pharo-project/pharo/pull/13192 > > - Factorize announcement subscribers #13185 > https://github.com/pharo-project/pharo/pull/13185 > > - Synch with p11 #13147 > https://github.com/pharo-project/pharo/pull/13147

April 3, 2023