- Pharo-users - lists.pharo.org

Re: [Pharo-users] P3 library - setting database in url?

by Sven Van Caekenberghe

Ben, > On 29 Jan 2018, at 15:27, Ben Coman <btc(a)openinworld.com> wrote: > > Hi Sven, > > I'm using your P3 library > https://github.com/svenvc/P3 > > to connect to TimescaleDB set up like this tutorial... > http://docs.timescale.com/v0.8/tutorials/tutorial-hello-nyc Cool. > but the following doesn't work unless I un-comment the second line... > (P3Client new url: > 'psql://postgres:password@localhost:5432/nyc_data') in: [ :client | > [ " client database: 'nyc_data'. " > client query: 'SELECT date_trunc(''day'', pickup_datetime) > as day, avg(fare_amount) > FROM rides > WHERE passenger_count > 1 AND pickup_datetime < ''2016-01-08'' > GROUP BY day ORDER BY day;' > ] ensure: [ client close ] > ]. > > Is it supposed to work without the second line, > just with the database set in the url ? Yes, it is supposed to work like that. Did you try with the latest #reset patch (split settings/properties) ? Sven > cheers -ben > > > P.S. TimescaleDB looks like cool tech... > https://blog.timescale.com/time-series-data-why-and-how-to-use-a-relational… > > Some notes for anyone wanting to try tutorial-hello-nyc... > a. Postgresql >9.6.3 is required, for which the default install on > Ubuntu 16.04 had a problem with libpq not being recent enough. I > needed to follow these steps... > https://askubuntu.com/questions/831292/how-to-install-postgresql-9-6-on-any… > > b. Downloading the sample data errored using the given "https" url, > but plain "http" worked... > http://timescaledata.blob.core.windows.net/datasets/nyc_data.tar.gz >

Jan. 29, 2018

P3 library - setting database in url?

by Ben Coman

Hi Sven, I'm using your P3 library https://github.com/svenvc/P3 to connect to TimescaleDB set up like this tutorial... http://docs.timescale.com/v0.8/tutorials/tutorial-hello-nyc but the following doesn't work unless I un-comment the second line... (P3Client new url: 'psql://postgres:password@localhost:5432/nyc_data') in: [ :client | [ " client database: 'nyc_data'. " client query: 'SELECT date_trunc(''day'', pickup_datetime) as day, avg(fare_amount) FROM rides WHERE passenger_count > 1 AND pickup_datetime < ''2016-01-08'' GROUP BY day ORDER BY day;' ] ensure: [ client close ] ]. Is it supposed to work without the second line, just with the database set in the url ? cheers -ben P.S. TimescaleDB looks like cool tech... https://blog.timescale.com/time-series-data-why-and-how-to-use-a-relational… Some notes for anyone wanting to try tutorial-hello-nyc... a. Postgresql >9.6.3 is required, for which the default install on Ubuntu 16.04 had a problem with libpq not being recent enough. I needed to follow these steps... https://askubuntu.com/questions/831292/how-to-install-postgresql-9-6-on-any… b. Downloading the sample data errored using the given "https" url, but plain "http" worked... http://timescaledata.blob.core.windows.net/datasets/nyc_data.tar.gz

Jan. 29, 2018

Re: [Pharo-users] Download pillar image -> Error 403: Forbidden

by Guillermo Polito

