August 2017 - Pharo-dev - lists.pharo.org

Little extensions to easily manage file versions

by Stephane Ducasse

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

Aug. 18, 2017

Re: [Pharo-dev] Is there a way to remove the extra protocol in calypso?

by Denis Kudriashov

Hi Stef. Yes, you need disable plugins. It is not available from settings browser. Use scripts: ClyInheritanceAnalyzerEnvironmentPlugin disable. ClyCriticEnvironmentPlugin disableMethodGroup But according to your logic method icons (up/down arrows) should be disabled too. Right now they are still managed by Nautilus method actions. To disable them use: ClyNautilusBrowserPlugin disable 2017-08-18 21:07 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > 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 > >

Aug. 18, 2017

Is there a way to remove the extra protocol in calypso?

by Stephane Ducasse

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

Aug. 18, 2017

Re: [Pharo-dev] Lowering the pain of newbies

by Stephane Ducasse

I have the impression that we should rethink the meta interface of classes and reflective calls. On Fri, Aug 18, 2017 at 10:44 AM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Hi > > I wrote proposal in issue > > 2017-08-18 0:52 GMT+02:00 Tim Mackinnon <tim(a)testit.works>: >> >> Is this a goal we can all share for 7.0? >> >> Sort out the expert tools (like git etc), but equally enable that >> simplicity you expect for a child/newbie/expert... >> >> I'm in! >> >> Tim >> >> Sent from my iPhone >> >> > On 17 Aug 2017, at 20:52, Stephane Ducasse <stepharo.self(a)gmail.com> >> > wrote: >> > >> > Hi guys >> > >> > my son coded in Pharo 60 >> > >> > testGuessUrlPart >> > >> > |dg8| >> > dg8 := GameItem new; >> > name: 'Dragon Quest VIII : Journey Of The Cursed King'; >> > console: 'PS2'. >> > self assert: dg8 guessUrlPart equals: >> > 'dragonquestviiijourneyofthecursedking' >> > >> > and guess what he broke the system. >> > >> > We should not accept such kind of behavior. >> > name: should not change the name of the class. >> > >> > I do not know the solution but I fear when I will teach 160 students >> > this fall. >> > We should make sure that Pharo is not a system only for experts! >> > >> > any idea is welcome >> > >> > >> > https://pharo.fogbugz.com/f/cases/20322/name-sent-to-a-class-SHOULD-NOT-aut… >> > >> > Stef >> > >> >> >

Aug. 18, 2017

Re: [Pharo-dev] [Vm-dev] Latest Debian, Ubuntu and CentOS packages of the pharo-vm

by Nicolas Cellier

Are the packaging stuff in opensmalltalk too, or just in pharo-vm? It would be great to move all to opensmalltalk. What is specificity of pharo-vm repository now? 2017-08-18 17:04 GMT+02:00 Eliot Miranda <eliot.miranda(a)gmail.com>: > > Hi Holger, > > > On Aug 18, 2017, at 2:54 AM, Holger Freyther <holger(a)freyther.de> wrote: > > > > Hi, > > > > when running Pharo in production you might want to install the image and > a VM from distribution packages. So far there were no current public > packages and during the last months I have modernized the debian packaging > and recently added CentOS rpm packaging as well. The process of generating > new source packages is integrated into the pharo-vm travis-ci build as well. > > > > Every time that master of pharo-vm.git is updated a new source package > will be uploaded to the Open(SUSE) Build Service and new packages will be > built and are available in a "latest" package feed. The generated (and > used) sourcecode is inside the source package and will be archived by the > OBS platform (one can even nicely diff versions). The "stable" VM is not > built from pharo-vm.git (yet?) so it doesn't show on OBS yet. > > Could/should this description be added to README.md on opensmalltalk-vm? > I think it would be great if we kept information on the various VM build CI > servers in README.md. It would help people find VMs instead of having to > build their own and it would give a good idea of the available platforms. > > > > Below are some semi-tested installation notes in case you want to try it > out. The binary names are picked to allow to install the 32bit and 64bit VM > in parallel. The names currently are: > > > > - pharo6-32 (32bit version) > > - pharo6-64 (64bit version) > > - pharo6-32-ui (32bit version with X11 dependencies) > > - pharo6-64-ui (64bit version with X11 dependencies) > > > > > > CentOS 6.8: > > > > # Add the repo > > $ yum-config-manager --add-repo http://download.opensuse.org/ > repositories/devel:/languages:/pharo:/latest/CentOS_6/devel: > languages:pharo:latest.repo > > > > # Install 32bit packages (with X11 dependency for *-ui or not) > > > > $ yum install pharo6-32-ui.i686 or pharo6-32.i386 > > > > # Install 64bit packages > > > > $ yum install pharo6-64-ui.x86_64 pharo6-64.x86_64 > > > > > > > > CentOS 7 (only 64bit): > > > > > > $ yum-config-manager --add-repo http://download.opensuse.org/ > repositories/devel:/languages:/pharo:/latest/CentOS_7/devel: > languages:pharo:latest.repo > > $ yum install pharo6-64-ui.x86_64 pharo6-64.x86_64 > > > > > > Debian 8: > > > > # Add signing key > > $ wget -O - http://download.opensuse.org/repositories/devel:/languages: > /pharo:/latest/Debian_8.0/Release.key | apt-key add - > > > > # Update and install > > $ apt update > > $ apt install pharo6-32-ui pharo6-64-ui (or pharo6-32 or pharo6-64) > > > > Ubuntu 14.04 LTS > > > > # Add signing key > > $ wget -O - http://download.opensuse.org/repositories/devel:/languages: > /pharo:/latest/xUbuntu_14.04/Release.key | apt-key add - > > > > # Update and install > > $ apt update > > $ apt install pharo6-32-ui pharo6-64-ui > > > > Ubuntu 16.04 > > > > # Add signing key > > $ wget -O - http://download.opensuse.org/repositories/devel:/languages: > /pharo:/latest/xUbuntu_16.04/Release.key | apt-key add - > > > > # Update and install > > $ apt update > > $ apt install pharo6-32-ui pharo6-64-ui > > > > > > >

