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

Re: [Pharo-dev] Rubric versus Athens

by Nicolai Hess

Great! GTPlayground with Text! (I used this version Rubric-AlainPlantec.173 But I got an error: RubParagraph(Object)>>doesNotUnderstand: #drawOnAthensCanvas:bounds:color: I added this method to RubParagraph, calliing self displayTextOnAthensCanvas: in: ) Many of your changes for Rubric are the same I had done for Paragraph. But yes, it is difficult to not duplicate this code, Rubric shares many parts with Paragraph and other Text related classes (DisplayScanner ..) but still different, so we can not use the same implementation. I'll have a closer look, maybe we can refactor out some common parts. nicolai 2015-02-26 22:55 GMT+01:00 Alain Plantec <alain.plantec(a)yahoo.com>: > Hello Nicolai, > > Iâve made a first pass. > Iâve not used your Athens* add ons. Instead, raw Athens drawing. > Less clean but done. > Hope it will help to continue Athens integration. > > Cheers > Alain

Feb. 26, 2015

Re: [Pharo-dev] The evil twin in 40516

by Johan Fabry

This is excellent! > On Feb 26, 2015, at 20:07, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > In 40516 there is now a strange, but rather powerful mechanism for CompiledMethod: the Twin. > > What does that do? > > you can call on a method #createTwin > > (ReflectivityExamples>>#exampleMethod) createTwin. > > after this, the CompiledMethod has a high-level representation (the AST) attached that itself references the CompiledMethod > (they form a twin). > > (ReflectivityExamples>>#exampleMethod) reflectiveMethod > > The fun thing is now that one can install either in the class. Call #invalidate to make sure the reflective method is installed. > > ReflectiveMethod implements #run:with:in: which calls a compilation hook (too re-create from the AST) and then installs that in the > method dict and then executes the method: > > (ReflectivityExamples>>#exampleMethod) createTwin. > (ReflectivityExamples>>#exampleMethod) invalidate. > self assert: (ReflectivityExamples>>#exampleMethod) class = ReflectiveMethod. > self assert: ReflectivityExamples new exampleMethod = 5. > self assert: (ReflectivityExamples>>#exampleMethod) class = CompiledMethod. > > Which means that this gives us an in-image, on-demand JIT compiler AST->Bytecode. In 50 lines of code. > > e.g. try on Morph: > > Morph methods do: #createTwin. > Morph methods do: #invalidate. > > Counting which twin is installed shows us the working set of Morph: > > (Morph methods select: [ :each | each class = CompiledMethod ]) size > > some 330 method out of nearly 900â¦. > > So what can one do with this? In essence this turns the AST into a reflective representation for Methods > (if you care to set up twin creation + invalidation correctly). > > What will this allow us to do? stay tuned... > > Marcus > > > > ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

Feb. 26, 2015

The evil twin in 40516

by Marcus Denker

Hi, In 40516 there is now a strange, but rather powerful mechanism for CompiledMethod: the Twin. What does that do? you can call on a method #createTwin (ReflectivityExamples>>#exampleMethod) createTwin. after this, the CompiledMethod has a high-level representation (the AST) attached that itself references the CompiledMethod (they form a twin). (ReflectivityExamples>>#exampleMethod) reflectiveMethod The fun thing is now that one can install either in the class. Call #invalidate to make sure the reflective method is installed. ReflectiveMethod implements #run:with:in: which calls a compilation hook (too re-create from the AST) and then installs that in the method dict and then executes the method: (ReflectivityExamples>>#exampleMethod) createTwin. (ReflectivityExamples>>#exampleMethod) invalidate. self assert: (ReflectivityExamples>>#exampleMethod) class = ReflectiveMethod. self assert: ReflectivityExamples new exampleMethod = 5. self assert: (ReflectivityExamples>>#exampleMethod) class = CompiledMethod. Which means that this gives us an in-image, on-demand JIT compiler AST->Bytecode. In 50 lines of code. e.g. try on Morph: Morph methods do: #createTwin. Morph methods do: #invalidate. Counting which twin is installed shows us the working set of Morph: (Morph methods select: [ :each | each class = CompiledMethod ]) size some 330 method out of nearly 900â¦. So what can one do with this? In essence this turns the AST into a reflective representation for Methods (if you care to set up twin creation + invalidation correctly). What will this allow us to do? stay tuned... Marcus

Feb. 26, 2015

[pharo-project/pharo-core] 657ef3: 40516

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 657ef34022736524166273d950d8b0adcb6f691a https://github.com/pharo-project/pharo-core/commit/657ef34022736524166273d9… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-02-26 (Thu, 26 Feb 2015) Changed paths: R KernelTests.package/DelayTest.class/instance/testing/testSemaphore.st A KernelTests.package/DelayTest.class/instance/testing/testSemaphoreNoTimeout.st A KernelTests.package/DelayTest.class/instance/testing/testSemaphoreTimeout.st R KernelTests.package/DelayTest.class/instance/testing/testTimeoutSemaphoreAfterMSecs.st A Reflectivity.package/MetaLink.class/README.md A Reflectivity.package/MetaLink.class/definition.st A Reflectivity.package/MetaLink.class/instance/accessing/metaObject.st A Reflectivity.package/MetaLink.class/instance/accessing/metaObject_.st A Reflectivity.package/MetaLink.class/instance/accessing/selector.st A Reflectivity.package/MetaLink.class/instance/accessing/selector_.st M Reflectivity.package/ReflectiveMethod.class/instance/invalidate/destroyTwin.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script515.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script516.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40515.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40516.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R Slot.package/MetaLink.class/README.md R Slot.package/MetaLink.class/definition.st R Slot.package/MetaLink.class/instance/accessing/metaObject.st R Slot.package/MetaLink.class/instance/accessing/metaObject_.st R Slot.package/MetaLink.class/instance/accessing/selector.st R Slot.package/MetaLink.class/instance/accessing/selector_.st A Slot.package/ProcessLocalSlot.class/README.md A Slot.package/ProcessLocalSlot.class/definition.st A Slot.package/ProcessLocalSlot.class/instance/code generation/emitStore_.st A Slot.package/ProcessLocalSlot.class/instance/code generation/emitValue_.st A Slot.package/ProcessLocalSlot.class/instance/initialization/initialize_.st A Slot.package/ProcessLocalSlot.class/instance/meta-object-protocol/read_.st A Slot.package/ProcessLocalSlot.class/instance/meta-object-protocol/wantsInitalization.st A Slot.package/ProcessLocalSlot.class/instance/meta-object-protocol/write_to_.st A Slot.package/PropertySlot.class/instance/code generation/emitStore_.st A Slot.package/PropertySlot.class/instance/code generation/emitValue_.st M Slot.package/Slot.class/instance/meta-object-protocol/link_.st R Slot.package/WeakSlot.class/instance/as yet unclassified/emitStore_.st R Slot.package/WeakSlot.class/instance/as yet unclassified/emitValue_.st R Slot.package/WeakSlot.class/instance/as yet unclassified/initialize_.st R Slot.package/WeakSlot.class/instance/as yet unclassified/read_.st R Slot.package/WeakSlot.class/instance/as yet unclassified/wantsInitalization.st R Slot.package/WeakSlot.class/instance/as yet unclassified/write_to_.st A Slot.package/WeakSlot.class/instance/code generation/emitStore_.st A Slot.package/WeakSlot.class/instance/code generation/emitValue_.st A Slot.package/WeakSlot.class/instance/initialization/initialize_.st A Slot.package/WeakSlot.class/instance/meta-object-protocol/read_.st A Slot.package/WeakSlot.class/instance/meta-object-protocol/wantsInitalization.st A Slot.package/WeakSlot.class/instance/meta-object-protocol/write_to_.st Log Message: ----------- 40516 14990 MonitorDelay>>#signalLock:afterMSecs:inMonitor:queue: should return MonitorDelay object https://pharo.fogbugz.com/f/cases/14990 15003 Bytecode Gen for Property Slot + small fixes reflectivity https://pharo.fogbugz.com/f/cases/15003 15004 Add ProcessLocalSlot https://pharo.fogbugz.com/f/cases/15004 http://files.pharo.org/image/40/40516.zip

Feb. 26, 2015

[pharo-project/pharo-core]

by GitHub

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

Feb. 26, 2015

Re: [Pharo-dev] Recording user actions in GTools

by Peter UhnÃ¡k

> > There are already tooltips, but likely in a version which is about to be > released for Pharo 4: > You can try Moose 5.1 for now. > Ah! I was looking at Pharo image; yes, this is what I was looking for. :) Peter

