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

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

by Sven Van Caekenberghe

> On 13 Jan 2018, at 16:58, Photon <nico-braun(a)live.de> wrote: > > Impossibru! Now it is working for me aswell. I don`t know if you changed > something syntax wise but thank you very much for you time and effort. No, no, I did not change anything, you just broke the URL by inserting newlines (inadvertently).

Jan. 13, 2018

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

by Photon

Impossibru! Now it is working for me aswell. I don`t know if you changed something syntax wise but thank you very much for you time and effort. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Jan. 13, 2018

Tonel code?

by Javier PimÃ¡s

Hi, I wanted to do some dialect porting experiments. I want to export to pharo using tonel file format and got some questions. 1. Is this the main source? https://github.com/pharo-vcs/tonel 2. Is it already loaded in pharo 7? 3. Seems to have dependencies with monticello, how hard would it be to have a port without monticello/port the needed monticello dependencies? 4. Any advice? Cheers, Javier -- Javier PimÃ¡s Ciudad de Buenos Aires

Jan. 13, 2018

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

by Sven Van Caekenberghe

Both of the following work for me: (ZnClient new get: 'https://raw.githubusercontent.com/SquareBracketAssociates/LearningOOPWithPh…') lines. (ZnClient new get: 'https://raw.githubusercontent.com/SquareBracketAssociates/LearningOOPWithPh…') lines Of course, the URL has to be on 1 line without newlines or other breaks that could result from copy/pasting. > On 13 Jan 2018, at 15:44, Photon <nico-braun(a)live.de> wrote: > > Oh yes of course... that`s what im saying. I did post it actually allready > twice but the forum seems to delete raw text. So i have to post and then > edit to put then tet back in every time. But yes here is the code: > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

Jan. 13, 2018

Re: [Pharo-dev] Blame support P7

by Sven Van Caekenberghe

> On 13 Jan 2018, at 15:13, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Hi Sven, > >> On Jan 13, 2018, at 6:01 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> >> >>> On 13 Jan 2018, at 05:22, 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? >> >> Eliot, >> >> Not trying to minimise your contributions (we all love the VM), and I know that you favour collaboration, but >> >> (1) what non-trivial code is actively maintained from a single code base between Pharo, Squeak and Cuis ? > > Alien Hmm, not that active. And it requires Pharo/Cuis to use an 'older' loading mechanism (from their perspective evolving to git SCM). Other than that, a very short list. You know just as well as that it is close to impossible to do this (Seaside and FUEL are the only real counter examples, and even there it is a lot of work). >> (2) how/where are you developing in Pharo ? I only see you contributing to Squeak, where only a handful of very experienced developers are making occasional, conservative changes to maintain their own environment. > > You may be using the 64-bit version of Pharo. That is my work. If you're using the FFI then I've had a part in it (callbacks being the most specific). And the new release will use the Sista bytecode set. That's me and ClÃ©ment. ClÃ©ment and others integrate stuff on my behalf. I also work closely with people in the Pharo community and get work from users of Pharo. Pharo is important to me. But this isn't about me. I started by saying that I know and appreciate your work. Since I did not say anything otherwise, you do not need to get defensive. "They integrate an my behalf" is exactly my point: you do something in your closed world and others can follow. > I disagree with your description of the Squeak community. St Potsdam it is used by students. The raspberry pi scratch was in Squeak until late last year. It is not as you describe. It is and you know it. >> For me, and many others the VM is a completely closed ecosystem, a black box. A know the simulator is cool, but I have never seen it. > > What does that have to do with this discussion? Because you argue about collaboration while you act in a certain way. Again, I am fine if you make certain choices, everyone does, but you cannot ask others to do what you do no do yourself. >> Your choice to use Squeak is a valid one that probably makes sense to you, but you must also respect the successful alternative that Pharo is. > > Again how does my criticisms my the git integration have anything to do with Pharo being a successful alternative? Do you think I want Pharo to fail? Do you think I would bother commenting if I wasn't interested? SCM and moving to git was argued about ad infinitum for years, Pharo (and others) are moving to it since a very long time. We're not there yet, but progress is good. (And yes the timestamps have to come back, the history is another issue). Starting 2018 by attacking that all that work is very cool indeed ;-) Stef explained factually how we still maintain enough modelling in Smalltalk. >> Sven >> >>> 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/

Jan. 13, 2018

Re: [Pharo-dev] Blame support P7

by Benoit St-Jean

Just a reminder... We're only 13 days into the new year... Let's take a deep breath everyone... We're all smalltalkers : I'm sure we can discuss all this in a civilized way, with arguments and good manners in a joyful and respectful atmosphere!Â We're not at war : we are exchanging ideas! If we didn't care about Pharo/Squeak/Cuis/Dolphin/OS/VW/VAST/Whatever, we wouldn't criticize at all. "On critique bien ceux que l'on aime bien" :)Â ----------------- 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)

Jan. 13, 2018

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

by Stephane Ducasse

Excellent! Tx pavel. On Sat, Jan 13, 2018 at 12:37 PM, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > 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] Protocol names convention

by Stephane Ducasse

Yes and In automaticMethodCategorizer (an old project that I improved for nothing) I did a protocol analyser to help taking some decision on protocol names. Stef On Sat, Jan 13, 2018 at 2:53 PM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > On 13 January 2018 at 13:50, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: >> Le 13/01/2018 Ã 13:46, Norbert Hartl a Ã©crit : >>> >>> Sounds great! In which class is the code that does the decision about the right name? I think I find my convention here.+ >>> >> >> There is MethodClassifier with pragma, prefix and suffix map class side. > > Which is called by NautilusUI>>compileAMethodFromCategory:withSource:notifying: > > Cheers, > Alistair >

Jan. 13, 2018

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

by Photon

Oh yes of course... that`s what im saying. I did post it actually allready twice but the forum seems to delete raw text. So i have to post and then edit to put then tet back in every time. But yes here is the code: -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Jan. 13, 2018

Re: [Pharo-dev] [squeak-dev] [Doodle] OpenSmalltalk VM Meeting

by Ben Coman

Any chance that parts of this can be recorded - particularly the update on Sista? For me these slots start 11pm to 4am and next week I'll be on-site getting up at 4am to head to work. I'm happy to do any post-production work. cheers -ben On 13 January 2018 at 21:27, Fabio Niephaus <lists(a)fniephaus.com> wrote: > Hi all, > This is a friendly reminder that you can still sign up for the below until > tomorrow evening. > > Best, > Fabio > > -- > > On Mon, Jan 8, 2018 at 8:46 PM Fabio Niephaus <lists(a)fniephaus.com> wrote: > >> Hi all, >> >> When ClÃ©ment and I recently talked about the next VM release, we thought >> it might be good to organize a meeting and invite everyone who would be >> interested. The agenda is yet to be finalized, but I think it would be >> great if ClÃ©ment and/or Eliot could give an update on their work on Sista. >> And I could give an overview of what still needs to be done for the release >> or how we plan to sign and update the release bundles. I'm sure there is a >> lot more we can talk about. >> >> If you would like to attend, please indicate your availability using this >> Doodle link by Sunday, 14th January: https://doodle.com/poll/ >> cyei4ax4sd43m522. >> >> Looking forward to seeing you all soon. >> >> Best, >> Fabio >> > > > >

Jan. 13, 2018