Aug. 18, 2017

Re: [Pharo-dev] [Pharo-users] [ann] moldable brick editor - alpha

by Aliaksei Syrel

Hello Stephan, > Yep. I tried with a clean 6.1 install. > The Moz2D library is downloaded, but does not seem to be installed > correctly Below is the list of dependencies for *64bit Ubuntu* and *32bit Pharo*: (on 64bit pharo it should theoretically work out of the box, except 64bit related issues) > sudo dpkg --add-architecture i386; > sudo apt-get update; > export PKG_CONFIG_PATH=/usr/lib/i386-linux-gnu/pkgconfig/; > > echo "Installing c++ libraries"; > sudo apt install libstdc++6:i386; > > echo "Installing GTK-2.0..."; > sudo apt-get install libgtk2.0-0:i386; > echo "Installing GTK-3.0..."; > sudo apt-get install libgtk-3-0:i386; > > echo "Installing libGL..."; > sudo apt-get install libglu1-mesa:i386; We have travis Build which is green: https://github.com/syrel/Sparta/blob/master/.travis.yml https://travis-ci.org/syrel/Sparta On Windows users should install Visual C++ Redistributable for Visual Studio 2015: (reduces binary size by >10mb) https://www.microsoft.com/en-US/download/details.aspx?id=48145 On OSX works out of the box Cheers, Alex On 18 August 2017 at 17:01, stephan <stephan(a)stack.nl> wrote: > On 12-08-17 10:47, Tudor Girba wrote: > >> Is this still an issue? >> > > Yep. I tried with a clean 6.1 install. > The Moz2D library is downloaded, but does not seem to be installed > correctly > > > Could you also try on another OS (just to make sure)? > > next step > > Stephan > >

Aug. 18, 2017

Re: [Pharo-dev] Latest Debian, Ubuntu and CentOS packages of the pharo-vm

by Eliot Miranda

