- Pharo-dev - lists.pharo.org

[ Pharo 70 ] Build 46 PR 200 Space-analysis-resurrection
by Stephane Ducasse Aug. 20, 2017

Aug. 20, 2017

https://pharo.fogbugz.com/f/cases/20256/Latin1TextConverter-should-know-mon… https://github.com/pharo-project/pharo/pull/200

1 0

[ Pharo 70 ] Build 46 PR 200 Latin1TextConverter-should-know-mone-encoding-names
by Stephane Ducasse Aug. 20, 2017

Aug. 20, 2017

https://pharo.fogbugz.com/f/cases/20256/Latin1TextConverter-should-know-mon… https://github.com/pharo-project/pharo/pull/200

1 0

Github and Fogbugz integration
by Guillermo Polito Aug. 20, 2017

Aug. 20, 2017

Hi all, we just configured fogbugz and github integration as follows: http://help.fogcreek.com/8048/integration-with-git Quoting the instructions: 1. Now you can refer to your FogBugz cases in your GitHub commits (just add â*case <number>*â in the commit message) That will link your fogbugz issues to the commits on integration. Sadly, this just works for the integration of commits into the main branches, not pull requests. For pull request integration we will probably need a home made solution. Cheers, Guille et al -- Guille Polito Research Engineer French National Center for Scientific Research - *http://www.cnrs.fr* <http://www.cnrs.fr> *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

6 10

Ugly smell: really long symbols/selectors
by Guillermo Polito Aug. 19, 2017

Aug. 19, 2017

#'thisIsAVeryLongSelectorAndIfYoureHereWeHaveOnly49ImagineIHaveToWriteAllThisToArriveTo87ThenThisTo100' (ByteSymbol allInstances select: [ :e | e size > 100 ]) size => 36 (ByteSymbol allInstances select: [ :e | e size between: 50 and: 100 ]) size => 653 -- Guille Polito Research Engineer French National Center for Scientific Research - *http://www.cnrs.fr* <http://www.cnrs.fr> *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

6 7

[ Pharo 70 ] Build 44 PR 175 Space-analysis-resurrection
by Stephane Ducasse Aug. 19, 2017

Aug. 19, 2017

[ Pharo 70 ] Build 44 PR 175 Space-analysis-resurrection https://pharo.fogbugz.com/f/cases/20230/Space-analysis-resurrection https://github.com/pharo-project/pharo/pull/175

1 0

Little extensions to easily manage file versions
by Stephane Ducasse Aug. 19, 2017

Aug. 19, 2017

Hi I really like (when I save little data files) to have a simple versioning. For example for my game collection I have Games.1.ston Games.2.ston ... and I like that this is managed for me by the system. I harvested this functionality from squeak long time ago. I rewrote it fast and dirty in Pharo. I find this two methods super handy and they provide cheap versioning for little files. lastNameFor: baseFileName extension: extension "Assumes a file name includes a version number encoded as '.' followed by digits preceding the file extension, e.g., games.22.ston Answer the file name with the largest number. If a version number is not found, raises an error" "FileSystem workingDirectory lastNameFor: 'games' extension: 'ston'" | files | files := self childrenMatching: baseFileName , '.*.' , extension. files ifEmpty: [ ^ self error: 'No file with number pattern' ]. ^ (files asSortedCollection: [ :a :b | a basename < b basename ]) last nextNameFor: baseFileName extension: extension "Assumes a file name includes a version number encoded as '.' followed by digits preceding the file extension, e.g., games.22.ston Increment the version number (of the largest one) and answer the new file name, e.g., games23.ston If a version number is not found, set the version to 1 and answer a new file name" "FileSystem workingDirectory nextNameFor: 'games' extension: 'ston'" | files splits version | files := self childrenMatching: baseFileName , '.*.' , extension. files ifEmpty: [ ^ baseFileName , '.1.' , extension ]. splits := files collect: [ :filename | filename basename splitOn: $. ] thenSelect: [ :split | (split at: 1) = baseFileName and: [ split size = 3 ] ]. splits := splits asSortedCollection: [ :a :b | (a at: 2) < (b at: 2) ]. version := splits isEmpty ifTrue: [ 1 ] ifFalse: [ (splits last at: 2) asNumber + 1 ]. ^ baseFileName , '.' , version asString , '.' , extension I think that these to methods can be a valuable addition to fileReference (the methods can be better implemented). Let me know what you think. https://pharo.fogbugz.com/f/cases/20324/Handy-file-automatic-numbering Stef

