April 2015 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

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

April 8, 2015

[pharo-project/pharo-core] d974e7: 40597

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: d974e742984b1b04eb3ba98739e64ecd00b3715c https://github.com/pharo-project/pharo-core/commit/d974e742984b1b04eb3ba987… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-04-08 (Wed, 08 Apr 2015) Changed paths: R ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script596.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script597.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40596.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40597.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Slot-Tests.package/BooleanSlotTest.class/instance/tests/testExampleTwoBooleanSlots.st A Slot.package/BooleanSlot.class/instance/accessing/offset.st M Slot.package/BooleanSlot.class/instance/class building/calculateOffset_.st M Slot.package/BooleanSlot.class/instance/class building/installingIn_.st Log Message: ----------- 40597 15308 Bugfix and test for BooleanSlot https://pharo.fogbugz.com/f/cases/15308 http://files.pharo.org/image/40/40597.zip

April 8, 2015

Re: [Pharo-dev] Can Monticello version message be a Text?

by Thierry Goubier

Hi Uko, Thanks, I'll have a look this afternoon (if I'm not doing some D4D support :)) Thierry 2015-04-08 9:44 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > > > On 07 Apr 2015, at 12:16, Thierry Goubier <thierry.goubier(a)gmail.com> > wrote: > > > > Le 07/04/2015 11:01, Yuriy Tymchuk a Ã©crit : > >> Hi, thank you very much for investigating this. > > > > You're working on it too :) > > > >> These are the steps to reproduce: > >> > >> 1. Clone a git repo (e.g. https://github.com/Uko/VnaExporter.git) > >> 2. Add it as gitfiletree repo to the pharo image. > >> 3. Change something, commit part of the changes with Komitter. > >> 4. Change something more. > >> 5. Open Komitter, you should see a strange diff. > >> 6. Select 1 or 2 methods & commit them. > >> 7. Now you should have only 2 methods in your repo. > > > > I did, and I don't see anything suspicious. Browsing the repository at > each step gave me the complete package as expected (minus the unsaved > changes, of course). > > > > Can you show a screenshot at step 5? > > I've done a screen recording > https://dl.dropboxusercontent.com/u/83145561/GitKomitter.mov > > Uko > > > > > Thierry > > > > >

April 8, 2015

Re: [Pharo-dev] Can Monticello version message be a Text?

by Yuriy Tymchuk

> On 07 Apr 2015, at 12:16, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > Le 07/04/2015 11:01, Yuriy Tymchuk a Ã©crit : >> Hi, thank you very much for investigating this. > > You're working on it too :) > >> These are the steps to reproduce: >> >> 1. Clone a git repo (e.g. https://github.com/Uko/VnaExporter.git) >> 2. Add it as gitfiletree repo to the pharo image. >> 3. Change something, commit part of the changes with Komitter. >> 4. Change something more. >> 5. Open Komitter, you should see a strange diff. >> 6. Select 1 or 2 methods & commit them. >> 7. Now you should have only 2 methods in your repo. > > I did, and I don't see anything suspicious. Browsing the repository at each step gave me the complete package as expected (minus the unsaved changes, of course). > > Can you show a screenshot at step 5? Iâve done a screen recording https://dl.dropboxusercontent.com/u/83145561/GitKomitter.mov Uko > > Thierry >

April 8, 2015

Re: [Pharo-dev] RTF reader/writer

by Sean P. DeNigris

Brian Brown-6 wrote > I have had this laying around for quite some time, and I don't quite > remember what all it can do, but you are welcome to do whatever you wish > with it :) It seems to work! I uploaded to http://smalltalkhub.com/#!/~SeanDeNigris/RTF/ and ported to Pharo 4.0 (tiny change to test) ----- Cheers, Sean -- View this message in context: http://forum.world.st/RTF-reader-writer-tp2125230p4818257.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 8, 2015

Re: [Pharo-dev] RTF reader/writer

by Sean P. DeNigris

hernanmd wrote > http://www.smalltalking.net/Goodies/VisualSmalltalk/index.htm Apparently only for non-commercial though: "You may not use or distribute this Software or any derivative work in any form for commercial purposes without written permission of the Author of this Software." http://www.smalltalking.net/goodies/GoodiesLicense.htm ----- Cheers, Sean -- View this message in context: http://forum.world.st/RTF-reader-writer-tp2125230p4818253.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 8, 2015

Re: [Pharo-dev] modifying ASTs

by Yuriy Tymchuk