On Mon, Jan 29, 2018 at 6:52 AM, HernÃ¡n Morales Durand < hernan.morales(a)gmail.com> wrote: > 2018-01-28 18:55 GMT-03:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > > Hernan > > > > what we can also do is the following: I set up the pillar project on > > github with travis and bintray and when you commit > > the book is automatically built. > > > > Ok, I would try that way. > > > > >> Tried both options, 1) downloading pre-compiled and 2) building from > >> sources+setting up environment. > >> 1) Nothing happened after "pillar archetype build", exit without > >> error, no stdout output, no _result folder > > > > this is super strange. We should check the AppVeyor because it should > > tell us what is not working on windows. > > > >> 2) I got confused with this: > >> > >> mv pillar ~/.pillar > > > > the idea was that once you get pillar on linux/mac we move the > > donwloaded version into ~./pillar > > so that after we have only one pillar installation for all the books > > (contrary to what is done in Pillar 50 and 60). > > > > here is what I get in my .pillar > > > > cd build > > > > A-ha, that's the thing. My build/ is created one level up and not > inside .pillar/ > > > ~/.pillar/build(newpipeline*) Â» ls > > Pharo.changes mustache pharo-ui pillar-db > > Pharo.image pharo pharo-vm pillar-dev-upgrade > > archetypes pharo-local pillar pillar-upgrade > > > > Another difference, you seem to have the wrapper scripts in build/ > > ~/.pillar/build (newpipeline) $ ls > pharo* Pharo.changes Pharo.image PharoDebug.log pharo-local/ > pharo-ui* pharo-vm/ stderr stdout > > > > and > > > > cd pillar > > > > ~/.pillar/pillar(newpipeline*) Â» ls > > LICENSE README.md archetypes scripts src > > > > ~/.pillar (newpipeline) $ ls > archetypes/ build/ LICENSE README.md scripts/ src/ > > > >> because now I have two directories: the .pillar in HOME and the build/ > >> directory separated. And no "pillar" shell script so should I copy the > >> one from 1) ? > > > > > > > > > > > > > >> I will re-check tomorrow maybe I'm reading this the wrong way. > >> > > So I checked, and discovered that the build image hasn't installed > Pillar because there wasn't installed any command handler for > introspect > Invalid arguments: "pillar introspect > --baseDirectory=C:/Users/mvs/.pillar mainDocument" [ > > The build.sh installs Pillar as follows through a magic variable: > > Metacello new > baseline: 'Pillar'; > repository: > 'filetree:///c/MySmalltalkProjects/Pillar/Latest/pillar/scripts/../src'; > load. > > But gives a SubscriptOutOfBounds: 2 because > WindowsStore>>printPath:on: expects "c:" > (I would love a better error description in stdout file "Invalid > arguments" is not that informative) > > Another load error is that BaselineOfPillar is installing OSSubprocess > and it doesn't work on Windows (#externalCallFailed). > > Should I open issue? > And that, is because I was holding windows support from integration in a separate branch. https://github.com/pillar-markup/pillar/pull/183 I did not want to integrate it yet because for some reason AppVeyor builds were failing the integration tests in pharo 61 and I couldn't grasp why nor reproduce it locally (but strangely enough they work on pharo 50). So, I'm going to wait the CI to finish and then integrate it. That should add support for ProcessWrapper and several path fixes in windows. > > > >>> so that I can see if this is working. > >>> I know that guille worked on windows and AppVeyor support but he got > >>> distracted by the github refactoring. > >>> We hope to come back this week to Pillar. We plan to release a version > >>> (still with Magritte) but with a full documentation. > >>> > >> > >> Cool, I will test because I have several chapters ready to publish. > >> > >>> Stef > >>> > >>> > >>> > >>> > >>> > >>> On Sat, Jan 27, 2018 at 4:47 PM, HernÃ¡n Morales Durand > >>> <hernan.morales(a)gmail.com> wrote: > >>>> Hi Stef > >>>> > >>>> 2018-01-27 9:30 GMT-03:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > >>>>> Hi Hernan > >>>>> > >>>>> > >>>>> > >>>>> On Thu, Jan 25, 2018 at 10:30 PM, HernÃ¡n Morales Durand > >>>>> <hernan.morales(a)gmail.com> wrote: > >>>>>> I am following the Publishing Pillar Booklet guide from here > >>>>>> https://github.com/SquareBracketAssociates/Booklet- > PublishingAPillarBooklet > >>>>> > >>>>> pay attention it is not public because it is in flux because we were > >>>>> working on Pillar 70. > >>>>> > >>>>> Now if you follow the readme of pillar-markup/pillar/ it should work > >>>>> since I used it yesterday. > >>>>> > >>>>> $ wget https://raw.githubusercontent.com/pillar-markup/pillar/ > master/download.sh > >>>>>> $ chmod +x download.sh > >>>>>> $ ./download.sh > >>>>> > >>>>>>./pillar archetype book > >>>>> make book. > >>>>> > >>>>> > >>>>> What you should know is that the stable version sucks at the > >>>>> infrastructure level (relying on too many servers + silent failures > in > >>>>> bash files). > >>>>> > >>>>> Can you retry and let me know? > >>>> > >>>> Ok I tried again using MinGW in Windows 8.1 > >>>> Image is downloaded ok but final step gives an error: > >>>> > >>>> $ make book > >>>> support/makefiles/prepare.mk:1: *** Undefined setting > OUTPUTDIRECTORY (Directory > >>>> for build products). Stop. > >>>> > >>>> I replaced the expanded shell variables in main.mk from using := to = > >>>> and it seems to "solve" this problem, though someone else should check > >>>> why this happens > >>>> > >>>> MAIN = $(shell ./pillar introspect mainDocument) > >>>> > >>>> OUTPUTDIRECTORY = $(shell ./pillar introspect outputDirectory) > >>>> LATEXTEMPLATE = $(shell ./pillar introspect latexTemplate) > >>>> LATEXCHAPTERTEMPLATE = $(shell ./pillar introspect > latexChapterTemplate) > >>>> HTMLTEMPLATE = $(shell ./pillar introspect htmlTemplate) > >>>> HTMLCHAPTERTEMPLATE = $(shell ./pillar introspect htmlChapterTemplate) > >>>> CHAPTERS = $(shell ./pillar introspect chapters) > >>>> > >>>> $ make book > >>>> make: *** No rule to make target `/.pdf', needed by `pdfbook'. Stop. > >>>> > >>>> I am using > >>>> $ make --version > >>>> GNU Make 3.81 > >>>> > >>>> > >>>>> BTW why do you want to compile Booklet-PublishingAPillarBooklet/ > >>>>> If you want just create your own repo and do > >>>>> > >>>>> wget https://raw.githubusercontent.com/pillar-markup/pillar/ > master/download.sh > >>>>> chmod +x download.sh > >>>>> ./download.sh > >>>>> ./pillar archetype book > >>>>> make book. > >>>>> > >>>> > >>>> Thanks, I just followed the install instructions. > >>>> > >>>> HernÃ¡n > >>>> > >>>>> > >>>>> Stef > >>>>> > >>>>> > >>>>>> $ git clone git@github.com:SquareBracketAssociates/Booklet- > PublishingAPillarBooklet.git > >>>>>> $ cd Booklet-PublishingAPillarBooklet/ > >>>>>> $ wget https://raw.githubusercontent.com/pillar-markup/pillar/ > master/download.sh > >>>>>> $ chmod +x download.sh > >>>>>> $ ./download.sh > >>>>>> > >>>>>> --2018-01-25 17:56:32-- http://get.pharo.org/vm50 > >>>>>> Resolving get.pharo.org (get.pharo.org) 164.132.235.17 > >>>>>> Connecting to get.pharo.org (get.pharo.org)|164.132.235.17|:80... > connected. > >>>>>> HTTP request sent, awaiting response... 200 OK > >>>>>> Length: 5819 (5.7K) > >>>>>> Saving to: 'STDOUT' > >>>>>> > >>>>>> 0K ..... 100% > 371K=0.02s > >>>>>> > >>>>>> 2018-01-25 17:56:33 (371 KB/s) - written to stdout [5819/5819] > >>>>>> > >>>>>> Downloading the latest pharoVM: > >>>>>> http://files.pharo.org/get-files/50/pharo-win-stable.zip > >>>>>> pharo-vm/Pharo.exe > >>>>>> Downloading PharoV50.sources: > >>>>>> http://files.pharo.org/get-files/50/sources.zip > >>>>>> Creating starter scripts pharo and pharo-ui > >>>>>> --2018-01-25 17:57:21-- > >>>>>> https://github.com/pillar-markup/pillar/releases/ > download/50/Pillar-deployment50.zip > >>>>>> Resolving github.com (github.com) 192.30.253.112, 192.30.253.113 > >>>>>> Connecting to github.com (github.com)|192.30.253.112|:443... > connected. > >>>>>> HTTP request sent, awaiting response... 302 Found > >>>>>> Location: https://github-production-release-asset-2e65be.s3. > amazonaws.com/41843105/f4ea97f0-e63b-11e7-9012- > edab5af1a547?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential= > AKIAIWNJYAX4CSVEH53A%2F20180125%2Fus-east-1%2Fs3% > 2Faws4_request&X-Amz-Date=20180125T205723Z&X-Amz- > Expires=300&X-Amz-Signature=9ecb9c284b9a92c8dbae0c15d8e490 > 324f0fc7ea3cbe98104080f99c4573e1d6&X-Amz-SignedHeaders=host& > actor_id=0&response-content-disposition=attachment%3B%20filename%3DPillar- > deployment50.zip&response-content-type=application%2Foctet-stream > >>>>>> [following] > >>>>>> --2018-01-25 17:57:23-- > >>>>>> https://github-production-release-asset-2e65be.s3. > amazonaws.com/41843105/f4ea97f0-e63b-11e7-9012- > edab5af1a547?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential= > AKIAIWNJYAX4CSVEH53A%2F20180125%2Fus-east-1%2Fs3% > 2Faws4_request&X-Amz-Date=20180125T205723Z&X-Amz- > Expires=300&X-Amz-Signature=9ecb9c284b9a92c8dbae0c15d8e490 > 324f0fc7ea3cbe98104080f99c4573e1d6&X-Amz-SignedHeaders=host& > actor_id=0&response-content-disposition=attachment%3B%20filename%3DPillar- > deployment50.zip&response-content-type=application%2Foctet-stream > >>>>>> Resolving github-production-release-asset-2e65be.s3.amazonaws.com > >>>>>> (github-production-release-asset-2e65be.s3.amazonaws.com) > >>>>>> 54.231.115.35 > >>>>>> Connecting to github-production-release- > asset-2e65be.s3.amazonaws.com > >>>>>> (github-production-release-asset-2e65be.s3.amazonaws.com) > |54.231.115.35|:443... > >>>>>> connected. > >>>>>> HTTP request sent, awaiting response... 200 OK > >>>>>> Length: 18482449 (18M) [application/octet-stream] > >>>>>> Saving to: 'imageLn5zD.zip' > >>>>>> > >>>>>> imageLn5zD.zip 10%[=> ] 1.88M 502 B/s > in 8m 7s > >>>>>> > >>>>>> 2018-01-25 18:15:45 (3.94 KB/s) - Read error at byte > 1966661/18482449 > >>>>>> (Bad file descriptor). Retrying. > >>>>>> > >>>>>> --2018-01-25 18:15:46-- (try: 2) > >>>>>> https://github-production-release-asset-2e65be.s3. > amazonaws.com/41843105/f4ea97f0-e63b-11e7-9012- > edab5af1a547?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential= > AKIAIWNJYAX4CSVEH53A%2F20180125%2Fus-east-1%2Fs3% > 2Faws4_request&X-Amz-Date=20180125T205723Z&X-Amz- > Expires=300&X-Amz-Signature=9ecb9c284b9a92c8dbae0c15d8e490 > 324f0fc7ea3cbe98104080f99c4573e1d6&X-Amz-SignedHeaders=host& > actor_id=0&response-content-disposition=attachment%3B%20filename%3DPillar- > deployment50.zip&response-content-type=application%2Foctet-stream > >>>>>> Connecting to github-production-release- > asset-2e65be.s3.amazonaws.com > >>>>>> (github-production-release-asset-2e65be.s3.amazonaws.com) > |54.231.115.35|:443... > >>>>>> connected. > >>>>>> HTTP request sent, awaiting response... 403 Forbidden > >>>>>> 2018-01-25 18:15:47 ERROR 403: Forbidden. > >>>>>> > >>>>>> > >>>>>> Also the download speed was super slow. > >>>>>> > >>>>>> Any ideas? > >>>>>> > >>>>>> Cheers, > >>>>>> > >>>>>> HernÃ¡n > >>>>>> > >>>>> > >>>> > >>> > >> > > > > -- 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

Jan. 29, 2018

Re: [Pharo-users] Iceberg and resource files

by Christophe Demarey

Hi Ken, > Le 27 janv. 2018 Ã 15:38, kmo <voxkmp(a)gmail.com> a Ã©crit : > > I don't understand how iceberg handles resource files that you might also > like to version along with the pharo code. For now, Iceberg do not really handle these files but it is planned in a next future. > Say I have an CSV file and a text file that my pharo application uses. How > do I include these in the iceberg commit/push? How do I see changes made in > these files from version to version? Currently, you cannot do anything related to this through the UI. What you could do is to call directly Iceberg API to commit ressources to the git repository: 1/ write the resource content in git working copy (std file system). There is a utility method: IceRepository>>#saveContent: aString inWorkingCopyFile: aRelativePathString 2/ add these files to git index through: IceRepository>>addFilesToIndex: aListOfPaths 3/ commit : iceRepository commitIndexWithMessage: commitMessage andParents: { iceRepository headCommit } You can also read ressources by suing IceRepository>>#contentOfFileNamed: aPathString commit: aCommitId Christophe. > Does iceberg only handle pharo code? Generally git clients don't care about > the file type - and it it is any kind of text you can see the actual > differences between each commit. > > Ken > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Jan. 29, 2018

Re: [Pharo-users] Download pillar image -> Error 403: Forbidden

by Guillermo Polito

On Sun, Jan 28, 2018 at 8:51 AM, HernÃ¡n Morales Durand < hernan.morales(a)gmail.com> wrote: > Hi Stef, > > 2018-01-28 4:15 GMT-03:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > > Ok I see. I think that I never tried this version of Pillar on windows. > > And I hate make because it is impossible for me to debug it. I will > > check with Damien > > because I do not get make. > > > > Now we removed the dependency to make in the dev branch > > Could you try the following: > > https://github.com/pillar-markup/pillar/blob/newpipeline/README.md > > > > Tried both options, 1) downloading pre-compiled and 2) building from > sources+setting up environment. > 1) Nothing happened after "pillar archetype build", exit without > error, no stdout output, no _result folder > 2) I got confused with this: > > mv pillar ~/.pillar > > because now I have two directories: the .pillar in HOME and the build/ > directory separated. And no "pillar" shell script so should I copy the > one from 1) ? > I will re-check tomorrow maybe I'm reading this the wrong way. > Ah! the instructions are not right :) Sorry for that. Actually, the instructions are written so you execute the build script from within the pillar repository. Something like this. $ git clone git@github.com:pillar-markup/pillar.git -b newpipeline $ cd pillar $ ./scripts/build.sh that is why the next lines are $ mv pillar ~/.pillar and $ export PILLAR_HOME="$HOME/.pillar/build"$ export PATH="$PATH:$PILLAR_HOME" Now, to fix your setup, you can try: $ mv build ~/.pillar/ and that should make the pillar launcher scripts available. We changed these scripts with stef a couple of weeks ago to keep not only the build directory but also the git repository, and so be able to upgrade pillar. But a docbug slipped in ^^. Can you check it like that? > > so that I can see if this is working. > > I know that guille worked on windows and AppVeyor support but he got > > distracted by the github refactoring. > > We hope to come back this week to Pillar. We plan to release a version > > (still with Magritte) but with a full documentation. > > > > Cool, I will test because I have several chapters ready to publish. > > > Stef > > > > > > > > > > > > On Sat, Jan 27, 2018 at 4:47 PM, HernÃ¡n Morales Durand > > <hernan.morales(a)gmail.com> wrote: > >> Hi Stef > >> > >> 2018-01-27 9:30 GMT-03:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > >>> Hi Hernan > >>> > >>> > >>> > >>> On Thu, Jan 25, 2018 at 10:30 PM, HernÃ¡n Morales Durand > >>> <hernan.morales(a)gmail.com> wrote: > >>>> I am following the Publishing Pillar Booklet guide from here > >>>> https://github.com/SquareBracketAssociates/Booklet- > PublishingAPillarBooklet > >>> > >>> pay attention it is not public because it is in flux because we were > >>> working on Pillar 70. > >>> > >>> Now if you follow the readme of pillar-markup/pillar/ it should work > >>> since I used it yesterday. > >>> > >>> $ wget https://raw.githubusercontent.com/pillar-markup/pillar/ > master/download.sh > >>>> $ chmod +x download.sh > >>>> $ ./download.sh > >>> > >>>>./pillar archetype book > >>> make book. > >>> > >>> > >>> What you should know is that the stable version sucks at the > >>> infrastructure level (relying on too many servers + silent failures in > >>> bash files). > >>> > >>> Can you retry and let me know? > >> > >> Ok I tried again using MinGW in Windows 8.1 > >> Image is downloaded ok but final step gives an error: > >> > >> $ make book > >> support/makefiles/prepare.mk:1: *** Undefined setting OUTPUTDIRECTORY > (Directory > >> for build products). Stop. > >> > >> I replaced the expanded shell variables in main.mk from using := to = > >> and it seems to "solve" this problem, though someone else should check > >> why this happens > >> > >> MAIN = $(shell ./pillar introspect mainDocument) > >> > >> OUTPUTDIRECTORY = $(shell ./pillar introspect outputDirectory) > >> LATEXTEMPLATE = $(shell ./pillar introspect latexTemplate) > >> LATEXCHAPTERTEMPLATE = $(shell ./pillar introspect latexChapterTemplate) > >> HTMLTEMPLATE = $(shell ./pillar introspect htmlTemplate) > >> HTMLCHAPTERTEMPLATE = $(shell ./pillar introspect htmlChapterTemplate) > >> CHAPTERS = $(shell ./pillar introspect chapters) > >> > >> $ make book > >> make: *** No rule to make target `/.pdf', needed by `pdfbook'. Stop. > >> > >> I am using > >> $ make --version > >> GNU Make 3.81 > >> > >> > >>> BTW why do you want to compile Booklet-PublishingAPillarBooklet/ > >>> If you want just create your own repo and do > >>> > >>> wget https://raw.githubusercontent.com/pillar-markup/pillar/ > master/download.sh > >>> chmod +x download.sh > >>> ./download.sh > >>> ./pillar archetype book > >>> make book. > >>> > >> > >> Thanks, I just followed the install instructions. > >> > >> HernÃ¡n > >> > >>> > >>> Stef > >>> > >>> > >>>> $ git clone git@github.com:SquareBracketAssociates/Booklet- > PublishingAPillarBooklet.git > >>>> $ cd Booklet-PublishingAPillarBooklet/ > >>>> $ wget https://raw.githubusercontent.com/pillar-markup/pillar/ > master/download.sh > >>>> $ chmod +x download.sh > >>>> $ ./download.sh > >>>> > >>>> --2018-01-25 17:56:32-- http://get.pharo.org/vm50 > >>>> Resolving get.pharo.org (get.pharo.org) 164.132.235.17 > >>>> Connecting to get.pharo.org (get.pharo.org)|164.132.235.17|:80... > connected. > >>>> HTTP request sent, awaiting response... 200 OK > >>>> Length: 5819 (5.7K) > >>>> Saving to: 'STDOUT' > >>>> > >>>> 0K ..... 100% > 371K=0.02s > >>>> > >>>> 2018-01-25 17:56:33 (371 KB/s) - written to stdout [5819/5819] > >>>> > >>>> Downloading the latest pharoVM: > >>>> http://files.pharo.org/get-files/50/pharo-win-stable.zip > >>>> pharo-vm/Pharo.exe > >>>> Downloading PharoV50.sources: > >>>> http://files.pharo.org/get-files/50/sources.zip > >>>> Creating starter scripts pharo and pharo-ui > >>>> --2018-01-25 17:57:21-- > >>>> https://github.com/pillar-markup/pillar/releases/download/50/Pillar- > deployment50.zip > >>>> Resolving github.com (github.com) 192.30.253.112, 192.30.253.113 > >>>> Connecting to github.com (github.com)|192.30.253.112|:443... > connected. > >>>> HTTP request sent, awaiting response... 302 Found > >>>> Location: https://github-production-release-asset-2e65be.s3. > amazonaws.com/41843105/f4ea97f0-e63b-11e7-9012- > edab5af1a547?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential= > AKIAIWNJYAX4CSVEH53A%2F20180125%2Fus-east-1%2Fs3% > 2Faws4_request&X-Amz-Date=20180125T205723Z&X-Amz- > Expires=300&X-Amz-Signature=9ecb9c284b9a92c8dbae0c15d8e490 > 324f0fc7ea3cbe98104080f99c4573e1d6&X-Amz-SignedHeaders=host& > actor_id=0&response-content-disposition=attachment%3B%20filename%3DPillar- > deployment50.zip&response-content-type=application%2Foctet-stream > >>>> [following] > >>>> --2018-01-25 17:57:23-- > >>>> https://github-production-release-asset-2e65be.s3. > amazonaws.com/41843105/f4ea97f0-e63b-11e7-9012- > edab5af1a547?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential= > AKIAIWNJYAX4CSVEH53A%2F20180125%2Fus-east-1%2Fs3% > 2Faws4_request&X-Amz-Date=20180125T205723Z&X-Amz- > Expires=300&X-Amz-Signature=9ecb9c284b9a92c8dbae0c15d8e490 > 324f0fc7ea3cbe98104080f99c4573e1d6&X-Amz-SignedHeaders=host& > actor_id=0&response-content-disposition=attachment%3B%20filename%3DPillar- > deployment50.zip&response-content-type=application%2Foctet-stream > >>>> Resolving github-production-release-asset-2e65be.s3.amazonaws.com > >>>> (github-production-release-asset-2e65be.s3.amazonaws.com) > >>>> 54.231.115.35 > >>>> Connecting to github-production-release-asset-2e65be.s3.amazonaws.com > >>>> (github-production-release-asset-2e65be.s3.amazonaws.com) > |54.231.115.35|:443... > >>>> connected. > >>>> HTTP request sent, awaiting response... 200 OK > >>>> Length: 18482449 (18M) [application/octet-stream] > >>>> Saving to: 'imageLn5zD.zip' > >>>> > >>>> imageLn5zD.zip 10%[=> ] 1.88M 502 B/s > in 8m 7s > >>>> > >>>> 2018-01-25 18:15:45 (3.94 KB/s) - Read error at byte 1966661/18482449 > >>>> (Bad file descriptor). Retrying. > >>>> > >>>> --2018-01-25 18:15:46-- (try: 2) > >>>> https://github-production-release-asset-2e65be.s3. > amazonaws.com/41843105/f4ea97f0-e63b-11e7-9012- > edab5af1a547?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential= > AKIAIWNJYAX4CSVEH53A%2F20180125%2Fus-east-1%2Fs3% > 2Faws4_request&X-Amz-Date=20180125T205723Z&X-Amz- > Expires=300&X-Amz-Signature=9ecb9c284b9a92c8dbae0c15d8e490 > 324f0fc7ea3cbe98104080f99c4573e1d6&X-Amz-SignedHeaders=host& > actor_id=0&response-content-disposition=attachment%3B%20filename%3DPillar- > deployment50.zip&response-content-type=application%2Foctet-stream > >>>> Connecting to github-production-release-asset-2e65be.s3.amazonaws.com > >>>> (github-production-release-asset-2e65be.s3.amazonaws.com) > |54.231.115.35|:443... > >>>> connected. > >>>> HTTP request sent, awaiting response... 403 Forbidden > >>>> 2018-01-25 18:15:47 ERROR 403: Forbidden. > >>>> > >>>> > >>>> Also the download speed was super slow. > >>>> > >>>> Any ideas? > >>>> > >>>> Cheers, > >>>> > >>>> HernÃ¡n > >>>> > >>> > >> > > > > -- 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

Jan. 29, 2018

[JOB][PhD] Infrastructure and Language Kernels for IoT Systems

by Marcus Denker

[JOB][PhD] Infrastructure and Language Kernels for IoT Systems The RMOD team of INRIA Lille and the CAR theme of IMT Lille Douai have an open position for a PhD student on Infrastructure and language kernels for IoT Systems. Description ========== Over the last years, the RMOD team of INRIA Lille and the CAR theme of IMT Lille Douai have been working together on creating tiny language core. For example, Guillermo Polito demonstrated in his PhD a fully reflective kernel that fits into 80 kb of memory and that it is possible to have hyper specialized kernels down to 11 kb. We have also worked on remote debugging (PhD of N. Papoulias) and dynamic code updates (PhD of P. Tesone) of such kernels. All of these works are prototyped in Pharo. More recently, RMOD have been working on advanced probes mechanisms (M. Denker) and a solid remote debugging infrastructure (D. Kudriashov). The goal of this PhD is to revisit the architecture around such mini-kernels for building IoT applications. The plan is to: ============= â¢ improve the tools to edit, compile, debug, deploy and update such kernels on IoT devices. Learn how to debug remotely and dynamically update such IoT systems using the TelePharo/PharoThings environment. This task will be in cooperation with M. Denker and D. Kudriashov on remote debugging for IoT and G. Polito for the kernel edition and tooling. â¢ define some language extensions to manage groups of IoT devices to program them at once. Managing hundreds or even thousands of IoT devices is a challenging task. We want to explore different solutions to help deploying and updating groups of IoT devices using some registration mechanism in a cloud server or some groups/roles based approaches for example. Note that ZweiDenker GmbH http://zweidenker.de/en/ is interested in collaboration on the IoT cloud management infrastructure â¢ expressing the architecture of IoT applications. We would like to explore also how to express IoT architectures and what are the abstractions that should be offered to developers such as expressing event-driven architectures with declarative ECA (Event-Conditions-Actions) rules. But we will study a couple of typical IoT applications. â¢ dynamically update an IoT application. An IoT application needs to adapt itself because unreachable or faulty devices or the diminution of available bandwith. We would like that the whole application can reconfigure itself in such situations as Guillaume Grondin proposes it in its PhD. â¢ explore Lightweight Virtual Machines. Virtual machines in the IoT context are very powerful for incremental deployment or dynamic updates. In this task, we would like to investigate what is the minimal memory consumption that we can reach for a VM usable for IoT. Application ========= To apply, please send us : â¢ a CV, â¢ a copy of your Master diploma â¢ a copy of your Master thesis â¢ 2 (two) reference letters, with the contact details of the referents â¢ links to videos of demos of your experiments and/or simulations The application materials should be sent by email to Prof. S. Ducasse stephane.ducasse(a)inria.fr. Email subject must start with : [PhD-RMoD-CAR-2018]. Bibliography ========= â¢ Guillermo Polito, Stephane Ducasse, N Bouraqadi, L Fabresse, M Mattone. Virtualization Support for Dynamic Core Library Update. Onward !, Oct 2015, Pittsburg, USA. â¢ Guillermo Polito. Virtualization Support for Application Runtime Virtualization and Extension. Ph.D. Thesis 2015. Co-delivree par lâUniversite de Lille et lâEcole des Mines de Douai. â¢ Extended results of Tornado : A Run-Fail-Grow approach for Dynamic Application Tayloring. Ecole des mines de Douai, France. 50p, July 2014 â¢ Nick Papoulias, Noury Bouraqadi, Luc Fabresse, Stephane Ducasse and Marcus Denker, Mercury: Properties and Design of a Remote Debugging Solution using Reflection, Journal of Object Technology, 14, 1 :1-36, 2015 Links ===== â¢ Pharo: http://www.pharo.org â¢ PharoThings: https://github.com/pharo-iot/PharoThings â¢ INRIA RMOD: http://rmod.lille.inria.fr â¢ INRIA Lille: http://www.inria.fr/lille â¢ INRIA in General: http://www.inria.fr â¢ Lille: â¢ http://en.wikipedia.org/wiki/Lille â¢ http://wikitravel.org/en/Lille Permanent Link: https://rmod.inria.fr/web/blog/2018-01-25

Jan. 29, 2018

Re: [Pharo-users] Pharo IDE - change mouse cursor color/size

by phil＠highoctane.be

If you are on Windows you can load Vista cursors from the catalog. Then you will have settings for the size. Not all cursors are implemented but it is easy to do. On Linux I had VM crashes when doing #beCursor. Maybe is it fixed these days. Phil On Jan 29, 2018 06:22, "Animosity" <bogdan.radacina+pharo(a)gmail.com> wrote: > Hi there, > > I'm not able to find any setting in the Pharo IDE related to changing the > mouse cursor color or size? > Can this be done at all? Thanks in advance. > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > > >

Jan. 29, 2018

Re: [Pharo-users] Download pillar image -> Error 403: Forbidden

by HernÃ¡n Morales Durand

What I meant with better error messages is for example the problem in main.mk: MAIN = $(shell ./pillar introspect mainDocument) or using MAIN := $(shell ./pillar introspect mainDocument) Which assumes the command always return a "valid" value. (I know make sucks) In my MinGW value of MAIN was empty, then file name is nothing = '.pdf'. But there was no way to figure it out without enabling debug in make. Also I had to setup set -x in shell scripts to see what's going on, and at least in Windows VM nothing is printed in the terminal, so you have to check stdout to see output. Cheers, HernÃ¡n 2018-01-29 2:52 GMT-03:00 HernÃ¡n Morales Durand <hernan.morales(a)gmail.com>: > 2018-01-28 18:55 GMT-03:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >> Hernan >> >> what we can also do is the following: I set up the pillar project on >> github with travis and bintray and when you commit >> the book is automatically built. >> > > Ok, I would try that way. > >> >>> Tried both options, 1) downloading pre-compiled and 2) building from >>> sources+setting up environment. >>> 1) Nothing happened after "pillar archetype build", exit without >>> error, no stdout output, no _result folder >> >> this is super strange. We should check the AppVeyor because it should >> tell us what is not working on windows. >> >>> 2) I got confused with this: >>> >>> mv pillar ~/.pillar >> >> the idea was that once you get pillar on linux/mac we move the >> donwloaded version into ~./pillar >> so that after we have only one pillar installation for all the books >> (contrary to what is done in Pillar 50 and 60). >> >> here is what I get in my .pillar >> >> cd build >> > > A-ha, that's the thing. My build/ is created one level up and not > inside .pillar/ > >> ~/.pillar/build(newpipeline*) Â» ls >> Pharo.changes mustache pharo-ui pillar-db >> Pharo.image pharo pharo-vm pillar-dev-upgrade >> archetypes pharo-local pillar pillar-upgrade >> > > Another difference, you seem to have the wrapper scripts in build/ > > ~/.pillar/build (newpipeline) $ ls > pharo* Pharo.changes Pharo.image PharoDebug.log pharo-local/ > pharo-ui* pharo-vm/ stderr stdout > > >> and >> >> cd pillar >> >> ~/.pillar/pillar(newpipeline*) Â» ls >> LICENSE README.md archetypes scripts src >> > > ~/.pillar (newpipeline) $ ls > archetypes/ build/ LICENSE README.md scripts/ src/ > > >>> because now I have two directories: the .pillar in HOME and the build/ >>> directory separated. And no "pillar" shell script so should I copy the >>> one from 1) ? >> >> >> >> >> >> >>> I will re-check tomorrow maybe I'm reading this the wrong way. >>> > > So I checked, and discovered that the build image hasn't installed > Pillar because there wasn't installed any command handler for > introspect > > Invalid arguments: "pillar introspect > --baseDirectory=C:/Users/mvs/.pillar mainDocument" [ > > The build.sh installs Pillar as follows through a magic variable: > > Metacello new > baseline: 'Pillar'; > repository: > 'filetree:///c/MySmalltalkProjects/Pillar/Latest/pillar/scripts/../src'; > load. > > But gives a SubscriptOutOfBounds: 2 because > WindowsStore>>printPath:on: expects "c:" > (I would love a better error description in stdout file "Invalid > arguments" is not that informative) > > Another load error is that BaselineOfPillar is installing OSSubprocess > and it doesn't work on Windows (#externalCallFailed). > > Should I open issue? > > >>>> so that I can see if this is working. >>>> I know that guille worked on windows and AppVeyor support but he got >>>> distracted by the github refactoring. >>>> We hope to come back this week to Pillar. We plan to release a version >>>> (still with Magritte) but with a full documentation. >>>> >>> >>> Cool, I will test because I have several chapters ready to publish. >>> >>>> Stef >>>> >>>> >>>> >>>> >>>> >>>> On Sat, Jan 27, 2018 at 4:47 PM, HernÃ¡n Morales Durand >>>> <hernan.morales(a)gmail.com> wrote: >>>>> Hi Stef >>>>> >>>>> 2018-01-27 9:30 GMT-03:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >>>>>> Hi Hernan >>>>>> >>>>>> >>>>>> >>>>>> On Thu, Jan 25, 2018 at 10:30 PM, HernÃ¡n Morales Durand >>>>>> <hernan.morales(a)gmail.com> wrote: >>>>>>> I am following the Publishing Pillar Booklet guide from here >>>>>>> https://github.com/SquareBracketAssociates/Booklet-PublishingAPillarBooklet >>>>>> >>>>>> pay attention it is not public because it is in flux because we were >>>>>> working on Pillar 70. >>>>>> >>>>>> Now if you follow the readme of pillar-markup/pillar/ it should work >>>>>> since I used it yesterday. >>>>>> >>>>>> $ wget https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh >>>>>>> $ chmod +x download.sh >>>>>>> $ ./download.sh >>>>>> >>>>>>>./pillar archetype book >>>>>> make book. >>>>>> >>>>>> >>>>>> What you should know is that the stable version sucks at the >>>>>> infrastructure level (relying on too many servers + silent failures in >>>>>> bash files). >>>>>> >>>>>> Can you retry and let me know? >>>>> >>>>> Ok I tried again using MinGW in Windows 8.1 >>>>> Image is downloaded ok but final step gives an error: >>>>> >>>>> $ make book >>>>> support/makefiles/prepare.mk:1: *** Undefined setting OUTPUTDIRECTORY (Directory >>>>> for build products). Stop. >>>>> >>>>> I replaced the expanded shell variables in main.mk from using := to = >>>>> and it seems to "solve" this problem, though someone else should check >>>>> why this happens >>>>> >>>>> MAIN = $(shell ./pillar introspect mainDocument) >>>>> >>>>> OUTPUTDIRECTORY = $(shell ./pillar introspect outputDirectory) >>>>> LATEXTEMPLATE = $(shell ./pillar introspect latexTemplate) >>>>> LATEXCHAPTERTEMPLATE = $(shell ./pillar introspect latexChapterTemplate) >>>>> HTMLTEMPLATE = $(shell ./pillar introspect htmlTemplate) >>>>> HTMLCHAPTERTEMPLATE = $(shell ./pillar introspect htmlChapterTemplate) >>>>> CHAPTERS = $(shell ./pillar introspect chapters) >>>>> >>>>> $ make book >>>>> make: *** No rule to make target `/.pdf', needed by `pdfbook'. Stop. >>>>> >>>>> I am using >>>>> $ make --version >>>>> GNU Make 3.81 >>>>> >>>>> >>>>>> BTW why do you want to compile Booklet-PublishingAPillarBooklet/ >>>>>> If you want just create your own repo and do >>>>>> >>>>>> wget https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh >>>>>> chmod +x download.sh >>>>>> ./download.sh >>>>>> ./pillar archetype book >>>>>> make book. >>>>>> >>>>> >>>>> Thanks, I just followed the install instructions. >>>>> >>>>> HernÃ¡n >>>>> >>>>>> >>>>>> Stef >>>>>> >>>>>> >>>>>>> $ git clone git@github.com:SquareBracketAssociates/Booklet-PublishingAPillarBooklet.git >>>>>>> $ cd Booklet-PublishingAPillarBooklet/ >>>>>>> $ wget https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh >>>>>>> $ chmod +x download.sh >>>>>>> $ ./download.sh >>>>>>> >>>>>>> --2018-01-25 17:56:32-- http://get.pharo.org/vm50 >>>>>>> Resolving get.pharo.org (get.pharo.org) 164.132.235.17 >>>>>>> Connecting to get.pharo.org (get.pharo.org)|164.132.235.17|:80... connected. >>>>>>> HTTP request sent, awaiting response... 200 OK >>>>>>> Length: 5819 (5.7K) >>>>>>> Saving to: 'STDOUT' >>>>>>> >>>>>>> 0K ..... 100% 371K=0.02s >>>>>>> >>>>>>> 2018-01-25 17:56:33 (371 KB/s) - written to stdout [5819/5819] >>>>>>> >>>>>>> Downloading the latest pharoVM: >>>>>>> http://files.pharo.org/get-files/50/pharo-win-stable.zip >>>>>>> pharo-vm/Pharo.exe >>>>>>> Downloading PharoV50.sources: >>>>>>> http://files.pharo.org/get-files/50/sources.zip >>>>>>> Creating starter scripts pharo and pharo-ui >>>>>>> --2018-01-25 17:57:21-- >>>>>>> https://github.com/pillar-markup/pillar/releases/download/50/Pillar-deploym… >>>>>>> Resolving github.com (github.com) 192.30.253.112, 192.30.253.113 >>>>>>> Connecting to github.com (github.com)|192.30.253.112|:443... connected. >>>>>>> HTTP request sent, awaiting response... 302 Found >>>>>>> Location: https://github-production-release-asset-2e65be.s3.amazonaws.com/41843105/f4… >>>>>>> [following] >>>>>>> --2018-01-25 17:57:23-- >>>>>>> https://github-production-release-asset-2e65be.s3.amazonaws.com/41843105/f4… >>>>>>> Resolving github-production-release-asset-2e65be.s3.amazonaws.com >>>>>>> (github-production-release-asset-2e65be.s3.amazonaws.com) >>>>>>> 54.231.115.35 >>>>>>> Connecting to github-production-release-asset-2e65be.s3.amazonaws.com >>>>>>> (github-production-release-asset-2e65be.s3.amazonaws.com)|54.231.115.35|:443... >>>>>>> connected. >>>>>>> HTTP request sent, awaiting response... 200 OK >>>>>>> Length: 18482449 (18M) [application/octet-stream] >>>>>>> Saving to: 'imageLn5zD.zip' >>>>>>> >>>>>>> imageLn5zD.zip 10%[=> ] 1.88M 502 B/s in 8m 7s >>>>>>> >>>>>>> 2018-01-25 18:15:45 (3.94 KB/s) - Read error at byte 1966661/18482449 >>>>>>> (Bad file descriptor). Retrying. >>>>>>> >>>>>>> --2018-01-25 18:15:46-- (try: 2) >>>>>>> https://github-production-release-asset-2e65be.s3.amazonaws.com/41843105/f4… >>>>>>> Connecting to github-production-release-asset-2e65be.s3.amazonaws.com >>>>>>> (github-production-release-asset-2e65be.s3.amazonaws.com)|54.231.115.35|:443... >>>>>>> connected. >>>>>>> HTTP request sent, awaiting response... 403 Forbidden >>>>>>> 2018-01-25 18:15:47 ERROR 403: Forbidden. >>>>>>> >>>>>>> >>>>>>> Also the download speed was super slow. >>>>>>> >>>>>>> Any ideas? >>>>>>> >>>>>>> Cheers, >>>>>>> >>>>>>> HernÃ¡n >>>>>>> >>>>>> >>>>> >>>> >>> >>

