October 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] How to add a trait to a class from an external package?

by Yuriy Tymchuk

By the way, this is an interesting conceptual question. Because couple of times Iâve encountered this problem that I had to extend different entities with the same methods, which results in duplication. Uko > On 27 Oct 2014, at 11:31, Max Leske <maxleske(a)gmail.com> wrote: > >> >> On 27.10.2014, at 11:27, phil(a)highoctane.be <mailto:phil@highoctane.be> wrote: >> >> On Mon, Oct 27, 2014 at 11:18 AM, Max Leske <maxleske(a)gmail.com <mailto:maxleske@gmail.com>> wrote: >> >> > On 27.10.2014, at 11:16, phil(a)highoctane.be <mailto:phil@highoctane.be> wrote: >> > >> > I have a TCXTBSButton trait that I want to add to a couple of WA classes. >> > >> > Now, I do not want to touch the WA classes as it would mean that I have to maintain them on my own, which isn't good. >> > >> > So, how do I add a trait to a class without changing its code? >> > Programmatically adding a trait to a class on package/configuration load. >> > >> > For methods, I can do a *myownpackage so that things will be saved there. >> > >> > But for traits, I do not know how. >> > >> > Help :-) >> >> I donât think thereâs any other option than doing a postload and recompiling those classes. Obviously, the packages of those classes will become dirty. >> >> Annoying. I do not want them dirty. >> >> In the meantime, I have subclassed the TagBrush I need and added the trait there. >> But that's a pain for all other features that do use the superclass as such. >> >> Phil > > If youâre adventurous you could maybe copy the methods from the trait to the classes and classify them as extensions of your package. Then at least only your package would be dirtyâ¦ > > But yeah, not very nice... > >> >> >> > >> > Phil

Oct. 27, 2014

Re: [Pharo-dev] How to add a trait to a class from an external package?

by Max Leske

> On 27.10.2014, at 11:27, phil(a)highoctane.be wrote: > > On Mon, Oct 27, 2014 at 11:18 AM, Max Leske <maxleske(a)gmail.com <mailto:maxleske@gmail.com>> wrote: > > > On 27.10.2014, at 11:16, phil(a)highoctane.be <mailto:phil@highoctane.be> wrote: > > > > I have a TCXTBSButton trait that I want to add to a couple of WA classes. > > > > Now, I do not want to touch the WA classes as it would mean that I have to maintain them on my own, which isn't good. > > > > So, how do I add a trait to a class without changing its code? > > Programmatically adding a trait to a class on package/configuration load. > > > > For methods, I can do a *myownpackage so that things will be saved there. > > > > But for traits, I do not know how. > > > > Help :-) > > I donât think thereâs any other option than doing a postload and recompiling those classes. Obviously, the packages of those classes will become dirty. > > Annoying. I do not want them dirty. > > In the meantime, I have subclassed the TagBrush I need and added the trait there. > But that's a pain for all other features that do use the superclass as such. > > Phil If youâre adventurous you could maybe copy the methods from the trait to the classes and classify them as extensions of your package. Then at least only your package would be dirtyâ¦ But yeah, not very nice... > > > > > > Phil

Oct. 27, 2014

Re: [Pharo-dev] How to add a trait to a class from an external package?

by phil＠highoctane.be

On Mon, Oct 27, 2014 at 11:18 AM, Max Leske <maxleske(a)gmail.com> wrote: > > > On 27.10.2014, at 11:16, phil(a)highoctane.be wrote: > > > > I have a TCXTBSButton trait that I want to add to a couple of WA classes. > > > > Now, I do not want to touch the WA classes as it would mean that I have > to maintain them on my own, which isn't good. > > > > So, how do I add a trait to a class without changing its code? > > Programmatically adding a trait to a class on package/configuration load. > > > > For methods, I can do a *myownpackage so that things will be saved there. > > > > But for traits, I do not know how. > > > > Help :-) > > I donât think thereâs any other option than doing a postload and > recompiling those classes. Obviously, the packages of those classes will > become dirty. > Annoying. I do not want them dirty. In the meantime, I have subclassed the TagBrush I need and added the trait there. But that's a pain for all other features that do use the superclass as such. Phil > > > > > Phil > > >

