February 2018 - Pharo-users

Initializing Iceberg's repository list

by Andrew P. Black

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

Adding text files to a commit

by Andrew P. Black

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] Exporting Pillar docs (Pillar7)

by Arturo Zambrano

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 > wrote: > > > On Sun, Feb 18, 2018 at 9:01 PM, Stephane Ducasse <stepharo.self(a)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> 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> >> > 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 > <http://www.cnrs.fr>* > > > *Web:* *http://guillep.github.io* <http://guillep.github.io> > > *Phone: *+33 06 52 70 66 13 >

Feb. 27, 2018

Re: [Pharo-users] depending on a group of a BaselineOf

by Jupiter Jones

(I hope this isnât posted twice - I accidentally sent it from an address that wasnât subscribed so this is a repost - apologies) Hi Peter, Iâve never had to use the provides: method even with fairly complex Baselines. This is an example of the kind of thing Iâve been using: baseline: spec <baseline> spec for #common do: [ spec âDependency on project with BaselineOf" baseline: 'Seaside3' with: [ spec loads: #('Core' 'Development' 'Zinc'); repository: 'github://SeasideSt/Seaside:master/repository <github://SeasideSt/Seaside:master/repository>' ]; âDependency on project with ConfigurationOf (note the version)â configuration: âMagritte3â with: [ spec versionString: '3.5.2'; repository: 'http://www.smalltalkhub.com/mc/Magritte/Magritte3/main <http://www.smalltalkhub.com/mc/Magritte/Magritte3/main>' ]; âNow define my project packagesâ package: 'MyProject-Model' with: [ spec requires: #(âMagritte3') ]; package: âMyProject-UI' with: [ spec requires: #('MyProject-Modelâ 'Seaside') ]; package: âMyProject-Tests-Modelâ with: [ spec requires: #('MyProject-Modelâ) ]; âNow define groups for convenience. Groups can load dependencies, packages, or other groupsâ group: âModel' with: #(âMyProject-Modelâ); group: âUI' with: #(âMyProject-UIâ); group: âTestsâ with: #(âMyProject-Testsâ) âMetacello will load the default group unless you specify otherwise" group: âdefaultâ with: #(Modelâ âUIâ); âOther possible convenience groupsâ group: âDevelopmentâ with: #(Modelâ âUIâ âTestsâ); group: âProductionâ with: #(Modelâ âUIâ) ] Then you can load groups like: Metacello new baseline: âMyProjectâ; repository: âgithub://MyGitHubUser/MyProject:master/repository' <github://MyGitHubUser/MyProject:master/repository'> loads: #(âDevelopmentâ); load Hope this helps :) Cheers, Jupiter > On 27 Feb 2018, at 9:30 am, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Hi, > > I'm trying to define a dependency on a group of BaselineOf. > > specifically #core of github://pharo-graphics/Bloc/src. > > I've looked at this https://github.com/Metacello/metacello/blob/master/docs/GettingStartedWithG… <https://github.com/Metacello/metacello/blob/master/docs/GettingStartedWithG…> > > which recommends using import:provides: > > baseline: spec > <baseline> > > spec for: #common do: [ > "Sample defines the group 'default'" > spec baseline: 'Sample' with: [ > spec repository: 'github://dalehenrich/Sample:master' ]. > spec import: 'Sample' provides: #('default'). > > "OtherSample *also* defines the group 'default'" > spec baseline: 'OtherSample' with: [ > spec repository: 'github://dalehenrich/Sample:master' ]. > spec import: 'OtherSample' provides: #('default'). > > "'default' can now be successfully resolved, even though > both projects define the same name" > spec package: 'OtherProject-Core with: [ > spec requires: 'default' ] ]. > > However this code is confusing... both Sample & OtherSample provide `default`, so on what does `OtherProject-Core` actually depend? > > In the examples here https://github.com/Metacello/metacello/blob/master/docs/LockCommandReferenc… <https://github.com/Metacello/metacello/blob/master/docs/LockCommandReferenc…> there are groups with the name of the project in them ('External Core' 'External Tests'), but this won't work if I don't control the project I am loading, plus it feels like a hackish workaround. > > Also, can it be unified with the way ConfigurationOf works? > > > Thanks, > Peter

Feb. 27, 2018

