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

Re: [Pharo-dev] cannot write to the changes file

by Cyril Ferlicot D.

Le 13/01/2018 Ã 12:36, Cyril Ferlicot D. a Ã©critÂ : > > Hi, > > For my part it inform that the source file cannot be written at launch > but in the end it is written. > > This problem comes from a refactoring in the location system I think. > Pavel located the problem with the merge of this PR: : https://github.com/pharo-project/pharo/pull/553 -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Jan. 13, 2018

Re: [Pharo-dev] cannot write to the changes file

by Cyril Ferlicot D.

Le 13/01/2018 Ã 05:43, Ben Coman a Ã©critÂ : > Before creating an Issue, can someone confirm the following behaviour on > Windows 10 ? > Downloaded and unzipped into the same folder... > *Â http://files.pharo.org/image/70/Pharo-7.0.0-alpha.build.425.sha.eb0a6fb.arc… > *Â http://files.pharo.org/vm/pharo-spur32/win/pharo-win-i386-201711262336-8879… > > The directory contains... > Pharo7.0-32bit-eb0a6fb.image > Pharo7.0-32bit-eb0a6fb.changes > Pharo.exe > > Double-clickingÂ Pharo.exeÂ produces notification... > Â Â Information > Â Â Pharo cannot write to the changes file namedÂ Â Â Â > Â Â Â Â C:\Users\....\pharo\Pharo7.0-32bit-eb0a6fb.changes. > Â Â Please check that you have write permission for this file. > Â Â You won't be able to save this image correctly until you fix this. > > However if I edit toÂ Â AST-Tests-Core >Â NumberParserTest >> testFail > to add "My Comment"Â Â > then close all windows, Save&Quit the Image, > restart Pharo by double-clicking on Pharo.exe, > and open System Browser on testFail > I can see my comment. > > I'm not clear on exactly how it works but I presume that restarting the > Image would require "My Comment" to be read from the changes file, > but notepad shows its not in the changes file. > So perhaps the error notification is part of a transition in-Image > sources and > nothing to worry about? > > cheers -ben Hi, For my part it inform that the source file cannot be written at launch but in the end it is written. This problem comes from a refactoring in the location system I think. -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Jan. 13, 2018

Re: [Pharo-dev] Protocol names convention

by Benoit St-Jean

Historically, it's always been 'initalize-release' Â ----------------- BenoÃ®t St-Jean Yahoo! Messenger: bstjean Twitter: @BenLeChialeux Pinterest: benoitstjean Instagram: Chef_Benito IRC: lamneth Blogue: endormitoire.wordpress.com "A standpoint is an intellectual horizon of radius zero".Â (A. Einstein) From: Norbert Hartl <norbert(a)hartl.name> To: Pharo Dev <pharo-dev(a)lists.pharo.org> Sent: Saturday, January 13, 2018 6:33 AM Subject: [Pharo-dev] Protocol names convention Iâm not the biggest fan of method categories/protocols but I try to. What strikes me is the huge mess in names we have. Everytime I create e.g. an initialize method Iâm asking myself which is the proper name to choose initialize initializing initialization â¦. Do we have a convention for this? Right now all names starting with init are initialization-data initialize-destroy initialization-filter initialize - release initialize initialization-union initialize - event initializing initialization initalize-release initailize-release initialization widgets initalize initialize-release initialization-release Norbert

Jan. 13, 2018

Protocol names convention

by Norbert Hartl

Iâm not the biggest fan of method categories/protocols but I try to. What strikes me is the huge mess in names we have. Everytime I create e.g. an initialize method Iâm asking myself which is the proper name to choose initialize initializing initialization â¦. Do we have a convention for this? Right now all names starting with init are initialization-data initialize-destroy initialization-filter initialize - release initialize initialization-union initialize - event initializing initialization initalize-release initailize-release initialization widgets initalize initialize-release initialization-release Norbert

Jan. 13, 2018

Re: [Pharo-dev] Blame support P7

by Eliot Miranda

