November 2017 - Pharo-users

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

by stephan

On 27-11-17 11:02, Alistair Grant wrote: > As > we've seen from Pillar and Magritte, the more dependencies the greater > the maintenance costs and potential for incompatibility. That conclusion is not supported by the actual code. The maintenance costs for Pillar were high because of ignoring existing users of the code and bad Metacello practices. Stephan

Nov. 27, 2017

Re: [Pharo-users] How do you store and manage small programs?

by Alistair Grant

On 27 November 2017 at 11:16, Alistair Grant <akgrant0710(a)gmail.com> wrote: > On 26 November 2017 at 13:07, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> Hi Andy >> >> As you saw there are plenty of solutions. >> >> Now what I learned is that it is often better in the long to have a >> little object because suddenly >> it opens your mind and you realise that you can teach him something more. >> >> So I often find myself realising that I created some class methods and >> that it was stupid >> better have a real little object because it can do more and in >> particular for open new path >> >> So now I do not use scripts but plain little classes with nice little >> printOn: methods and arguments >> to get customized. > > +1 > > And if you create a class method to do the most common operation(s), > you can add the "<script>" pragma and a button appears in the browser > to run the operation. Often better than a printOn: is to create a #gtInspectIn: method, allowing you to display tables, graphs, etc. as appropriate in the inspector. Actually, this has worked so well that I haven't written a "real UI" for anything I use in my personal environment, which includes downloading media, all my note keeping, tracking finances, etc. Cheers, Alistair

Nov. 27, 2017

Re: [Pharo-users] How do you store and manage small programs?

by phil＠highoctane.be

QuickAccess is also a great option. *https://pharoweekly.wordpress.com/2015/11/06/quickaccess/ <https://pharoweekly.wordpress.com/2015/11/06/quickaccess/>* On Mon, Nov 27, 2017 at 11:16 AM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > On 26 November 2017 at 13:07, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: > > Hi Andy > > > > As you saw there are plenty of solutions. > > > > Now what I learned is that it is often better in the long to have a > > little object because suddenly > > it opens your mind and you realise that you can teach him something more. > > > > So I often find myself realising that I created some class methods and > > that it was stupid > > better have a real little object because it can do more and in > > particular for open new path > > > > So now I do not use scripts but plain little classes with nice little > > printOn: methods and arguments > > to get customized. > > +1 > > And if you create a class method to do the most common operation(s), > you can add the "<script>" pragma and a button appears in the browser > to run the operation. > > Cheers, > Alistair > > >

Nov. 27, 2017

Re: [Pharo-users] How do you store and manage small programs?

by Alistair Grant

On 26 November 2017 at 13:07, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi Andy > > As you saw there are plenty of solutions. > > Now what I learned is that it is often better in the long to have a > little object because suddenly > it opens your mind and you realise that you can teach him something more. > > So I often find myself realising that I created some class methods and > that it was stupid > better have a real little object because it can do more and in > particular for open new path > > So now I do not use scripts but plain little classes with nice little > printOn: methods and arguments > to get customized. +1 And if you create a class method to do the most common operation(s), you can add the "<script>" pragma and a button appears in the browser to run the operation. Cheers, Alistair

Nov. 27, 2017

Re: [Pharo-users] Pharo-Chrome (was: Soup bug(fix))

by Alistair Grant

Hi Stef, On 26 November 2017 at 22:39, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi Alistair > > If you want help I can add a baseline that automtically load DataFrame. > Because users should not load by themselves external project. Thanks for the offer, but Pharo-Chrome isn't actually dependent on DataFrame. I just used it in an example in the README as it makes inspecting the results easy (it's possible to inspect the results without DataFrame, you'll just be looking at an Array of Arrays). As we've seen from Pillar and Magritte, the more dependencies the greater the maintenance costs and potential for incompatibility. If there's a compelling reason to automatically load DataFrame I'm happy to do that, but at the moment I'm not seeing it. Cheers, Alistair > Stef > > On Sat, Nov 25, 2017 at 3:57 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> Alistair Grant wrote >>> https://github.com/PolyMathOrg/DataFrame >> >> Cool, thanks! I didn't know about this project. >> >> >> >> ----- >> Cheers, >> Sean >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >

Nov. 27, 2017

Re: [Pharo-users] Removing instance variables doesn't recompile the methods

by Peter UhnÃ¡k

