February 2018 - Pharo-users

Re: [Pharo-users] Dynamically updating the inspector window

by Andrei Chis

Hi, Are you in Pharo 6.1? There is a setting to enable automatic refresh in the inspector. I think it's called Step Refresh in the settings browser. Should be enabled by default in Pharo 7. Just now all presentations from the inspector have the automatic refresh implemented. Cheers, Andrei On Thu, Mar 1, 2018 at 12:52 AM, Andy Burnett < andy.burnett(a)knowinnovation.com> wrote: > Is there a way to make the inspector automatically update itself, when the > value it is inspecting changes? For example, if I were inspecting an > array, and at:1 put: 'blah' I would like the inspector to reflect that > change. > > I know I can get the window to update by clicking the refresh icon, I just > wondered if there is a 'live' way to do this? > > Cheers > Andy >

Feb. 28, 2018

Dynamically updating the inspector window

by Andy Burnett

Is there a way to make the inspector automatically update itself, when the value it is inspecting changes? For example, if I were inspecting an array, and at:1 put: 'blah' I would like the inspector to reflect that change. I know I can get the window to update by clicking the refresh icon, I just wondered if there is a 'live' way to do this? Cheers Andy

Feb. 28, 2018

Re: [Pharo-users] Exporting Pillar docs (Pillar7)

by Offray Vladimir Luna CÃ¡rdenas

Hi Arturo, It seems that you have a project with documentation is pretty important. I don't want to start a holly war pointing that there is alternatives to Pillar in Pharo, but maybe you should check Grafoscopio + Pandoc. We can write pretty complex documents using it, like the Grafoscopio User Manual [1], the Data Journalism Handbook[2] and Pasos para una Biblioteca Digital de BogotÃ¡[3] (both in Spanish). [1] http://mutabit.com/repos.fossil/grafoscopio/doc/tip/Docs/En/Books/Manual/ma… [2] http://mutabit.com/repos.fossil/mapeda/ [3] http://mutabit.com/repos.fossil/dataweek/doc/tip/Artefactos/BibliotecaDigit… Cheers, Offray On 27/02/18 08:42, Arturo Zambrano wrote: > Thanks for your help. > > I will use markdown as a preview, so th PR*Writer write:document is OK. > For the last phase I plan to use latex to generate a pdf following > certain presentation rules. > > I wonder if it is possible to use pillar 7 templates programmatically. > Is there some example I can follow? > > Thanks again! > > > > On Mon, Feb 19, 2018 at 6:42 AM, Guillermo Polito > <guillermopolito(a)gmail.com <mailto:guillermopolito@gmail.com>> wrote: > > > > On Sun, Feb 18, 2018 at 9:01 PM, Stephane Ducasse > <stepharo.self(a)gmail.com <mailto:stepharo.self@gmail.com>> wrote: > > Hi arturo > > What you saw is the pipeline to produce book and others. Now I > do not > think that you need it. > To export markdown you do not need the pillar configuration > and the rest. > Check the chapter 6 in the publishing a booklet with pillar > document. > > You can just get your document using the Pillar parser. > > | wiki doc | > wiki := '!My Document'. > doc := PRPillarParser parse: wiki > > Or from a file: > > Â Â Â PRPillarParser parse: (FileSystem workingDirectory / > 'foo.pillar') > > Â Â Â Â Â readStream > > You can also instantiate the document model, one node after > the other, > start- ing with PRDocument and adding sub-instances of > PRDocumentItem: > > Â Â Â | document title figure| > > Â Â Â document := PRDocument new. > > Â Â Â title := PRHeader new > > Â Â Â Â Â level: 1; > > Â Â Â Â Â add: (PRText content: 'foo'); > > Â Â Â Â Â yourself. > > Â Â Â figure := PRFigure new > > Â Â Â Â Â add: (PRText content: 'Alias'); > > then to export in HTML you just ask the htmlWriter. So I think > that > this is the same for markdown. > > PRHTMLWriter write: document > > > Now pay attention because we are currently rewriting the > pipeline of > document production in Pillar 70. > > > Yeh, but ideally the pipeline should only automatically > orchestrate what people should be still able to do programatically :)Â > > So I think keeping > > PRHTMLWriter write: document > > and > > PRHTMLWriter write: document toStream: ... > > & family, is good. > Â > > This is why this is not in master but in a specific branch. > > Stef > > > > > > > On Sun, Feb 18, 2018 at 7:13 PM, Arturo Zambrano > <arturo.zambrano(a)gmail.com <mailto:arturo.zambrano@gmail.com>> > wrote: > > Hi, > > I figured it out (at least in part) > > > >Â Â Â Â configuration := PRPillarConfiguration new. > >Â Â Â Â configuration outputType: PRMarkdownWriter. > >Â Â Â Â export:=PRExportPhase new . > >Â Â Â Â export executeOn: > >Â Â (PRCompilationContext withDocument: document > withConfiguration: > > configuration) > > > > > > This code snipped generates a Json file which contains the > markdown... how > > do I generate just the markdown? > > > > TIA > > Arturo > > > > > > On Sun, Feb 18, 2018 at 2:16 PM, Arturo Zambrano > <arturo.zambrano(a)gmail.com <mailto:arturo.zambrano@gmail.com>> > > wrote: > >> > >> Hi, > >>Â Â can someone please tell me how to export a document using > pillar7? > >> > >>Â For pillar5Â the example used to be: > >> > >> configuration := PRPillarConfiguration new. > >> configuration outputType: PRHTMLWriter. > >> PRExportPhase executeOn: { document } with: configuration. > >> > >> > >> Thanks! > > > > > > > > > -- > > Â Â Â > > > > Guille Polito > > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > French National Center for Scientific Research - _http://www.cnrs.fr_ > > > *Web:* _http://guillep.github.io_ > > *Phone: *+33 06 52 70 66 13 > >

