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

Re: [Pharo-dev] Pharo running with spur (work in process)

by Norbert Hartl

Woohooo! So it has started and it will progress. Wonderful! And it is the path to 64bit as well :) thanks Esteban, Eliot and Guille Norbert Am 02.07.2014 um 16:13 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > Hi, > > Iâve been working on prepare Pharo to run with the new Spur VMâ¦ and finally this week Guille and I sit together and make a huge advance :) > here a screenshot of pharo 4 running with spur: > <Screen Shot 2014-07-02 at 15.58.17.png> > for more information, same image before migration, with a regular cogvm gives this numbers: '1297023432 bytecodes/sec; 161029354 sends/secâ, so that means that the tiny benchmarks run at 166% the speed of the old vmâ¦ > Of course this is just one benchmark, but Iâm very impressed :) > > Now, it is still not usable but Iâm confident I can put a jenkins job to work very soon :) > > Esteban > > ps: before you start asking: Spur WILL NOT be available for Pharo3, it will be part of Pharo4. > > >

July 2, 2014

Re: [Pharo-dev] Pharo running with spur (work in process)

by Sven Van Caekenberghe

On 02 Jul 2014, at 16:26, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > On 02 Jul 2014, at 16:23, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> Excellent work, Esteban & Guillermo (and of course Eliot to begin with), very good to hear. >> >> Now, I guess the actual debugging road will be long and dangerous ;-) >> >> Apart from the speedup, does this also include 64-bit memory ? > > nope :( > but this is a necessary step to allow us to start working on the 64bits vm (which I hope to start soon too) OK, we'll get there, I am sure. >> >> On 02 Jul 2014, at 16:13, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >>> Hi, >>> >>> Iâve been working on prepare Pharo to run with the new Spur VMâ¦ and finally this week Guille and I sit together and make a huge advance :) >>> here a screenshot of pharo 4 running with spur: >>> <Screen Shot 2014-07-02 at 15.58.17.png> >>> for more information, same image before migration, with a regular cogvm gives this numbers: '1297023432 bytecodes/sec; 161029354 sends/secâ, so that means that the tiny benchmarks run at 166% the speed of the old vmâ¦ >>> Of course this is just one benchmark, but Iâm very impressed :) >>> >>> Now, it is still not usable but Iâm confident I can put a jenkins job to work very soon :) >>> >>> Esteban >>> >>> ps: before you start asking: Spur WILL NOT be available for Pharo3, it will be part of Pharo4. >>> >>> >>> >> >> > >

July 2, 2014

Re: [Pharo-dev] Pharo running with spur (work in process)

by Esteban Lorenzano

On 02 Jul 2014, at 16:23, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Excellent work, Esteban & Guillermo (and of course Eliot to begin with), very good to hear. > > Now, I guess the actual debugging road will be long and dangerous ;-) > > Apart from the speedup, does this also include 64-bit memory ? nope :( but this is a necessary step to allow us to start working on the 64bits vm (which I hope to start soon too) > > On 02 Jul 2014, at 16:13, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> Hi, >> >> Iâve been working on prepare Pharo to run with the new Spur VMâ¦ and finally this week Guille and I sit together and make a huge advance :) >> here a screenshot of pharo 4 running with spur: >> <Screen Shot 2014-07-02 at 15.58.17.png> >> for more information, same image before migration, with a regular cogvm gives this numbers: '1297023432 bytecodes/sec; 161029354 sends/secâ, so that means that the tiny benchmarks run at 166% the speed of the old vmâ¦ >> Of course this is just one benchmark, but Iâm very impressed :) >> >> Now, it is still not usable but Iâm confident I can put a jenkins job to work very soon :) >> >> Esteban >> >> ps: before you start asking: Spur WILL NOT be available for Pharo3, it will be part of Pharo4. >> >> >> > >

July 2, 2014

Re: [Pharo-dev] Pharo running with spur (work in process)

by Sven Van Caekenberghe

Excellent work, Esteban & Guillermo (and of course Eliot to begin with), very good to hear. Now, I guess the actual debugging road will be long and dangerous ;-) Apart from the speedup, does this also include 64-bit memory ? On 02 Jul 2014, at 16:13, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi, > > Iâve been working on prepare Pharo to run with the new Spur VMâ¦ and finally this week Guille and I sit together and make a huge advance :) > here a screenshot of pharo 4 running with spur: > <Screen Shot 2014-07-02 at 15.58.17.png> > for more information, same image before migration, with a regular cogvm gives this numbers: '1297023432 bytecodes/sec; 161029354 sends/secâ, so that means that the tiny benchmarks run at 166% the speed of the old vmâ¦ > Of course this is just one benchmark, but Iâm very impressed :) > > Now, it is still not usable but Iâm confident I can put a jenkins job to work very soon :) > > Esteban > > ps: before you start asking: Spur WILL NOT be available for Pharo3, it will be part of Pharo4. > > >

July 2, 2014

Pharo running with spur (work in process)

by Esteban Lorenzano

Hi, Iâve been working on prepare Pharo to run with the new Spur VMâ¦ and finally this week Guille and I sit together and make a huge advance :) here a screenshot of pharo 4 running with spur: for more information, same image before migration, with a regular cogvm gives this numbers: '1297023432 bytecodes/sec; 161029354 sends/secâ, so that means that the tiny benchmarks run at 166% the speed of the old vmâ¦ Of course this is just one benchmark, but Iâm very impressed :) Now, it is still not usable but Iâm confident I can put a jenkins job to work very soon :) Esteban ps: before you start asking: Spur WILL NOT be available for Pharo3, it will be part of Pharo4.

