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

Re: [Pharo-dev] [Pharo-users] [SURVEY] Pillar input/output files.

by H. Hirzel

On 5/4/15, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > If I understand correctly... then, why the pillar.conf is not just a pillar > file? (And the conf is the header if the file?) :) That would be fine not to have a pillar.conf file but just a heard in a regular pillar file which does some configuration. --Hannes > > El lun., 4 de may. de 2015 a la(s) 2:50 p. m., Damien Cassou < > damien.cassou(a)inria.fr> escribiÃ³: > >> >> Cyril Ferlicot <cyril.ferlicot(a)gmail.com> writes: >> >> > Hi, >> > I'm currently working on the way we manage the input files and the >> output files. >> > The way we manage the files now makes hard some improvement of Pillar. >> > That's why with Damien we though about makes some changes. The changes >> > are big so I wanted to talk about that with you. >> > We propose to have always 1 file with all the work inside. That can >> > use the inputFile tag. For example: >> > >> > "${inputFile:Chapter1.pillar}$ >> > >> > ${inputFile:Chapter2.pillar}$ >> > >> > ${inputFile:Chapter3.pillar}$ >> > >> > ${inputFile:Chapter4.pillar}$" >> > >> > And the option "separateOutputFiles" will now create 1 file each time >> > we have a new Chapter. (!Level 1 header). >> > That will make simpler the way to number everything and to create >> > anchor because those 2 doesn't work well with the "separateOutputFile" >> > option. >> > >> > What do you thing? That would be good with you? >> >> this change proposes to remove the option inputFiles from Pillar. Pillar >> will now take only 1 Pillar input file that must include the rest. This >> will simplify pillar.conf, this will simplify compile.sh, this will make >> it easier for the author to understand the process, and this will >> simplify Pillar's implementation. With this in place, we think we can >> fix the problems with anchors and inter-chapter links. >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Success is the ability to go from one failure to another without >> losing enthusiasm." --Winston Churchill >> >> >

May 18, 2015

Re: [Pharo-dev] Main pillar web site?

by H. Hirzel

Thank you. Is it possible to add a short paragraph about the Rational for Pillar? It seems to be a text format for the PRnnn classes which is easy to parse. Which formats does the Pillar documentation tool chain read and which ones are generated? --Hannes On 5/4/15, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > Hi. > The documentation is now here: > https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… > > We're still updating the documentation so that still can change. > > On 4 May 2015 at 16:14, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >> Thank you! >> >> Here is the summary >> >> >> >> Pillar documentation >> ==================== >> >> Start page >> http://www.smalltalkhub.com/#!/~Pier/Pillar >> >> >> Documentation >> https://github.com/pillar-markup/pillar-documentation >> >> >> >> First Google hit >> https://ci.inria.fr/pharo-contribution/job/PharoProjectCatalog/HTML_Report/… >> >> Leads to Pharo contribution CI server (Confirm security exception, it is >> safe). >> >> >> >> Pillar tool chain repositories >> ------------------------------- >> >> https://github.com/pillar-markup >> > > > > -- > Cheers > Cyril Ferlicot > >

May 18, 2015

Re: [Pharo-dev] Loading Pillar in 4.0

by H. Hirzel

Any news on this? --Hannes On 5/12/15, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > Hi, > i'll correct that un the next version of pillar! > Thank you. > > Le mardi 12 mai 2015, Sean P. DeNigris <sean(a)clipperadams.com> a Ã©crit : > >> Loading from the Configuration Browser gives: >> >> This package depends on the following classes: >> PRWarning >> You must resolve these dependencies before you will be able to load these >> definitions: >> PRParameterWarning >> >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: >> http://forum.world.st/Loading-Pillar-in-4-0-tp4825915.html >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> >> > > -- > Cheers > Cyril Ferlicot >

May 18, 2015

Re: [Pharo-dev] Performance of GT-Inspector on large collections

by Cyril Ferlicot