Feb. 28, 2018

Re: [Pharo-users] PharoDays?

by Stephane Ducasse

Or 24-25 of May Or 31 - 1 June? On Wed, Feb 28, 2018 at 6:09 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi guys > > many people are asking when and where there will be PharoDays. > And we do not know. > We are looking for local organisers and else we do it at Lille. > Now what would be a good date? > > What about > 7-8 June? > > Stef

Feb. 28, 2018

PharoDays?

by Stephane Ducasse

Hi guys many people are asking when and where there will be PharoDays. And we do not know. We are looking for local organisers and else we do it at Lille. Now what would be a good date? What about 7-8 June? Stef

Feb. 28, 2018

Re: [Pharo-users] Adding text files to a commit

by Peter UhnÃ¡k

> And it turns out that if the file is unchanged, then adding it to the index has no effect, so I can skip that step. this is equivalent to "git add"; further git can only track changes... so adding a file that hasn't changed produces an empty diff I have it on a class-side in a script method... which also embeds the content of the changelog into the image (compiles into the method)... But the menus of iceberg are easily extensible (don't remember what exactly you need to subclass)... so you could add a context-menu on a repository with "add file to index" which would open a file dialog. Peter On Wed, Feb 28, 2018 at 1:24 AM, Andrew P. Black <apblack(a)pdx.edu> wrote: > > > On 28 Feb 2018, at 12:32 , Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > > > I'm using the following > > > > | repo | > > repo := IceRepository registry detect: [ :each | each name = 'my-repo' ]. > > repo addFilesToIndex: {'CHANGELOG.md'}. > > > > so then the iceberg commit will also include the (external) file change > > > > Thank you! And it turns out that if the file is unchanged, then adding it > to the index has no effect, so I can skip that step. > > Have you hooked the above code into Iceberg, or do you run it manually? > > Andrew > > > >

Feb. 28, 2018

Re: [Pharo-users] Adding text files to a commit

by Andrew P. Black

