- Pharo-dev - lists.pharo.org

any ideas why we need to have Point >> bitShiftPoint: bits?
by stephane ducasse March 29, 2022

March 29, 2022

Point >> bitShiftPoint: bits x := x bitShift: bits. y := y bitShift: bits S

1 0

Re: [Esug-list] [PDFtalk] Porting to non-namespace Smalltalks
by stephane ducasse March 26, 2022

March 26, 2022

Hi guys > > I started to port Values to Pharo. > If you want to give an hand my current effort is here. > > https://github.com/Ducasse/PharoValues <https://github.com/Ducasse/PharoValues> > > should migrate license and other stuff too. > > S > >> On 1 Mar 2022, at 19:08, christian.haider(a)smalltalked-visuals.com <mailto:christian.haider@smalltalked-visuals.com> wrote: >> >> Hi all, >> >> PDFtalk is a PDF library for VisualWorks[1]. The library has been ported successfully to Gemstone[2]. >> Now, there is interest from companies in a port to Squeak and VA Smalltalk. >> >> The project[3] has started and we are making good progress. >> The first step: porting the Values package. >> This is easy, because there are no namespace issues. >> >> The next step is to implement class renamings so that namespaced classes can be renamed to global prefixed names. >> >> Then PDFtalk with all its components, except for the UI, can be ported. >> >> The porting approach is different to the traditional way of loading and fixing. >> The import files for other Smalltalks are generated from VisualWorks where the code is transformed by declarative rules. >> The approach is documented in [4]. >> >> I set up a GitHub organization for this project[5]. There, the fileouts for each dialect are published (Gemstone, Squeak and VA Smalltalk so far), so that people without VisualWorks can work with the code in their Smalltalk. >> >> Also, I record and explain all steps of the porting process for Squeak in great detail[6], so that people can follow it. >> >> I would like to invite Smalltalkers from all dialects to take part in this project. >> The code transformations for Squeak will be quite similar to the ones needed for Pharo and Cuis. >> Therefore, each port to one Smalltalk will help the port to other Smalltalks. >> >> Any takers? >> >> Happy hacking, >> Christian >> >> >> [1] https://wiki.pdftalk.de/doku.php?id=start <https://wiki.pdftalk.de/doku.php?id=start> >> [2] https://wiki.pdftalk.de/doku.php?id=pdftalk4gemstone <https://wiki.pdftalk.de/doku.php?id=pdftalk4gemstone> >> [3] https://wiki.pdftalk.de/doku.php?id=pdftalknonnamespacefileout <https://wiki.pdftalk.de/doku.php?id=pdftalknonnamespacefileout> >> [4] https://wiki.pdftalk.de/doku.php?id=smalltalktransform <https://wiki.pdftalk.de/doku.php?id=smalltalktransform> >> [5] https://github.com/PortingPDFtalk <https://github.com/PortingPDFtalk> >> [6] https://wiki.pdftalk.de/doku.php?id=valuesportinglog <https://wiki.pdftalk.de/doku.php?id=valuesportinglog>_______________________________________________ >> Esug-list mailing list -- esug-list(a)lists.esug.org <mailto:esug-list@lists.esug.org> >> To unsubscribe send an email to esug-list-leave(a)lists.esug.org <mailto:esug-list-leave@lists.esug.org> > >

1 0

Default selection when compiling a method
by pmissech March 25, 2022

March 25, 2022

Hello, We have worked today with Iona on https://github.com/pharo-project/pharo/issues/11052. Basically the hierarchy is reversed by default, which we don't like. We proposed a PR to change the default behavior. The issue we want to share with you today is the following. You select a method that is installed in a class different from your current class in the Calyspo browser. You want to change it. Upon compiling your changes, Calypso asks for where the method should be installed. We are wondering whether we should have a default selection in the Class list. Two cases that we thought of: (1) When selecting a subclassResponsibility, We would like to pre select the current class to install the new method. (2) When selecting a random method from the hierarchy, we tend to think that the class in which the method is implemented should be selected by default. Â Â Â When working on your own projects, this makes sense to us. Â Â Â When navigating through other projects/core packages, it would make less sense. We tend to think that we should select the current class every time. (basically case (1)) But what do you think ? Have a nice day Pierre & Iona

1 0

This week (12/2022) on the Pharo Issue Tracker MD Marcus Denker
by Marcus Denker March 25, 2022

March 25, 2022