Oct. 27, 2014

Re: [Pharo-dev] How to add a trait to a class from an external package?

by Max Leske

> On 27.10.2014, at 11:16, phil(a)highoctane.be wrote: > > I have a TCXTBSButton trait that I want to add to a couple of WA classes. > > Now, I do not want to touch the WA classes as it would mean that I have to maintain them on my own, which isn't good. > > So, how do I add a trait to a class without changing its code? > Programmatically adding a trait to a class on package/configuration load. > > For methods, I can do a *myownpackage so that things will be saved there. > > But for traits, I do not know how. > > Help :-) I donât think thereâs any other option than doing a postload and recompiling those classes. Obviously, the packages of those classes will become dirty. > > Phil

Oct. 27, 2014

How to add a trait to a class from an external package?

by phil＠highoctane.be

I have a TCXTBSButton trait that I want to add to a couple of WA classes. Now, I do not want to touch the WA classes as it would mean that I have to maintain them on my own, which isn't good. So, how do I add a trait to a class without changing its code? Programmatically adding a trait to a class on package/configuration load. For methods, I can do a *myownpackage so that things will be saved there. But for traits, I do not know how. Help :-) Phil

Oct. 27, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40329 Home: https://github.com/pharo-project/pharo-core

Oct. 27, 2014

