January 2018 - Pharo-users - lists.pharo.org

[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

Re: [Pharo-users] New booklets organisation and new booklet

by Offray Vladimir Luna CÃ¡rdenas

Hi, Nice to see this collection organized in this way with more targeted reading audiences. The DrGeo PDFs are linked in the pageÂ Phil pointed to: * English: https://launchpadlibrarian.net/300141633/drgeo-english.pdf * French: https://launchpadlibrarian.net/322576649/drgeo.pdf You could add several books which are made with Grafoscopio: * The User Manual (pdf): http://mutabit.com/repos.fossil/grafoscopio/doc/tip/Docs/En/Books/Manual/ma… * Manual de Periodismo de datos (The Data Driven Journalist Handbook) o PDF: http://mutabit.com/repos.fossil/mapeda/uv/mapeda.pdf o Epub: http://mutabit.com/repos.fossil/mapeda/uv/mapeda.epub o Repo: http://mutabit.com/repos.fossil/mapeda/ * Pasos para una Biblioteca Digital de BogotÃ¡ (Steps towards the Bogota Digital Library): o PDF: http://mutabit.com/repos.fossil/dataweek/uv/Artefactos/BibliotecaDigitalBog… o Repo: http://mutabit.com/repos.fossil/dataweek/doc/tip/Artefactos/BibliotecaDigit… We are just starting, but I think that the local community will be producing a good collection of digital publications, mainly books and booklets, powered by Grafoscopio, and done easily in a multiplatform and portable setup (Windows, Linux, Mac). We plan to follow a similar approach to GitBook [1] and LeanPub [2], and we have made some contacts with some publishers, authors and translators who would like to have a Open Reproducible Publishing Light Environment. Once we have more work done we will build our own books and booklets collection, so, may be we can showcase this work in some "powered by Pharo" publishing examples. [1] https://www.gitbook.com/ [2] https://leanpub.com/ I know there is a very vocal opposition in this community about using anything but Pillar for documentation, but I think that showing that there is a strong support for writing complex documents, using Pharo powered tools and playing well with others, can be a strong point of advocacy about what is possible within this ecosystem, tech and community for a wider audience beyond programmers, like kids, school teachers, journalist, hacktivist, librarians, and so on. Cheers, Offray On 28/01/18 16:44, Stephane Ducasse wrote: > If hilaire send me a pdf I will add them. I did not about them. > > Stef > > On Sun, Jan 28, 2018 at 11:55 AM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: >> Looks nice. >> >> We should also put the books of Dr Geo in there but maybe they are GPL. >> >> But at least a link to http://www.drgeo.eu/help would be nice. >> >> Phil >> >> On Sun, Jan 28, 2018 at 10:47 AM, Esteban Lorenzano <estebanlm(a)gmail.com> >> wrote: >>> +1 >>> >>>> On 27 Jan 2018, at 20:55, Stephane Ducasse <stepharo.self(a)gmail.com> >>>> wrote: >>>> >>>> Hi >>>> >>>> We reorganised the books.pharo.org web site to make the distinction >>>> between technology and teaching oriented booklet. >>>> We will have specific covers soon and print available on lulu. >>>> >>>> In addition we got the new booklet from C. Bera that explains Call >>>> Stack Management. >>>> >>>> http://books.pharo.org >>>> >>>> Stef >>>> >>> >>> >

Jan. 29, 2018

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

by Stephane Ducasse

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. > 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 ~/.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 and cd pillar ~/.pillar/pillar(newpipeline*) Â» ls LICENSE README.md archetypes 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 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. 28, 2018

Re: [Pharo-users] New booklets organisation and new booklet

by Stephane Ducasse

If hilaire send me a pdf I will add them. I did not about them. Stef On Sun, Jan 28, 2018 at 11:55 AM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > Looks nice. > > We should also put the books of Dr Geo in there but maybe they are GPL. > > But at least a link to http://www.drgeo.eu/help would be nice. > > Phil > > On Sun, Jan 28, 2018 at 10:47 AM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: >> >> +1 >> >> > On 27 Jan 2018, at 20:55, Stephane Ducasse <stepharo.self(a)gmail.com> >> > wrote: >> > >> > Hi >> > >> > We reorganised the books.pharo.org web site to make the distinction >> > between technology and teaching oriented booklet. >> > We will have specific covers soon and print available on lulu. >> > >> > In addition we got the new booklet from C. Bera that explains Call >> > Stack Management. >> > >> > http://books.pharo.org >> > >> > Stef >> > >> >> >> >

Jan. 28, 2018

Re: [Pharo-users] How to specify generic (non-github) git dependency?

by Stephane Ducasse

Yes such solution will be back ported to Pharo 6.1 On Sun, Jan 28, 2018 at 10:05 PM, <herby(a)mailbox.sk> wrote: > > > On January 28, 2018 9:54:44 PM GMT+01:00, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> wrote: >>Herby, >> >>Right now there is "no portable way" to specify arbitrary hosts in a >>Metacello spec ... but Esteban and I will be talking about this on >>Monday ... Thierry Goubier seems to have a nice scheme for gitfiletree > > I already early-adopted tonel, so... (Btw, make it easier to set tonel to new repo / first src commit, now it's so arcane I tried maybe six times to actually get there correctly; I always ended with filtree or only half-baked tonel without .properties) > >>and I think that iceberg might support additional urls and schemes... > > Npm uses git+https IIRC, scp is also used, it would be also nice if usr@host:path gets parsed. > > Thanks again, plus I hope it will be backported to 6.1. > >>Dale > > Herby > >> >> >>On 01/28/2018 01:52 AM, Herbert VojÄÃk wrote: >>> Hi, >>> >>> I know I can do, for example, >>> >>> [..snip..] >>> package: 'Foo' with: [ spec >>> requires: #('Mocketry') ]; >>> >>> baseline: 'Mocketry' with: [ spec >>> repository: 'github://dionisiydk/Mocketry:v4.0.x' ]; >>> [..snip..] >>> >>> but when I want to add dependency to a repo which is not on github >>nor >>> on bitbucket, how do I specify (https or scp) git depedency in >>generic >>> way? >>> >>> Thanks, Herby >>> >

Jan. 28, 2018

Re: [Pharo-users] How to specify generic (non-github) git dependency?

by herby＠mailbox.sk

On January 28, 2018 9:54:44 PM GMT+01:00, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> wrote: >Herby, > >Right now there is "no portable way" to specify arbitrary hosts in a >Metacello spec ... but Esteban and I will be talking about this on >Monday ... Thierry Goubier seems to have a nice scheme for gitfiletree I already early-adopted tonel, so... (Btw, make it easier to set tonel to new repo / first src commit, now it's so arcane I tried maybe six times to actually get there correctly; I always ended with filtree or only half-baked tonel without .properties) >and I think that iceberg might support additional urls and schemes... Npm uses git+https IIRC, scp is also used, it would be also nice if usr@host:path gets parsed. Thanks again, plus I hope it will be backported to 6.1. >Dale Herby > > >On 01/28/2018 01:52 AM, Herbert VojÄÃk wrote: >> Hi, >> >> I know I can do, for example, >> >> [..snip..] >> Â Â Â Â package: 'Foo' with: [ spec >> Â Â Â Â Â Â Â requires: #('Mocketry') ]; >> >> Â Â Â Â baseline: 'Mocketry' with: [ spec >> Â Â Â Â Â Â Â repository: 'github://dionisiydk/Mocketry:v4.0.x' ]; >> [..snip..] >> >> but when I want to add dependency to a repo which is not on github >nor >> on bitbucket, how do I specify (https or scp) git depedency in >generic >> way? >> >> Thanks, Herby >>

Jan. 28, 2018