We merged 15 PRs and closed 14 issues this week. Fixes ===== - fix row background color loss when hovering a table with alternated color configured #11020 https://github.com/pharo-project/pharo/pull/11020 - Fix Cmd-t again #11022 https://github.com/pharo-project/pharo/pull/11022 - this change enables click + control, and click + alt in morphic #11032 https://github.com/pharo-project/pharo/pull/11032 - 11007 isPrime does not work for large numbers #11030 https://github.com/pharo-project/pharo/pull/11030 - Fix for specific failure of isPrime for certain squares introduced byâ¦ #11047 https://github.com/pharo-project/pharo/pull/11047 - use fixed spec version (for release) #11014 https://github.com/pharo-project/pharo/pull/11014 - Change UserInterrupt detection to use character codes rather than scaâ¦ #11004 https://github.com/pharo-project/pharo/pull/11004 Documentation ============= - ClassDefinitionPrinter-Comments #11005 https://github.com/pharo-project/pharo/pull/11005 Speed ===== - 11018 SmallInteger isPrime is inefficient #11043 https://github.com/pharo-project/pharo/pull/11043 Cleanup ======= - Renamed protocol name from accesing to accessing #10967 https://github.com/pharo-project/pharo/pull/10967 - Align a few categories in Zinc with the rest of system #11029 https://github.com/pharo-project/pharo/pull/11029 - Cleanup: protocol "activating" -> "activation" #11034 https://github.com/pharo-project/pharo/pull/11034 - Cleanup: protocol "activation hooks" -> "activation - hooks" #11036 https://github.com/pharo-project/pharo/pull/11036 - Cleanup: align protocols in UITheme #11040 https://github.com/pharo-project/pharo/pull/11040 - Cleanup waiting protocols in Monitor #11042 https://github.com/pharo-project/pharo/pull/11042 Pharo9 ====== - Backport Fix #11001: Stateful Traits: Adding One Corrupts Existing Instances #11016 https://github.com/pharo-project/pharo/pull/11016

1 0

Positions at lifeware :)
by stephane ducasse March 21, 2022

March 21, 2022

1 0

Extension Traits/Slots
by sean＠clipperadams.com March 19, 2022

March 19, 2022

Has this ever been considered? We can add methods from a package different than the host class and thereby avoid dirtying its package, but what if we could do the same for traits and slots?

2 1

Stateful Traits: Adding One Corrupts Existing Instances
by sean＠clipperadams.com March 18, 2022

March 18, 2022

This is a bad one. Can someone have a look? Anyone I should tag on the issue? https://github.com/pharo-project/pharo/issues/11001

1 1

This week (11/2022) on the Pharo Issue Tracker
by Marcus Denker March 18, 2022

March 18, 2022

We fixed 11 issues and closed 10 PRs this week. Fixes ===== - 10982 refactoring remove arg is not working nice #11009 https://github.com/pharo-project/pharo/pull/11009 - 11001-Stateful-Traits-Adding-One-Corrupts-Existing-Instances #11008 https://github.com/pharo-project/pharo/pull/11008 - 8082-Code-import-does-not-with-fluid-class-definition #10979 https://github.com/pharo-project/pharo/pull/10979 - 10971-Calypso-breaks-while-autocompleting-related-to-super-in-Traits #10976 https://github.com/pharo-project/pharo/pull/10976 - 10991-AbstractBinaryFileStream-has-no-write-equivalent-to-readIntostartingAtcount #11000 https://github.com/pharo-project/pharo/pull/11000 - Allow to alternate colors of a table #10966 https://github.com/pharo-project/pharo/pull/10966 - Expand the class comment for Bag #10989 https://github.com/pharo-project/pharo/pull/10989 - Making inline refactoring's confirmation message more clear #11006 https://github.com/pharo-project/pharo/pull/11006 - SycOpenReflectivityMenuCommand-remove-shortcut #10995 https://github.com/pharo-project/pharo/pull/10995

1 0

ANN: Linux Open Build Service new versions
by Esteban Lorenzano March 17, 2022

March 17, 2022

Hi, I have been preparing our OBS builds [1] for the Pharo 10 release. We now include: Fedora 35 Ubuntu 21.10 Debian 11 And we fixed the rolling releases: Arch OpenSUSE Thumbleweed Enjoy! Esteban [1] https://software.opensuse.org//download.html?project=devel%3Alanguages%3Aph…

2 3

Pharo VM Release - v9.0.13
by tesonep＠gmail.com March 16, 2022

March 16, 2022

Hello, I have released a new version of the Pharo VM for Pharo 9 and Pharo 10. 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. Changelog: - Correct handling OOB (Out of Band Data) in Window - Blocking signals while signalling semaphores to avoid deadlocks caused by signal handlers - Make MAXHOSTNAMELEN at least 256: improving resolution of names in Linux - Improving VM Simulator Machine debugger - Integrating Processor Simulator for RISCV - Using a new SDL2 version built for OSX Mojave compatibility 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

2 1