[pharo-project/pharo-core] 180a19: 40329

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 180a19f80caa0398b6a8eecb9b7bb87241b09a02 https://github.com/pharo-project/pharo-core/commit/180a19f80caa0398b6a8eecb… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-10-27 (Mon, 27 Oct 2014) Changed paths: M Monticello.package/MCClassDefinition.class/instance/installing/createClass.st M Monticello.package/MCTraitDefinition.class/instance/visiting/createClass.st R Network-Kernel.package/Socket.class/class/examples/timeTest.st R Network-Kernel.package/Socket.class/class/examples/timeTestUDP.st R Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/accessing/windowActiveDropShadowStyle_.st R Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/as yet unclassified/scrollbarPressedThumbFillStyleFor_.st R Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/basic-colors/treeLineWidth.st R Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/border-styles-buttons/buttonSelectedBorderStyleFor_.st A Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/border-styles-scrollbars/scrollbarPressedThumbFillStyleFor_.st R Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/border-styles-scrollbars/scrollbarThumbCornerStyleIn_.st R Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/defaults/buttonMinHeight.st R Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/defaults/buttonMinWidth.st R Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/fill-styles/resizerGripNormalFillStyleFor_.st R Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/growl - specific/growlContentsColorFor_.st R Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/initialize-release/newTreeExpandedForm.st R Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/initialize-release/newTreeUnexpandedForm.st R Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/initialize-release/newWindowInactiveControlForm.st R Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/label-styles/createCollapseBoxFor_.st R Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/label-styles/createExpandBoxFor_.st R Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/label-styles/windowCloseOverForm.st R Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/label-styles/windowMaximizeOverForm.st R Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/label-styles/windowMinimizeOverForm.st R Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/morph creation/newCloseControlIn_for_action_help_.st R Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/scrollbars/verticesForSimpleArrow_.st R Polymorph-Widgets.package/Pharo3Theme.class/instance/accessing/windowActiveDropShadowStyle_.st R Polymorph-Widgets.package/Pharo3Theme.class/instance/basic-colors/treeLineWidth.st R Polymorph-Widgets.package/Pharo3Theme.class/instance/border-styles-buttons/buttonSelectedBorderStyleFor_.st R Polymorph-Widgets.package/Pharo3Theme.class/instance/border-styles-scrollbars/scrollbarThumbCornerStyleIn_.st R Polymorph-Widgets.package/Pharo3Theme.class/instance/defaults/buttonMinHeight.st R Polymorph-Widgets.package/Pharo3Theme.class/instance/defaults/buttonMinWidth.st R Polymorph-Widgets.package/Pharo3Theme.class/instance/fill-styles/resizerGripNormalFillStyleFor_.st R Polymorph-Widgets.package/Pharo3Theme.class/instance/growl - specific/growlContentsColorFor_.st R Polymorph-Widgets.package/Pharo3Theme.class/instance/initialize-release/initialize.st R Polymorph-Widgets.package/Pharo3Theme.class/instance/initialize-release/newTreeExpandedForm.st R Polymorph-Widgets.package/Pharo3Theme.class/instance/initialize-release/newTreeUnexpandedForm.st R Polymorph-Widgets.package/Pharo3Theme.class/instance/initialize-release/newWindowInactiveControlForm.st R Polymorph-Widgets.package/Pharo3Theme.class/instance/label-styles/configureWindowLabelAreaFor_.st R Polymorph-Widgets.package/Pharo3Theme.class/instance/label-styles/createCollapseBoxFor_.st R Polymorph-Widgets.package/Pharo3Theme.class/instance/label-styles/createExpandBoxFor_.st R Polymorph-Widgets.package/Pharo3Theme.class/instance/label-styles/windowCloseOverForm.st R Polymorph-Widgets.package/Pharo3Theme.class/instance/label-styles/windowMaximizeOverForm.st R Polymorph-Widgets.package/Pharo3Theme.class/instance/label-styles/windowMinimizeOverForm.st R Polymorph-Widgets.package/Pharo3Theme.class/instance/morph creation/newCloseControlIn_for_action_help_.st R Polymorph-Widgets.package/Pharo3Theme.class/instance/scrollbars/verticesForSimpleArrow_.st R Polymorph-Widgets.package/PharoUIThemeIcons.class/instance/private - contents/windowCloseFormContents.st R Polymorph-Widgets.package/PharoUIThemeIcons.class/instance/private - contents/windowMaximizeFormContents.st M Polymorph-Widgets.package/TextHighlightByBounds.class/instance/drawing/drawOn_in_offset_.st M Polymorph-Widgets.package/ThemeSettings.class/definition.st M Polymorph-Widgets.package/TickSelectionListNode.class/definition.st M RPackage-Tests.package/RPackageClassesSynchronisationTest.class/instance/tests - recategorizing class/testRecategorizeClassRaisesClassRepackagedEvent.st M RPackage-Tests.package/RPackageMCSynchronisationTest.class/instance/to move to a simple RPackage test case/testNotRepackagedAnnouncementWhenModifyMethodByMovingInSameExtensionCategory.st M RPackage-Tests.package/RPackageMCSynchronisationTest.class/instance/to move to a simple RPackage test case/testNotRepackagedAnnouncementWhenMovingClassicCategories.st M RPackage-Tests.package/RPackageMCSynchronisationTest.class/instance/to move to a simple RPackage test case/testRepackagedAnnouncementWhenModifyMethodByMovingFromClassicCategoryToExtensionCategory.st M RPackage-Tests.package/RPackageMCSynchronisationTest.class/instance/to move to a simple RPackage test case/testRepackagedAnnouncementWhenModifyMethodByMovingFromDifferentExtensionCategories.st M RPackage-Tests.package/RPackageMCSynchronisationTest.class/instance/to move to a simple RPackage test case/testRepackagedAnnouncementWhenModifyMethodByMovingFromExtensionCategoryToClassicCategory.st M RPackage-Tests.package/RPackageObsoleteTest.class/instance/tests/testAnnouncementClassRemovedIsRaisedOnRemoveFromSystem.st M RPackage-Tests.package/RPackageTest.class/instance/tests/testAddClass.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script329.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40329.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40329 14323 Replace Announcer>>#on:send:to:s senders in RPackage-Tests https://pharo.fogbugz.com/f/cases/14323 14274 Socket timeTestUDP fails https://pharo.fogbugz.com/f/cases/14274 14320 Small clean in Polymorph https://pharo.fogbugz.com/f/cases/14320 5139 Monticello uses the wrong compiler for class and trait definitions https://pharo.fogbugz.com/f/cases/5139 http://files.pharo.org/image/40/40329.zip

Oct. 27, 2014