Re: [Pharo-users] depending on a group of a BaselineOf

by Pavel Krivanek

in BaselineOfBasicTools we use something like. spec baseline: 'SUnit' with: [ spec repository: repository. spec loads: #('UI' 'Help')]. -- Pavel 2018-02-26 23:30 GMT+01:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com>: > Hi, > > I'm trying to define a dependency on a group of BaselineOf. > > specifically #core of github://pharo-graphics/Bloc/src. > > I've looked at this > https://github.com/Metacello/metacello/blob/master/docs/GettingStartedWithG… > > which recommends using import:provides: > > baseline: spec > <baseline> > > spec for: #common do: [ > "Sample defines the group 'default'" > spec baseline: 'Sample' with: [ > spec repository: 'github://dalehenrich/Sample:master' ]. > spec import: 'Sample' provides: #('default'). > > "OtherSample *also* defines the group 'default'" > spec baseline: 'OtherSample' with: [ > spec repository: 'github://dalehenrich/Sample:master' ]. > spec import: 'OtherSample' provides: #('default'). > > "'default' can now be successfully resolved, even though > both projects define the same name" > spec package: 'OtherProject-Core with: [ > spec requires: 'default' ] ]. > > > However this code is confusing... both Sample & OtherSample provide > `default`, so on what does `OtherProject-Core` actually depend? > > In the examples here > https://github.com/Metacello/metacello/blob/master/docs/LockCommandReferenc… > there are groups with the name of the project in them ('External Core' > 'External Tests'), but this won't work if I don't control the project I am > loading, plus it feels like a hackish workaround. > > Also, can it be unified with the way ConfigurationOf works? > > > Thanks, > Peter

Feb. 27, 2018

depending on a group of a BaselineOf

by Peter UhnÃ¡k

Hi, I'm trying to define a dependency on a group of BaselineOf. specifically #core of github://pharo-graphics/Bloc/src. I've looked at this https://github.com/Metacello/metacello/blob/master/docs/GettingStartedWithG… which recommends using import:provides: baseline: spec <baseline> spec for: #common do: [ "Sample defines the group 'default'" spec baseline: 'Sample' with: [ spec repository: 'github://dalehenrich/Sample:master' ]. spec import: 'Sample' provides: #('default'). "OtherSample *also* defines the group 'default'" spec baseline: 'OtherSample' with: [ spec repository: 'github://dalehenrich/Sample:master' ]. spec import: 'OtherSample' provides: #('default'). "'default' can now be successfully resolved, even though both projects define the same name" spec package: 'OtherProject-Core with: [ spec requires: 'default' ] ]. However this code is confusing... both Sample & OtherSample provide `default`, so on what does `OtherProject-Core` actually depend? In the examples here https://github.com/Metacello/metacello/blob/master/docs/LockCommandReferenc… there are groups with the name of the project in them ('External Core' 'External Tests'), but this won't work if I don't control the project I am loading, plus it feels like a hackish workaround. Also, can it be unified with the way ConfigurationOf works? Thanks, Peter

Feb. 26, 2018

Re: [Pharo-users] adding 1 year to the date - bug?

by Richard O'Keefe

It makes sense to add a Duration to a DateAndTime. It does not make sense to add a Duration to a Date. I can't check Pharo because I haven't managed to get it working on this laptop (x86-64 + ubuntu 17), but Squeak has Date>>addMonths: (edited for clarity): addMonths: monthCount |m year month maxDaysInMonth day| m := monthCount + self monthIndex - 1. year := m // 12 + self year. month := m \\ 12 + 1. maxDaysInMonth := Month daysInMonth: month forYear: year. day := self dayOfMonth min: maxDaysInMonth. ^ Date newDay: day month: month year: year This may or may not do what your customer wants. On 26 February 2018 at 22:43, Petr Fischer <petr.fischer(a)me.com> wrote: > Hello, just simple test: > > (Date year: 2019 month: 2 day: 26) + 1 year. > returns: 26 February 2020 > OK > > (Date year: 2020 month: 2 day: 26) + 1 year. > returns: 25 February 2021 > What? > > (maybe I do not understand something about dates again) > > Thanks! pf > >

Feb. 26, 2018

Re: [Pharo-users] adding 1 year to the date - bug?

by Petr Fischer

Thanks for discussion thread link. And yes, I need to implement it myself for customer needs, especially things like: January 31 + 1 month = February 28/29 February 29 + 1 year = February 28 etc. :) pf > This is a discussion we already had years ago. And comes back every once in > a while. > > Pharo, and all dialects to my knowledge, uses incremental based > calculations instead of field based calculations (like java.util.Calendar). > > This is the best thread I remember where we discussed this. > http://forum.world.st/Interesting-Date-Time-Thread- > on-Squeak-Dev-td4778652.html#a4778970 > > > Regards, > > -- > Esteban. > > El feb. 26, 2018 7:33 AM, "jtuchel(a)objektfabrik.de" <jtuchel(a)objektfabrik.de> > escribiÃ³: > > Am 26.02.18 um 11:13 schrieb Petr Fischer: > > So "date addMonths: 12" behaves better for my needs. Thanks > > > Hmm. We've had this discussion just the other day at Lunch. What is a > month? Should addMonths: 1 and then subtractMonths: 1 on January 31st bring > you back to January 31st? How would you implement that? > > I guess this is a problem that cannot be solved by a machine without > additional context. Does 1 month later mean "on this day next month" or > does it mean "exactly as many days in the future as the current month has > days"? None of the two? Can one month later be in March when today is > January 30th? > > It seems years and months are a bit incompatible with informatics ;-) In my > opinion, there is more info needed than "x months/years later" in order to > calculate the correct result. > > Joachim > > > > > > > > > > Hello, just simple test: > >> > >> (Date year: 2019 month: 2 day: 26) + 1 year. > >> returns: 26 February 2020 > >> OK > >> > >> (Date year: 2020 month: 2 day: 26) + 1 year. > >> returns: 25 February 2021 > >> What? > >> > >> (maybe I do not understand something about dates again) > >> > >> Thanks! pf > >> > >> > > > -- > ----------------------------------------------------------------------- > Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de > Fliederweg 1 http://www.objektfabrik.de > D-71640 Ludwigsburg http://joachimtuchel.wordpress.com > Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1