July 2, 2014

[pharo-project/pharo-core]

by GitHub

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

July 2, 2014

[pharo-project/pharo-core] 937d90: 40058

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 937d900c132708614731a9b3a02666ef0904d980 https://github.com/pharo-project/pharo-core/commit/937d900c132708614731a9b3… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-07-02 (Wed, 02 Jul 2014) Changed paths: M OpalCompiler-Core.package/OCSlotVariable.class/README.md M OpalCompiler-Core.package/OCUndeclaredVariable.class/README.md A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script58.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40058.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Slot.package/InstanceVariableSlot.class/README.md M Slot.package/InstanceVariableSlot.class/class/cleanup/resetIvarSlots.st A Slot.package/LinkWrapper.class/README.md A Slot.package/LinkWrapper.class/definition.st A Slot.package/LinkWrapper.class/instance/accessing/link.st A Slot.package/LinkWrapper.class/instance/accessing/link_.st A Slot.package/LinkWrapper.class/instance/accessing/slot.st A Slot.package/LinkWrapper.class/instance/accessing/slot_.st A Slot.package/LinkWrapper.class/instance/emitting/emitValue_.st M Slot.package/Slot.class/README.md M Slot.package/TestSlot.class/README.md Log Message: ----------- 40058 13411 Some Slot instances left...re-run cleanup https://pharo.fogbugz.com/f/cases/13411 13453 add LinkWrapper and some comments for Slots https://pharo.fogbugz.com/f/cases/13453 13454 Failing test: SlotIntegrationTest.testSlotScopeParallelism https://pharo.fogbugz.com/f/cases/13454 http://files.pharo.org/image/40/40058.zip

July 2, 2014

Re: [Pharo-dev] [ANN]: Little NeoJSON Helper

by Sven Van Caekenberghe

Let's classify it as a brilliant, advanced hack then ;-) On 01 Jul 2014, at 03:54, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Sven Van Caekenberghe-2 wrote >> I just don't know, what do you think about it in retrospect ? > > Thanks for taking a look! I don't know either :) > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/ANN-Little-NeoJSON-Helper-tp4756763p4765873.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

July 2, 2014

Re: [Pharo-dev] Athens and TextMorphs

by stepharo

Hi nicolai what would be good is to give feedback to igor on the TxText because this is the future :) Stef > Working with Text and Athens only works for FreeType fonts and > with Athens primitive drawString: method. > Morphs with Text can not be used on an Athens. > (No TextMorph rendering and no font emphasis on String or LabelMorph). > > But there is a AthensText package with some classes for > text morph/renderer/scanner/paragraph. > These are only used in AthensTextRenderTest and AthensTextMorph > both don't work and AthensTextMorph should not be used (?) > Classcomment: "this class is subject of changes/removal. do not use it." > > Where do we go from here? > What is supposed to work and is it worth while to fix the > missing/wrong implementations? > > > nicolai >

July 2, 2014

Re: [Pharo-dev] [Pharo-users] PillarHub

by kilon alios

Definitely one step closer to a Pharo Wiki. Great news indeed. Will it also offer a version control system so we can reverse changes in case of spams or mistakes etc ? On Wed, Jul 2, 2014 at 1:05 PM, J.F. Rick <self(a)je77.com> wrote: > Awesome. Not that I have time right now but I have always wanted to bring > Swiki / AniAniWeb into the present. This would be the right foundational > work to make this a useful reality. > > On a side note, I apologize for all the bad qualities of Pillar markup. > Back in 1999, I created ComSwiki out of the beginning that was PWS Swiki > (the first wiki to eschew camel case for links). One of the first things I > did was to make changes to the markup to improve it. Of course, once we had > some users and established content, all the decisions I made at that early > point in the project were made permanent. Looking at Pillar, it pretty much > uses the syntax I created back then (with a few improvements). I'm sure the > markup just drifted through the Smalltalk community and was then adopted by > Pillar. It's not a bad design but I've always felt that a better, more > extensible syntax was possible. As usual, the good proved to be the enemy > of the great. > > Cheers, > > Jeff > > > On Wed, Jul 2, 2014 at 10:57 AM, phil(a)highoctane.be <phil(a)highoctane.be> > wrote: > >> >> Superb! >> >> Keep on pushing, that's how we can attain the critical momentum. >> >> Hopefully, I'll be able to show something from my side as well on the >> commercial products front. >> >> Phil >> >> >> >> On Wed, Jul 2, 2014 at 10:00 AM, Sven Van Caekenberghe <sven(a)stfx.eu> >> wrote: >> >>> Wow, amazing - great work ! >>> >>> On 02 Jul 2014, at 09:28, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >>> >>> > Hi everyone. >>> > >>> > Iâm so excited that I cannot keep silent. Guys from Pharocloud have >>> implemented online editor (and storage) for Pillar documents. This is >>> really amazing, and you can check it out here: >>> http://pillarhub.pharocloud.com/hub/pillarhub/about. >>> > >>> > They have a really nice plans, and now we can write pillar docs with >>> live compilation and share them online. >>> > >>> > Cheers! >>> > Uko >>> >>> >>> >> > > > -- > Jochen "Jeff" Rick, Ph.D. > http://www.je77.com/ > Skype ID: jochenrick >

July 2, 2014