Feb. 26, 2015

Re: [Pharo-dev] Recording user actions in GTools

by Juraj Kubelka

> 26. 2. 2015 v 19:04, Peter UhnÃ¡k <i.uhnak(a)gmail.com>: > > before the Pharo code freeze, a small extension to GT tools (300 lines of code) that records and sends usage data. > > various actions you do in spotter (open, close, search, dive-in, dive-out, select element, etc) > If there are no tooltips what shortcuts to use people cannot dive-in and there is nothing to record :)... so please please :) There are already tooltips, but likely in a version which is about to be released for Pharo 4: You can try Moose 5.1 for now. Cheers, Juraj

Feb. 26, 2015

Re: [Pharo-dev] Recording user actions in GTools

by Peter UhnÃ¡k

> > before the Pharo code freeze, a small extension to GT tools (300 lines of > code) that records and sends usage data. > > various actions you do in spotter (open, close, search, dive-in, dive-out, > select element, etc) > If there are no tooltips what shortcuts to use people cannot dive-in and there is nothing to record :)... so please please :) But I certainly don't mind. Peter

Feb. 26, 2015

Rubric versus Athens

by Alain Plantec

Hello Nicolai, Iâve made a first pass. Iâve not used your Athens* add ons. Instead, raw Athens drawing. Less clean but done. Hope it will help to continue Athens integration. Cheers Alain

Feb. 26, 2015

Re: [Pharo-dev] zipped and unzipped methods for ByteArray

by stepharo

Why do we have to put everything in string? why Zip string: 'hello' Zip bzip string: 'hello' Zip gzip string: 'hello' would not be more modular? Zip could be a factory and have subclasses. This is not because can extend classes that we should think about nicer way. I like for example the DateFormatter strategy related to Date from other languages because I can specify the way I want it. Stef Le 25/2/15 16:52, Juraj Kubelka a Ã©crit : >> 25. 2. 2015 v 12:28, Sven Van Caekenberghe <sven(a)stfx.eu>: >> >> This seems related to adding 'easy of use' methods to String. >> >> There are many different compression schemes (zip, bzip, bzip2, gzip, ...), are we going to add them all ? >> >> How much do we want to couple different parts of the system ? > I prefer to couple the compression schemes with String and ByteArray. Methods like #zipped, #unzipped are not that simple and it is not well apparent how to use that compression scheme. > > Cheers, > Juraj > >>> On 25 Feb 2015, at 16:23, Juraj Kubelka <juraj.kubelka(a)gmail.com> wrote: >>> >>> Can I add ByteArray>>#zipped and #unzipped methods the way it is for String? I want to compress bytes before sending through internet, for example. >>> >>> Do you agree? >>> Thanks, >>> Juraj >> > >

Feb. 26, 2015