September 2016 - Pharo-users

Re: [Pharo-users] [ANN] Pillar 4.0.0

by stepharo

Le 17/9/16 Ã 13:22, Tudor Girba a Ã©crit : > Hi Stef, > > Indeed, it took a bit of time to get things to work. > > I think the welcome archetype is a bit misleading in that it does not serve a specific purpose. I would focus the instructions on the book archetype (welcome is not a book). yes I think so too. I started to update the tutorial - with script to download pillar - avoid to modify the makefile to change the output. Pay attention it seems that when you do ./pillar archetype welcome you cannot to ./pillar archetype book so I flushed everything and it "worked" > I see that there are some changes recently, so I would wait to try. > > What I did previously was: > wget --no-check-certificate https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh > chmod +x download.sh > ./download.sh > ./pillar archetype book With me this work. make book Now I was puzzled by the resulting pdf :) The template should be probably modified because I could not get why there is an empty chapter + a part + chapters after > Then I had to override copySupport.mk with the following file (because it does not work on Mac): > wget --no-check-certificate https://github.com/SquareBracketAssociates/BuildingUIWithSpec/blob/master/c… > mv copySupport.mk support/makefiles/copySupport.mk Strange. I have the impression it worked at my place. I would code all that in Pharo instead of arcane and undebuggable bash unix mix of scripts. Damien is telling to me that it would take longer to develop but I do not believe that a recursive copy not copying figures would be that complex :). And at least we can debug it. I just did not get the time to do it. Stef > > Cheers, > Doru > > > > >> On Sep 17, 2016, at 12:11 PM, stepharo <stepharo(a)free.fr> wrote: >> >> Hi >> >> I followed the pillarChap and I could get it running :( >> >> >> >> Installing and Exporting your First Document >> >> You first need to get Pillar. For that, we recommend downloading and exe- cuting the script available at https://raw.githubusercontent.com/pillar-markup/ pillar/master/download.sh in the base directory if you are on an Unix environ- ment. >> >> wget >> >> https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh >> chmod +x download.sh >> ./download.sh >> >> Then, you can load an archetype (see Section 14.2) with command: >> >> ./pillar archetype welcome >> >> You have the possibility to rename the directory in which your files will be exported. To do that you have to change the OUTPUTDIRECTORY variable in the Makefile: >> >> OUTPUTDIRECTORY = result >> >> Then, you can check everything is working fine by creating a first.pillar file with this content: >> >> !Hello World >> >> And finally compiling it from a terminal (see Section 14.6 for more informa- tion about the command-line interface): >> >> make result/first.html >> >> >> >> >> make result/welcome.html >> make: *** No rule to make target `result/welcome.html'. Stop. >> >> >> there is a welcome.pillar so I should be able to get welcome.html >> >> Now I do not get the expression make result/first.html >> >> >> cp welcome.pillar first.pillar >> tryingFromDoc make result/first.html >> make: *** No rule to make target `result/first.html'. Stop. >> >> I think that this doc is simply bogus. Each time I tried it >> I have to fix it radically. >> >> >> >> make welcome is working so may be this is what we should add to the doc. >> I do not think that Pillar guys are reading this mailing-list so I will try to save what should be saved. :( >> >> Stef >> >> Stef >> >> >> >> >> >> > -- > www.tudorgirba.com > www.feenk.com > > "Obvious things are difficult to teach." > > > > > >

Sept. 17, 2016

Re: [Pharo-users] [ANN] Pillar 4.0.0

by stepharo

