Pharo-users

By thread

pharo-users@lists.pharo.org

50345 messages

UKSTUG meeting (*with corrected links*) - Christian Haider: How values make systems simpler - 25 Sep 2024 @ 7pm BST

by UK Smalltalk

Distinguishing between stateful Objects and Values has long been recognized as fruitful. Values are universal context-free abstractions that prevent side effects and allow for a functional programming style. Though programming languages provide simple Values like Integer and String, more complex Values are usually not supported. We show how to model complex structures as Values in Smalltalk, which allows for a simple and versatile implementation. The resulting Smalltalk systems are simple, clear and easily testable. Christian Haider [1] is the author of the PDFtalk library [2] used in smallCharts [3] and other projects. Underlying is a simple implementation of Values [4] which he uses extensively. Christian will show how Values make systems simpler and easier. Examples for some uses and the limits of the approach will be discussed. Since Values use only standard Smalltalk features, it can be used in most other Smalltalks. All of this code is available with MIT licence. This will be an online meeting from home. If you'd like to join us, please sign up in advance on: https://www.meetup.com/ukstug/events/302453141 [1] https://christianhaider.de/index_en.html [2] https://pdftalk.de/doku.php [3] https://smallcharts.de/english/ [4] https://pdftalk.de/doku.php?id=complexvalues

Sept. 23, 2024

Re: Pharo 12 and instanceVariables

by Herve Verjus

Great! ð Herve Sep 22, 2024 22:11:55 stephane ducasse <stephane.ducasse(a)inria.fr>: > > https://github.com/pharo-project/pharo/pull/17151Â with less typos :) > > > > > >> On 22 Sep 2024, at 22:01, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: >> >> Thanks for your question. >> I will add the following to the doc folder :) >> >> <fluid.pdf> > > 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 > > > > >

Sept. 22, 2024

Re: Pharo 12 and instanceVariables

by stephane ducasse

https://github.com/pharo-project/pharo/pull/17151 with less typos :) > On 22 Sep 2024, at 22:01, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: > > Thanks for your question. > I will add the following to the doc folder :) > > <fluid.pdf> 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

Sept. 22, 2024

Re: Pharo 12 and instanceVariables

by stephane ducasse

Thanks for your question. I will add the following to the doc folder :)

Sept. 22, 2024

Re: Pharo 12 and instanceVariables

by Herve Verjus

