- Pharo-users - lists.pharo.org

GTK3 / PDF Viewer

by robert＠robkuz.com

Hi, what is the best way to integrate a PDF Viewer with a Spec2 / GTK3 application on Windows? I couldn't find any mentioning of PDF viewer on the GTK3 site. Thx for your help Best Robert

Aug. 16, 2020

Move image

by robert＠robkuz.com

Hi, when I create a new image using the launcher then the image will be created at the following location (C:\Users\robert\Documents\Pharo\images\Pharo 8.0 - 64bit (stable)). Is there a way to define a different location when creating an image (or afterwards)? Best regards Robert

Aug. 16, 2020

Re: [Pharo-users] [ANN] Smalltalk's Successor

by tbrunz

Hi Richard, I had the same impression, that "Pharo is Smalltalk's successor". (Without any negative feelings toward VAST and VW; they fill a very important role for commercial use -- businesses depend on the kind of support that a commercial distribution provides and are very willing to fund that.) The future of Smalltalk is being created every day with commits to the Pharo Project. Who's to say a company can't be created to provide commercial support for Pharo in the way that Red Hat does for Linux? And the Pharo Consortium is, in many ways, already one such entity. So please do contribute to making the booklets better, Richard! I started last fall (and need to start up again) and found it very fulfilling, as well as educational. It's easy to do; for you & others, here are the basic steps: 1. Fork a booklet repository and then clone it. 2. Set a git 'upstream' to the original (because you'll be trading revisions as you go). 3. Edit the Pillar markdown, add new material, etc. 4. Push and submit a Pull Request. 5. Continue working (i.e., start a 'pipeline' of edit submissions). 6. Note that you can modify the target of a PR while the PR is still "in review". 6. Check the WIP 'releases' that the CI system generates to proofread. I was using Atom and it's markdown rendering, which is imperfect, but it was sufficient. Sean DeNigris recently suggest editing in Gtoolkit's live Pillar editor: "It's beta, but a compelling experience. I did a little screencast here: https://youtu.be/GZOYF82h9qA". I'm looking at it this week for my own use. There's also the 'Documentation' channel on the Pharo Discord site. I'd like to see the 'doc writers' start to interact there (and here); the last Discord entry was 6 weeks ago... -Ted -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Aug. 13, 2020

Re: [Pharo-users] [ANN] Smalltalk's Successor

by StÃ©phane Ducasse