As far as I know this has been a _feature_ for a very long time. Automatic recompiling methods is not the best idea, because: 1) you compile a method with temp var "hello" that uses inst var "world" 2) you add a inst var "hello" 3) you remove "world" 4) trying to recompile the method will fail, because suddenly there's a clash between temp var "hello" and inst var "hello" Don't forget that the methods are compiled, not interpreted. So this behavior is expected. Peter On Mon, Nov 27, 2017 at 6:03 AM, Ben Coman <btc(a)openinworld.com> wrote: > Thanks for reporting Abdelghani. > Now it would be doubly useful if you could isolate which build introduced > the problem. > PharoLauncher can be used to help bisect working/non-working images. > > cheers -ben > > On 27 November 2017 at 04:08, abdelghani ALIDRA via Pharo-users < > pharo-users(a)lists.pharo.org> wrote: > >> >> >> ---------- Forwarded message ---------- >> From: abdelghani ALIDRA <alidrandco(a)yahoo.fr> >> To: "pharo-users(a)lists.pharo.org" <pharo-users(a)lists.pharo.org> >> Cc: >> Bcc: >> Date: Sun, 26 Nov 2017 20:08:29 +0000 (UTC) >> Subject: Removing instance variables doesn't recompile the methods >> >> Hi, >> >> In a fresh pharo 6 image, I add a class with an instance variable x and >> implement accessors. >> Then I write a test method for the accessors of x >> MyClassTest>>testReadWriteX >> self assert (MyClass new x: 0) x equals: 0 >> >> I run the test and obviously it is green >> >> BUT >> >> I remove the instance variable x. Obviously, the accessors are broken and >> the test should be red when I execute it again but it is not!!! >> >> I can even change the class again (to recompile it I thought) or even >> load the code in a new image and the tests are still green. >> I can also invoque the broken methods in a playground or in an inspector >> : MyClass new x: 0; increment; x then printIt. and astonishingly 1 is >> printed. >> The only way to detect the error is to recompile the method but this does >> not happen (maybe it should) when instance variables are modified or >> removed in the class (even when you use the refactoring tool!) >> >> I think this is annoying because one can no more really trust his tests. >> >> Cheers >> Abdelghani >> >> >> >> >

Nov. 27, 2017

Re: [Pharo-users] How to write a little REPL

by phil＠highoctane.be

Or https://github.com/guillep/Scale but linux. Phil On Nov 27, 2017 03:56, "Holger Freyther" <holger(a)freyther.de> wrote: > > > On 27. Nov 2017, at 05:38, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: > > > > Hi > > Hey! > > > > I'm working on a mini scheme implementation and I would like to add a > REPL and > > I wonder how I can super easily get a read line. > > The easiest might just be to use "rlwrap your-interpreter"? But I think > you want to allow multi-line input. So either link libreadline (GPL) or > libedit? > > holger > >

Nov. 27, 2017

Re: [Pharo-users] How to write a little REPL

by phil＠highoctane.be

NeoConsole could be an option. https://github.com/svenvc/pharo-server-tools/blob/master/README.md Phil On Nov 27, 2017 03:56, "Holger Freyther" <holger(a)freyther.de> wrote: > On 27. Nov 2017, at 05:38, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Hi Hey! > I'm working on a mini scheme implementation and I would like to add a REPL and > I wonder how I can super easily get a read line. The easiest might just be to use "rlwrap your-interpreter"? But I think you want to allow multi-line input. So either link libreadline (GPL) or libedit? holger

Nov. 27, 2017

Re: [Pharo-users] How to write a little REPL

by Pavel Krivanek

Do you want it in the command line or in the Morphic UI? -- Pavel 2017-11-26 22:38 GMT+01:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > Hi > > I'm working on a mini scheme implementation and I would like to add a REPL > and > I wonder how I can super easily get a read line. > > Stef > >

Nov. 27, 2017

Re: [Pharo-users] I love the launcher!!!!

by Ben Coman