Hello Steph, many thanks. It's now clear I think ð. My first understanding considering slots as objects representing instance variables wasn't bad. I wasn't sure because I was reading something to not consider slots as instance vars. Your answer lights me a lot ð. HVE Sep 22, 2024 19:18:24 stephane ducasse <stephane.ducasse(a)inria.fr>: > Hello Herve > > I will add a description in the doc/ folder in P13 and may be P12. > > If you need you can bring the menu on the class definition (put the caret on the class name) and select expand and you will see all the definition possibilities.Â > > > [cid:0A8FCA81-F1A9-490A-B051-8DE6F56A4E00][Capture 2024-09-22 at 19.06.35.png][cid:0A8FCA81-F1A9-490A-B051-8DE6F56A4E00][cid:EAC3AD2D-8376-429F-A59C-EE02E4ED5275][Capture 2024-09-22 at 19.06.44.png][cid:EAC3AD2D-8376-429F-A59C-EE02E4ED5275] > > > > - layout: is for the different class formats > > For exampleÂ > ArrayedCollection << #Array > layout: VariableLayout; > tag: 'Base'; > package: 'Collections-Sequenceableâ > > is the same asÂ > > ArrayedCollection variableSubclass: #Array > instanceVariableNames: '' > classVariableNames: '' > package: 'Collections-Sequenceable-Base' > > - traits: Â for traits > > > For the rest, consider that this is the same with different names (because slots are compatible with instance variables). > > SoÂ > > Object << #Point > slots: { #x . #y }; > tag: 'BasicObjects'; > package: âKernel' > > is the same as > > Object subclass: #Point > instanceVariableNames: 'x y' > classVariableNames: '' > package: 'Kernel-BasicObjectsâ > > > andÂ > > WeakIdentityKeyDictionary << #ASTCache > sharedVariables: { #CacheMissStrategy }; > tag: 'Parser'; > package: 'AST-Core' > > is the same asÂ > > WeakIdentityKeyDictionary subclass: #ASTCache > instanceVariableNames: '' > classVariableNames: 'CacheMissStrategy' > package: 'AST-Core-Parser' > > > What you see is that we do not have to specify empty lists :) > > The only mandatary information is the class name and the package > > Object << #Foo > package: âMyPackageâ > > is a nice class definition. > > The template show empty slots: {}; but this is not needed this is because some people do not like that type of slots: { }; > > > BTW we use the new syntax in the Advanced Design Mooc and I started to migrate books too (not Pharo by Example because it is a big amount of work).Â > > > Tell us if this is clear for you.Â > I plan to change the slides of the Pharo mooc (Iâm currently converting them to use a nice slide syntax)Â > to use the fluid syntax.Â > >> >> Hi Everybody, >> >> I try to be up-to-date with Pharo trends and releases. In Pharo 12, we are switching to use fluid class declaration. Its' not easy to find stuffs illustrating fluid API. I have spend many hours to browse Pharo documentation, Github repos, slides, MOOcs, books, papers finding a way to clearly explain this "new way" of declaring a class. All Pharo introduction resources and Pharo 12 videos do not use fluid class declaration but the "old" way. I also use (and let's say teach) Pharo in my OOP lectures ð > > If you have links please send them and we will convert them.Â > > >> If I'm not wrong, the fluid class declaration does no more explicitly deal with instance (and class) variables. Instead, it deals now with slots, tags, shared variables, traits,...At a fist look, I was understanding that slots was a dynamic way to declare instance variables. > > A Slot is first an object representing an instance variable.Â > Now by default the programmer should use a symbolÂ > so you go from > > âx yâ to {#x . #y} > > This syntax let us write more complex class definitions such as > > SpPresenter << #SpDialogPresenter > slots: { > #parentWindow => WeakSlot . > #acceptAction . > #cancelAction . > #image }; > package: 'Spec2-Dialogs' > > here #parentWindow => WeakSlot creates a slot of the class WeakSlot (does not count for garbage collector) > > >> After reading some pieces of paper, and if I'm not wrong , slots are not really instance variables and shared variables are not class variables. >> >> Avoiding the old class declaration, i.e. >> >> Â Â Â Â Â Object subclass #SomeClassName instanceVariableNames: 'instaVar1 instVar2 ...' ... >> >> is there a simple way to add an instance (or class) variable? > > you use slots: { Â . Â }; > andÂ > > sharedVariables: are for classVarNames:Â > This is because sharedVariables are shared between the instance and class side > and like that we do not have the confusion ofÂ > class variables and metaclass instance variables.Â > > > > > For example TextConstants defines the following sharedVariables: > > SharedPool << #TextConstants > slots: {}; > sharedVariables: { #Ctrls . #Ctrlh . #CtrlR . #CtrlG . #DefaultMarginTabsArray . #Ctrlx . #Ctrlm . #Ctrlb . #BS . #CtrlL . #CtrlA . #CtrlW . #DefaultRule . #DefaultFontFamilySize . #Ctrlr . #Ctrlg . #CtrlQ . #EndOfRun . #CtrlF . #Italic . #Basal . #Ctrlw . #Ctrll . #Ctrla . #CtrlV . #CtrlK . #Bold . #Justified . #Ctrlf . #Ctrlq . #CtrlP . #CtrlE . #LeftMarginTab . #CtrlOpenBrackets . #DefaultSpace . #Ctrlv . #Ctrlk . #CtrlU . #CtrlJ . #Ctrlp . #Ctrle . #CtrlZ . #CtrlO . #CtrlD . #DefaultBaseline . #CrossedX . #LeftFlush . #Space . #Ctrlj . #CtrlT . #CtrlI . #RightFlush . #DefaultTab . #Ctrlu . #Centered . #Ctrlz . #Ctrlo . #Ctrld . #CtrlY . #CtrlN . #CtrlC . #Enter . #DefaultLineGrid . #ESC . #Ctrlt . #Ctrli . #CtrlS . #CtrlH . #Clear . #CR . #CtrlDigits . #DefaultMask . #Ctrln . #Ctrlc . #RightMarginTab . #CtrlM . #CtrlX . #BS2 . #Tab . #TextSharedInformation . #DefaultTabsArray . #Ctrly . #CtrlB }; > tag: 'Base'; > package: 'Text-Core' > > > ArrayedCollection subclass: #Text > instanceVariableNames: 'string runs' > classVariableNames: '' > poolDictionaries: 'TextConstants' > package: 'Text-Core-Base' > > is now > > ArrayedCollection << #Text > slots: { #string . #runs }; > sharedPools: { TextConstants }; > tag: 'Base'; > package: 'Text-Core' > > Because this is years that poolDictionaries do not exist anymore (they have SharedPool e.g. a special class holding sharedVariables) > >> Are instance variables gone in Pharo? I assume I missed something, but what? > > No just empowered and backwards compatible.Â > > >> >> Many thanks. Cheers, >> >> Herve > > 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 > > > > >