> I bet you left the makefile unchanged. Try `make book-result/welcome.html` Yes I read the makefile and saw it and I fixed the tutorial. I updated the tutorial so that when one reads it we are not forced to edit the makefile. I'm perfectly happy with the default ouput name. > > Here it tries to run ./pillar something something that looks correct > (but fails because I didn't download the pillar image in that directory) > > DISCLAIMER: I'm not fixing the other archetypes until I'm happy with > the book one. So don't expect them to work this weekend. > > > On 17 September 2016 at 12:11, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > Hi > > I followed the pillarChap and I could get it running :( > > > > Installing and Exporting your First Document > > You first need to get Pillar. For that, we recommend downloading > and exe- cuting the script available at > https://raw.githubusercontent.com/pillar-markup/ > <https://raw.githubusercontent.com/pillar-markup/> > pillar/master/download.sh in the base directory if you are on an > Unix environ- ment. > > wget > https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh > <https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh> > > > chmod +x download.sh ./download.sh > > Then, you can load an archetype (see Section 14.2) with command: > > ./pillar archetype welcome > > You have the possibility to rename the directory in which your > files will be exported. To do that you have to change the > OUTPUTDIRECTORY variable in the Makefile: > > OUTPUTDIRECTORY = result > > Then, you can check everything is working fine by creating a > first.pillar file with this content: > > !Hello World > > And finally compiling it from a terminal (see Section 14.6 for > more informa- tion about the command-line interface): > > make result/first.html > make result/welcome.html > make: *** No rule to make target `result/welcome.html'. Stop. > > there is a welcome.pillar so I should be able to get welcome.html > Now I do not get the expression make result/first.html cp > welcome.pillar first.pillar tryingFromDoc make result/first.html > make: *** No rule to make target `result/first.html'. Stop. I > think that this doc is simply bogus. Each time I tried it I have > to fix it radically. make welcome is working so may be this is > what we should add to the doc. I do not think that Pillar guys are > reading this mailing-list so I will try to save what should be > saved. :( Stef Stef >

Sept. 17, 2016

Is someone working on RFID tags?

by HernÃ¡n Morales Durand

Recently I've been working on a model for RFID for animal identification using ISO 11784. I would like to have a nice model of RFID Tag types, Readers ,etc. (alternatively, if you know an object model to share I am also interested). If there is someone working on this in Pharo we could join efforts. Cheers, HernÃ¡n

Sept. 17, 2016

Re: [Pharo-users] JSON-RPC implementation

by Esteban A. Maringolo

Cool. Thanks. I couldn't find it with the search and wasn't aware of the list feature El sept. 17, 2016 3:15 AM, "stepharo" <stepharo(a)free.fr> escribiÃ³: > smalltalkhub.com/list is your friend > > > http://smalltalkhub.com/#!/~MasashiUmezawa/LtJsonRpc > > > Le 17/9/16 Ã 04:19, Esteban A. Maringolo a Ã©crit : > >> Does anybody implemented a JSON-RPC library for pharo? >> >> I don't see any listed here >> <http://json-rpc.org/wiki/implementations>, but maybe somebody is >> keeping it secret :) >> >> Regards! >> >> Esteban A. Maringolo >> >> >> > >

Sept. 17, 2016

Re: [Pharo-users] [ANN] Pillar 4.0.0

by Damien Pollet

On 17 September 2016 at 13:26, Tudor Girba <tudor(a)tudorgirba.com> wrote: > I just tried the latest Makefile, but it does not work. Are you working on > it? Are you trying the book archetype ? (I'm trying not to do work stuff during weekends) > Interesting. However, given that we are anyway relying on Pharo, why are > the scripts not in Pharo? Reimplementing make is just diluting manpower closer to homeopathic levels, and pillar is already a proven cause of burnout. > > About the list of chapters in pillar.conf, for instance: if the document > has parts, then chapters are not a flat list; it's one of those things > where form is content is formâ¦ > > Yes, indeed. Looking deeper I realize that we could scavenge the > information out of +include+ directives from pillar files. This should be > enough to provide a tree index view of all files. > Check this issue; there are already a couple visitors that could be exporting this info, but they don't list everything, and don't output deps as makefile syntax https://github.com/pillar-markup/pillar/issues/130

Sept. 17, 2016

Re: [Pharo-users] [ANN] Pillar 4.0.0

by Tudor Girba

Hi, > On Sep 17, 2016, at 1:05 PM, Damien Pollet <damien.pollet+pharo(a)gmail.com> wrote: > > Most important would be to check that what I do is compatible with how you use Pillar. I'm leaving in the terminal all day, so the workflow that I'll be pushing will be biased in that direction. (Hello, my name's Damien and I'm a shell addictâ¦ Hello, Damien!) Ok. I just tried the latest Makefile, but it does not work. Are you working on it? > It will be difficult to get a perfect makefile that can do minimal incremental recompilations unless Pillar can export a proper list of dependencies of a document (and even thenâ¦). I remember mentioning that to Thibault and Yann but it doesn't seem to be there. I need the same information for building tools. > In the meantime my goal is to make it a bit more robust and to factor stuff as much as possible. I also intend to make it self-documented, using this pretty nice trick: http://marmelab.com/blog/2016/02/29/auto-documented-makefile.html Interesting. However, given that we are anyway relying on Pharo, why are the scripts not in Pharo? > About the list of chapters in pillar.conf, for instance: if the document has parts, then chapters are not a flat list; it's one of those things where form is content is formâ¦ Yes, indeed. Looking deeper I realize that we could scavenge the information out of +include+ directives from pillar files. This should be enough to provide a tree index view of all files. Cheers, Doru > On 17 September 2016 at 12:45, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi Damien, > > As I said, just let me know if I can be of help for developing or testing something. I happen to be focusing on using Pillar these days. > > Cheers, > Doru > > > > On Sep 17, 2016, at 12:20 PM, Damien Pollet <damien.pollet+pharo(a)gmail.com> wrote: > > > > I bet you left the makefile unchanged. Try `make book-result/welcome.html` > > > > Here it tries to run ./pillar something something that looks correct (but fails because I didn't download the pillar image in that directory) > > > > DISCLAIMER: I'm not fixing the other archetypes until I'm happy with the book one. So don't expect them to work this weekend. > > > > > > On 17 September 2016 at 12:11, stepharo <stepharo(a)free.fr> wrote: > > Hi > > > > I followed the pillarChap and I could get it running :( > > > > > > > > Installing and Exporting your First Document > > > > You first need to get Pillar. For that, we recommend downloading and exe- cuting the script available at https://raw.githubusercontent.com/pillar-markup/ pillar/master/download.sh in the base directory if you are on an Unix environ- ment. > > > > wget > > > > https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh > > chmod +x download.sh > > ./download.sh > > > > Then, you can load an archetype (see Section 14.2) with command: > > > > ./pillar archetype welcome > > > > You have the possibility to rename the directory in which your files will be exported. To do that you have to change the OUTPUTDIRECTORY variable in the Makefile: > > > > OUTPUTDIRECTORY = result > > > > Then, you can check everything is working fine by creating a first.pillar file with this content: > > > > !Hello World > > > > And finally compiling it from a terminal (see Section 14.6 for more informa- tion about the command-line interface): > > > > make result/first.html > > > > > > > > > > make result/welcome.html > > make: *** No rule to make target `result/welcome.html'. Stop. > > > > > > there is a welcome.pillar so I should be able to get welcome.html > > > > Now I do not get the expression make result/first.html > > > > > > cp welcome.pillar first.pillar > > tryingFromDoc make result/first.html > > make: *** No rule to make target `result/first.html'. Stop. > > > > I think that this doc is simply bogus. Each time I tried it > > I have to fix it radically. > > > > > > > > make welcome is working so may be this is what we should add to the doc. > > I do not think that Pillar guys are reading this mailing-list so I will try to save what should be saved. :( > > > > Stef > > > > Stef > > > > > > > > > > > > > > > > -- > www.tudorgirba.com > www.feenk.com > > "From an abstract enough point of view, any two things are similar." > > > > > > -- www.tudorgirba.com www.feenk.com "Don't give to get. Just give."

Sept. 17, 2016

Re: [Pharo-users] [ANN] Pillar 4.0.0

by Tudor Girba

Hi Stef, Indeed, it took a bit of time to get things to work. I think the welcome archetype is a bit misleading in that it does not serve a specific purpose. I would focus the instructions on the book archetype (welcome is not a book). I see that there are some changes recently, so I would wait to try. What I did previously was: wget --no-check-certificate https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh chmod +x download.sh ./download.sh ./pillar archetype book Then I had to override copySupport.mk with the following file (because it does not work on Mac): wget --no-check-certificate https://github.com/SquareBracketAssociates/BuildingUIWithSpec/blob/master/c… mv copySupport.mk support/makefiles/copySupport.mk Cheers, Doru > On Sep 17, 2016, at 12:11 PM, stepharo <stepharo(a)free.fr> wrote: > > Hi > > I followed the pillarChap and I could get it running :( > > > > Installing and Exporting your First Document > > You first need to get Pillar. For that, we recommend downloading and exe- cuting the script available at https://raw.githubusercontent.com/pillar-markup/ pillar/master/download.sh in the base directory if you are on an Unix environ- ment. > > wget > > https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh > chmod +x download.sh > ./download.sh > > Then, you can load an archetype (see Section 14.2) with command: > > ./pillar archetype welcome > > You have the possibility to rename the directory in which your files will be exported. To do that you have to change the OUTPUTDIRECTORY variable in the Makefile: > > OUTPUTDIRECTORY = result > > Then, you can check everything is working fine by creating a first.pillar file with this content: > > !Hello World > > And finally compiling it from a terminal (see Section 14.6 for more informa- tion about the command-line interface): > > make result/first.html > > > > > make result/welcome.html > make: *** No rule to make target `result/welcome.html'. Stop. > > > there is a welcome.pillar so I should be able to get welcome.html > > Now I do not get the expression make result/first.html > > > cp welcome.pillar first.pillar > tryingFromDoc make result/first.html > make: *** No rule to make target `result/first.html'. Stop. > > I think that this doc is simply bogus. Each time I tried it > I have to fix it radically. > > > > make welcome is working so may be this is what we should add to the doc. > I do not think that Pillar guys are reading this mailing-list so I will try to save what should be saved. :( > > Stef > > Stef > > > > > > -- www.tudorgirba.com www.feenk.com "Obvious things are difficult to teach."

Sept. 17, 2016

Re: [Pharo-users] [ANN] Pillar 4.0.0

by Damien Pollet

Most important would be to check that what I do is compatible with how you use Pillar. I'm leaving in the terminal all day, so the workflow that I'll be pushing will be biased in that direction. (Hello, my name's Damien and I'm a shell addictâ¦ Hello, Damien!) It will be difficult to get a perfect makefile that can do minimal incremental recompilations unless Pillar can export a proper list of dependencies of a document (and even thenâ¦). I remember mentioning that to Thibault and Yann but it doesn't seem to be there. In the meantime my goal is to make it a bit more robust and to factor stuff as much as possible. I also intend to make it self-documented, using this pretty nice trick: http://marmelab.com/blog/2016/02/29/auto-documented-makefile.html About the list of chapters in pillar.conf, for instance: if the document has parts, then chapters are not a flat list; it's one of those things where form is content is formâ¦ On 17 September 2016 at 12:45, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi Damien, > > As I said, just let me know if I can be of help for developing or testing > something. I happen to be focusing on using Pillar these days. > > Cheers, > Doru > > > > On Sep 17, 2016, at 12:20 PM, Damien Pollet < > damien.pollet+pharo(a)gmail.com> wrote: > > > > I bet you left the makefile unchanged. Try `make > book-result/welcome.html` > > > > Here it tries to run ./pillar something something that looks correct > (but fails because I didn't download the pillar image in that directory) > > > > DISCLAIMER: I'm not fixing the other archetypes until I'm happy with the > book one. So don't expect them to work this weekend. > > > > > > On 17 September 2016 at 12:11, stepharo <stepharo(a)free.fr> wrote: > > Hi > > > > I followed the pillarChap and I could get it running :( > > > > > > > > Installing and Exporting your First Document > > > > You first need to get Pillar. For that, we recommend downloading and > exe- cuting the script available at https://raw.githubusercontent. > com/pillar-markup/ pillar/master/download.sh in the base directory if you > are on an Unix environ- ment. > > > > wget > > > > https://raw.githubusercontent.com/pillar-markup/pillar/ > master/download.sh > > chmod +x download.sh > > ./download.sh > > > > Then, you can load an archetype (see Section 14.2) with command: > > > > ./pillar archetype welcome > > > > You have the possibility to rename the directory in which your files > will be exported. To do that you have to change the OUTPUTDIRECTORY > variable in the Makefile: > > > > OUTPUTDIRECTORY = result > > > > Then, you can check everything is working fine by creating a > first.pillar file with this content: > > > > !Hello World > > > > And finally compiling it from a terminal (see Section 14.6 for more > informa- tion about the command-line interface): > > > > make result/first.html > > > > > > > > > > make result/welcome.html > > make: *** No rule to make target `result/welcome.html'. Stop. > > > > > > there is a welcome.pillar so I should be able to get welcome.html > > > > Now I do not get the expression make result/first.html > > > > > > cp welcome.pillar first.pillar > > tryingFromDoc make result/first.html > > make: *** No rule to make target `result/first.html'. Stop. > > > > I think that this doc is simply bogus. Each time I tried it > > I have to fix it radically. > > > > > > > > make welcome is working so may be this is what we should add to the doc. > > I do not think that Pillar guys are reading this mailing-list so I will > try to save what should be saved. :( > > > > Stef > > > > Stef > > > > > > > > > > > > > > > > -- > www.tudorgirba.com > www.feenk.com > > "From an abstract enough point of view, any two things are similar." > > > > > >

Sept. 17, 2016

Re: [Pharo-users] [ANN] Pillar 4.0.0

by Tudor Girba

Hi Damien, As I said, just let me know if I can be of help for developing or testing something. I happen to be focusing on using Pillar these days. Cheers, Doru > On Sep 17, 2016, at 12:20 PM, Damien Pollet <damien.pollet+pharo(a)gmail.com> wrote: > > I bet you left the makefile unchanged. Try `make book-result/welcome.html` > > Here it tries to run ./pillar something something that looks correct (but fails because I didn't download the pillar image in that directory) > > DISCLAIMER: I'm not fixing the other archetypes until I'm happy with the book one. So don't expect them to work this weekend. > > > On 17 September 2016 at 12:11, stepharo <stepharo(a)free.fr> wrote: > Hi > > I followed the pillarChap and I could get it running :( > > > > Installing and Exporting your First Document > > You first need to get Pillar. For that, we recommend downloading and exe- cuting the script available at https://raw.githubusercontent.com/pillar-markup/ pillar/master/download.sh in the base directory if you are on an Unix environ- ment. > > wget > > https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh > chmod +x download.sh > ./download.sh > > Then, you can load an archetype (see Section 14.2) with command: > > ./pillar archetype welcome > > You have the possibility to rename the directory in which your files will be exported. To do that you have to change the OUTPUTDIRECTORY variable in the Makefile: > > OUTPUTDIRECTORY = result > > Then, you can check everything is working fine by creating a first.pillar file with this content: > > !Hello World > > And finally compiling it from a terminal (see Section 14.6 for more informa- tion about the command-line interface): > > make result/first.html > > > > > make result/welcome.html > make: *** No rule to make target `result/welcome.html'. Stop. > > > there is a welcome.pillar so I should be able to get welcome.html > > Now I do not get the expression make result/first.html > > > cp welcome.pillar first.pillar > tryingFromDoc make result/first.html > make: *** No rule to make target `result/first.html'. Stop. > > I think that this doc is simply bogus. Each time I tried it > I have to fix it radically. > > > > make welcome is working so may be this is what we should add to the doc. > I do not think that Pillar guys are reading this mailing-list so I will try to save what should be saved. :( > > Stef > > Stef > > > > > > > -- www.tudorgirba.com www.feenk.com "From an abstract enough point of view, any two things are similar."

Sept. 17, 2016

Re: [Pharo-users] [ANN] Pillar 4.0.0

by Damien Pollet

I bet you left the makefile unchanged. Try `make book-result/welcome.html` Here it tries to run ./pillar something something that looks correct (but fails because I didn't download the pillar image in that directory) DISCLAIMER: I'm not fixing the other archetypes until I'm happy with the book one. So don't expect them to work this weekend. On 17 September 2016 at 12:11, stepharo <stepharo(a)free.fr> wrote: > Hi > > I followed the pillarChap and I could get it running :( > > > > Installing and Exporting your First Document > > You first need to get Pillar. For that, we recommend downloading and exe- > cuting the script available at https://raw.githubusercontent. > com/pillar-markup/ pillar/master/download.sh in the base directory if you > are on an Unix environ- ment. > > wget > https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh > > chmod +x download.sh > ./download.sh > > Then, you can load an archetype (see Section 14.2) with command: > > ./pillar archetype welcome > > You have the possibility to rename the directory in which your files will > be exported. To do that you have to change the OUTPUTDIRECTORY variable > in the Makefile: > > OUTPUTDIRECTORY = result > > Then, you can check everything is working fine by creating a first.pillar file > with this content: > > !Hello World > > And finally compiling it from a terminal (see Section 14.6 for more > informa- tion about the command-line interface): > > make result/first.html > > > make result/welcome.html > make: *** No rule to make target `result/welcome.html'. Stop. > there is a welcome.pillar so I should be able to get welcome.html > > Now I do not get the expression make result/first.html > > > cp welcome.pillar first.pillar > tryingFromDoc make result/first.html > make: *** No rule to make target `result/first.html'. Stop. > > I think that this doc is simply bogus. Each time I tried it > I have to fix it radically. > > > > make welcome is working so may be this is what we should add to the doc. > I do not think that Pillar guys are reading this mailing-list so I will try to save what should be saved. :( > > Stef > > Stef > > > > >

Sept. 17, 2016