Exp with GT-Inspector: 0:00:00:23.492 Exp with EyeInspector: 0:00:00:00.629 for me On 18 May 2015 at 16:57, Alejandro Infante <alejandroinfante91(a)gmail.com> wrote: > Hello, > I have noticed that working with large collections in the new inspector is noticeable slower than with the old one :( > > I executed a tiny benchmark that is just inspecting a 1.000.000 objects collection: > âââââââââ > Smalltalk tools inspectorTool: GTInspector. > Transcript show: 'Exp with GT-Inspector: '. > Transcript show: [ > ((1 to: 1000000) collect: [ :i | Object new ]) inspect ] timeToRun. > Transcript cr. > Smalltalk tools inspectorTool: EyeInspector. > Transcript show: 'Exp with EyeInspector: '. > Transcript show: [ > ((1 to: 1000000) collect: [ :i | Object new ]) inspect ] timeToRun. > âââââââââ > > And the results were: > Exp with GT-Inspector: 0:00:01:04.979 > Exp with EyeInspector: 0:00:00:00.381 > > Are you facing the same issue? > > Alejandro -- Cheers Cyril Ferlicot

May 18, 2015

Re: [Pharo-dev] Performance of GT-Inspector on large collections

by Tudor Girba

Yes. Doru On Mon, May 18, 2015 at 4:57 PM, Alejandro Infante < alejandroinfante91(a)gmail.com> wrote: > Hello, > I have noticed that working with large collections in the new inspector is > noticeable slower than with the old one :( > > I executed a tiny benchmark that is just inspecting a 1.000.000 objects > collection: > âââââââââ > Smalltalk tools inspectorTool: GTInspector. > Transcript show: 'Exp with GT-Inspector: '. > Transcript show: [ > ((1 to: 1000000) collect: [ :i | Object new ]) inspect ] > timeToRun. > Transcript cr. > Smalltalk tools inspectorTool: EyeInspector. > Transcript show: 'Exp with EyeInspector: '. > Transcript show: [ > ((1 to: 1000000) collect: [ :i | Object new ]) inspect ] > timeToRun. > âââââââââ > > And the results were: > Exp with GT-Inspector: 0:00:01:04.979 > Exp with EyeInspector: 0:00:00:00.381 > > Are you facing the same issue? > > Alejandro > -- www.tudorgirba.com "Every thing has its own flow"

May 18, 2015

Performance of GT-Inspector on large collections

by Alejandro Infante

Hello, I have noticed that working with large collections in the new inspector is noticeable slower than with the old one :( I executed a tiny benchmark that is just inspecting a 1.000.000 objects collection: âââââââââ Smalltalk tools inspectorTool: GTInspector. Transcript show: 'Exp with GT-Inspector: '. Transcript show: [ ((1 to: 1000000) collect: [ :i | Object new ]) inspect ] timeToRun. Transcript cr. Smalltalk tools inspectorTool: EyeInspector. Transcript show: 'Exp with EyeInspector: '. Transcript show: [ ((1 to: 1000000) collect: [ :i | Object new ]) inspect ] timeToRun. âââââââââ And the results were: Exp with GT-Inspector: 0:00:01:04.979 Exp with EyeInspector: 0:00:00:00.381 Are you facing the same issue? Alejandro

May 18, 2015

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

by Franck Warlouzet

Ok I was not looking the solution in Nautilus, but in Rubric ... Thanks a lot ! My eyes are alive again Franck To: pharo-dev(a)lists.pharo.org From: pharo-dev(a)lists.pharo.org CC: alain.plantec(a)yahoo.com Subject: Re: [Pharo-dev] Trying to use Rubric in Nautilus .... Date: Mon, 18 May 2015 07:38:15 -0700 --PiÃ¨ce jointe du message transmise-- Subject: Re: [Pharo-dev] Trying to use Rubric in Nautilus .... From: alain.plantec(a)yahoo.com Date: Mon, 18 May 2015 16:37:59 +0200 To: pharo-dev(a)lists.pharo.org also send #withCodeSizeFeedback to have almost the same look as with PluggableTextMorph. AbstractNautilusUI >>buildNewSourceTextArea sourceTextArea := self textMorphClass on: self text: #sourceCodeFrom: accept: #compileSource:notifying: readSelection: #contentsSelectionFrom: menu: #sourceCodeMenu:shifted:. sourceTextArea askBeforeDiscardingEdits: true; beForSmalltalkCode; withLineNumbers; withCodeSizeFeedback; <==== here ====== beWrapped; vResizing: #spaceFill; hResizing: #spaceFill; font: StandardFonts codeFont; spaceFillWeight: 3; on: #keyStroke send: #keyStroke:fromSourceCodeMorph: to: self. self setSourceCodeShorcutsTo: sourceTextArea. ^ sourceTextArea Alain On 18 May 2015, at 16:17, Alain Plantec <alain.plantec(a)yahoo.com> wrote:Hello Franck, just changed shoutAboutToStyle: as follow:AbstractNautilusUI>>shoutAboutToStyle: aPluggableShoutMorphOrView âThe comments are not styled" ^ aPluggableShoutMorphOrView ~= commentTextArea and it seems to work. Now, pay attention that, with Rubric, this is the editing mode that is passed as argument (for aPluggableShoutMorphOrView). Here, a RubSmalltalkCodeMode. if you plan to use a Rubric also for the comments, then, normally shoutAboutToStyle: will not be sent because I guess a RubPlainTextMode will be used for the comment pane. This mode do not use shout.In that case the final version should be: AbstractNautilusUI>>shoutAboutToStyle: aPluggableShoutMorphOrView ^ true CheersAlain On 18 May 2015, at 14:41, Franck Warlouzet <franck.warlouzet(a)hotmail.fr> wrote:Hi, With Alain's last commit of Rubric (205) we made a few changes to put Rubric in Nautilus. You can see thoses changes in the attached file. As you can see there is no colors in the browser... Is RubScrolledTextMorph>>beForSmalltalkCode the good option ? I thought there would be just an option like aboutToStyle: true or something like that but there is not. I do not know if I missed something obvious or if I have to add the connection to RubShoutStylerDecorator. Any idea everyone ? I am losing my eyes with uncolored code but I guess it is worth it. Thanks, Franck To: pharo-dev(a)lists.pharo.org From: pharo-dev(a)lists.pharo.org CC: alain.plantec(a)yahoo.com Subject: Re: [Pharo-dev] Trying to use Rubric in Nautilus .... Date: Thu, 14 May 2015 05:16:30 -0700 --PiÃ¨ce jointe du message transmise-- Subject: Re: [Pharo-dev] Trying to use Rubric in Nautilus .... From: alain.plantec(a)yahoo.com Date: Thu, 14 May 2015 14:16:16 +0200 To: pharo-dev(a)lists.pharo.org done & committedCheersAlain On 14 May 2015, at 12:06, Alain Plantec <alain.plantec(a)yahoo.com> wrote:ahh, good remark :)the menu stuff is not finished.I do it nowthanks Alain On 13 May 2015, at 18:09, Franck Warlouzet <franck.warlouzet(a)hotmail.fr> wrote:Hi alain thanks a lot! This helps us a lot. We got nearly something working. We will produce a list of methods and changes we had to do. see in the attached cs. Now lookupMenu "default implementation of the algorithm that lookup the menu" | default | default := [ self editingMode menu ]. ^ self model ifNil: [ default value ] ifNotNil: [ :m | m menu ifNil: [ default value ] ] We add a new method in nautilus that creates a menu as follow because m is our NautilusModel menu ^ self sourceCodeMenu: MenuMorph new shifted: false. But I was wondering why m menu does not take into account the information we passed when we created the rubPluggable sourceTextArea := self textMorphClass on: self text: #sourceCodeFrom: accept: #compileSource:notifying: readSelection: #contentsSelectionFrom: menu: #sourceCodeMenu:shifted:. I see that RubEditingArea has a policy but we could find how we can improve RubPluggable to use the menu: To: pharo-dev(a)lists.pharo.org From: pharo-dev(a)lists.pharo.org CC: alain.plantec(a)yahoo.com Subject: Re: [Pharo-dev] Trying to use Rubric in Nautilus .... Date: Wed, 13 May 2015 07:26:15 -0700 --PiÃ¨ce jointe du message transmise-- Subject: Re: [Pharo-dev] Trying to use Rubric in Nautilus .... From: alain.plantec(a)yahoo.com Date: Wed, 13 May 2015 16:25:34 +0200 To: pharo-dev(a)lists.pharo.org 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. cheersAlain 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 sourceCodeAnd 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 <glueRubNautilus.2.cs> <Unnamed.cs>

May 18, 2015

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

by Alain Plantec

also send #withCodeSizeFeedback to have almost the same look as with PluggableTextMorph. AbstractNautilusUI >>buildNewSourceTextArea sourceTextArea := self textMorphClass on: self text: #sourceCodeFrom: accept: #compileSource:notifying: readSelection: #contentsSelectionFrom: menu: #sourceCodeMenu:shifted:. sourceTextArea askBeforeDiscardingEdits: true; beForSmalltalkCode; withLineNumbers; withCodeSizeFeedback; <==== here ====== beWrapped; vResizing: #spaceFill; hResizing: #spaceFill; font: StandardFonts codeFont; spaceFillWeight: 3; on: #keyStroke send: #keyStroke:fromSourceCodeMorph: to: self. self setSourceCodeShorcutsTo: sourceTextArea. ^ sourceTextArea Alain > On 18 May 2015, at 16:17, Alain Plantec <alain.plantec(a)yahoo.com> wrote: > > Hello Franck, > > just changed shoutAboutToStyle: as follow: > AbstractNautilusUI>>shoutAboutToStyle: aPluggableShoutMorphOrView > âThe comments are not styled" > ^ aPluggableShoutMorphOrView ~= commentTextArea > > and it seems to work. > > Now, pay attention that, with Rubric, this is the editing mode that is passed as argument (for aPluggableShoutMorphOrView). Here, a RubSmalltalkCodeMode. > > if you plan to use a Rubric also for the comments, then, normally shoutAboutToStyle: will not be sent because I guess a RubPlainTextMode will be used for the comment pane. This mode do not use shout. > In that case the final version should be: > > AbstractNautilusUI>>shoutAboutToStyle: aPluggableShoutMorphOrView > ^ true > > > Cheers > Alain > > >> On 18 May 2015, at 14:41, Franck Warlouzet <franck.warlouzet(a)hotmail.fr <mailto:franck.warlouzet@hotmail.fr>> wrote: >> >> Hi, >> >> With Alain's last commit of Rubric (205) we made a few changes to put Rubric in Nautilus. You can see thoses changes in the attached file. >> As you can see there is no colors in the browser... Is RubScrolledTextMorph>>beForSmalltalkCode the good option ? I thought there would be just an option like aboutToStyle: true or something like that but there is not. I do not know if I missed something obvious or if I have to add the connection to RubShoutStylerDecorator. Any idea everyone ? >> I am losing my eyes with uncolored code but I guess it is worth it. >> >> Thanks, >> >> Franck >> >> >> To: pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org> >> From: pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org> >> CC: alain.plantec(a)yahoo.com <mailto:alain.plantec@yahoo.com> >> Subject: Re: [Pharo-dev] Trying to use Rubric in Nautilus .... >> Date: Thu, 14 May 2015 05:16:30 -0700 >> >> >> >> --PiÃ¨ce jointe du message transmise-- >> Subject: Re: [Pharo-dev] Trying to use Rubric in Nautilus .... >> From: alain.plantec(a)yahoo.com <mailto:alain.plantec@yahoo.com> >> Date: Thu, 14 May 2015 14:16:16 +0200 >> To: pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org> >> >> done & committed >> Cheers >> Alain >> On 14 May 2015, at 12:06, Alain Plantec <alain.plantec(a)yahoo.com <mailto:alain.plantec@yahoo.com>> wrote: >> >> ahh, good remark :) >> the menu stuff is not finished. >> I do it now >> thanks >> Alain >> >> On 13 May 2015, at 18:09, Franck Warlouzet <franck.warlouzet(a)hotmail.fr <mailto:franck.warlouzet@hotmail.fr>> wrote: >> >> Hi alain >> >> thanks a lot! >> This helps us a lot. We got nearly something working. We will produce a list of methods and changes we had to do. >> see in the attached cs. >> >> Now >> >> lookupMenu >> "default implementation of the algorithm that lookup the menu" >> >> | default | >> default := [ self editingMode menu ]. >> ^ self model >> ifNil: [ default value ] >> ifNotNil: [ :m | m menu ifNil: [ default value ] ] >> >> We add a new method in nautilus that creates a menu as follow >> because m is our NautilusModel >> >> menu >> ^ self sourceCodeMenu: MenuMorph new shifted: false. >> >> But I was wondering why m menu does not take into account the information we passed when we created the rubPluggable >> >> sourceTextArea := self textMorphClass >> on: self >> text: #sourceCodeFrom: >> accept: #compileSource:notifying: >> readSelection: #contentsSelectionFrom: >> menu: #sourceCodeMenu:shifted:. >> >> I see that >> RubEditingArea has a policy but we could find how we can improve RubPluggable to use the menu: >> >> >> >> >> To: pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org> >> From: pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org> >> CC: alain.plantec(a)yahoo.com <mailto:alain.plantec@yahoo.com> >> Subject: Re: [Pharo-dev] Trying to use Rubric in Nautilus .... >> Date: Wed, 13 May 2015 07:26:15 -0700 >> >> >> >> --PiÃ¨ce jointe du message transmise-- >> Subject: Re: [Pharo-dev] Trying to use Rubric in Nautilus .... >> From: alain.plantec(a)yahoo.com <mailto:alain.plantec@yahoo.com> >> Date: Wed, 13 May 2015 16:25:34 +0200 >> To: pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org> >> >> 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 <mailto:stepharo@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 >> >> >> >> >> >> <glueRubNautilus.2.cs> >> >> >> <Unnamed.cs> >

May 18, 2015

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

by Alain Plantec

Hello Franck, just changed shoutAboutToStyle: as follow: AbstractNautilusUI>>shoutAboutToStyle: aPluggableShoutMorphOrView âThe comments are not styled" ^ aPluggableShoutMorphOrView ~= commentTextArea and it seems to work. Now, pay attention that, with Rubric, this is the editing mode that is passed as argument (for aPluggableShoutMorphOrView). Here, a RubSmalltalkCodeMode. if you plan to use a Rubric also for the comments, then, normally shoutAboutToStyle: will not be sent because I guess a RubPlainTextMode will be used for the comment pane. This mode do not use shout. In that case the final version should be: AbstractNautilusUI>>shoutAboutToStyle: aPluggableShoutMorphOrView ^ true Cheers Alain > On 18 May 2015, at 14:41, Franck Warlouzet <franck.warlouzet(a)hotmail.fr> wrote: > > Hi, > > With Alain's last commit of Rubric (205) we made a few changes to put Rubric in Nautilus. You can see thoses changes in the attached file. > As you can see there is no colors in the browser... Is RubScrolledTextMorph>>beForSmalltalkCode the good option ? I thought there would be just an option like aboutToStyle: true or something like that but there is not. I do not know if I missed something obvious or if I have to add the connection to RubShoutStylerDecorator. Any idea everyone ? > I am losing my eyes with uncolored code but I guess it is worth it. > > Thanks, > > Franck > > > To: pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org> > From: pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org> > CC: alain.plantec(a)yahoo.com <mailto:alain.plantec@yahoo.com> > Subject: Re: [Pharo-dev] Trying to use Rubric in Nautilus .... > Date: Thu, 14 May 2015 05:16:30 -0700 > > > > --PiÃ¨ce jointe du message transmise-- > Subject: Re: [Pharo-dev] Trying to use Rubric in Nautilus .... > From: alain.plantec(a)yahoo.com <mailto:alain.plantec@yahoo.com> > Date: Thu, 14 May 2015 14:16:16 +0200 > To: pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org> > > done & committed > Cheers > Alain > On 14 May 2015, at 12:06, Alain Plantec <alain.plantec(a)yahoo.com <mailto:alain.plantec@yahoo.com>> wrote: > > ahh, good remark :) > the menu stuff is not finished. > I do it now > thanks > Alain > > On 13 May 2015, at 18:09, Franck Warlouzet <franck.warlouzet(a)hotmail.fr <mailto:franck.warlouzet@hotmail.fr>> wrote: > > Hi alain > > thanks a lot! > This helps us a lot. We got nearly something working. We will produce a list of methods and changes we had to do. > see in the attached cs. > > Now > > lookupMenu > "default implementation of the algorithm that lookup the menu" > > | default | > default := [ self editingMode menu ]. > ^ self model > ifNil: [ default value ] > ifNotNil: [ :m | m menu ifNil: [ default value ] ] > > We add a new method in nautilus that creates a menu as follow > because m is our NautilusModel > > menu > ^ self sourceCodeMenu: MenuMorph new shifted: false. > > But I was wondering why m menu does not take into account the information we passed when we created the rubPluggable > > sourceTextArea := self textMorphClass > on: self > text: #sourceCodeFrom: > accept: #compileSource:notifying: > readSelection: #contentsSelectionFrom: > menu: #sourceCodeMenu:shifted:. > > I see that > RubEditingArea has a policy but we could find how we can improve RubPluggable to use the menu: > > > > > To: pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org> > From: pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org> > CC: alain.plantec(a)yahoo.com <mailto:alain.plantec@yahoo.com> > Subject: Re: [Pharo-dev] Trying to use Rubric in Nautilus .... > Date: Wed, 13 May 2015 07:26:15 -0700 > > > > --PiÃ¨ce jointe du message transmise-- > Subject: Re: [Pharo-dev] Trying to use Rubric in Nautilus .... > From: alain.plantec(a)yahoo.com <mailto:alain.plantec@yahoo.com> > Date: Wed, 13 May 2015 16:25:34 +0200 > To: pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org> > > 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 <mailto:stepharo@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 > > > > > > <glueRubNautilus.2.cs> > > > <Unnamed.cs>

May 18, 2015

[pharo-project/pharo-core] 0c77aa: 50049

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 0c77aac8e97adf1d258ac772125041bcd6628980 https://github.com/pharo-project/pharo-core/commit/0c77aac8e97adf1d258ac772… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-05-18 (Mon, 18 May 2015) Changed paths: R Athens-Cairo.package/AthensCairoCanvas.class/instance/drawing text/setFont_.st R Athens-Cairo.package/AthensCairoPDFSurface.class/instance/private/newCanvas.st A Athens-Core.package/extension/BitmapFillStyle/instance/asAthensPaintOn_.st M Athens-Morphic.package/AthensParagraph.class/instance/as yet unclassified/secondarySelection_.st R Athens-Morphic.package/AthensWorldMorph.class/instance/world state/viewBox_.st R Athens-Morphic.package/AthensWrapWorldMorph.class/instance/drawing/fullDrawOnAthensCanvas_.st R Athens-Morphic.package/AthensWrapWorldMorph.class/instance/drawing/render.st M Athens-Morphic.package/extension/EllipseMorph/instance/asAthensShapeOn_.st M Athens-Morphic.package/extension/EllipseMorph/instance/drawOnAthensCanvas_.st A Athens-Morphic.package/extension/PolygonMorph/instance/adjustSegmentPointsForArrows.st A Athens-Morphic.package/extension/PolygonMorph/instance/asAthensCurvedOpenPathOn_.st A Athens-Morphic.package/extension/PolygonMorph/instance/asAthensCurvedPathOn_.st A Athens-Morphic.package/extension/PolygonMorph/instance/asAthensLinePathOn_.st A Athens-Morphic.package/extension/PolygonMorph/instance/asAthensPathOn_.st A Athens-Morphic.package/extension/PolygonMorph/instance/computeCurvedSegmentCtrlPoints.st A Athens-Morphic.package/extension/PolygonMorph/instance/drawArrowOnAthensCanvas_at_from_.st A Athens-Morphic.package/extension/PolygonMorph/instance/drawArrowsOnAthensCanvas_.st A Athens-Morphic.package/extension/PolygonMorph/instance/drawOnAthensCanvas_.st A Athens-Morphic.package/extension/PolygonMorph/instance/hasTwoColorDash.st A Athens-Morphic.package/extension/PolygonMorph/instance/setDashOnStroke_.st A Athens-Morphic.package/extension/PolygonMorph/instance/setSecondColorDashOnStroke_.st A ConfigurationOfAthens.package/ConfigurationOfAthens.class/instance/versions/version35_.st M Manifest-Core.package/extension/RPackage/instance/packageManifest.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50048.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50049.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50048.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50049.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50049 15557 New PackageManifests should be classes, not instances https://pharo.fogbugz.com/f/cases/15557 15556 use new athens configuration 3.5 https://pharo.fogbugz.com/f/cases/15556 http://files.pharo.org/image/50/50049.zip

May 18, 2015