Re: [Pharo-dev] Way to embed efficiently data?

by phil＠highoctane.be

I've seen a couple configurations retrieve tar files from DropBox. http://www.smalltalkhub.com/#!/~hernan/ApplicationSecurity loads NaCl library (libsodium) from Dropbox. See ConfigurationOfNacl>>preLoad | url fileRef response | url := self platformLibraryUrl asZnUrl. fileRef := FileSystem disk workingDirectory / url pathSegments last. (response := ZnEasy get: url) isSuccess ifTrue: [ fileRef writeStreamDo: [ : stream | stream nextPutAll: response contents ] ] ifFalse: [ self error: 'Cannot download compiled library file' ]. self uncompress: fileRef. platformLibraryUrl " Answer a download URL for the compiled version of library " Smalltalk os isWin32 ifTrue: [ ^ 'http://dl.dropboxusercontent.com/u/103833630/libsodium.zip' ]. Smalltalk os isUnix ifTrue: [ ^ 'http://dl.dropboxusercontent.com/u/103833630/libsodium.so.gz' ]. Smalltalk os isMacOSX ifTrue: [ ^ 'http://dl.dropboxusercontent.com/u/103833630/libsodium.dylib.gz' ]. self error: 'Cannot find library for your OS platform'. It looks like a good way to solve these things. Forget about Dropbox versioning. But with a proper naming scheme, it is doable. Phil On Mon, Oct 27, 2014 at 1:40 AM, Sebastian Sastre < sebastian(a)flowingconcept.com> wrote: > > > On Oct 26, 2014, at 9:22 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> > wrote: > > > > 2014-10-26 20:14 GMT-03:00 Sebastian Sastre < > sebastian(a)flowingconcept.com>: > >> I donât think that storing binary files in git is good practice > >> > >> git shines on declarative content > >> > >> But Google about it and see how other people experiences resulted. Are > they happy or not? > > > > It's not efficient in terms of storage, but I know of people who uses > > git to manage PSD files and other "non code" files. > > > > I'm particularly interested in git for Pharo for the same reason, I > > want to be able to commit everything (Pharo and static files) in a > > single command. > > Well, then you should use that in the exact same way you would commit in > one command entire VirtualBox guests VMs > > git is a tool suposed to help in integrating work and not make your life > too hard when solving merge conflicts when they happen. If you do things > that diverge from that then, well.. then you start eroding the profit itâs > trying to give you > > > > > Esteban A. Maringolo > > > > >

Oct. 27, 2014

Re: [Pharo-dev] Way to embed efficiently data?

by Sebastian Sastre

> On Oct 26, 2014, at 9:22 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > > 2014-10-26 20:14 GMT-03:00 Sebastian Sastre <sebastian(a)flowingconcept.com>: >> I donât think that storing binary files in git is good practice >> >> git shines on declarative content >> >> But Google about it and see how other people experiences resulted. Are they happy or not? > > It's not efficient in terms of storage, but I know of people who uses > git to manage PSD files and other "non code" files. > > I'm particularly interested in git for Pharo for the same reason, I > want to be able to commit everything (Pharo and static files) in a > single command. Well, then you should use that in the exact same way you would commit in one command entire VirtualBox guests VMs git is a tool suposed to help in integrating work and not make your life too hard when solving merge conflicts when they happen. If you do things that diverge from that then, well.. then you start eroding the profit itâs trying to give you > > Esteban A. Maringolo >

Oct. 27, 2014

Re: [Pharo-dev] Way to embed efficiently data?

by Esteban A. Maringolo

2014-10-26 20:14 GMT-03:00 Sebastian Sastre <sebastian(a)flowingconcept.com>: > I donât think that storing binary files in git is good practice > > git shines on declarative content > > But Google about it and see how other people experiences resulted. Are they happy or not? It's not efficient in terms of storage, but I know of people who uses git to manage PSD files and other "non code" files. I'm particularly interested in git for Pharo for the same reason, I want to be able to commit everything (Pharo and static files) in a single command. Esteban A. Maringolo

Oct. 26, 2014