2 2

[ Pharo 70 ] Build 44 PR 212 Add-build-number-to-SystemVersion
by Stephane Ducasse Aug. 18, 2017

Aug. 18, 2017

https://pharo.fogbugz.com/f/cases/20321/Add-build-number-to-SystemVersion https://github.com/pharo-project/pharo/pull/212

1 0

Is there a way to remove the extra protocol in calypso?
by Stephane Ducasse Aug. 18, 2017

Aug. 18, 2017

Hi denis The extra protocols are super confusing for newbies. Is there a setting to remove the critiques (because it flickers) from the protocols. Can we remove the overrides and inherited? I do not care to know that I overrides initialize from Object for example. When you learn a system you do not need to have bells and whistles. You should be able to concentrate. Stef

2 7

Initial Feedback on Pharo 7 contribution process
by Torsten Bergmann Aug. 18, 2017

Aug. 18, 2017

Hi, even when contributing to Pharo 7.0 is still very very cumbersome I was able to sort out most of the problems and contribute already a few smaller things. Unfortunately there is not much communication on what is currently in the pipe or planned on easing the process - which can easily lead to the impression that we do not really move or slow us down. I know step by step it goes and at least we have again the build process rolling https://pharoweekly.wordpress.com/2017/08/16/pharo-70-is-starting-to-roll-f… Nonetheless one of my PRs was already integrated and the integration of my WebBrowser package is still in the pipe (https://github.com/pharo-project/pharo/pull/193) The descriptions from Guille helped me - but there are still things I need answers to: 1. Will or is it still possible to automatically update" an image in Pharo 7 or in the future? The World menu entry "System" -> "System update" has been removed? Is this temporary of will it return once we know how it could be done again? 2. In latest Pharo 7.0 image there is a glitch that a method category has a typo in class "HEBinaryReaderWriter" and is "writting" instead of "writing". Lets assume I want to fix such a simple problem. But Hermes was an external package managed on GitHub. And it is now part of the image and therefore also in the "pharo" repo on GitHub. So how is it maintainted/managed with the new process? So do I fix this as a regular PR for Pharo 7 https://github.com/pharo-project/pharo or should it be fixed in the original repo https://github.com/tesonep/hermes and Hermes is synched from time to time into or from Pharo. 3. What still hit me most is that it is hard to identify the images and find out how "new" they are. Example: In Guilles example https://github.com/guillep/PharoIntegrationProcess/wiki/Contribute-a-fix-to… it is written that one should use wget -O - get.pharo.org/70+vm | bash This gives me an image file called "Pharo.image" and after a few days I do not know how old it is or what it was built from. When I start the image and look into the about box it gives me Pharo 7.0 Latest update: #0 telling me nothing and when I run SystemVersion current it says "Pharo7.0SNAPSHOT of 16 August 2017 update 0" which is also very useless. Both do not tell me anything about the build number!!! I can only guess the git commit from the name of the sources file: Pharo7.0-32bit-c28bff9.sources When I check https://github.com/pharo-project/pharo/commits/development with "c28bff9" then at least I have an idea how old it is. Especially the last topic is a pain point and the most pressuring to be discussed - without a clear image build number in the version/about box nobody is able to reproduce in which image one run into trouble or he is basing his work on. I know during transition time we need more patience and things will get more stable and we make progress over time. But I whised we would have more communication on the overall topic (current work, plans, ...) on this list here. I have no idea who is working on what already regarding making the process more easier. Thanks for any comments or own feedback you can share. Regards T.

6 8

[ Pharo 70 ] Build 43 PR 208 Open-a-package-extending-a-class-via-the-extension-protocol
by Stephane Ducasse Aug. 18, 2017

Aug. 18, 2017

https://pharo.fogbugz.com/f/cases/20062/Open-a-package-extending-a-class-vi… https://github.com/pharo-project/pharo/pull/208

1 0