Hi Holger, > On Aug 18, 2017, at 2:54 AM, Holger Freyther <holger(a)freyther.de> wrote: > > Hi, > > when running Pharo in production you might want to install the image and a VM from distribution packages. So far there were no current public packages and during the last months I have modernized the debian packaging and recently added CentOS rpm packaging as well. The process of generating new source packages is integrated into the pharo-vm travis-ci build as well. > > Every time that master of pharo-vm.git is updated a new source package will be uploaded to the Open(SUSE) Build Service and new packages will be built and are available in a "latest" package feed. The generated (and used) sourcecode is inside the source package and will be archived by the OBS platform (one can even nicely diff versions). The "stable" VM is not built from pharo-vm.git (yet?) so it doesn't show on OBS yet. Could/should this description be added to README.md on opensmalltalk-vm? I think it would be great if we kept information on the various VM build CI servers in README.md. It would help people find VMs instead of having to build their own and it would give a good idea of the available platforms. > Below are some semi-tested installation notes in case you want to try it out. The binary names are picked to allow to install the 32bit and 64bit VM in parallel. The names currently are: > > - pharo6-32 (32bit version) > - pharo6-64 (64bit version) > - pharo6-32-ui (32bit version with X11 dependencies) > - pharo6-64-ui (64bit version with X11 dependencies) > > > CentOS 6.8: > > # Add the repo > $ yum-config-manager --add-repo http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/C… > > # Install 32bit packages (with X11 dependency for *-ui or not) > > $ yum install pharo6-32-ui.i686 or pharo6-32.i386 > > # Install 64bit packages > > $ yum install pharo6-64-ui.x86_64 pharo6-64.x86_64 > > > > CentOS 7 (only 64bit): > > > $ yum-config-manager --add-repo http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/C… > $ yum install pharo6-64-ui.x86_64 pharo6-64.x86_64 > > > Debian 8: > > # Add signing key > $ wget -O - http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/D… | apt-key add - > > # Update and install > $ apt update > $ apt install pharo6-32-ui pharo6-64-ui (or pharo6-32 or pharo6-64) > > Ubuntu 14.04 LTS > > # Add signing key > $ wget -O - http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/x… | apt-key add - > > # Update and install > $ apt update > $ apt install pharo6-32-ui pharo6-64-ui > > Ubuntu 16.04 > > # Add signing key > $ wget -O - http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/x… | apt-key add - > > # Update and install > $ apt update > $ apt install pharo6-32-ui pharo6-64-ui > > >

Aug. 18, 2017

Re: [Pharo-dev] [Pharo-users] [ANN] Pharo 6.1 (summer) released!

by Esteban Lorenzano

