- Pharo-dev - lists.pharo.org

Re: [ANN] CBOR for Pharo

by Sven Van Caekenberghe

> On 23 Jun 2023, at 00:06, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: > > Super nice > for a moment I thought that you forgot the final G of the name :) Haha, that would have been nice. It is a bit of a weird acronym. I must admit that I did not hear about it until recently. There are several binary JSON specifications, but this one has an elegance to it, I liked it immediately. And the best way to understand it or get a feel for it is to implement it. From time to time I need to do a project like this: small scope, clear spec, no drama. I would also like to iterate that doing binary coding in Pharo is really nice, elegant and powerful. >> On 21 Jun 2023, at 11:25, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> [ANN] CBOR for Pharo >> >> https://github.com/svenvc/CBOR >> >> Concise Binary Object Representation (CBOR) is a binary data serialization format. CBOR is based on the JSON data model: a number of primitive types (integers, floats, booleans, strings and null), lists and maps (which represent objects or structures). Being binary, CBOR is more efficient than JSON, which is text based. CBOR also supports binary data and optional extensions (called tags). This implementation has native support for string and epoch based timestamps (DateAndTime) and big integers (Integer). >> >> This project contains encoding/decoding support for the half-precision, IEEE 754 16-bit (binary16) floating-point format. >> >> Sven >> >> >> -- >> Sven Van Caekenberghe >> Proudly supporting Pharo >> http://pharo.org >> http://association.pharo.org >> http://consortium.pharo.org >> >> >>

June 23, 2023

This week (25/2023) on the Pharo Issue Tracker

by Marcus Denker

# Misc / Fixes - 14089-problem-showing-dock-icon-for-some-compiler-warnings-eg-name-aready-defined #14090 https://github.com/pharo-project/pharo/pull/14090 - Updated version of graph algos to use the latest one #14103 https://github.com/pharo-project/pharo/pull/14103 - Fix package file out #14076 https://github.com/pharo-project/pharo/pull/14076 - 14061-SequenceableCollectiongroupByRuns-should-be-packaged-in-Collections #14075 https://github.com/pharo-project/pharo/pull/14075 - adding-perm-space-statistics #14052 https://github.com/pharo-project/pharo/pull/14052 - Move Margin from Kernel to Graphics #14044 https://github.com/pharo-project/pharo/pull/14044 - Simplify #doBrowseImplementors and #doBrowseSenders #1411 https://github.com/pharo-spec/Spec/pull/1411 - [P12] Fix DNU when recompiling block with dead home #552 https://github.com/pharo-spec/NewTools/pull/552 - Trivial dead code cleanup #550 https://github.com/pharo-spec/NewTools/pull/550 # ClassBuilder / Fluid Class Definitions - reduce the usage of the non-fluid class definiton methods #14058 https://github.com/pharo-project/pharo/pull/14058 - another simplification of class builder users: Traits #14079 https://github.com/pharo-project/pharo/pull/14079 - Fix trait definition in Calypso when fluid is enabled #14088 https://github.com/pharo-project/pharo/pull/14088 - Non-Fluid class creation: use class builder, last batch #14099 https://github.com/pharo-project/pharo/pull/14099 - ClassInstaller: improve #update:to: to do the #fillFor: #14095 https://github.com/pharo-project/pharo/pull/14095 - ClassBuilder: reduce the need of #asSlotCollection and #asTraitComposition #14074 https://github.com/pharo-project/pharo/pull/14074 - ClassBuilder users: Do not set 'Unclassified' category/package explicitly #14066 https://github.com/pharo-project/pharo/pull/14066 - Fix class parser for non-fluid nil subclass definitions #14054 https://github.com/pharo-project/pharo/pull/14054 # Protocols / Categories - Update MethodAddition to use #protocol #14050 https://github.com/pharo-project/pharo/pull/14050 - Remove hardcoded 'as yet unclassified' #14085 https://github.com/pharo-project/pharo/pull/14085 - Remove ClyMethodTagsEditorMorph #14083 https://github.com/pharo-project/pharo/pull/14083 - Deprecate CompiledMethod>>#tags #14078 https://github.com/pharo-project/pharo/pull/14078 - Simplify ClyMethodEditorToolMorph #14069 https://github.com/pharo-project/pharo/pull/14069 - Deprecate CompiledMethod>>untagFrom: #14060 https://github.com/pharo-project/pharo/pull/14060 - Deprecated CompiledMethod>>tagWith: #14049 https://github.com/pharo-project/pharo/pull/14049 - Deprecated CompiledMethod>>category #14047 https://github.com/pharo-project/pharo/pull/14047 # RPackage Cleanup: Monticello - Merge MCWorkingCopy and MCPackageManager #14041 https://github.com/pharo-project/pharo/pull/14041 - Simplify MCWorkingCopy management #14040 https://github.com/pharo-project/pharo/pull/14040 - Remove some Monticello GUI #14059 https://github.com/pharo-project/pharo/pull/14059 - Decouple Monticello and RPackage on package removal #14072 https://github.com/pharo-project/pharo/pull/14072 - Finish Monticello decoupling in RPackage #14077 https://github.com/pharo-project/pharo/pull/14077 - Extract Monticello from package renmaing #14065 https://github.com/pharo-project/pharo/pull/14065 - Move WorkingCopy creation to Monticello #14036 https://github.com/pharo-project/pharo/pull/14036 - Move Monticello diffs to its own package #14067 https://github.com/pharo-project/pharo/pull/14067 - Remove double initialization of MCWorkingCopy #14064 https://github.com/pharo-project/pharo/pull/14064 - Iteration on package tag announcements #14081 https://github.com/pharo-project/pharo/pull/14081 # RPackage cleanup: Epicea (Source logging) - Epicea: Fix application of package addition and cleanup EpPackageAddition #1410 https://github.com/pharo-project/pharo/pull/14101 - Epicea: Add test on PackageAddition event #14092 https://github.com/pharo-project/pharo/pull/14092 - Epicea: Clean package addition and fix bugs #14087 https://github.com/pharo-project/pharo/pull/14087 # Compiler: Variables - rename ReservedVariable to PseudoVariable #14071 https://github.com/pharo-project/pharo/pull/14071 - PseudoVariable: add deprecations / cleanups #14082 https://github.com/pharo-project/pharo/pull/14082 - 14039-P12-RBVariableisDefinition-does-not-return-true-when-it-should #14051 https://github.com/pharo-project/pharo/pull/14051 # Refactoring Engine - Cleanup: change method name refactoring #14097 https://github.com/pharo-project/pharo/pull/14097 - Refactor: Add "(T)" prefix to Find and Replace transformation #14091 https://github.com/pharo-project/pharo/pull/14091 - Enh/refact pass on preconditions #14048 https://github.com/pharo-project/pharo/pull/14048

