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

[Pharo 7.0-dev] Build #438: 20953-Gitlab Private Project Support (via Iceberg)
by ci-pharo-ci-jenkins2＠inria.fr Jan. 20, 2018

Jan. 20, 2018

There is a new Pharo build available! The status of the build #438 was: FAILURE. The Pull Request #667 was integrated: "20953-Gitlab Private Project Support (via Iceberg)" Pull request url: https://github.com/pharo-project/pharo/pull/667 Issue Url: https://pharo.fogbugz.com/f/cases/20953 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] Fari â a shell tool to fetch & prepare your fresh images
by Damien Pollet Jan. 20, 2018

Jan. 20, 2018

Here it is, tell me what you think: https://github.com/cdlm/fari.sh We discussed it with Christophe and of course there is some overlap with PharoLauncher, and in the future, it might get replaced by a command-line version of PharoLauncher based on Clap. But for the moment it works and fits my twisted mind better ð -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

3 3

[IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!
by Esteban Lorenzano Jan. 19, 2018

Jan. 19, 2018

Hi! Iâm working on simplifying the contribution process, after collecting opinions/experiences last couple of months. As you know, Pharo contribution process is still WIP and we aim to have it as smooth as possible for Pharo 7.0 release. Now, after observe the idea of the âsystem repositoriesâ was a bad idea because it introduced extra and non standard âpathâ to contribution, I managed to remove that to reestablish âthe regular wayâ: you will now need to add pharo repository just as any other repository you add, by cloning or adding local repository. I took Guilleâs doc and moved it to pharo project (it does not has sense to have it living in a contributorâs repository when is so important). You can find it here: https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo <https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo> This document is also updated to reveal this new process, please read it. How to update your startup scripts? Some people has added startup scripts to easy the first part of contribution. Instead enabling system repositories, etc. you now need to replace that with this: (IceRepositoryCreator new location: '/path/to/pharo-project/pharo' asFileReference; subdirectory: 'src'; createRepository) register PLEASE, PLEASE, PLEASEâ¦ take a moment to read and try the document. Is very important that document reflects new process and works reliable in different scenarios (I validated it on macOS and Windows, and assumed it worked fine on linux but you knowâ¦ bad assumptions is the base of failure ;) ) Iâm eager to hear your feedback and continue enhancing the process. (yes, Stef, I know UI is still cumbersomeâ¦ Iâm working on that :) ) cheers! Esteban

13 57

Esteban's ChangeLog week of 8 January 2018
by estebanlm＠gmail.com Jan. 19, 2018

Jan. 19, 2018