> On 18 Aug 2017, at 14:53, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > The problem is that doing a release 6.1 takes half a day of work. We could improve that, but then with Pharo7 all this changed anyway, so we will not improve this process. > half day? apply murphy law for system estimation: - raise measure unit by one: day=week - double time: 1/2 = 1 it took me one week to deliver the 6.1 release :( this is something we will be fixing with 7.0 process: each image would be like a final image, then we will be able (or we *should* be able) to create a new release by just changing a file and pushing it. Esteban

Aug. 18, 2017

Re: [Pharo-dev] [ANN] Pharo 6.1 (summer) released!

by Eliot Miranda

Hi Tim, > On Aug 18, 2017, at 4:08 AM, Tim Mackinnon <tim(a)testit.works> wrote: > > Thanks Marcus - and definitely we all appreciate that its holiday season and that a lot of this is driven by community and people donating their free time. > > Iâm still a bit unclear on the moving parts. To paraphrase what you have said: > > We start each yearly cycle with a X.0 new release. Then there may be point releases 6.1, 6.2 etc where there is a breaking change (typically a new VM I guess - but is there anything else that would cause a .x release?). Ignoring plugins, since VMs are backward compatible, new VMs are never breaking changes. A new vm may have a bug in it, but that would be superseded with a fixed vm asap, the previous good vm being used until that time. But we never release a new vm that won't run old image, except in a major release cycle, and even then not every release cycle. The VM is much like a real processor which always runs code in its instruction set but new instructions get added from time to time. The change from Squeak/Pharo 4.x to 5.x was a major change (Spur memory manager). But now we're back in the regime of backward compatibility in which the 6.x VMs will happily run 5.x images. But indeed this simple story might be violated by important plugins. > Then there are âhot fixesâ that causes an image number change (these have worked there way through the CI, as it triggered a new build)? The implication is then that what I download from Pharo.org is the last point release, but then I can go and find a newer image âhot fixâ if I want some of the latest more minor fixes (and I guess this then answers m .x question above - as I guess that if there was a major bug in the image it might also trigger a new point release so that new users would get that fix when downloading from pharo.org?) > > So a reasonably active Pharo user (but not a more bleeding edge new release user) should typically download the latest image every month to stay current? > > We should encourage more seasoned users to also try a leading edge point release, and apply the latest hot fix image particularly in the latter part of year when we are trying to stabilise for the next release cycle. And then there are the instructions about taking the next leap for contributing backâ¦ > > Is this right? > > Tim > >>> On 18 Aug 2017, at 08:56, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> >>> >>> What I think would have been good is to list all the updates that where done between >>> releasing 6.0 and 6.1 *as part of the changelog* of 6.1 (even though they were already >>> in the image that you got a minute before Pharo6.1 was released, as they where released as >>> hot fixes before). >>> >> >> The changelog of things done between releasing 6.0 and the release of 6.1: >> >> 20262 Update Iceberg to 0.5.4 >> https://pharo.fogbugz.com/f/cases/20262 >> >> 20268 update iceberg v0.5.5 >> https://pharo.fogbugz.com/f/cases/20268 >> >> 20226 TabMorph should use stepping mechanism for animating background building >> https://pharo.fogbugz.com/f/cases/20226 >> >> 20238 Run out of memory the image hangs without out of memory warning >> https://pharo.fogbugz.com/f/cases/20238 >> >> 20218 Master branch (Pharo 6) needs to be safely merged into development branch (Pharo 7). >> https://pharo.fogbugz.com/f/cases/20218 >> >> 20187 Request use of block in certain methods >> https://pharo.fogbugz.com/f/cases/20187 >> >> 20188 Request representation of integer literal without float exponent >> https://pharo.fogbugz.com/f/cases/20188 >> >> 20182 Extra dot in literal array >> https://pharo.fogbugz.com/f/cases/20182 >> >> 18760 Failing test: WeakAnnouncerTest>>#testNoDeadWeakSubscriptions >> https://pharo.fogbugz.com/f/cases/18760 >> >> 20186 Request removal of extra statement separators (dot) >> https://pharo.fogbugz.com/f/cases/20186 >> >> 20185 Request pipe after block argments >> https://pharo.fogbugz.com/f/cases/20185 >> >> 20183 TraitDescription>>fileOutLocalMethodsInCategory:on: method temp var name overlap >> https://pharo.fogbugz.com/f/cases/20183 >> >> 20184 Request space between argument and selector in StdioStream>>next: >> https://pharo.fogbugz.com/f/cases/20184 >> >> 20167 Regression with PNGReaderWriter in P6 >> https://pharo.fogbugz.com/f/cases/20167 >> >> 20198 inner structure access does not work on multiple architecture >> https://pharo.fogbugz.com/f/cases/20198 >> >> 20110 AllocationTest>>#testOutOfMemorySignal not well suited to 64-bit >> https://pharo.fogbugz.com/f/cases/20110 >> >> 20096 Add script pragma to SpaceTally>>printSpaceAnalysis >> https://pharo.fogbugz.com/f/cases/20096 >> >> 20174 In the debug halo of a morph: clicking on "inspect morph" and "explore morph" bring up the same window. >> https://pharo.fogbugz.com/f/cases/20174 >> >> 20093 Missing source stamp makes changes hard to view >> https://pharo.fogbugz.com/f/cases/20093 >> >> 20148 transforming deprecations should take #showWarning into account >> https://pharo.fogbugz.com/f/cases/20148 >> >> 20146 ZnHTTPSTests>>#testGetPharoVersion started to fail >> https://pharo.fogbugz.com/f/cases/20146

Aug. 18, 2017

Re: [Pharo-dev] [ANN] Pharo 6.1 (summer) released!

by Marcus Denker

> On 18 Aug 2017, at 15:41, Tim Mackinnon <tim(a)testit.works> wrote: > > If you donât mind - let me try a second attempt at paraphrasing what you are saying (just to make sure Iâm clear, but it might help others too). > > We start each yearly cycle with an X0 new release (our current release is 6). Then there may be point releases 6.1, 6.2 etc where there is a breaking change (typically a new VM. Our last point release was 6.1). > > Thought the year (typically every few days) there are âhot fixesâ that causes an image number change (these have worked there way through the CI, and have triggered a new artefect). These images can be found at http://files.pharo.org/image/60/ <http://files.pharo.org/image/60/> (where 60 designates the last release cycle, we donât use point designations for this directory name). > > When you download the latest point release, you are getting all the major elements of that release plus any of the hot fixes that have occurred since that official release. So you have the most up to date version of a stable Pharo at the time that you download this file from: http://pharo.org/download <http://pharo.org/download> > yes > The implication of the above, is that if you want to revert to exactly what was present in the launch of an official point release, you will need to download the latest release from Pharo.org <http://pharo.org/> and then find the image number that corresponded to that release at http://files.pharo.org/image/60/ <http://files.pharo.org/image/60/> (is there an easy way to determine this and then find that file? Or is there an official archive of the first point release?). > > If you want to say up to date, you should periodically download the latest point release (or you can simply find that latest named image file from: http://files.pharo.org/image/60/ <http://files.pharo.org/image/60/> and use your current VM). > > If the above is the case - it seems like a reasonable way of operating, although it might be good to know what the exact image number was in the first issued point release (just for traceability). > > Have I now got it straight now? > Yes. And maybe it is not goodâ¦ maybe it would be better to accumulate the changes between the point release without changing the download and have the version numbers more prominent in the downloaded files (so that it is easy to find old versions, too). With Pharo7 we can improve this... Marcus

Aug. 18, 2017