Feb. 26, 2018

Re: [Pharo-users] adding 1 year to the date - bug?

by Esteban A. Maringolo

This is a discussion we already had years ago. And comes back every once in a while. Pharo, and all dialects to my knowledge, uses incremental based calculations instead of field based calculations (like java.util.Calendar). This is the best thread I remember where we discussed this. http://forum.world.st/Interesting-Date-Time-Thread- on-Squeak-Dev-td4778652.html#a4778970 Regards, -- Esteban. El feb. 26, 2018 7:33 AM, "jtuchel(a)objektfabrik.de" <jtuchel(a)objektfabrik.de> escribiÃ³: Am 26.02.18 um 11:13 schrieb Petr Fischer: So "date addMonths: 12" behaves better for my needs. Thanks > Hmm. We've had this discussion just the other day at Lunch. What is a month? Should addMonths: 1 and then subtractMonths: 1 on January 31st bring you back to January 31st? How would you implement that? I guess this is a problem that cannot be solved by a machine without additional context. Does 1 month later mean "on this day next month" or does it mean "exactly as many days in the future as the current month has days"? None of the two? Can one month later be in March when today is January 30th? It seems years and months are a bit incompatible with informatics ;-) In my opinion, there is more info needed than "x months/years later" in order to calculate the correct result. Joachim > > Hello, just simple test: >> >> (Date year: 2019 month: 2 day: 26) + 1 year. >> returns: 26 February 2020 >> OK >> >> (Date year: 2020 month: 2 day: 26) + 1 year. >> returns: 25 February 2021 >> What? >> >> (maybe I do not understand something about dates again) >> >> Thanks! pf >> >> > -- ----------------------------------------------------------------------- Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de Fliederweg 1 http://www.objektfabrik.de D-71640 Ludwigsburg http://joachimtuchel.wordpress.com Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1

Feb. 26, 2018

Re: [Pharo-users] adding 1 year to the date - bug?

by Sean P. DeNigris

NorbertHartl wrote > Forgot to say that this is something you can experience quite often. To me > the problem is that 1 year gives a duration immediately. It should work as > all units that 1 year is a unit of magnitude 1 and unit year. If you apply > this to a date you could make it properly to give the date one year later. Yes!!! ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Feb. 26, 2018