For #formattedCode also adds parentheses :(. Iâll try to dig into it more Uko > On 07 Apr 2015, at 17:56, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > Le 07/04/2015 17:47, Yuriy Tymchuk a Ã©crit : >> One more question. How do I get the new source string? Because if I >> use #sourceCode I get old code, if I use #printString it also puts >> extra parenthesis. > > #formattedCode > > Thierry > >> Uko >> >>> On 07 Apr 2015, at 17:39, Thierry Goubier >>> <thierry.goubier(a)gmail.com> wrote: >>> >>> Le 07/04/2015 17:24, Marcus Denker a Ã©crit : >>>> >>>>> On 07 Apr 2015, at 17:20, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> >>>>> wrote: >>>>> >>>>> Hi, I need to change source code of a method by for example >>>>> adding a pragma. Can I just manipulate itâs AST without >>>>> carrying about source code anchors? Because it seems that I >>>>> have to set from/to values and it looks painful. >>>>> >>>> >>>> I would do the change, print the code and recompile itâ¦ not nice, >>>> but for now the easiest. >>> >>> I conccur with Marcus. It's good enough; RB works this way. >>> >>> Note that you can change the AST without bothering with the from/to >>> stuff, in most cases (except syntax errors messages?). >>> >>>> (this way they old AST gets garbage collected and the new one has >>>> all the offsets into the text correct). >>> >>> It's a lot easier than trying to shift the offsets depending on >>> what you have added/not added. >>> >>>> I would like to explore if we canât build a system where >>>> everything we manipulate is ASTsâ¦ >>> >>> You're the compiler guy: everything is an AST :) >>> >>> Thierry >>> >> >> >> >> > >

April 7, 2015

Re: [Pharo-dev] gitfiletree doesn't throw error when repository doesn't exist

by Thierry Goubier

Hi Peter, good find. I'll fix that. Thierry Le 07/04/2015 19:02, Peter UhnÃ¡k a Ã©crit : > When I load non-existing repository, e.g. > > Metacello new > baseline: 'WhatEver'; > repository: 'gitfiletree:///hoewrtory'; > load > > then Metacello just silently executes it and doesn't do anything. I > would expect some error to pop-up that it doesn't exist. > > Thanks, > Peter

April 7, 2015

gitfiletree doesn't throw error when repository doesn't exist

by Peter UhnÃ¡k

When I load non-existing repository, e.g. Metacello new baseline: 'WhatEver'; repository: 'gitfiletree:///hoewrtory'; load then Metacello just silently executes it and doesn't do anything. I would expect some error to pop-up that it doesn't exist. Thanks, Peter

April 7, 2015

Re: [Pharo-dev] Updating ZeroConf! Please do not use it until new advice!

by Esteban Lorenzano

> On 07 Apr 2015, at 18:20, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > Hi Esteban, > > the links to the effectives VMs and images behind the scripts haven't changed? well, no and yes. old zeroconf was pointing, for example, to files.pharo.org/image/30/latest.zip <http://files.pharo.org/image/30/latest.zip> what I did is to put an intermediary, who works as a consolidation. so, now, if you do: get.pharo.org/30 <http://get.pharo.org/30> it will go fetch the image to: files.pharo.org/get-files/30/pharo.zip <http://files.pharo.org/get-files/30/pharo.zip> and that is a symlink to files.pharo.org/image/30/latest.zip <http://files.pharo.org/image/30/latest.zip> with vmâs is âalmostâ the same. With the difference that now I create a symlink in (for example) files.pharo.org/vm/pharo/mac/ <http://files.pharo.org/vm/pharo/mac/> to the âstableâ which is called âstable-YYMMDDâ then in download files: files.pharo.org/get-files/30/pharo-mac-stable.zip <http://files.pharo.org/get-files/30/pharo-mac-stable.zip> is a symlink to the stable we decide isâ¦ well, stable :) the intermediary give us much more control. next steps is to change also the build jobs to create the distribution files taking into account consolidation directoryâ¦ but well, thatâs next step :) Esteban > > Thierry > > Le 07/04/2015 17:24, Esteban Lorenzano a Ã©crit : >> okâ¦ success :) >> now, this is the change: >> >> from now, each version is married with one vm. >> >> so, if you download /30+vm it will download the Pharo30 image with its corresponding "vm30" >> >> which means some links do not have sense anymore: >> >> /vm >> /vmLatest >> >> but you have >> >> /vm12 >> ... >> /vm20 >> /vm30 >> /vm40 >> /vmLatest40 >> >> the concept of âlatest vmâ is also now married to development imageâ¦ while an image is being developed (40 now, 50 next week), it will have a âlatestâ vmâ¦ but once releases, release will come with a âblessedâ vmâ¦ the one is good for you to use. >> >> of course, that does not means vmâs are not exchangeable, as usualâ¦ it means we are blessing one version of the vm to be used with one version of the image. >> >> Now, the vm will download just ONE source version (vm30 will download PharoV3.sources)â¦ so we can keep many version without bloating our downloads. >> >> Also, this prepares us to future non compatible VM versions (like Spur), so is a good change. >> >> I hope it is clear for you :) >> >> cheers, >> Esteban >> >> >> >>> On 07 Apr 2015, at 16:56, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>> Ok, retrying. DO NOT USE THEM! >>> >>> Esteban >>> >>>> On 07 Apr 2015, at 16:20, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>> >>>> ok, you can use it now. Update failed and I need to leave for half na hourâ¦. I will retry later. >>>> >>>> cheers, >>>> Esteban >>>> >>>>> On 07 Apr 2015, at 16:03, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>>> >>>>> thatâ¦ we need to change it :P >>>> >>> >> >> >> >> > >

April 7, 2015