May 2021 - Pharo-dev - lists.pharo.org

Re: Open Sound Control Package for Pharo 9.0

by Sven Van Caekenberghe

Hi GÃ¼nter, Thanks for answering, I expected that you would mention this aspect. I don't know about OSC, but from your description it sounds like it basically is a binary protocol, where some sequences of bytes are to be interpreted as ASCII encoded strings. I would just work on binary streams and do the encoding/decoding as needed. ASCII is trivial, you can either do: ZnCharacterEncoder ascii encodeString: 'OSC' or 'OSC' asByteArray And the inverse is either ZnCharacterEncoder ascii decodeBytes: #[79 83 67]. or #[79 83 67] asString. The OSC spec says: OSC-string A sequence of non-null ASCII characters followed by a null, followed by 0-3 additional null characters to make the total number of bits a multiple of 32. One approach could be: #writeOSCString: string on: stream stream nextPutAll: (ZnCharacterEncoder ascii encodeString: string). stream nextPut: 0. (string size + 1) // 4 timesRepeat: [ stream nextPut: 0 ] #readOSCStringFrom: stream | string | string := ByteArray streamContents: [ :out | [ stream peekFor: 0 ] whileFalse: [ out nextPut: stream next ] ]. (string size + 1) // 4 timesRepeat: [ stream next ]. ^ ZnCharacterEncoder ascii decodeBytes: string My point being that you probably don't need RWTextOrBinaryStream at all. Of course, if you ported existing code and don't want to change it much, your solution is acceptable. Sven > On 21 May 2021, at 15:39, GÃ¼nter Khyo <erde(a)chello.at> wrote: > > A RWTextOrBinaryStream instance can operate in binary or ascii mode, the mode can be switched at any time by sending ascii or binary, and some methods are mode-sensitive, e.g., contents will respond with a ByteArray in binary mode and a ByteString in ascii mode. (OSC uses ASCII encoding for addresses and strings, and binary formats for numbers and blobs.) > > The OSC testcases and the parser rely on this behavior. > > On 5/21/21 3:00 PM, Sven Van Caekenberghe wrote: >> >>> On 21 May 2021, at 14:02, GÃ¼nter Khyo via Pharo-dev <pharo-dev(a)lists.pharo.org> >>> wrote: >>> >>> Hi, >>> >>> I have ported the Open Sound Control package to Pharo 9.0. Since the Catalog Browser is marked as legacy, I was wondering how to submit the patch. Is there a git repository? I attached the fileout to this email in case anybody wants to take a look at the package or knows how/where to add it to Pharo 9.0, >>> >>> Patch Note: >>> >>> OSC relies on the removed RWTextOrBinaryStream class which has very specific behavior that I could not emulate using the available stream and codec classes, so I pulled in the class from Squeak 5, renamed it to OSCStream and added it to the OSC package. This seemed to be the easiest way to do it without changing the OSC implementation, but I welcome any suggestions for a cleaner solution. >>> >> I am curious, what was the specific behaviour that you could not emulate ? >> >> >>> GÃ¼nter >>> >>> <OSC.st> >>>

May 21, 2021

Re: Open Sound Control Package for Pharo 9.0

by GÃ¼nter Khyo

A RWTextOrBinaryStream instance can operate in binary or ascii mode, the mode can be switched at any time by sending /ascii/ or /binary/, and some methods are mode-sensitive, e.g., /contents/ will respond with a ByteArray in binary mode and a ByteString in ascii mode. (OSC uses ASCII encoding for addresses and strings, and binary formats for numbers and blobs.) The OSC testcases and the parser rely on this behavior. On 5/21/21 3:00 PM, Sven Van Caekenberghe wrote: > >> On 21 May 2021, at 14:02, GÃ¼nter Khyo via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: >> >> Hi, >> >> I have ported the Open Sound Control package to Pharo 9.0. Since the Catalog Browser is marked as legacy, I was wondering how to submit the patch. Is there a git repository? I attached the fileout to this email in case anybody wants to take a look at the package or knows how/where to add it to Pharo 9.0, >> >> Patch Note: >> >> OSC relies on the removed RWTextOrBinaryStream class which has very specific behavior that I could not emulate using the available stream and codec classes, so I pulled in the class from Squeak 5, renamed it to OSCStream and added it to the OSC package. This seemed to be the easiest way to do it without changing the OSC implementation, but I welcome any suggestions for a cleaner solution. > I am curious, what was the specific behaviour that you could not emulate ? > >> GÃ¼nter >> >> <OSC.st>

May 21, 2021

Re: Open Sound Control Package for Pharo 9.0

by Sven Van Caekenberghe

> On 21 May 2021, at 14:02, GÃ¼nter Khyo via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > Hi, > > I have ported the Open Sound Control package to Pharo 9.0. Since the Catalog Browser is marked as legacy, I was wondering how to submit the patch. Is there a git repository? I attached the fileout to this email in case anybody wants to take a look at the package or knows how/where to add it to Pharo 9.0, > > Patch Note: > > OSC relies on the removed RWTextOrBinaryStream class which has very specific behavior that I could not emulate using the available stream and codec classes, so I pulled in the class from Squeak 5, renamed it to OSCStream and added it to the OSC package. This seemed to be the easiest way to do it without changing the OSC implementation, but I welcome any suggestions for a cleaner solution. I am curious, what was the specific behaviour that you could not emulate ? > GÃ¼nter > > <OSC.st>

May 21, 2021

Open Sound Control Package for Pharo 9.0

by GÃ¼nter Khyo

Hi, I have ported the Open Sound Control package to Pharo 9.0. Since the Catalog Browser is marked as legacy, I was wondering how to submit the patch. Is there a git repository? I attached the fileout to this email in case anybody wants to take a look at the package or knows how/where to add it to Pharo 9.0, Patch Note: OSC relies on the removed /RWTextOrBinaryStream/ class which has very specific behavior that I could not emulate using the available stream and codec classes, so I pulled in the class from Squeak 5, renamed it to OSCStream and added it to the OSC package. This seemed to be the easiest way to do it without changing the OSC implementation, but I welcome any suggestions for a cleaner solution. GÃ¼nter

May 21, 2021

This week (20/2021) on the Pharo Issue Tracker

by Marcus Denker

We merged 17 Pull Requests and closed 13 issues. As we are preparing the release of Pharo9, we are focussing in bug fixes and trivial cleanups. Update to fuel 303 #9283 ======================== https://github.com/pharo-project/pharo/pull/9283 Fixes ===== improving-drtests-plugin-support #9276 https://github.com/pharo-project/pharo/pull/9276 Resurrected old beahviour where it was possible to use cmd-s https://github.com/pharo-project/pharo/pull/9293 Add possibility to wrap text in the text comparator #9200 https://github.com/pharo-project/pharo/pull/9200 fixing light/dark themes disabled colors #9281 https://github.com/pharo-project/pharo/pull/9281 fix SHRBTextStyler messing Transcript. #9292 https://github.com/pharo-project/pharo/pull/9292 slowFactorial call corrected #9295 https://github.com/pharo-project/pharo/pull/9295 9093--in-floatArray-changes-the-second-array- #9149 https://github.com/pharo-project/pharo/pull/9149 8897 restart quick method smashes stack #9185 https://github.com/pharo-project/pharo/pull/9185 RB - Improve Refactoring presenters #9285 https://github.com/pharo-project/pharo/pull/9285 RB - Fix Lazy initialization #9265 https://github.com/pharo-project/pharo/pull/9265 Cleanups ======== Remove argument from parseExpression: and parseMethod: in Parser #9279 https://github.com/pharo-project/pharo/pull/9279 Deprecations for removed #parse methods in RBParser #9300 https://github.com/pharo-project/pharo/pull/9300 Mark abstract classes in Microdown package - Second attempt #9212 https://github.com/pharo-project/pharo/pull/9212 9280-CompiledMethod--valueWithReceiver-aReceiver-arguments-anArray-comments-is-arcane #9296 https://github.com/pharo-project/pharo/pull/9296 roundUpTo deserves executable comments #9298 https://github.com/pharo-project/pharo/pull/9298 Removes method DialogWindow >> setButtonFont: #9274 https://github.com/pharo-project/pharo/pull/9274

May 21, 2021

Re: Pharo Progress Report 19/05/2021 (The Return)

by Noury Bouraqadi