Sept. 22, 2024

Re: Pharo 12 and instanceVariables

by stephane ducasse

Hello Herve I will add a description in the doc/ folder in P13 and may be P12. If you need you can bring the menu on the class definition (put the caret on the class name) and select expand and you will see all the definition possibilities. ï¿¼ï¿¼ - layout: is for the different class formats For example ArrayedCollection << #Array layout: VariableLayout; tag: 'Base'; package: 'Collections-Sequenceableâ is the same as ArrayedCollection variableSubclass: #Array instanceVariableNames: '' classVariableNames: '' package: 'Collections-Sequenceable-Base' - traits: for traits For the rest, consider that this is the same with different names (because slots are compatible with instance variables). So Object << #Point slots: { #x . #y }; tag: 'BasicObjects'; package: âKernel' is the same as Object subclass: #Point instanceVariableNames: 'x y' classVariableNames: '' package: 'Kernel-BasicObjectsâ and WeakIdentityKeyDictionary << #ASTCache sharedVariables: { #CacheMissStrategy }; tag: 'Parser'; package: 'AST-Core' is the same as WeakIdentityKeyDictionary subclass: #ASTCache instanceVariableNames: '' classVariableNames: 'CacheMissStrategy' package: 'AST-Core-Parser' What you see is that we do not have to specify empty lists :) The only mandatary information is the class name and the package Object << #Foo package: âMyPackageâ is a nice class definition. The template show empty slots: {}; but this is not needed this is because some people do not like that type of slots: { }; BTW we use the new syntax in the Advanced Design Mooc and I started to migrate books too (not Pharo by Example because it is a big amount of work). Tell us if this is clear for you. I plan to change the slides of the Pharo mooc (Iâm currently converting them to use a nice slide syntax) to use the fluid syntax. > > Hi Everybody, > > I try to be up-to-date with Pharo trends and releases. In Pharo 12, we are switching to use fluid class declaration. Its' not easy to find stuffs illustrating fluid API. I have spend many hours to browse Pharo documentation, Github repos, slides, MOOcs, books, papers finding a way to clearly explain this "new way" of declaring a class. All Pharo introduction resources and Pharo 12 videos do not use fluid class declaration but the "old" way. I also use (and let's say teach) Pharo in my OOP lectures ð If you have links please send them and we will convert them. > If I'm not wrong, the fluid class declaration does no more explicitly deal with instance (and class) variables. Instead, it deals now with slots, tags, shared variables, traits,...At a fist look, I was understanding that slots was a dynamic way to declare instance variables. A Slot is first an object representing an instance variable. Now by default the programmer should use a symbol so you go from âx yâ to {#x . #y} This syntax let us write more complex class definitions such as SpPresenter << #SpDialogPresenter slots: { #parentWindow => WeakSlot . #acceptAction . #cancelAction . #image }; package: 'Spec2-Dialogs' here #parentWindow => WeakSlot creates a slot of the class WeakSlot (does not count for garbage collector) > After reading some pieces of paper, and if I'm not wrong , slots are not really instance variables and shared variables are not class variables. > > Avoiding the old class declaration, i.e. > > Object subclass #SomeClassName instanceVariableNames: 'instaVar1 instVar2 ...' ... > > is there a simple way to add an instance (or class) variable? you use slots: { . }; and sharedVariables: are for classVarNames: This is because sharedVariables are shared between the instance and class side and like that we do not have the confusion of class variables and metaclass instance variables. For example TextConstants defines the following sharedVariables: SharedPool << #TextConstants slots: {}; sharedVariables: { #Ctrls . #Ctrlh . #CtrlR . #CtrlG . #DefaultMarginTabsArray . #Ctrlx . #Ctrlm . #Ctrlb . #BS . #CtrlL . #CtrlA . #CtrlW . #DefaultRule . #DefaultFontFamilySize . #Ctrlr . #Ctrlg . #CtrlQ . #EndOfRun . #CtrlF . #Italic . #Basal . #Ctrlw . #Ctrll . #Ctrla . #CtrlV . #CtrlK . #Bold . #Justified . #Ctrlf . #Ctrlq . #CtrlP . #CtrlE . #LeftMarginTab . #CtrlOpenBrackets . #DefaultSpace . #Ctrlv . #Ctrlk . #CtrlU . #CtrlJ . #Ctrlp . #Ctrle . #CtrlZ . #CtrlO . #CtrlD . #DefaultBaseline . #CrossedX . #LeftFlush . #Space . #Ctrlj . #CtrlT . #CtrlI . #RightFlush . #DefaultTab . #Ctrlu . #Centered . #Ctrlz . #Ctrlo . #Ctrld . #CtrlY . #CtrlN . #CtrlC . #Enter . #DefaultLineGrid . #ESC . #Ctrlt . #Ctrli . #CtrlS . #CtrlH . #Clear . #CR . #CtrlDigits . #DefaultMask . #Ctrln . #Ctrlc . #RightMarginTab . #CtrlM . #CtrlX . #BS2 . #Tab . #TextSharedInformation . #DefaultTabsArray . #Ctrly . #CtrlB }; tag: 'Base'; package: 'Text-Core' ArrayedCollection subclass: #Text instanceVariableNames: 'string runs' classVariableNames: '' poolDictionaries: 'TextConstants' package: 'Text-Core-Base' is now ArrayedCollection << #Text slots: { #string . #runs }; sharedPools: { TextConstants }; tag: 'Base'; package: 'Text-Core' Because this is years that poolDictionaries do not exist anymore (they have SharedPool e.g. a special class holding sharedVariables) > Are instance variables gone in Pharo? I assume I missed something, but what? No just empowered and backwards compatible. > > Many thanks. Cheers, > > Herve 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