June 23, 2023

Re: [ANN] CBOR for Pharo

by Guillermo Polito

Thanks Sven :) > El 23 jun. 2023, a las 00:06, stephane ducasse <stephane.ducasse(a)inria.fr> escribiÃ³: > > Super nice > for a moment I thought that you forgot the final G of the name :) > >> On 21 Jun 2023, at 11:25, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> [ANN] CBOR for Pharo >> >> https://github.com/svenvc/CBOR >> >> Concise Binary Object Representation (CBOR) is a binary data serialization format. CBOR is based on the JSON data model: a number of primitive types (integers, floats, booleans, strings and null), lists and maps (which represent objects or structures). Being binary, CBOR is more efficient than JSON, which is text based. CBOR also supports binary data and optional extensions (called tags). This implementation has native support for string and epoch based timestamps (DateAndTime) and big integers (Integer). >> >> This project contains encoding/decoding support for the half-precision, IEEE 754 16-bit (binary16) floating-point format. >> >> Sven >> >> >> -- >> Sven Van Caekenberghe >> Proudly supporting Pharo >> http://pharo.org >> http://association.pharo.org >> http://consortium.pharo.org >> >> >>

June 23, 2023

Re: [ANN] CBOR for Pharo

by stephane ducasse

Super nice for a moment I thought that you forgot the final G of the name :) > On 21 Jun 2023, at 11:25, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > [ANN] CBOR for Pharo > > https://github.com/svenvc/CBOR > > Concise Binary Object Representation (CBOR) is a binary data serialization format. CBOR is based on the JSON data model: a number of primitive types (integers, floats, booleans, strings and null), lists and maps (which represent objects or structures). Being binary, CBOR is more efficient than JSON, which is text based. CBOR also supports binary data and optional extensions (called tags). This implementation has native support for string and epoch based timestamps (DateAndTime) and big integers (Integer). > > This project contains encoding/decoding support for the half-precision, IEEE 754 16-bit (binary16) floating-point format. > > Sven > > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > >

June 22, 2023

Re: [ANN] CBOR for Pharo

by Martin Dias

El miÃ©, 21 jun 2023 a la(s) 05:25, Sven Van Caekenberghe (sven(a)stfx.eu) escribiÃ³: > [ANN] CBOR for Pharo > > https://github.com/svenvc/CBOR > > Concise Binary Object Representation (CBOR) is a binary data serialization > format. CBOR is based on the JSON data model: a number of primitive types > (integers, floats, booleans, strings and null), lists and maps (which > represent objects or structures). Being binary, CBOR is more efficient than > JSON, which is text based. CBOR also supports binary data and optional > extensions (called tags). This implementation has native support for string > and epoch based timestamps (DateAndTime) and big integers (Integer). > > This project contains encoding/decoding support for the half-precision, > IEEE 754 16-bit (binary16) floating-point format. > Thanks Sven, it looks awesome. regards, MartÃn > > Sven > > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > > >

June 22, 2023

[ANN] CBOR for Pharo

by Sven Van Caekenberghe

[ANN] CBOR for Pharo https://github.com/svenvc/CBOR Concise Binary Object Representation (CBOR) is a binary data serialization format. CBOR is based on the JSON data model: a number of primitive types (integers, floats, booleans, strings and null), lists and maps (which represent objects or structures). Being binary, CBOR is more efficient than JSON, which is text based. CBOR also supports binary data and optional extensions (called tags). This implementation has native support for string and epoch based timestamps (DateAndTime) and big integers (Integer). This project contains encoding/decoding support for the half-precision, IEEE 754 16-bit (binary16) floating-point format. Sven -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

June 21, 2023

Re: Fwd: [Pharo-users] Kind reminder: Survey on the usage of the system browser

by Noury Bouraqadi

Thank you Marcus for the repost. Koen's mail was in my spam. @Koen Welcome back to Smalltalk and Pharo :-) See you all at ESUG 2023 next August in Lyon, France. Noury On Jun 20 2023, at 12:09 pm, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > > Begin forwarded message: > > From: Koen De Hondt <koen(a)all-objects-all-the-time.st> > > Subject: [Pharo-users] Kind reminder: Survey on the usage of the system browser > > > > Date: 20 June 2023 at 12:08:00 CEST > > > > To: pharo-users(a)lists.pharo.org > > > > Reply-To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > > > > > > Hi Pharo users, > > > > A few weeks ago I sent the invitation below. I have received 45 responses. A big thanks to all who have taken the survey! > > > > If you have not taken the survey yet, I invite you again to do so. It will make the survey results better, and it will make the ESUG presentation better. > > > > Thank you! > > > > Best regards, > > Koen > > > > > Begin forwarded message: > > > From: Koen De Hondt <koen(a)all-objects-all-the-time.st> > > > Subject: [Pharo-users] Survey on the usage of the system browser > > > > > > Date: 31 May 2023 at 08:15:01 CEST > > > > > > To: pharo-users(a)lists.pharo.org > > > > > > Reply-To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > > > > > > > > > Dear Pharo users, > > > > > > I have submitted a proposal for a presentation at ESUGâ23. Part of the presentation will report on the results of a survey about the usage of the Pharo system browser. I need your help to produce the results ð. Therefore I invite you to take the survey at https://forms.gle/cBYs7DRwZvAVAyQb9. It is not too long, and totally anonymous. Your feedback is very much appreciated! > > > > > > Thanks in advance. > > > > > > Kind regards, > > > Koen > > > > > > PS: Maybe you wonder who this new kid on the block is. Actually, it is an old kid on the block. ð See https://all-objects-all-the-time.st (https://all-objects-all-the-time.st/)

June 21, 2023

Help Pharo by tagging your pharo projects on GH

by stephane ducasse

Hi guys We would like to make sure that the numbers given in the following page https://github.com/topics/pharo reflects a bit better the numbers of projects in Github. So could you tag your pharo projects on github with the Pharo tag? Thanks in advance. S

June 20, 2023

Fwd: [Pharo-users] Kind reminder: Survey on the usage of the system browser

by Marcus Denker