Thanks Esteban. I like your idea of showing the direction. Noury On May 19 2021, at 10:59 am, Esteban Lorenzano <estebanlm(a)netc.eu> wrote: > Hello! > > The other day Torsten mention in discord that before was easier to follow what was going on due the reports we were publishing, and I think he is right. This reports stopped to being produced when the pandemic arise and lock-down was the norm... our organisation of work suffered and the reports were an undesirable victim :) > I intend to resume the publication of weekly status reports, with a difference: focusing on immediate changes is not productive anymore because we have the excelent report of Marcus for that (which follows the integrations in Pharo development branch). > So, I will talk about immediate and medium-term goals, and steps we are doing following them. > This is the first, let's see if this helps people to follow :) > Short-term goals: > - Improve integration infrastructure for Spec2 and NewTools frameworks. > - Improve quality and quantity of tests in Spec2 and NewTools frameworks. > - Improve quality of class comments in Spec2 framework. > - Since we are in freeze mode: fixing important bugs on Pharo9 and its components (this issue will stay here until release). > > Medium-term goals: > - Removal of GTTools > - M1 VM release > - Release 9.0 > > # Last week work > ## Last week: > - moved newtools and spec infrastructure to github actions (travis was being slow) > - fixed several bugs on SpGridLayout, SpDropListPresenter,SpTreePresenter and SpTreeTablePresenter > - fixed wrong enable/disable dynamic and style of buttons (also in toolbars). > - added some inspector extensions to improve visibility of Morph data > - added a lot of tests to new Playground, SpCodePresenter, SpTreePresenter and SpTreeTablePresenter. > - Pablo and Guille were working hard on improving the VM profiling infrastructure. > - making the ARM simulator work > - Working in the parallel execution of tests > - Improving the stability of Socket primitives > - Fixing problems in the Large Images support > - Extending DrTest to delegate the UI construction to the plugins > - Stef ported MethodWrappers to Pharo 9 (which allow a lot of profiling and "object centric" stuff. > - Finally, Marcus was busy processing PRs and discussing future steps (in part with me ;) ) > > ## This week > (as always, this is just pointing in a direction, what later comes in depends on the work load, problems, and "unknowns") > > - finish new infrastructure to improve integration speed of Spec2 and NewTools > - add tests to new Inspector > - more freezing actions (bugfixing, PR processing) > > cheers! > Esteban

May 19, 2021

Pharo Progress Report 19/05/2021 (The Return)

by Esteban Lorenzano

Hello! The other day Torsten mention in discord that before was easier to follow what was going on due the reports we were publishing, and I think he is right. This reports stopped to being produced when the pandemic arise and lock-down was the norm... our organisation of work suffered and the reports were an undesirable victim :) I intend to resume the publication of weekly status reports, with a difference: focusing on immediate changes is not productive anymore because we have the excelent report of Marcus for that (which follows the integrations in Pharo development branch). So, I will talk about immediate and medium-term goals, and steps we are doing following them. This is the first, let's see if this helps people to follow :) Short-term goals: - Improve integration infrastructure for Spec2 and NewTools frameworks. - Improve quality and quantity of tests in Spec2 and NewTools frameworks. - Improve quality of class comments in Spec2 framework. - Since we are in freeze mode: fixing important bugs on Pharo9 and its components (this issue will stay here until release). Medium-term goals: - Removal of GTTools - M1 VM release - Release 9.0 # Last week work ## Last week: - moved newtools and spec infrastructure to github actions (travis was being slow) - fixed several bugs on SpGridLayout, SpDropListPresenter,SpTreePresenter and SpTreeTablePresenter - fixed wrong enable/disable dynamic and style of buttons (also in toolbars). - added some inspector extensions to improve visibility of Morph data - added a lot of tests to new Playground, SpCodePresenter, SpTreePresenter and SpTreeTablePresenter. - Pablo and Guille were working hard on improving the VM profiling infrastructure. - making the ARM simulator work - Working in the parallel execution of tests - Improving the stability of Socket primitives - Fixing problems in the Large Images support - Extending DrTest to delegate the UI construction to the plugins - Stef ported MethodWrappers to Pharo 9 (which allow a lot of profiling and "object centric" stuff. - Finally, Marcus was busy processing PRs and discussing future steps (in part with me ;) ) ## This week (as always, this is just pointing in a direction, what later comes in depends on the work load, problems, and "unknowns") - finish new infrastructure to improve integration speed of Spec2 and NewTools - add tests to new Inspector - more freezing actions (bugfixing, PR processing) cheers! Esteban

May 19, 2021

Re: Progress Report -> Refactoring Project - ( May 10 - May 14)

by Evelyn Cusi Lopez