Sept. 22, 2024

Pharo 12 and instanceVariables

by Herve Verjus

Hi Everybody, I try to be up-to-date with Pharo trends and releases. In Pharo 12, we are switching to use fluid class declaration. Its' not easy to find stuffs illustrating fluid API. I have spend many hours to browse Pharo documentation, Github repos, slides, MOOcs, books, papers finding a way to clearly explain this "new way" of declaring a class. All Pharo introduction resources and Pharo 12 videos do not use fluid class declaration but the "old" way. I also use (and let's say teach) Pharo in my OOP lectures ð If I'm not wrong, the fluid class declaration does no more explicitly deal with instance (and class) variables. Instead, it deals now with slots, tags, shared variables, traits,...At a fist look, I was understanding that slots was a dynamic way to declare instance variables. After reading some pieces of paper, and if I'm not wrong , slots are not really instance variables and shared variables are not class variables. Avoiding the old class declaration, i.e. Â Â Â Â Â Object subclass #SomeClassName instanceVariableNames: 'instaVar1 instVar2 ...' ... is there a simple way to add an instance (or class) variable? Are instance variables gone in Pharo? I assume I missed something, but what? Many thanks. Cheers, Herve

Sept. 22, 2024

Smalltalk Meetup in Zurich, 18 October 2024

by Peter Ursprung

Hi all, We are organizing the next Smalltalk Meetup in Zurich, Switzerland. It will be on Friday, 18 October 2024, starting at 18:00. We will meet in a meeting room where we will have short Smalltalk talks, then we will go to a nearby restaurant. If you are interested, please register on this website by Friday, 11 October 2024: https://zurich.smalltalk.world <https://zurich.smalltalk.world> We are still looking for presentations: if you have something interesting to show, please mention it in the registration. Regards, Peter

Sept. 13, 2024

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

by Marcus Denker

# Pharo 12 - 17093-Backport-17090-Wrong-compilation-to-ConstantBlockClosure #17095 https://github.com/pharo-project/pharo/pull/17095 # VM - initialize stack pages during simulation #853 https://github.com/pharo-project/pharo-vm/pull/853 - Forward porting p10 p12 #851 https://github.com/pharo-project/pharo-vm/pull/851 # Feature - Added open method to AndreasProfiler #835 https://github.com/pharo-spec/NewTools/pull/835 # Fixes - Fix drag detection in MouseClickState to take changes to the client morphâs transform into account #17019 https://github.com/pharo-project/pharo/pull/17019 - 17090-Wrong-compilation-to-ConstantBlockClosure #17094 https://github.com/pharo-project/pharo/pull/17094 - Make implementors of #transferFrom:event: add #shouldCopy from the TransferMorph to the SpDragAndDropTransfer #1588 https://github.com/pharo-spec/Spec/pull/1588 - Add log on recategorization with nil old protocol #17086 https://github.com/pharo-project/pharo/pull/17086 - Fix adapter tests, that should access the widget via the adapter, not directly. #1599 https://github.com/pharo-spec/Spec/pull/1599 # Refactoring - [Refactoring] Fix Duplicate + browse class -> raises Error #17085 https://github.com/pharo-project/pharo/pull/17085 # Settings - Add setting browser tabs #834 https://github.com/pharo-spec/NewTools/pull/834 - Minor fixes and convenience methods to debug settings #17082 https://github.com/pharo-project/pharo/pull/17082 # Cleanup - Renraku should not use old icon names #17096 https://github.com/pharo-project/pharo/pull/17096 - Cleanup metacello spec resolution #17076 https://github.com/pharo-project/pharo/pull/17076