> Begin forwarded message: > > From: Koen De Hondt <koen(a)all-objects-all-the-time.st> > Subject: [Pharo-users] Kind reminder: Survey on the usage of the system browser > Date: 20 June 2023 at 12:08:00 CEST > To: pharo-users(a)lists.pharo.org > Reply-To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > > Hi Pharo users, > > A few weeks ago I sent the invitation below. I have received 45 responses. A big thanks to all who have taken the survey! > > If you have not taken the survey yet, I invite you again to do so. It will make the survey results better, and it will make the ESUG presentation better. > > Thank you! > > Best regards, > Koen > >> Begin forwarded message: >> >> From: Koen De Hondt <koen(a)all-objects-all-the-time.st> >> Subject: [Pharo-users] Survey on the usage of the system browser >> Date: 31 May 2023 at 08:15:01 CEST >> To: pharo-users(a)lists.pharo.org >> Reply-To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> >> >> Dear Pharo users, >> >> I have submitted a proposal for a presentation at ESUGâ23. Part of the presentation will report on the results of a survey about the usage of the Pharo system browser. I need your help to produce the results ð. Therefore I invite you to take the survey at https://forms.gle/cBYs7DRwZvAVAyQb9. It is not too long, and totally anonymous. Your feedback is very much appreciated! >> >> Thanks in advance. >> >> Kind regards, >> Koen >> >> PS: Maybe you wonder who this new kid on the block is. Actually, it is an old kid on the block. ð See https://all-objects-all-the-time.st <https://all-objects-all-the-time.st/> >> >

June 20, 2023

This week (24/2023) on the Pharo Issue Tracker

by Marcus Denker