Ok please accept my apologies if I hurt you. My point richard is that you can have an impact on Pharo. It is easy if you design libraries running on top of Pharo and make them public. S. > On 13 Aug 2020, at 03:44, Richard O'Keefe <raoknz(a)gmail.com> wrote: > > Am I starting to hallucinate, or did I read some time in the last year that there are plans for a "long term stability" branch of Pharo? That had me giving thanks. Pharo is splendid, and that will give us the best of both worlds: a stable base for development WITHOUT holding back development of Pharo itself. > > I think StÃ©phane Ducasse may have completely misunderstood me. I wonder what he thinks my "choice" is? The only choice I'm aware of making is to continue being engaged with Pharo. (Hint: I am not on the Squeak mailing list. I don't even know if there is one any more.) The unpleasantly disparate nature of "Smalltalk" does not make *Pharo* a bad choice, it just means that anyone who develops in Pharo with the aim of deploying in VW is facing a much harder task than they might have been led to expect. > > I would also like to praise S.D. and his merry band for > (a) the free Smalltalk books > (b) the continuing series of books specifically about Pharo. > Is there some way I can contribute to the Pharo book(let)s? > I'm not too bad at proof-reading. > > > > > > On Thu, 13 Aug 2020 at 01:43, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr>> wrote: > "Protect me from my friends I will deal with my ennemies." > > Pharo is Pharo. > > The smalltalk community likes to complain but we prefer to invent the future. > For the record we are helping companies to DELIVER and we are engaging > any people that want to invent the future with us. > > I have often the impression that having success is bad in this wonderful communauty > > Horrido canât you spend your energy in something more productive? > What a drag? > > Richard OâKeefe, this is a pity because we will never learn much from your experience. > Anyway this is your choice but a strange one. > > I would love to have a type inferencer for Pharo. > > Sorry no time to spend more time on this. > > S. > > I did not do Pharo for ego I did it because else I would have join Lua or Python > because Squeak and VW were killing my Smalltalk flame. > I prefer doing than talking. -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

Aug. 13, 2020

Re: [Pharo-users] [ANN] Smalltalk's Successor

by Richard O'Keefe

One other point. When I saw the subject line "Smalltalk's successor", I expected to read that *Pharo* already is Smalltalk's successor, what with traits and GT and direct support for Git &c. I think "The future of Smalltalk is not far-off it's Pharo and it's here" is a claim that could well be made. On Thu, 13 Aug 2020 at 13:44, Richard O'Keefe <raoknz(a)gmail.com> wrote: > Am I starting to hallucinate, or did I read some time in the last year > that there are plans for a "long term stability" branch of Pharo? That had > me giving thanks. Pharo is splendid, and that will give us the best of > both worlds: a stable base for development WITHOUT holding back development > of Pharo itself. > > I think StÃ©phane Ducasse may have completely misunderstood me. I wonder > what he thinks my "choice" is? The only choice I'm aware of making is to > continue being engaged with Pharo. (Hint: I am not on the Squeak mailing > list. I don't even know if there is one any more.) The unpleasantly > disparate nature of "Smalltalk" does not make *Pharo* a bad choice, it just > means that anyone who develops in Pharo with the aim of deploying in VW is > facing a much harder task than they might have been led to expect. > > I would also like to praise S.D. and his merry band for > (a) the free Smalltalk books > (b) the continuing series of books specifically about Pharo. > Is there some way I can contribute to the Pharo book(let)s? > I'm not too bad at proof-reading. > > > > > > On Thu, 13 Aug 2020 at 01:43, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > wrote: > >> "Protect me from my friends I will deal with my ennemies." >> >> Pharo is Pharo. >> >> The smalltalk community likes to complain but we prefer to invent >> the future. >> For the record we are helping companies to DELIVER and we are >> engaging >> any people that want to invent the future with us. >> >> I have often the impression that having success is bad in this >> wonderful communauty >> >> Horrido canât you spend your energy in something more productive? >> What a drag? >> >> Richard OâKeefe, this is a pity because we will never learn much >> from your experience. >> Anyway this is your choice but a strange one. >> >> I would love to have a type inferencer for Pharo. >> >> Sorry no time to spend more time on this. >> >> S. >> >> I did not do Pharo for ego I did it because else I would have join Lua or >> Python >> because Squeak and VW were killing my Smalltalk flame. >> I prefer doing than talking. >> >

Aug. 13, 2020

Re: [Pharo-users] [ANN] Smalltalk's Successor

by Richard O'Keefe

Am I starting to hallucinate, or did I read some time in the last year that there are plans for a "long term stability" branch of Pharo? That had me giving thanks. Pharo is splendid, and that will give us the best of both worlds: a stable base for development WITHOUT holding back development of Pharo itself. I think StÃ©phane Ducasse may have completely misunderstood me. I wonder what he thinks my "choice" is? The only choice I'm aware of making is to continue being engaged with Pharo. (Hint: I am not on the Squeak mailing list. I don't even know if there is one any more.) The unpleasantly disparate nature of "Smalltalk" does not make *Pharo* a bad choice, it just means that anyone who develops in Pharo with the aim of deploying in VW is facing a much harder task than they might have been led to expect. I would also like to praise S.D. and his merry band for (a) the free Smalltalk books (b) the continuing series of books specifically about Pharo. Is there some way I can contribute to the Pharo book(let)s? I'm not too bad at proof-reading. On Thu, 13 Aug 2020 at 01:43, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > "Protect me from my friends I will deal with my ennemies." > > Pharo is Pharo. > > The smalltalk community likes to complain but we prefer to invent > the future. > For the record we are helping companies to DELIVER and we are > engaging > any people that want to invent the future with us. > > I have often the impression that having success is bad in this > wonderful communauty > > Horrido canât you spend your energy in something more productive? > What a drag? > > Richard OâKeefe, this is a pity because we will never learn much > from your experience. > Anyway this is your choice but a strange one. > > I would love to have a type inferencer for Pharo. > > Sorry no time to spend more time on this. > > S. > > I did not do Pharo for ego I did it because else I would have join Lua or > Python > because Squeak and VW were killing my Smalltalk flame. > I prefer doing than talking. >