Hello Gabriel, Thank you very much for the suggestions, at the moment they have a default name, but of course I could add the option to rename them. Right now we are making the combination of environments accessible, using the RBAndEnvironment, RBOrEnvironment and RBNotEnvironment classes. Regards, Evelyn Cusi El lun, 17 may 2021 a las 8:41, Gabriel Cotelli (<g.cotelli(a)gmail.com>) escribiÃ³: > Evelyn, > It is really good to see these improvements. May I suggest allowing the > user to give a name to a specific scope?. Because having a large list of > packages or classes in the scope and using them to infer the name will not > scale well. I'm envisioning creating these scopes programmatically for our > packages and having the possibility of giving them a proper name is a must. > > Another idea that I think can be useful is to allow combining existing > scopes into a new one. > > Keep up the good work. > > > On Mon, May 17, 2021 at 9:19 AM Evelyn Cusi Lopez <cusi.evelyn(a)gmail.com> > wrote: > >> Hi everyone, >> >> Last week I did these tasks: >> >> - Improve presenter of scope list using trees, add modal to show details >> of scopes >> - Add RBClassHierarchyEnvironment >> - Add commands to add HierarchyScope (from simple class), add NOT command >> to do operations in scopeList. >> - Add direct access from the toolbar. Check these changes in the branch: DefaultScope >> branch >> <https://github.com/pharo-project/pharo/compare/Pharo9.0...Lin777:DefaultSco…> Check >> the behavior in this video: Youtube video <https://youtu.be/Ex5P49Lyx_E>. >> - Change preview of refactorings from Modal to Dialog, refactor some >> components of refactoring presenters and add focus order in rename method >> preview. Check changes here: PR >> <https://github.com/pharo-project/pharo/pull/9285> >> >> Tasks for this week: >> <https://github.com/pharo-project/pharo/issues/9142> >> >> - Use the scopeList with refactorings (as default environments). >> - Fix issues: #9060 <https://github.com/pharo-project/pharo/issues/9060> >> and #5894 <https://github.com/pharo-project/pharo/issues/5894>. Now >> refactoring preview presenter is already a Dialog, Still missing to convert >> the renaming, select methods, variables, etc.presents to dialogs >> - Improve messages: No understable message #9229 >> <https://github.com/pharo-project/pharo/issues/9241> >> - Fix issue: RB - Inline all senders of class methods (instance >> creation) doesn't work, need improve pattern to search #9142 >> <https://github.com/pharo-project/pharo/issues/9142> >> - Fix issue: RB - Improve instance variable refactoring #8665 >> <https://github.com/pharo-project/pharo/issues/8665> >> <https://github.com/pharo-project/pharo/issues/9241> >> >> Regards, >> >> Evelyn C. >> >

May 17, 2021

Re: Progress Report -> Refactoring Project - ( May 10 - May 14)

by Gabriel Cotelli

Evelyn, It is really good to see these improvements. May I suggest allowing the user to give a name to a specific scope?. Because having a large list of packages or classes in the scope and using them to infer the name will not scale well. I'm envisioning creating these scopes programmatically for our packages and having the possibility of giving them a proper name is a must. Another idea that I think can be useful is to allow combining existing scopes into a new one. Keep up the good work. On Mon, May 17, 2021 at 9:19 AM Evelyn Cusi Lopez <cusi.evelyn(a)gmail.com> wrote: > Hi everyone, > > Last week I did these tasks: > > - Improve presenter of scope list using trees, add modal to show details > of scopes > - Add RBClassHierarchyEnvironment > - Add commands to add HierarchyScope (from simple class), add NOT command > to do operations in scopeList. > - Add direct access from the toolbar. Check these changes in the branch: DefaultScope > branch > <https://github.com/pharo-project/pharo/compare/Pharo9.0...Lin777:DefaultSco…> Check > the behavior in this video: Youtube video <https://youtu.be/Ex5P49Lyx_E>. > - Change preview of refactorings from Modal to Dialog, refactor some > components of refactoring presenters and add focus order in rename method > preview. Check changes here: PR > <https://github.com/pharo-project/pharo/pull/9285> > > Tasks for this week: > <https://github.com/pharo-project/pharo/issues/9142> > > - Use the scopeList with refactorings (as default environments). > - Fix issues: #9060 <https://github.com/pharo-project/pharo/issues/9060> > and #5894 <https://github.com/pharo-project/pharo/issues/5894>. Now > refactoring preview presenter is already a Dialog, Still missing to convert > the renaming, select methods, variables, etc.presents to dialogs > - Improve messages: No understable message #9229 > <https://github.com/pharo-project/pharo/issues/9241> > - Fix issue: RB - Inline all senders of class methods (instance creation) > doesn't work, need improve pattern to search #9142 > <https://github.com/pharo-project/pharo/issues/9142> > - Fix issue: RB - Improve instance variable refactoring #8665 > <https://github.com/pharo-project/pharo/issues/8665> > <https://github.com/pharo-project/pharo/issues/9241> > > Regards, > > Evelyn C. >

May 17, 2021

Re: Progress Report -> Refactoring Project - ( May 3 - May 7)

by Evelyn Cusi Lopez

Hello Sean, Thank you very much, I was not quite sure how to handle living objects, with those comments I have a little clearer idea of how to proceed with this task. Thanks :) Regards, Evelyn Cusi El vie, 14 may 2021 a las 9:32, Sean P. DeNigris (<sean(a)clipperadams.com>) escribiÃ³: > EVELYN CUSI LOPEZ wrote > > Tasks for this week: > > - Fix issue: RB - Improve instance variable refactoring #8665 > > Glad to see this on the horizon! This is an important one. It can be a big > gotcha for us naive users. I added a comment to the issue - hope it helps. > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

May 17, 2021