This week (24/2023) on the Pharo Issue Tracker # Fixes - compilationContext is lazily initialise so the acessor should be used #13964 https://github.com/pharo-project/pharo/pull/13964 - [DrTest] removing a trace from within the presenter. #13997 https://github.com/pharo-project/pharo/pull/13997 - Handle single-sized collection in stdev method. #13999 https://github.com/pharo-project/pharo/pull/13999 - Modified the UUID class to use a primitive and added parsing options #13965 https://github.com/pharo-project/pharo/pull/13965 - move the extension methods of Spec to the class SHRBTextStyler #14011 https://github.com/pharo-project/pharo/pull/14011 - Update BaselineOfPharo.class.st with new Roassal Version #13995 https://github.com/pharo-project/pharo/pull/13995 - Add values and valuesDo: methods to FinalizationRegistry #14005 https://github.com/pharo-project/pharo/pull/14005 - 13387-Find-and-replace-dialog-close-gives-failure-when-Playground-is-already-closed #14031 https://github.com/pharo-project/pharo/pull/14031 - Fluid: show empty slots on the class side, too #14028 https://github.com/pharo-project/pharo/pull/14028 - Fix finder selection #14042 https://github.com/pharo-project/pharo/pull/14042 # UI / Scaling - Make initial extent of StSpotter and StInspector take the display scale factor into account #546 https://github.com/pharo-spec/NewTools/pull/546 - Make #extent in SpToolbarDisplayMode hierarchy take the display scale factor into account #1409 https://github.com/pharo-spec/Spec/pull/1409 - Make width constants in RubTextSegmentIconDisplayer take the display scale factor into account #13954 https://github.com/pharo-project/pharo/pull/13954 - Rework UITheme tree forms for better display scaling support #13987 https://github.com/pharo-project/pharo/pull/13987 - Make WorldState and ProfStef take the display scale factor into account for the world menu items with the #pharo icon #14023 https://github.com/pharo-project/pharo/pull/14023 - Make HaloMorph>>#handleSize take the display scale factor into account #14020 https://github.com/pharo-project/pharo/pull/14020 - Change colors of the âgrabâ and ârotateâ halo morph handles for better contrast with their icons #14021 https://github.com/pharo-project/pharo/pull/14021 - Fix #menuBorderWidth display scaling #14022 https://github.com/pharo-project/pharo/pull/14022 # RPackage - Rename packages announcements #13970 https://github.com/pharo-project/pharo/pull/13970 - Remove announcement registration doing nothing #14019 https://github.com/pharo-project/pharo/pull/14019 - Improve RPackageOrganizer>>ensureExistAndRegisterPackageNamed: #14018 https://github.com/pharo-project/pharo/pull/14018 - Remove RPackageOrganizer package name cache #14026 https://github.com/pharo-project/pharo/pull/14026 - Reduce Monticello coupling in RPackage #14025 https://github.com/pharo-project/pharo/pull/14025 # Protocols / Categories - Ensure renaming of protocol announce the changes #13494 https://github.com/pharo-project/pharo/pull/13494 - Update the way we deal with protocols from other classes #13967 https://github.com/pharo-project/pharo/pull/13967 - Use more protocol object in RPackage #13768 https://github.com/pharo-project/pharo/pull/13768 - CompiledMethod>>protocol should return a protocol #13951 https://github.com/pharo-project/pharo/pull/13951 - Update some CompiledMethod>>#category senders #14035 https://github.com/pharo-project/pharo/pull/14035 # Refactorig Engine - Refactor: Move methods to class that only uses them #13956 https://github.com/pharo-project/pharo/pull/13956 - 13957--RBRefactoringonErrordo--should-accept-both-0-and-1-arg-block #13959 https://github.com/pharo-project/pharo/pull/13959 - fix 13903 RBReplaceMessageSendTransformation #13955 https://github.com/pharo-project/pharo/pull/13955 - Refact/clean #13960 https://github.com/pharo-project/pharo/pull/13960 - 13972 create a separate data for tests for rb1 and rb2 #13973 https://github.com/pharo-project/pharo/pull/13973 - Emh/merge t set up into class #13977 https://github.com/pharo-project/pharo/pull/13977 - Emh/failure in selector #13979 https://github.com/pharo-project/pharo/pull/13979 - Removing RBDummyCLass and subclasses - all tests green #13980 https://github.com/pharo-project/pharo/pull/13980 - removing spurious class compilation and logging in Epicea in RBRefactâ¦ #13992 https://github.com/pharo-project/pharo/pull/13992 - Clean redundant preconditions by defining a common supercase. #14006 https://github.com/pharo-project/pharo/pull/14006 - first fix some release test and may be a test is readded by the tests #14013 https://github.com/pharo-project/pharo/pull/14013 - adding comments, better tests #14037 https://github.com/pharo-project/pharo/pull/14037 # Bootstrap - Move Color startup registration #13929 https://github.com/pharo-project/pharo/pull/13929 # Tests - 13942-TraitCompositionTesttestAliasCompositions--passes-but-for-the-wrong-reason #13961 https://github.com/pharo-project/pharo/pull/13961 - Simplify Metacello testing #13996 https://github.com/pharo-project/pharo/pull/13996 - MetacelloPharoCommonPlatform>>#suspendSystemUpdateEventsDuring: should use #suspendAllWhile: #14009 https://github.com/pharo-project/pharo/pull/14009 - Fix broken release tests + improve a test #14015 https://github.com/pharo-project/pharo/pull/14015 - Clean manifest builder test and cut dependency to Monticello #14012 https://github.com/pharo-project/pharo/pull/14012 - Do not poluate Monticello cache in tests #14046 https://github.com/pharo-project/pharo/pull/14046 # Cleanup: selectors send but not implemented - add more #ignoreNotImplementedSelectors: tags #14007 https://github.com/pharo-project/pharo/pull/14007 - 13988-two-senders-of-finalizeValues-in-WeakKeyDictionaryTest-class #14003 https://github.com/pharo-project/pharo/pull/14003 - tag-more-ignoreNotImplementedSelectors-06-12 #14004 https://github.com/pharo-project/pharo/pull/14004 - ReSendsUnknownMessageToGlobalRule and #ignoreNotImplementedSelectors: #13963 https://github.com/pharo-project/pharo/pull/13963 - Tag-ignoreNotImplementedSelectors-06-09 #13962 https://github.com/pharo-project/pharo/pull/13962 - Cleanup CDNode Hierarchy: #acceptVisitor: #14032 https://github.com/pharo-project/pharo/pull/14032 - add more #ignoreNotImplementedSelectors: #548 https://github.com/pharo-spec/NewTools/pull/548 # Cleanups - Renamed method StInspectorTransmissionNode>>#transmissionBlock: #547 https://github.com/pharo-spec/NewTools/pull/547 - SHRBTextStyler-simplify-stylehandling #14027 https://github.com/pharo-project/pharo/pull/14027 - fix and move SHRBTextStyler #1413 https://github.com/pharo-spec/Spec/pull/1413 - Remove some unecessary packages #14029 https://github.com/pharo-project/pharo/pull/14029 - Remove empty packages #13969 https://github.com/pharo-project/pharo/pull/13969 - Remove unloaded deprecated packages #14043 https://github.com/pharo-project/pharo/pull/14043

June 16, 2023