On 27 November 2017 at 05:25, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > So, I try it on my CentOS 7 64 bit and... as there is no 64 bit version of > the launcher... > > pharo6-64-ui PharoLauncher.image > This interpreter (vers. 68021) cannot read image file (vers. 6521). > Press CR to quit... > > How is one using the launcher for 64 bit stuff? > Starting with a fresh 64-bit image, install from the Catalog or Monticello repository. http://smalltalkhub.com/#!/~Pharo/PharoLauncher cheers -ben > > Phil > > On Sun, Nov 26, 2017 at 9:45 PM, Stephane Ducasse <stepharo.self(a)gmail.com > > wrote: > >> If you don't try you will not understand what you miss. >> >> On Sun, Nov 26, 2017 at 2:10 PM, Herby VojÄÃk <herby(a)mailbox.sk> wrote: >> > Stephane Ducasse wrote: >> >> >> >> Then do not try :) like that you will never get a chance to know :) >> > >> > >> > Could you please explain? I understood your sentence has high dose of >> homour >> > which I cannot decipher since I lack certain abilities for that. >> > >> > Thanks, Herby >> > >> >> Stef >> >> >> >> >> >> On Sun, Nov 26, 2017 at 1:48 PM, Herby VojÄÃk<herby(a)mailbox.sk> >> wrote: >> >>> >> >>> Stephane Ducasse wrote: >> >>>> >> >>>> Why don't you try? It does not bite. >> >>>> >> >>>> For me it works in all scenario. I have projects that i manage over >> >>>> several weeks and others I drop day to day. >> >>>> And I have also startup script per versions. >> >>> >> >>> >> >>> Maybe I will. The main problem was I didn't what it's good about at >> all - >> >>> load image for a version, runs it - what's the "wow it's great" about? >> >>> Missed part was it loads correct vm; plus makes sense when you have >> >>> hundreds >> >>> (I don't). Now it must be combined with the startup script magic to >> work >> >>> with long-time projects, but those are also new to me - did not know >> of >> >>> them >> >>> until your booklet, not using them at all yet. >> >>> >> >>> Herby >> >>> >> >>> >> >>>> Stef >> >>>> >> >>>> On Fri, Nov 24, 2017 at 3:10 PM, Herby VojÄÃk<herby(a)mailbox.sk> >> wrote: >> >>>>> >> >>>>> Thank you all, now I understand it better. Good for lots of >> "branches". >> >>>>> >> >>>>> However, I wonder how does it work with the rule I read somewhere: >> >>>>> "start >> >>>>> each day [of work on a project] with a new image", which means I >> should >> >>>>> not >> >>>>> reuse clean new image (as it needs populating from VCSes etc.) nor >> >>>>> reuse >> >>>>> existing image (I should start with the new one). Or does it combine >> >>>>> with >> >>>>> some startup-magic described in one of the recent Steph's booklets, >> the >> >>>>> "one >> >>>>> start per [new] image" case (but again, one should discriminate >> >>>>> projects >> >>>>> from each other)? >> >>>>> >> >>>>> Thanks, Herby >> >>>>> >> >>>>> Peter UhnÃ¡k wrote: >> >>>>>> >> >>>>>> Hi Herby, >> >>>>>> >> >>>>>> normally people use different images for their different projects, >> >>>>>> different versions, trying things, etc. Which means we end up with >> >>>>>> many >> >>>>>> locations on disk, and it can be hard to track. >> >>>>>> So PharoLauncher is a nice tool where you can download fresh image >> >>>>>> just >> >>>>>> by clicking, and you see the list of your local images and can >> launch >> >>>>>> them, etc. >> >>>>>> >> >>>>>> Peter >> >>>>>> >> >>>>>> On Thu, Nov 23, 2017 at 12:56 PM, Herby VojÄÃk<herby(a)mailbox.sk >> >>>>>> <mailto:herby@mailbox.sk>> wrote: >> >>>>>> >> >>>>>> Stephane Ducasse wrote: >> >>>>>> >> >>>>>> Hi >> >>>>>> >> >>>>>> I love the PharoLauncher. >> >>>>>> >> >>>>>> >> >>>>>> Pardon my question, I have downloaded it and looked at it, >> but I >> >>>>>> don't get it. What does it do / what are the use cases >> (honest >> >>>>>> question)? >> >>>>>> >> >>>>>> Thanks, Herby >> >>>>>> >> >>>>>> >> >>>>>> It helps me to manage my parallel development and >> projects. >> >>>>>> >> >>>>>> We should put a link on the Pharo web site because >> >>>>>> >> >>>>>> http://files.pharo.org/platform/launcher/ >> >>>>>> <http://files.pharo.org/platform/launcher/> >> >>>>>> >> >>>>>> is arcane. >> >>>>>> >> >>>>>> Stef >> >>>>>> >> >>>>>> >> >>>>>> >> >>>>>> >> >>> >> >> >> > >> > >> >> >> >

Nov. 27, 2017