December 2018 - Pharo-users

Re: [Pharo-users] Sending a message to pharo from commandline

by Damien Pollet

Hi Steve, Have a look at Clap: https://github.com/cdlm/clap-st https://speakerdeck.com/cdlm/clap-esug-2018 Coral was a nice idea but tried to be too many things at once (scripting syntax â commandline API); in contrast, Clap is only about defining commandline APIs for Pharo code. Feel free to send questions & feedback my way, too :-) On Tue, 25 Dec 2018 at 19:46, Steve Quezadas <steve(a)thestever.net> wrote: > What happened to the pharo commandline "eval" function? > > Does anyone know what happened to the pharo "eval" function on the > comnandline? It seems to have disappeared in the newer versions. The > Coral thing also seems to be abandoned as the readme is no longer there: > http://smalltalkhub.com/#!/~PharoExtras/Coral > > Is there any way to send messages to pharo from commandline? Sometimes I > write an object in pharo and it can be useful to use if I am runing a > linux shell. Sometimes I have a bash script or something that needs an > answer from pharo. > > - Steve > > >

Dec. 26, 2018

Move methods to other class in P7/Calypso

by Esteban Maringolo

What the canonical way of moving a set of methods from one class to another? I couldn't find it in the contextual menu or in the refactorings. Regards, Esteban A. Maringolo

Dec. 26, 2018

Re: [Pharo-users] PostgresV3 with parameter binding

by Esteban Maringolo

Excellent, thank your for this. Esteban A. Maringolo El mar., 25 dic. 2018 a las 5:16, Pierce Ng (<pierce(a)samadhiweb.com>) escribiÃ³: > > Hi all, > > I've modified PostgresV3 to do parameter binding, i.e., parsing SQL and > binding/executing with data are performed in separate protocol steps. > I've add a simple client API with some examples demonstrating usage. The > examples require a PostgreSQL server loaded with the Sakila database. > Instructions on bringing the database up and running the examples are in > my blog post: > > https://www.samadhiweb.com/blog/2018.12.25.postgresv3.html > > Season's greetings! > > Pierce > > > > >

Dec. 26, 2018

Re: [Pharo-users] Sending a message to pharo from commandline

by Sven Van Caekenberghe

Hi Steve, > On 25 Dec 2018, at 19:45, Steve Quezadas <steve(a)thestever.net> wrote: > > What happened to the pharo commandline "eval" function? > > Does anyone know what happened to the pharo "eval" function on the comnandline? It seems to have disappeared in the newer versions. The Coral thing also seems to be abandoned as the readme is no longer there: > http://smalltalkhub.com/#!/~PharoExtras/Coral > > Is there any way to send messages to pharo from commandline? Sometimes I write an object in pharo and it can be useful to use if I am runing a linux shell. Sometimes I have a bash script or something that needs an answer from pharo. > > - Steve What do you mean, AFAICT it is still there and works as before. Here is a terminal transcript on macOS: prometheus:2018-12-20 sven$ ./pharo Pharo.image printVersion [version] 'Pharo7.0.0' 'Pharo-7.0.0+rc1.build.66.sha.0ff3a6c1c0f1d9b2876c50e19b790dd7bb926dd9 (64 Bit)' prometheus:2018-12-20 sven$ ./pharo Pharo.image --list Currently installed Command Line Handlers: loadHermes Loads the hermes files passed as parameter printVersion Print image version save Rename the image and changes file initializePackages Initialize packages and protocols from a given lists st Loads and executes .st source files config Install and inspect Metacello Configurations from the command line metacello Install and inspect Metacello Baselines/Configurations from the command line test A command line test runner Fuel Loads fuel files clean Run image cleanup get Install catalog projects from the command line (consult catalog at http://catalog.pharo.org) perform Perform given message on a specified class or global eval Directly evaluates passed in one line scripts prometheus:2018-12-20 sven$ ./pharo Pharo.image eval --help Usage: eval [--help] [--save] [ --no-quit ] <smalltalk expression> --help list this help message --save save the image after evaluation of the expression --no-quit if specified, the image continues runing after evaluating the <smalltalk expression> <smallltalk expression> a valid Smalltalk expression which is evaluated and the result is printed on stdout Documentation: A CommandLineHandler that reads a string from the command line, outputs the evaluated result and quits the image. This handler either evaluates the arguments passed to the image: pharo Pharo.image eval 1 + 2 or it can read directly from stdin: echo "1+2" | $PHARO_VM my.image eval Important: don't manually save the image at the end of the expression by calling something like 'Smalltalk snapshot: true andSave: true'! Instead, use the safer --save option. prometheus:2018-12-20 sven$ ./pharo Pharo.image eval '42 factorial' 1405006117752879898543142606244511569936384000000000 HTH, Sven

Dec. 25, 2018

Sending a message to pharo from commandline

by Steve Quezadas