Hello! This is my weekly ChangeLog, from 8 January 2018 to 14 January 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=8/1/2018&to=14/1/2018 ChangeLog ========= 12 January 2018: ---------------- * So well... it was the full week trying to compile all dependences for win64. and failed. Not that I didn't make any progress... but I still cann't compile +libssh2+ not +cairo+ :( (all the others are being built correctly) 8 January 2018: --------------- * Still trying to compile dependences for win64 (stuck on libssh2 for now) :( cheers! Esteban

2 1

[JOB][Research] Inria Research CRCN Position
by Marcus Denker Jan. 19, 2018

Jan. 19, 2018

FULL TIME PERMANENT RESEARCH POSITIONS IN LILLE, FRANCE Inria opens on January 15, 2018 nine competitions of normal class researchers. 23 positions will be filled in the 8 research centers of the Institute. The deadline for submitting applications is 19 February 2018 midnight French time. CRCN âYoung graduate scientistâ The CRCN position is a research position for both Junior (old CR2) and Senior (old CR1) level researchers. No teaching, permanent position with tenure after a probation period of 12 Months. Requirements: â¢ Holders of a doctorate or equivalent degree; â¢ Applicants able to prove publications and scientific work deemed equivalent. There are no age limits or nationality requirements for the recruitment of young graduated scientists. More information: https://www.inria.fr/en/institute/recruitment/offers/young-graduate-scienti… PROFILE The candidate must have a doctoral degree, a strong background in Computer Science, and internationally significant research achievements in software engineering (particularly software evolution) and/or programming languages. Duties include: â¢ Research (no teaching). â¢ Help manage the RMoD Research group. â¢ Be involved with the self-governance of the Inria Lab and Inria as a whole. â¢ Guide PhD students (and therefore get a French habilitation to be able to formally supervise PhD students). â¢ Help acquire additional funds for PhD students, Postdocs and Engineers. â¢ Transfer research results to the real world. MISSION Join one of our two lines of research: Tools for Software Maintenance or New Programming Language Constructs for Software Evolution. THE REGION Lille is strategically located in Northern Europe with train connections to Paris (1h) , London (1h30) and Brussels (30 min.) The Nord Pas de Calais region is a dynamic area in both industry and research for computer science with companies that are european leaders in their branch. Lille, the capital of northern France is an attractive metropolis of over 1 million inhabitants. Cost of living in Lille is lower than that of very big cities such as Paris and London. THE TEAM RMoD is an Inria research project team. It consists of 6 permant researchers (Inria CR and DR, as well as University Assistant Professors) and Engineers, postdocs and students (Master and PhD). RMoD is an international team with more than 20 members from six countries. LINKS: â¢ 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 APPLICATION Please contact the head of the research team: Stephane.Ducasse(a)inria.fr or one of the following group members: Nicolas.Anquetil(a)inria.fr, Marcus.Denker(a)inria.fr

1 0

[Pharo 7.0-dev] Build #437: 20992-Use-Stdio-class-instead-of-VTermOutputDriver
by ci-pharo-ci-jenkins2＠inria.fr Jan. 19, 2018

Jan. 19, 2018

There is a new Pharo build available! The status of the build #437 was: SUCCESS. The Pull Request #691 was integrated: "20992-Use-Stdio-class-instead-of-VTermOutputDriver" Pull request url: https://github.com/pharo-project/pharo/pull/691 Issue Url: https://pharo.fogbugz.com/f/cases/20992 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Ann] Calypso scoped refactoring
by Denis Kudriashov Jan. 18, 2018

Jan. 18, 2018

I finally implemented scopes support for refactorings in Calypso to be able restrict system changes to particular set of packages or classes. The new preview tool is copy of old ChangesBrowser with additional scopes list widget: In this picture I requested Announcer>>initialize rename and switched scope to the Announcer package. Scopes are filled by browser where refactoring was requested. It is same logic how method browser receives scopes from original browser. When user changes scope all refactoring changes are recomputed. It was last dependency of Calypso from Nautilus related packages. Now it can be loaded without Nautilus. Best regards, Denis

4 3

[Pharo 7.0-dev] Build #436: 20942-Integrate-Epicea-826-in-Ph7
by ci-pharo-ci-jenkins2＠inria.fr Jan. 18, 2018

Jan. 18, 2018

There is a new Pharo build available! The status of the build #436 was: SUCCESS. The Pull Request #690 was integrated: "20942-Integrate-Epicea-826-in-Ph7" Pull request url: https://github.com/pharo-project/pharo/pull/690 Issue Url: https://pharo.fogbugz.com/f/cases/20942 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] Pharo TechTalk Dates
by Marcus Denker Jan. 18, 2018

Jan. 18, 2018

Hi, Here are the next dates for the Pharo Techtalks. (for recording of the past ones, see: http://pharo.org/TechTalk ) Jan 30: Pharo TechTalk: Genetic Algorithms https://association.pharo.org/event-2757884 For the others we have no topic yet, but dates are pre-fixed to: Feb 15 https://association.pharo.org/event-2797065 March 22 https://association.pharo.org/event-2797067 April 12 https://association.pharo.org/event-2797068 May 17 https://association.pharo.org/event-2797069 June 14 https://association.pharo.org/event-2797070 - If you have ideas for topics, please tell us! - With no topic, we will use this slot for a general free discussion. - If you want to do a TechTalk about a topic but no date is good, we can change the date! Marcus

2 2

Re: [Pharo-dev] [Pharo-users] [Vm-dev] Running headless on Windows
by Nicolai Hess Jan. 18, 2018

Jan. 18, 2018

2017-12-29 16:53 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > 2017-12-29 16:13 GMT+01:00 Andrei Stebakov <lispercat(a)gmail.com>: > >> Nicolai, the maximize/non-maximize trick worked! Thanks! I wonder if it's >> an easy fix to put in Pharo. >> > > So it means that something in image is not initialised. It can be another > bug of wrong startup order > Maybe a problem on the image and the vm side. Even in headless mode, starting pharo creates a window. Even if it is hidden, it has some size. Quit and Saving an image will write the current width/height into the image file. Starting the vm will create a window and set the size of the window to the last size. The window is always created in normal (not-maximized) mode and the available size is a little bit smaller than for a maximized window. Now, the image checks for a change of the size of the current DisplayScreen instance and the actual screen size. If this is different (as in this case) a new DisplayScreen is initialized which will call a full screen update (ioForceDisplayUpdate). And this method will show a hidden (headless) image. > > >> >> On Fri, Dec 29, 2017 at 6:22 AM, phil(a)highoctane.be <phil(a)highoctane.be> >> wrote: >> >>> I am using nssm because the service option is broken. >>> >>> The code seems to still be in the image but disabled (there are quite a >>> few things like that actually). >>> >>> Phil >>> >>> >>> On Fri, Dec 29, 2017 at 11:59 AM, Torsten Bergmann <astares(a)gmx.de> >>> wrote: >>> >>>> >>>> Hi, (cross posting vm-dev) >>>> >>>> nssm is nice - but requires additional tools. >>>> >>>> Since the days of Squeak the windows VM had the >>>> >>>> -service "ServiceName" >>>> >>>> option and one was able to run Squeak as a windows service out of the >>>> box. >>>> >>>> See http://wiki.squeak.org/squeak/105 for details. >>>> >>>> This option allows to register/deregister with the windows service >>>> manager and run >>>> a headless image. >>>> >>>> I run a Squeak Wiki (Swiki/Comanche) since years with this and it is >>>> very nice and stable. >>>> >>>> Unfortunately this is broken in recent Pharo VMs and so far Esteban or >>>> others did not >>>> have the time to look into this issue. Would be really nice if this >>>> option could >>>> be recovered in 2018. So one could easily deploy and run Seaside or >>>> Teapot/Tealight >>>> or Zinc/WebClient based web services on Windows. >>>> >>>> If we want to deploy Smalltalk based web applications or services on >>>> Windows we >>>> should support that. It will keep Windows administrators happy and we >>>> would integrate with >>>> the whole ecosystem (for instance you can start/stop a service using >>>> Windows scripting for >>>> doing backups, etc.) right out of the box. >>>> >>>> Bye >>>> T. >>>> >>>> >>>> >>>> Gesendet: Freitag, 29. Dezember 2017 um 11:36 Uhr >>>> Von: "phil(a)highoctane.be" <phil(a)highoctane.be> >>>> An: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org> >>>> Betreff: Re: [Pharo-users] Running headless on Windows >>>> >>>> If you want to run Pharo as a service, I have found nssm to be working >>>> well. >>>> https://nssm.cc >>>> >>>> Phil >>>> >>>> On Dec 29, 2017 09:25, "Nicolai Hess" <nicolaihess(a)gmail.com[mailto: >>>> nicolaihess(a)gmail.com]> wrote: >>>> >>>> >>>> 2017-12-29 3:07 GMT+01:00 Andrei Stebakov <lispercat(a)gmail.com[mailto: >>>> lispercat(a)gmail.com]>: >>>> Pierce, I tried all of those "no display" options, the result is the >>>> same >>>> >>>> >>>> On Dec 28, 2017 8:37 PM, "Pierce Ng" <pierce(a)samadhiweb.com[mailto: >>>> pierce(a)samadhiweb.com]> wrote:On Wed, Dec 27, 2017 at 04:58:39PM >>>> +0100, Cyril Ferlicot D. wrote: >>>> > On 12/27/2017 04:39 PM, Andrei Stebakov wrote: >>>> > > When I run Pharo 6.1 with -- headless option on Windows, it >>>> executes the >>>> > > eval command as expected but during the execution (which lasts 4 >>>> sec) it >>>> > > opens the Pharo GUI. >>>> > > Is it expected? I thought headless means that the whole execution >>>> would >>>> > > happen in the background >>>> > >>>> > I think that currently Pharo does not have a "real" headless. But I >>>> > heard there was work on that part for Pharo 7. >>>> >>>> I know OP is talking about Windows... I've been running server >>>> applications on >>>> Linux without X11 with -vm-display-null and in-image RFBServer for >>>> access to >>>> Pharo over VNC. This works very well for me. >>>> >>>> I believe "real" headless means GUI is not run at all and therefore >>>> does not >>>> consume CPU cycles, which is very welcome. Meanwhile, maybe >>>> -vm-display-null >>>> works on Windows for scripting purposes? >>>> >>>> Pierce >>>> >>>> >>>> >>>> Hi Andrei, >>>> >>>> can you try this: >>>> >>>> Open Pharo normal (no headless option). >>>> Change the window size to "not-maximized" (eve if it is actually not >>>> maximized, maximize it ones and change it back to "not-maximized") >>>> Save and quit the image. >>>> >>>> After that, a call like >>>> >>>> pharo --headless pharo.image eval "DateAndTime now" >>>> will write the output to the stdout file, without opening a window. >>>> >>>> >>>> >>>> >>>> >>>> >>> >>> >> >

1 0