> On Jan 13, 2018, at 2:28 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > > > >> Am 13.01.2018 um 05:22 schrieb Eliot Miranda <eliot.miranda(a)gmail.com>: >> >> Hi Stephane, >> >>> On Fri, Jan 12, 2018 at 1:26 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >>> Hi torsten >>> >>> we have a super long list of *important* fixes and enhancements to do. >> >> Isn't it important to preserve the ability to exchange code between Pharo, Squeak and Cuis? Don't you care that the VM development is directly affected by this? Is the VM and plugin support not important to Pharo? >> > Sure it is important. If you would ask if anyone considers this as not important youâll have a hard time finding many. That is not the point. If everyone stays in its own personal context and judges from there it is obvious that most decisions outside look non-sense from there. > This community is about collaboration. And collaboration does not mean that everyone understands everyone elseâs decision. It means that if you donât understand a decision from someone you still be able to believe he has good reason to do so. If the community is about collaboration then one prioritizes that which promotes collaboration and fixing that which hinders it. > > my 2 cents, > > Norbert > >>> >>> Stef >>> >>> On Fri, Jan 12, 2018 at 1:09 AM, Torsten Bergmann <astares(a)gmx.de> wrote: >>> > Not having timestamps/authors in Pharo 7 due to git and missing blame support >>> > (see [1]) has other bad side effects: >>> > >>> > >>> > - it clobbers all method stamps in an MCZ package [1] if you use Monticello >>> > which can lead easily to trouble/lamenting >>> > >>> > - it is not possible to fileout a changeset [2] in the ChangeSorter >>> > >>> > Was there any further discussion/decision for P7 on solving this >>> > or adding blame support? >>> > >>> > Thx >>> > T. >>> > >>> > >>> > [1] http://forum.world.st/Author-name-in-version-Iceberg-td4968472.html >>> > [2] http://lists.squeakfoundation.org/pipermail/vm-dev/2018-January/026350.html >>> > [3] https://pharo.fogbugz.com/f/cases/20951/ >>> > >>> >> >> >> >> -- >> _,,,^..^,,,_ >> best, Eliot >

Jan. 13, 2018

Re: [Pharo-dev] Blame support P7

by Norbert Hartl

> Am 13.01.2018 um 05:22 schrieb Eliot Miranda <eliot.miranda(a)gmail.com>: > > Hi Stephane, > > On Fri, Jan 12, 2018 at 1:26 AM, Stephane Ducasse <stepharo.self(a)gmail.com <mailto:stepharo.self@gmail.com>> wrote: > Hi torsten > > we have a super long list of *important* fixes and enhancements to do. > > Isn't it important to preserve the ability to exchange code between Pharo, Squeak and Cuis? Don't you care that the VM development is directly affected by this? Is the VM and plugin support not important to Pharo? > Sure it is important. If you would ask if anyone considers this as not important youâll have a hard time finding many. That is not the point. If everyone stays in its own personal context and judges from there it is obvious that most decisions outside look non-sense from there. This community is about collaboration. And collaboration does not mean that everyone understands everyone elseâs decision. It means that if you donât understand a decision from someone you still be able to believe he has good reason to do so. my 2 cents, Norbert > > Stef > > On Fri, Jan 12, 2018 at 1:09 AM, Torsten Bergmann <astares(a)gmx.de <mailto:astares@gmx.de>> wrote: > > Not having timestamps/authors in Pharo 7 due to git and missing blame support > > (see [1]) has other bad side effects: > > > > > > - it clobbers all method stamps in an MCZ package [1] if you use Monticello > > which can lead easily to trouble/lamenting > > > > - it is not possible to fileout a changeset [2] in the ChangeSorter > > > > Was there any further discussion/decision for P7 on solving this > > or adding blame support? > > > > Thx > > T. > > > > > > [1] http://forum.world.st/Author-name-in-version-Iceberg-td4968472.html <http://forum.world.st/Author-name-in-version-Iceberg-td4968472.html> > > [2] http://lists.squeakfoundation.org/pipermail/vm-dev/2018-January/026350.html <http://lists.squeakfoundation.org/pipermail/vm-dev/2018-January/026350.html> > > [3] https://pharo.fogbugz.com/f/cases/20951/ <https://pharo.fogbugz.com/f/cases/20951/> > > > > > > > -- > _,,,^..^,,,_ > best, Eliot

Jan. 13, 2018

Re: [Pharo-dev] cannot write to the changes file

by Alistair Grant

On 13 January 2018 at 08:35, Ben Coman <btc(a)openinworld.com> wrote: > > > On 13 January 2018 at 12:43, Ben Coman <btc(a)openinworld.com> wrote: >> >> Before creating an Issue, can someone confirm the following behaviour on >> Windows 10 ? >> Downloaded and unzipped into the same folder... >> * >> http://files.pharo.org/image/70/Pharo-7.0.0-alpha.build.425.sha.eb0a6fb.arc… >> * >> http://files.pharo.org/vm/pharo-spur32/win/pharo-win-i386-201711262336-8879… >> >> The directory contains... >> Pharo7.0-32bit-eb0a6fb.image >> Pharo7.0-32bit-eb0a6fb.changes >> Pharo.exe >> >> Double-clicking Pharo.exe produces notification... >> Information >> Pharo cannot write to the changes file named >> C:\Users\....\pharo\Pharo7.0-32bit-eb0a6fb.changes. >> Please check that you have write permission for this file. >> You won't be able to save this image correctly until you fix this. > > > and btw, with notepad I can edit and and save the file no problem. > cheers -ben If I open a playground (after getting the "cannot write" error above) and execute: SourceFiles close; ensureOpen The changes file is successfully opened and written to. Cheers, Alistair