What happened to the pharo commandline "eval" function? Does anyone know what happened to the pharo "eval" function on the comnandline? It seems to have disappeared in the newer versions. The Coral thing also seems to be abandoned as the readme is no longer there: http://smalltalkhub.com/#!/~PharoExtras/Coral Is there any way to send messages to pharo from commandline? Sometimes I write an object in pharo and it can be useful to use if I am runing a linux shell. Sometimes I have a bash script or something that needs an answer from pharo. - Steve

Dec. 25, 2018

PostgresV3 with parameter binding

by Pierce Ng

Hi all, I've modified PostgresV3 to do parameter binding, i.e., parsing SQL and binding/executing with data are performed in separate protocol steps. I've add a simple client API with some examples demonstrating usage. The examples require a PostgreSQL server loaded with the Sakila database. Instructions on bringing the database up and running the examples are in my blog post: https://www.samadhiweb.com/blog/2018.12.25.postgresv3.html Season's greetings! Pierce

Dec. 25, 2018

Re: [Pharo-users] [Moose-dev] Re: glamorous toolkit: v0.4.0

by Offray Vladimir Luna CÃ¡rdenas

Hi Doru, On 21/12/18 17:40, Tudor Girba wrote: > Hi Offray, > > Thanks for describing your concerns. > Thanks to you for this conversation. > First, letâs address the technical part. Please go to gtoolkit.com > <http://gtoolkit.com> and download the 64Bit distribution that > includes the image and the VM. We will remove the standalone image > option from the website until the VM situation gets clarified. On the technical side, the 64Bit distribution in the smoothest installation of the new GT I had have so far. Just unzip it and launch the image and you are done! After that you are welcomed with a nice welcome window with beauty typographical render and you can explore what the GT has to offer and experience its potential first hand, which still brings kind of a mixed experience: * The new interfaces and some demo of the graphical elements look pretty good * After just some operations including window resizing I just get the Red Window of Death [1](https://i.imgur.com/Cbx7uyH.png). * I like the little triangles to expand thing in the document and the run buttons for embedded code, and the "embeddability" of elements in the document in a tree like fashion, which of course could lead to documents that embed pieces of documents, which embed pieces of documents... But the dual panel view of code in one side with results in the right panel of old GT didn't tend to create such "recursion". This dual modal view is the same of Atom[2](https://is.gd/kegaso) and CodiMD[3](https://is.gd/wudugi) for interactive documentation and I would like to see examples more in that line... but I don't know how it suits the philosophy behind Documenter, which seems more aligned to a modal non dual view of the document where you enter into edit mode once you click a piece of the document and into a view mode once you are out of it (instead of the proposed dual view). Would be nice to see is such dual view can be used to directly operate on the rendered view and see changes in the markup (i.e resizing an image in the rendered view changes the value on the edit view). * I like the different view that a document can have, markup wise: Pillar, Markdown, LaTeX, HTML, DeckJS AsciiDoc as is demoed in the authoring part [4](https://i.imgur.com/Jc1T5Rm.png). * Its difficult to travel between the panels of a playground. Previously you just make click in the lower circle representing the panel you want to go at it was done [5](https://i.imgur.com/4CDAM2o.png), but now clicking on the upper rectangle representing such panel has no effect [6](https://i.imgur.com/8Obo3Ct.png). * Auto-completion and shortcuts for selecting text doesn't work well on code cells of the new playground. Selecting whole words with Ctrl arrow doesn't work, neither using down arrows to choose from suggestions and even you can end with previous suggestions floating around your playground [7](https://i.imgur.com/4awyIft.png) [8](https://i.imgur.com/7qXc64b.png). * The default data science example didn't work at all [8](https://i.imgur.com/YhNb8el.png) > > Now, a clarification. The old GT was produced over a period of 4 years > by an open-source team. The project had its own identity, and in 2014 > the core of it was first integrated in Pharo. I say the core of it, > because the visual part and other libraries are not in Pharo today. > The full potential is found in Moose. In any case, during this > process, GT got to be identified with Pharo and that was a good thing. > > The new GT is a product produced by feenk, a company. Much of the > original team is still active in the new version, but now we commit to > our product in a different way. The product is free and open-source, > but itâs still a product with an identity and a goal. At present time, > both the team, identity and goal are different than those of Pharo. > > Our goal is to offer a fundamentally new alternative to program > (including comparing to what is possible now in Pharo). We are not > looking for marginal improvements, and we are not aiming at backward > compatibility. I used Moose to build the first Grafoscopio versions, but there was a lot of stuff that was related with software analysis that I didn't really need for reproducible interactive documentation and publishing nor for data science, activism and storytelling. So once old GT was integrated into Pharo with Spec I used a more minimal setup to deliver a more focused experience. I think that most times this relationship between Pharo and Moose can be of creative tension, one pushing the boundaries and the other offering a more stable experience where the innovations of the former are integrated and debugged. But even after using Moose as a fully integrated vision of what old GT have to offer in the back and front end, I didn't see any migration path from previous Moose with the old GT to the current GT, which is kind of worrisome. I understand the idea of forks in FLOSS as a way of dealing with politics behind the FLOSS movement and the relationship between differentÂ visions and actors (individuals, communities, enterprises, foundations, associations and so on). It has happened before with Squeak, Pharo and Cuis and I'm fine with that. And I understand that a healthy relationship with the past means sometimes to break with it and jump into the future. That's why I think that the role of for profit and non for profit institutions is to balance a sense of momentum and stability around FLOSS. I would like to see a more clear road map for GT, knowing ahead where backward compatibility will be broken and why, which are the visions and, more importantly, how to participate and where are the boundaries. These are difficult tasks, but if the participation and boundaries are explored collectively, you can also know about the first ones (visions, versions, forks, compatibility). In that sense I think that Pharo is putting a good example: we have a clear road map document and participation process in the public repositories, there are public channels for users and developers and the private companies know about them, so they can put the boundaries about what is going to be done in the open, with the community, and what is to be kept closed inside company's frontiers and channels and the company's own velocity. I don't know if Feenk is planing something similar for its new vision, product and identity, and I don't know if the new alternative will have its own non-profit organizations as a neutral entity for all players using GT, but would be good to know about that, not because there are not people willing to jump into the future, but we would like to know to which future we're jumping on.Â Without that I think that is a safer bet for myself to rely on Pharo and see how migration paths could ensure compatibility with my own past and the one of my local community using Pharo and GT based tools. I hope that the open source nature of both products (Pharo and new GT) will ease the cross-pollination of the more interesting ideas, even without sharing code, visions or UI. > > To build this alternative we invested in a whole new stack. That is > not a tiny challenge and getting it right requires many iterations and > feedback. We say we are in alpha not because of inconveniences of > installation but because we are still very much developing the product. > > We announced the first alpha version in September and since then much > has changed.Â At present time, we did manage to reach a situation where > downloading the distribution should run on Mac, Linux and Windows. > Even so, the current version is only for people that do want to try > knowing that there will be hurdles. I think that not only installation inconveniences is related alpha, but also this jumping from old GT to new one without a clear migration path (as is expected from alpha software and processes). I'm fine with that too, but I think that once the new GT reaches beta status the backward compatibility should be more important and meanwhile the non regard of that should be stated more promptly for previous and future GT users. I imagine that, at some point Feenk will provide its users and customers with clear support and migration paths regarding its open source products (kind of what happens with Canonical and the Long Term Support versions of Ubuntu). > > A word about the user experience. The current version runs inside the > Pharo UI because we need to bootstrap. But, our goal is to build a > complete IDE on the new stack. If you want to judge the user > experience, it is only meaningful to do it within the GT windows, and > not by comparing it with the rest of the existing Pharo UI. > > Does this clarify the situation? > > Cheers, > Doru > Yes, it does. It seems that a fork is coming, at least UI wise regarding Pharo and new GT, but if the community knows about it, I'm fine with that. I think this thread also clarifies what active users of old GT will expect from upcoming versions of new (non alpha) GT regarding compatibility, open processes, visions and so on. Hopefully we will reach that place together. Cheers, Offray

