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

Re: [Pharo-dev] Trying to use Rubric in Nautilus ....

by Alain Plantec

see Rubric-AlainPlantec.196 in the Rubric repo. Iâve added RubPluggableTextMorph and RubPluggableTextMorphExample. Need to be polished certainly but it should facilitate the integration of Rubric in Nautilus. cheers Alain > On 12 May 2015, at 22:45, stepharo <stepharo(a)free.fr> wrote: > > For fun I put the following trace in > > sourceCodeFrom: aTextMorph > Transcript show: '.'. > ^ self sourceCode > > And in general this method is invoked three times instead of one :) > > >> >> Before asking we read all the examples and I saw that selector: is used to communicate and update the code pane. >> >> (UIManager default newAutoAcceptTextEntryFor: self >> get: #selector >> set: #selector: >> class: String >> getEnabled: #haveClassName >> help: 'Enter a selector' translated >> entryCompletion: entryCompletion) >> acceptOnCR: false; >> ghostText: 'Selector'; >> withDropListButton; >> >> >> I think this is only for the drop down list. > > What I meant is that I could use set: and pass the selector to be invoked by the dropdown when the drop down is selected. > And it will notify self with the selector: selector. So we could sepcify any selector (ie I can register to the drop box and say call me once you are set). > > >> In RubMethodEditingExample>>#selector: >> it calls the update explicit >> self updateCodeWith: (cls sourceCodeAt: selector) >> and updateCodeWith: sets the text on the text model. >> >> >> >> >> Now my problem (and may be there is not solution) is how can I connect from a pluggableListMorph to a RubScrollText >> when the list does not generate announcement. >> This is why I tried to pass via dependents or something like that. >> >> I will try to generate announcements but this is a lot more work and I do not know if it will work. >> >> Stef >> >> > >

May 13, 2015

Re: [Pharo-dev] Transcript needs your love

by Sven Van Caekenberghe

I tried to abstract the Transcript API from the Pharo perspective in https://pharo.fogbugz.com/f/cases/15528/Add-TTranscript-and-DailyNonInterac… If the Cuis Transcript implementation conformed to this, it could become just a plugin replacement/alternative, next to others already present. > On 13 May 2015, at 16:08, J. Vuletich (mail lists) <juanlists(a)jvuletich.org> wrote: > > Hi Alain, > > Quoting Alain Rastoul <alf.mmm.cat(a)gmail.com>: > >> Le 08/05/2015 11:34, stepharo a Ã©crit : >>> Hi guys >>> >>> the Transcript in Pharo is that it's not asynchronous so I can't use it >>> in VM development to show the current progress of the simulation. For >>> example: >>> 1 to: 100 do: [ :i | >>> 0.1 seconds asDelay wait. >>> Transcript show: 'x'. ] >>> => on Squeak, this shows a x every 0.1 second in the Transcript >>> => on Pharo, nothing happens during 10 seconds then all the x are shown. >>> >>> https://pharo.fogbugz.com/default.asp?15515 >>> >>> >> Hi, >> I updated the fogbugz entry with a changeset containing the sources Stef already put here, so that it should be easy for anybody to load CuisTranscript into a Pharo image and have a look. > > Today I did a new commit to the Cuis repo. The Cuis image is now in Cog format (6505) instead of Closures format (6504). I hope this allows you to run Cuis in your system. > > I also addressed some of the issues you raised. I optimized the refresh, and avoided the "bolder text" effect. > > Now, > Time millisecondsToRun: [ 1000 timesRepeat: [ Transcript show: 'x' ] ]. > takes 2 ms, even while updating the Display. (Hundreds of times faster). > > I hope the slugginess you see also gets better. > > >> IMHO another solution has to be found, or a big review of this has to be done. >> see details in fogbugz entry. >> >> -- >> Regards, >> >> Alain > > Cheers, > Juan Vuletich

May 13, 2015

Re: [Pharo-dev] Transcript needs your love

by J. Vuletich (mail lists)

Hi Alain, Quoting Alain Rastoul <alf.mmm.cat(a)gmail.com>: > Le 08/05/2015 11:34, stepharo a Ã©crit : >> Hi guys >> >> the Transcript in Pharo is that it's not asynchronous so I can't use it >> in VM development to show the current progress of the simulation. For >> example: >> 1 to: 100 do: [ :i | >> 0.1 seconds asDelay wait. >> Transcript show: 'x'. ] >> => on Squeak, this shows a x every 0.1 second in the Transcript >> => on Pharo, nothing happens during 10 seconds then all the x are shown. >> >> https://pharo.fogbugz.com/default.asp?15515 >> >> > Hi, > I updated the fogbugz entry with a changeset containing the sources > Stef already put here, so that it should be easy for anybody to load > CuisTranscript into a Pharo image and have a look. Today I did a new commit to the Cuis repo. The Cuis image is now in Cog format (6505) instead of Closures format (6504). I hope this allows you to run Cuis in your system. I also addressed some of the issues you raised. I optimized the refresh, and avoided the "bolder text" effect. Now, Time millisecondsToRun: [ 1000 timesRepeat: [ Transcript show: 'x' ] ]. takes 2 ms, even while updating the Display. (Hundreds of times faster). I hope the slugginess you see also gets better. > IMHO another solution has to be found, or a big review of this has > to be done. > see details in fogbugz entry. > > -- > Regards, > > Alain Cheers, Juan Vuletich

May 13, 2015

Re: [Pharo-dev] Transcript needs your love

by Ben Coman

On Wed, May 13, 2015 at 6:32 AM, Alain Rastoul <alf.mmm.cat(a)gmail.com> wrote: > Le 12/05/2015 19:02, Alain Rastoul a Ã©crit : > >> Le 08/05/2015 11:34, stepharo a Ã©crit : >> >>> Hi guys >>> >>> the Transcript in Pharo is that it's not asynchronous so I can't use it >>> in VM development to show the current progress of the simulation. For >>> example: >>> 1 to: 100 do: [ :i | >>> 0.1 seconds asDelay wait. >>> Transcript show: 'x'. ] >>> => on Squeak, this shows a x every 0.1 second in the Transcript >>> => on Pharo, nothing happens during 10 seconds then all the x are shown. >>> >>> https://pharo.fogbugz.com/default.asp?15515 >>> >>> >>> Hi, >> I updated the fogbugz entry with a changeset containing the sources Stef >> already put here, so that it should be easy for anybody to load >> CuisTranscript into a Pharo image and have a look. >> >> IMHO another solution has to be found, or a big review of this has to be >> done. >> see details in fogbugz entry. >> >> > A very ugly but simple workaround could be > > ThreadSafeTranscript>>endEntry: > accessSemaphore critical: [ > deferredEndEntry := true . > " is Synchronous coudl be a setting" > self isSynchronous > ifTrue: [ > self stepGlobal . "handles appendEntry" > World displayWorldSafely "redraw now" ] ]. > > with a setings for isSynchronous > ugly but works, > > The problem with this is that non-UI threads call #endEntry: which bypasses the intent of #stepGlobal only being called from the UI thread. (btw I should update its comment to reflect this.) So the minimal effective change would be... ThreadSafeTranscript>>endEntry: accessSemaphore critical: [ deferredEndEntry := true ]. (UIManager default uiProcess = Processor activeProcess) ifTrue: [ self stepGlobal. World displayWorldSafely. ]. However this would need to massaged to remove the referenced global classes (UIManager and World) to avoid introducing dependencies breaking the Image shrink work. Maybe these can be passed into the Transcript object where #stepGlobal is currently called from. Note that #stepGlobal already uses accessSemaphore, so doesn't need to be protected here. cheers -ben

May 13, 2015

[pharo-project/pharo-core]

by GitHub

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

May 13, 2015

[pharo-project/pharo-core] 294023: 50045

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 294023693d55e4de1cd73d5e961f72ed42c34d62 https://github.com/pharo-project/pharo-core/commit/294023693d55e4de1cd73d5e… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-05-13 (Wed, 13 May 2015) Changed paths: M FileSystem-Core.package/Path.class/class/private/absoluteWindowsPathRegex.st M Kernel.package/Object.class/class/instance creation/newFrom_.st A Keymapping-KeyCombinations.package/KMNamedCharKeyCombination.class/README.md A Keymapping-KeyCombinations.package/KMNamedCharKeyCombination.class/class/accessing/specialKeys.st A Keymapping-KeyCombinations.package/KMNamedCharKeyCombination.class/class/initialization/newSpecialKeys.st A Keymapping-KeyCombinations.package/KMNamedCharKeyCombination.class/class/instance creation/key_name_.st A Keymapping-KeyCombinations.package/KMNamedCharKeyCombination.class/class/instance creation/space.st A Keymapping-KeyCombinations.package/KMNamedCharKeyCombination.class/class/testing/ifSpecialKey_do_.st A Keymapping-KeyCombinations.package/KMNamedCharKeyCombination.class/definition.st A Keymapping-KeyCombinations.package/KMNamedCharKeyCombination.class/instance/accessing/name.st A Keymapping-KeyCombinations.package/KMNamedCharKeyCombination.class/instance/accessing/name_.st R Keymapping-KeyCombinations.package/KMUntypeableSingleKeyCombination.class/instance/printing/printOn_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50044.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50045.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50044.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50045.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Tool-FilePackageBrowser.package/FileContentsBrowser.class/class/System-FileRegistry/serviceBrowseCode.st Log Message: ----------- 50045 15525 cleanup from issue 13065 https://pharo.fogbugz.com/f/cases/15525 15531 Fix typo in method comment in Object>>newFrom: https://pharo.fogbugz.com/f/cases/15531 15533 Uppercase button title for Code when selecting an st file in FileList https://pharo.fogbugz.com/f/cases/15533 15529 add Character space to the special km single Keycombination class https://pharo.fogbugz.com/f/cases/15529 http://files.pharo.org/image/50/50045.zip

May 13, 2015

Re: [Pharo-dev] Code generation for ASTs with syntax errors

by Denis Kudriashov

Thanks's Marcus. It is beautiful thing. Is parsing locate errors by "dot"s? I mean how it will parse "3+. 1+2"? It will be super cool if we have only "3+." as error but remains code as good one Best regards, Denis 2015-05-13 9:35 GMT+03:00 Marcus Denker <marcus.denker(a)inria.fr>: > We can parse code with syntax errors: it generates partial ASTs with the > faulty part of the input as a RBParseErrorNode. > > Only three methods are needed to allow generating executable methods from > such an AST: the SyntaxErrorNotification > is raised at runtime instead of compile time. > > testEvalSimpleMethodWithError > | ast cm | > ast := OpalCompiler new > source: 'method 3+'; > useFaultyForParsing: true; > parse. > > self assert: ast isMethod. > self assert: ast isFaulty. > > cm := ast compiledMethod. > self should: [cm valueWithReceiver: nil arguments: #()] raise: > SyntaxErrorNotification > > The syntax error instance is compiled in via a literal variable, in the > end the only thing needed was: > > visitParseErrorNode: anErrorNode > methodBuilder > pushLiteralVariable: #error -> anErrorNode > asSyntaxErrorNotification; > send: #signal. > > This is in #50044. > > Future work: introduce a RuntimeSyntaxError that can be turned off per > error and globally. > > Marcus >

May 13, 2015

Re: [Pharo-dev] Installing trait blow the method def in hierarchy

by Camille

> On 13 May 2015, at 10:42, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > >> >> On 13 May 2015, at 09:25, Nicolai Hess <nicolaihess(a)web.de <mailto:nicolaihess@web.de>> wrote: >> >> >> 2015-05-12 12:06 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>>: >> Hi, >> >> Iâve noticed that if you install a trait on a class and a trait defines explicit requirement method, and this method is defined in a super class, it is being looked up during execution through #explicitRequirement method. It was slowing down my execution by almost 20%. Is there a special way to use a Trait to avoid that, or itâs work-in-progress solution? >> >> I find this behavior questionable, when did this change? ( I thought self explicitRequirement always signals an error and does not try to find the method in the superclass chain). >> Anyway, if you want to use the super class method, you can just remove the method from the trait usage. >> >> ASuperClass subclass: #MySubclass >> uses: ATrait - {#theMethodDefinedInSuperclassAndTrait } >> instanceVariableNames: '' >> classVariableNames: '' >> category: â' > > Good to know, thanks. I donât know the philosophy behind this case, but from my point of view - trait requires a method, and the class has it, itâs just that the method is defined higher in the hierarchy. I agree, this is the behavior I would expect too. From this point of view, the problem is the 20% slowdown. A solution would be that traits does not install explicit requirements in their users if suitable methods are already in their hierarchy. Then traits needs to listen to method addition/removal announcements to install/remove the explicit requirement methods in their users accordingly. Another solution is to never install explicit requirement methods and have a modified version of doesNotUnderstand: that detect when the missing method is an explicit requirement. So we have four solution: - explicit requirements does not override methods in the hierarchies of the trait users: 1. current situation: nothing to do but 20% slowdown (but no slowdown by removing the explicit requirement from the trait composition). 2. automatic installation/removal of explicit requirement in traits users: adds more complexity in trait installation logic but transparent to user. 3. dynamic detection of explicit requirement in doesNotUnderstand: slower DNU but still transparent to user. - explicit requirements always override methods in the hierarchies of the trait users: 4. explicit resolution by removing overriding explicit requirements from trait compositions: less magic but maybe confusing for users I vote for 2 (then 1, 3, 4). Camille > Uko > >> >> >> regards >> Nicolai >> >> >> Uko

May 13, 2015

Re: [Pharo-dev] Installing trait blow the method def in hierarchy

by Yuriy Tymchuk

> On 13 May 2015, at 09:25, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > 2015-05-12 12:06 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>>: > Hi, > > Iâve noticed that if you install a trait on a class and a trait defines explicit requirement method, and this method is defined in a super class, it is being looked up during execution through #explicitRequirement method. It was slowing down my execution by almost 20%. Is there a special way to use a Trait to avoid that, or itâs work-in-progress solution? > > I find this behavior questionable, when did this change? ( I thought self explicitRequirement always signals an error and does not try to find the method in the superclass chain). > Anyway, if you want to use the super class method, you can just remove the method from the trait usage. > > ASuperClass subclass: #MySubclass > uses: ATrait - {#theMethodDefinedInSuperclassAndTrait } > instanceVariableNames: '' > classVariableNames: '' > category: â' Good to know, thanks. I donât know the philosophy behind this case, but from my point of view - trait requires a method, and the class has it, itâs just that the method is defined higher in the hierarchy. Uko > > > regards > Nicolai > > > Uko >

May 13, 2015

Re: [Pharo-dev] Code generation for ASTs with syntax errors

by Damien Pollet

On 13 May 2015 at 08:35, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Only three methods are needed to allow generating executable methods from > such an AST: the SyntaxErrorNotification > is raised at runtime instead of compile time. > I can hear the noise of eyebrows raising in the compiler community :) Syntax errors shouldn't require immediate fixing during compilation per se, but there should be a way to deal with them "at compile time" âwhatever that means for us. For instance, faulty methods could have a flashy icon in the browser; I think I'd even color the whole package-class-protocol-selector in red if either of them contain faulty methods. -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

May 13, 2015