> On 28 Feb 2018, at 12:32 , Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > I'm using the following > > | repo | > repo := IceRepository registry detect: [ :each | each name = 'my-repo' ]. > repo addFilesToIndex: {'CHANGELOG.md'}. > > so then the iceberg commit will also include the (external) file change > Thank you! And it turns out that if the file is unchanged, then adding it to the index has no effect, so I can skip that step. Have you hooked the above code into Iceberg, or do you run it manually? Andrew

Feb. 28, 2018

Re: [Pharo-users] Initializing Iceberg's repository list

by Peter UhnÃ¡k

I think you are looking for this thread http://forum.world.st/Adding-an-Iceberg-repository-at-startup-td5016693.html ? Peter On Tue, Feb 27, 2018 at 11:07 PM, Andrew P. Black <apblack(a)pdx.edu> wrote: > I believe that there is a way one can add one or more repositories to > Icebergâs list of local repositories, so that when one opens a new image > (new = just dowloaded using the Pharo launcher), the repository is already > present in Icebergâs list. StÃ©ph showed me how to do this once, but Iâve > lost the configuration file (or whatever it was) and canât now figure out > where to put it. > > Can someone point me to the documentation? > > Andrew > > >

Feb. 27, 2018

Re: [Pharo-users] Adding text files to a commit

by Peter UhnÃ¡k

I'm using the following | repo | repo := IceRepository registry detect: [ :each | each name = 'my-repo' ]. repo addFilesToIndex: {'CHANGELOG.md'}. so then the iceberg commit will also include the (external) file change Peter On Tue, Feb 27, 2018 at 11:06 PM, Andrew P. Black <apblack(a)pdx.edu> wrote: > I have some text files that I would like to include in every commit (if > they have changed since the prior commit). What is the right way to make > this happen automatically? Or else I forget to add them ... > > Adding the files to a _separate_ commit breaks Iceberg, because it decides > that the image is behind the repo, but there is no code that it can load to > bring it up to date. Iâm hoping that if the text files go in the same > commit, all will be well. > > Iâve made some progress with this. I have found that if I have staged the > text files before I do the commit with Iceberg, then they will be included > in the commit. So what I need is a way of detecting modifications in the > local repository (the equivalent of "git status") and then doing a "git add > ..." for the changed files. And then, ideally, hooking this into Iceberg. > Alternatively, I could I suppose write a pre-commit hook as a shell script > and just put it in the .git/hooks directory. >

Feb. 27, 2018

Re: [Pharo-users] how to load compiled code in the image and to change methods already on the stack?

by Andrew P. Black

> On 26 Feb 2018, at 22:59 , Steven Costiou <steven.costiou(a)kloum.io <mailto:steven.costiou@kloum.io>> wrote: > > Hi Pablo, > > thanks :) I will try Hermes. > > Basic scenario is adding/removing metalinks to a lot of a methods in an iot app: > > 1- If the add/remove occurs a lot of time, then there is a slowdown due to recompilation of methods. As this is a remote app, i want to try recompiling all methods locally then upload them. I will also try with Hermes. > > > 2- If metalinks are put inside a loop that is running, for now i understand i cannot update the method unless i replace it on the stack. Experimenting that is somewhere in my todolist, but i'm taking any advice ;) Maybe that is not really possible. > > > Steven. My suggestion would be not to try updating methods that are on the stack, but to update the methods that are executed in response to messages sent by what is on the stack. So, for example, instead of longRunningLoopThatHandlesEvents [ terminationCondition ] whileFalse: [ big loop body inline here ] write: longRunningLoopThatHandlesEvents [ terminationCondition ] whileFalse: [ self doOneIteration ] doOneIteration big loop body here Then you can upload a new version of doOneIteration, and next time around the even loop, thatâs what will be executed. This is much cleaner; you donât have to worry about changing code in the midst of its execution and somehow preserving the values of temporaries while you do so. You can see the same thing in Pharo if you are examining an execution in the debugger, and edit and recompile one of the executing methods. The method on the stack wonât change, but after the execution context has popped off the stack, you will see the new version execute in response to subsequent message sends. Andrew

Feb. 27, 2018