Dec. 24, 2018

Re: [Pharo-users] SQL Server

by eftomi

PS: I managed to connect to SQL Server with ODBC package (loaded from Project Catalog) in Pharo 6.0, however I have problems with character encodings. Loading the ODBC package into Pharo 6.1 doesn't succeed, in ends with the following in Transcript: Loading 1.3 of ConfigurationOfODBC... â¦ â¦ ... Fetched -> ODBC-TorstenBergmann.14 --- http://smalltalkhub.com/mc/PharoExtras/ODBC/main/ --- http://smalltalkhub.com/mc/PharoExtras/ODBC/main/MessageNotUnderstood: RBParser>>externalFunctionDeclaration And, of course, I'd like to use Glorp :-) -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Dec. 23, 2018

Re: [Pharo-users] SQL Server

by eftomi

Hi, are there any news regarding SQL Server access from Pharo..? -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Dec. 23, 2018

Re: [Pharo-users] [Moose-dev] Re: glamorous toolkit: v0.4.0

by Gour

On Sat, 22 Dec 2018 12:53:16 -0500 Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: > I don't know yet, but I would like to use Tonel and some import/export > tools to use Fossil as my backend for file based storage instead of > Git. I can fully understand you - using Fossil is so easy and safe in comparison with Git where one never knows... > These days are particularly slow in Colombia, but I will post advances > as soon as I have something. Thank you. Btw, I looked at Grafoscopio and it is interesting you had been looking or using tools like Leo editor, Pollen - I also considered Skribilo (Guile) - since I am also searching some toolchain to improve web publishing (paper output is not problem with LateX or ConTeXt) , but still haven't decided what to use/learn since learning Racket/Pharo requires some extra time until it can pay off (I want to stay focused on my writing and studying and not turn myself into programmer)...for now I'm still using Emacs/markdown-mode although in the past I spent time with both AÑciidoc(tor) and rst markups. Sincerely, Gour -- The senses, the mind and the intelligence are the sitting places of this lust. Through them lust covers the real knowledge of the living entity and bewilders him.

Dec. 23, 2018