Jan. 29, 2018

Re: [Pharo-users] Download pillar image -> Error 403: Forbidden

by HernÃ¡n Morales Durand

2018-01-28 18:55 GMT-03:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > Hernan > > what we can also do is the following: I set up the pillar project on > github with travis and bintray and when you commit > the book is automatically built. > Ok, I would try that way. > >> Tried both options, 1) downloading pre-compiled and 2) building from >> sources+setting up environment. >> 1) Nothing happened after "pillar archetype build", exit without >> error, no stdout output, no _result folder > > this is super strange. We should check the AppVeyor because it should > tell us what is not working on windows. > >> 2) I got confused with this: >> >> mv pillar ~/.pillar > > the idea was that once you get pillar on linux/mac we move the > donwloaded version into ~./pillar > so that after we have only one pillar installation for all the books > (contrary to what is done in Pillar 50 and 60). > > here is what I get in my .pillar > > cd build > A-ha, that's the thing. My build/ is created one level up and not inside .pillar/ > ~/.pillar/build(newpipeline*) Â» ls > Pharo.changes mustache pharo-ui pillar-db > Pharo.image pharo pharo-vm pillar-dev-upgrade > archetypes pharo-local pillar pillar-upgrade > Another difference, you seem to have the wrapper scripts in build/ ~/.pillar/build (newpipeline) $ ls pharo* Pharo.changes Pharo.image PharoDebug.log pharo-local/ pharo-ui* pharo-vm/ stderr stdout > and > > cd pillar > > ~/.pillar/pillar(newpipeline*) Â» ls > LICENSE README.md archetypes scripts src > ~/.pillar (newpipeline) $ ls archetypes/ build/ LICENSE README.md scripts/ src/ >> because now I have two directories: the .pillar in HOME and the build/ >> directory separated. And no "pillar" shell script so should I copy the >> one from 1) ? > > > > > > >> I will re-check tomorrow maybe I'm reading this the wrong way. >> So I checked, and discovered that the build image hasn't installed Pillar because there wasn't installed any command handler for introspect Invalid arguments: "pillar introspect --baseDirectory=C:/Users/mvs/.pillar mainDocument" [ The build.sh installs Pillar as follows through a magic variable: Metacello new baseline: 'Pillar'; repository: 'filetree:///c/MySmalltalkProjects/Pillar/Latest/pillar/scripts/../src'; load. But gives a SubscriptOutOfBounds: 2 because WindowsStore>>printPath:on: expects "c:" (I would love a better error description in stdout file "Invalid arguments" is not that informative) Another load error is that BaselineOfPillar is installing OSSubprocess and it doesn't work on Windows (#externalCallFailed). Should I open issue? >>> so that I can see if this is working. >>> I know that guille worked on windows and AppVeyor support but he got >>> distracted by the github refactoring. >>> We hope to come back this week to Pillar. We plan to release a version >>> (still with Magritte) but with a full documentation. >>> >> >> Cool, I will test because I have several chapters ready to publish. >> >>> Stef >>> >>> >>> >>> >>> >>> On Sat, Jan 27, 2018 at 4:47 PM, HernÃ¡n Morales Durand >>> <hernan.morales(a)gmail.com> wrote: >>>> Hi Stef >>>> >>>> 2018-01-27 9:30 GMT-03:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >>>>> Hi Hernan >>>>> >>>>> >>>>> >>>>> On Thu, Jan 25, 2018 at 10:30 PM, HernÃ¡n Morales Durand >>>>> <hernan.morales(a)gmail.com> wrote: >>>>>> I am following the Publishing Pillar Booklet guide from here >>>>>> https://github.com/SquareBracketAssociates/Booklet-PublishingAPillarBooklet >>>>> >>>>> pay attention it is not public because it is in flux because we were >>>>> working on Pillar 70. >>>>> >>>>> Now if you follow the readme of pillar-markup/pillar/ it should work >>>>> since I used it yesterday. >>>>> >>>>> $ wget https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh >>>>>> $ chmod +x download.sh >>>>>> $ ./download.sh >>>>> >>>>>>./pillar archetype book >>>>> make book. >>>>> >>>>> >>>>> What you should know is that the stable version sucks at the >>>>> infrastructure level (relying on too many servers + silent failures in >>>>> bash files). >>>>> >>>>> Can you retry and let me know? >>>> >>>> Ok I tried again using MinGW in Windows 8.1 >>>> Image is downloaded ok but final step gives an error: >>>> >>>> $ make book >>>> support/makefiles/prepare.mk:1: *** Undefined setting OUTPUTDIRECTORY (Directory >>>> for build products). Stop. >>>> >>>> I replaced the expanded shell variables in main.mk from using := to = >>>> and it seems to "solve" this problem, though someone else should check >>>> why this happens >>>> >>>> MAIN = $(shell ./pillar introspect mainDocument) >>>> >>>> OUTPUTDIRECTORY = $(shell ./pillar introspect outputDirectory) >>>> LATEXTEMPLATE = $(shell ./pillar introspect latexTemplate) >>>> LATEXCHAPTERTEMPLATE = $(shell ./pillar introspect latexChapterTemplate) >>>> HTMLTEMPLATE = $(shell ./pillar introspect htmlTemplate) >>>> HTMLCHAPTERTEMPLATE = $(shell ./pillar introspect htmlChapterTemplate) >>>> CHAPTERS = $(shell ./pillar introspect chapters) >>>> >>>> $ make book >>>> make: *** No rule to make target `/.pdf', needed by `pdfbook'. Stop. >>>> >>>> I am using >>>> $ make --version >>>> GNU Make 3.81 >>>> >>>> >>>>> BTW why do you want to compile Booklet-PublishingAPillarBooklet/ >>>>> If you want just create your own repo and do >>>>> >>>>> wget https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh >>>>> chmod +x download.sh >>>>> ./download.sh >>>>> ./pillar archetype book >>>>> make book. >>>>> >>>> >>>> Thanks, I just followed the install instructions. >>>> >>>> HernÃ¡n >>>> >>>>> >>>>> Stef >>>>> >>>>> >>>>>> $ git clone git@github.com:SquareBracketAssociates/Booklet-PublishingAPillarBooklet.git >>>>>> $ cd Booklet-PublishingAPillarBooklet/ >>>>>> $ wget https://raw.githubusercontent.com/pillar-markup/pillar/master/download.sh >>>>>> $ chmod +x download.sh >>>>>> $ ./download.sh >>>>>> >>>>>> --2018-01-25 17:56:32-- http://get.pharo.org/vm50 >>>>>> Resolving get.pharo.org (get.pharo.org) 164.132.235.17 >>>>>> Connecting to get.pharo.org (get.pharo.org)|164.132.235.17|:80... connected. >>>>>> HTTP request sent, awaiting response... 200 OK >>>>>> Length: 5819 (5.7K) >>>>>> Saving to: 'STDOUT' >>>>>> >>>>>> 0K ..... 100% 371K=0.02s >>>>>> >>>>>> 2018-01-25 17:56:33 (371 KB/s) - written to stdout [5819/5819] >>>>>> >>>>>> Downloading the latest pharoVM: >>>>>> http://files.pharo.org/get-files/50/pharo-win-stable.zip >>>>>> pharo-vm/Pharo.exe >>>>>> Downloading PharoV50.sources: >>>>>> http://files.pharo.org/get-files/50/sources.zip >>>>>> Creating starter scripts pharo and pharo-ui >>>>>> --2018-01-25 17:57:21-- >>>>>> https://github.com/pillar-markup/pillar/releases/download/50/Pillar-deploym… >>>>>> Resolving github.com (github.com) 192.30.253.112, 192.30.253.113 >>>>>> Connecting to github.com (github.com)|192.30.253.112|:443... connected. >>>>>> HTTP request sent, awaiting response... 302 Found >>>>>> Location: https://github-production-release-asset-2e65be.s3.amazonaws.com/41843105/f4… >>>>>> [following] >>>>>> --2018-01-25 17:57:23-- >>>>>> https://github-production-release-asset-2e65be.s3.amazonaws.com/41843105/f4… >>>>>> Resolving github-production-release-asset-2e65be.s3.amazonaws.com >>>>>> (github-production-release-asset-2e65be.s3.amazonaws.com) >>>>>> 54.231.115.35 >>>>>> Connecting to github-production-release-asset-2e65be.s3.amazonaws.com >>>>>> (github-production-release-asset-2e65be.s3.amazonaws.com)|54.231.115.35|:443... >>>>>> connected. >>>>>> HTTP request sent, awaiting response... 200 OK >>>>>> Length: 18482449 (18M) [application/octet-stream] >>>>>> Saving to: 'imageLn5zD.zip' >>>>>> >>>>>> imageLn5zD.zip 10%[=> ] 1.88M 502 B/s in 8m 7s >>>>>> >>>>>> 2018-01-25 18:15:45 (3.94 KB/s) - Read error at byte 1966661/18482449 >>>>>> (Bad file descriptor). Retrying. >>>>>> >>>>>> --2018-01-25 18:15:46-- (try: 2) >>>>>> https://github-production-release-asset-2e65be.s3.amazonaws.com/41843105/f4… >>>>>> Connecting to github-production-release-asset-2e65be.s3.amazonaws.com >>>>>> (github-production-release-asset-2e65be.s3.amazonaws.com)|54.231.115.35|:443... >>>>>> connected. >>>>>> HTTP request sent, awaiting response... 403 Forbidden >>>>>> 2018-01-25 18:15:47 ERROR 403: Forbidden. >>>>>> >>>>>> >>>>>> Also the download speed was super slow. >>>>>> >>>>>> Any ideas? >>>>>> >>>>>> Cheers, >>>>>> >>>>>> HernÃ¡n >>>>>> >>>>> >>>> >>> >> >

Jan. 29, 2018

Pharo IDE - change mouse cursor color/size

by Animosity

Hi there, I'm not able to find any setting in the Pharo IDE related to changing the mouse cursor color or size? Can this be done at all? Thanks in advance. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Jan. 29, 2018