Jan. 13, 2018

Re: [Pharo-dev] Blame support P7

by Stephan Eggermont

Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > Isn't it important to preserve the ability to exchange code between Pharo, > Squeak and Cuis? Don't you care that the VM development is directly > affected by this? Is the VM and plugin support not important to Pharo? Git support turns out to be much more work than we hoped and expected. Too many library updates needed, support for different workflows and platforms, switch to file per class. The Iceberg channel on Discord is one of the busiest channels. Stephan

Jan. 13, 2018

Re: [Pharo-dev] ZnClient issue: ZdcPlugin Missing

by Sven Van Caekenberghe

Hi, You need a VM directory that looks like this: $ ls -la ~/Downloads/pharo-win-stable/ total 37608 drwx------@ 20 sven staff 640 Jan 13 10:56 . drwx------+ 802 sven staff 25664 Jan 13 10:56 .. -rwxrwxr-x@ 1 sven staff 173178 May 31 2017 FT2Plugin.dll -rwxrwxr-x@ 1 sven staff 2863994 May 31 2017 Pharo.exe -rwxrwxr-x@ 1 sven staff 2863994 May 31 2017 PharoConsole.exe -rwxr-x---@ 1 sven staff 1752312 May 31 2017 SDL2.dll -rwxrwxr-x@ 1 sven staff 161880 May 31 2017 SqueakSSL.dll -rwxrwxr-x@ 1 sven staff 107648 May 31 2017 SurfacePlugin.dll -rwxr-xr-x@ 1 sven staff 27136 May 31 2017 iconv.dll -rwxr-x---@ 1 sven staff 1369559 May 31 2017 libcairo-2.dll -rwxr-x---@ 1 sven staff 2275722 May 31 2017 libeay32.dll -rwxr-x---@ 1 sven staff 831910 May 31 2017 libfreetype.dll -rwxr-xr-x@ 1 sven staff 92672 May 31 2017 libgcc_s_sjlj-1.dll -rwxr-x---@ 1 sven staff 1493721 May 31 2017 libgit2.dll -rwxr-x---@ 1 sven staff 3676680 May 31 2017 libpixman-1-0.dll -rwxr-x---@ 1 sven staff 461894 May 31 2017 libpng16-16.dll -rwxr-x---@ 1 sven staff 328519 May 31 2017 libssh2-1.dll -rwxr-xr-x@ 1 sven staff 48147 May 31 2017 libwinpthread-1.dll -rwxr-x---@ 1 sven staff 589372 May 31 2017 ssleay32.dll -rwxr-x---@ 1 sven staff 101888 May 31 2017 zlib1.dll You probably miss SqueakSSL.dll or a dependent DLL. HTH, Sven > On 13 Jan 2018, at 10:11, Photon <nico-braun(a)live.de> wrote: > > Hey Cyril, > > thanks for your reply. I do not quite understand your instructions tho. I > mean I get the anti virus part. I checked both folders, the zipped and > unzipped one. They both do not hold any Zclient or Zdc plugin only a > zlib1.dll > > The weird part is that the unzipped ffolder contains more items besides of > my images. There were two particular wich I found in the unzipped folder but > not in the zipped folder: > stderr and stdout wich are just "files"... > > I do not understand what it means to sign the vm to windows tho. How do i do > that? I want to give it a shot. > > Cheers > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

Jan. 13, 2018

Re: [Pharo-dev] [ANN] Dates Pharo Sprints 2018 till June

by Peter UhnÃ¡k

Hi, is it possible to add the events as a google calendar so it updates automatically? Thanks, Peter On Fri, Jan 12, 2018 at 2:37 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > For Pharo sprints for the next months, we suggest these dates: > > Jan 26 > Feb 23 > Mar 30 > Apr 20 > Mai 25 > Jun 29 > > > I have added the first one already to the events page: > https://association.pharo.org/events > > the others will be added later. > Marcus >

Jan. 13, 2018