Aug. 13, 2020

Re: [Pharo-users] [ANN] Smalltalk's Successor

by StÃ©phane Ducasse

> On 12 Aug 2020, at 19:27, horrido <horrido.hobbies(a)gmail.com> wrote: > > You are quite right, which is why I'm retiring as Smalltalk evangelist. There > is simply nothing more I can say about Smalltalk. Over the last 5 years, > I've said everything there is to say and I've said them in every way > imaginable. What I see is in fact that you believed that you impact doing your kind of dull propaganda. You could have probably a lot more impact developing a couple of nice libraries (I have tons of ideas) or to write some little book chapters. > My last act as Smalltalk evangelist will be Camp Smalltalk Supreme in 2022. > Then I shall spend the remainder of my days searching for personal > enlightenment. I wish it to you. Now my state of mind is that we can always learn something and we can always do something small but that it an improvement. You believed that advocating smalltalk will resurrect. It wont. > > Offray Vladimir Luna CÃ¡rdenas-2 wrote >> I see that your articles tend to reiterate the same points time and >> again about Smalltalk (historicity, simplicity, agility, proven record), >> which can be fine for a new comer to it, but gets old for the people who >> is actually engaging with reading you. > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

Aug. 12, 2020

Re: [Pharo-users] [ANN] Smalltalk's Successor

by horrido

You are quite right, which is why I'm retiring as Smalltalk evangelist. There is simply nothing more I can say about Smalltalk. Over the last 5 years, I've said everything there is to say and I've said them in every way imaginable. My last act as Smalltalk evangelist will be Camp Smalltalk Supreme in 2022. Then I shall spend the remainder of my days searching for personal enlightenment. Offray Vladimir Luna CÃ¡rdenas-2 wrote > I see that your articles tend to reiterate the same points time and > again about Smalltalk (historicity, simplicity, agility, proven record), > which can be fine for a new comer to it, but gets old for the people who > is actually engaging with reading you. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Aug. 12, 2020

Re: [Pharo-users] [ANN] Smalltalk's Successor

by StÃ©phane Ducasse

"Protect me from my friends I will deal with my ennemies." Pharo is Pharo. The smalltalk community likes to complain but we prefer to invent the future. For the record we are helping companies to DELIVER and we are engaging any people that want to invent the future with us. I have often the impression that having success is bad in this wonderful communauty Horrido canât you spend your energy in something more productive? What a drag? Richard OâKeefe, this is a pity because we will never learn much from your experience. Anyway this is your choice but a strange one. I would love to have a type inferencer for Pharo. Sorry no time to spend more time on this. S. I did not do Pharo for ego I did it because else I would have join Lua or Python because Squeak and VW were killing my Smalltalk flame. I prefer doing than talking.

Aug. 12, 2020

Re: [Pharo-users] [ANN] Smalltalk's Successor

by Konrad Hinsen

Am 12.08.20 um 06:28 schrieb Richard O'Keefe: > The contrast between "flexibility of choice" and "tyranny of one > standard" is, um, a little over-drawn.Â I have three different Common > Lisp systems on this laptop: CMUCL, SBCL, and CCL.Â I have the > flexibility of choice between them *because* the adhere to a common > standard.Â Each of them has its own extra bits, but I am free to choose > between them because everything *else* is not idiosyncratic. Very true. Software tends to form high stacks with many layers of dependencies. Productive work on any given layer requires stability in the layers below. But if anyone depends on *your* work, that's a constraint on your freedom to innovate. Smalltalk today is in the same situation as Scheme (but unlike Common Lisp): there are more people interested in evolving Smalltalk than people building applications on top of Smalltalk. And that makes Smalltalk unattractive for those application builders for whom the progress in the quality of their tools is not worth the cost of the diversity and instability that require constant attention. It all depends on what you are working on, and in particular on the time scale of evolution of your work. If your application's requirement change rapidly, it's easier to deal with an unstable platform than if you are working on a complex design to be used over decades. Konrad.

Aug. 12, 2020