Sept. 13, 2024

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

by Marcus Denker

# Pharo 12 - Upgrade iceberg to v2.3.2 #17069 https://github.com/pharo-project/pharo/pull/17069 # VM - Update SDL2 version in OSX (Intel & Apple) #849 https://github.com/pharo-project/pharo-vm/pull/849 - Adding option for pin behaviour #844 https://github.com/pharo-project/pharo-vm/pull/844 # Features - Add SocketAddressInformation for IPv6 support #16879 https://github.com/pharo-project/pharo/pull/16879 - 17035-Adding-VM-parameter-for-Pin-behaviour #17036 https://github.com/pharo-project/pharo/pull/17036 - Add Icons Pack Manager UI #17057 https://github.com/pharo-project/pharo/pull/17057 - Just add the menu to load Bloc and Toplo that was present in Pharo 12. #17048 https://github.com/pharo-project/pharo/pull/17048 # Fixes - 17033 Requesting references to globals in Calypso raises error #17039 https://github.com/pharo-project/pharo/pull/17039 - Update External Browser class definition access #1705 https://github.com/pharo-project/pharo/pull/17052 - Adapt #ensureWindowOpen on EDDisplayInterface to use of ScalingCanvas in OSWindowFormRenderer #17056 https://github.com/pharo-project/pharo/pull/17056 - Port froward:â¯Avoid rewriting methods that are not installed #17068 https://github.com/pharo-project/pharo/pull/17068 - Add #block accessor #17071 https://github.com/pharo-project/pharo/pull/17071 - fix faling test Spec2.Code.Tests.SpCodePresenterTest.testDoBrowseImplementors #1589 https://github.com/pharo-spec/Spec/pull/1589 - fix #1593 selectAll in SpAbstractTextPresenter is buggy #1594 https://github.com/pharo-spec/Spec/pull/1594 - Fix missing updates in File Browser file/directory name presenter #822 https://github.com/pharo-spec/NewTools/pull/822 - 826 Spotter should select the text when selection is set at opening #827 https://github.com/pharo-spec/NewTools/pull/827 - Speedup class search and minor fixes #829 https://github.com/pharo-spec/NewTools/pull/829 - Fix Autoscroll file tree presenter when opened #831 https://github.com/pharo-spec/NewTools/pull/831 # Rules - Fix the class comment of OverridesDeprecatedMethodRule #1705 https://github.com/pharo-project/pharo/pull/17051 - Fix some wrong rewritting of the ReCollectionProtocolRule #17047 https://github.com/pharo-project/pharo/pull/17047 - Fix false positive in ReGuardRule #17042 https://github.com/pharo-project/pharo/pull/17042 # Cleanup - fix #17037: DAPackageAnalyzerDiffTreePresenter uses old Spec method #17041 https://github.com/pharo-project/pharo/pull/17041 - Remove store:path:node: (broken and unused) #17049 https://github.com/pharo-project/pharo/pull/17049 - Moved refactoring stuff from SycSourceCodeCommand to SycSourceCodeRefactoringCommand #17054 https://github.com/pharo-project/pharo/pull/17054 - Keep renaming ASTâ¯nodes to start with AST instead of RB #17067 https://github.com/pharo-project/pharo/pull/17067 - Rename RBComment into ASTCommentNode #17040 https://github.com/pharo-project/pharo/pull/17040 - Remove refs to ChangesBrowser because it has been deprecated. #825 https://github.com/pharo-spec/NewTools/pull/825 - Clean unused TickDialogWindow #17065 https://github.com/pharo-project/pharo/pull/17065 - Fix Issue downloading icon packs #17061 https://github.com/pharo-project/pharo/pull/17061

Sept. 6, 2024

Jump to page: