December 2018 - Pharo-users

Sending a message to pharo from commandline
by Steve Quezadas Dec. 26, 2018

Dec. 26, 2018

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

3 2

PostgresV3 with parameter binding
by Pierce Ng Dec. 26, 2018

Dec. 26, 2018

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

2 1

Re: [Pharo-users] SQL Server
by linkerstorm Dec. 23, 2018

Dec. 23, 2018

Thanks. Following your suggestion, I found this thread, with the same problem : https://groups.google.com/forum/#!topic/dbxtalk/xoQILQhu_mo <https://groups.google.com/forum/#!topic/dbxtalk/xoQILQhu_mo> I'm not alone anymore -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

2 2

Teapot and SSL
by horrido Dec. 23, 2018

Dec. 23, 2018

I had this working some many months ago, but now I can't get it to work. Really annoying. The entire process is so arcane... My HTTP server starts like this: Teapot stopAll. Teapot on Get: blah blah blah Then I visit http://localhost:1701/. I created a self-signed cert called newcert.pem. My HTTPS server starts like this: Teapot stopAll. secureServer := (ZnSecureServer on: 1443) certificate: '/home/richard/newcert.pem'; logToTranscript; start; yourself. teapot := Teapot configure: { #znServer -> secureServer }. teapot Get: blah blah blah When I visit https://localhost/, I get "Unable to connect". I tried localhost:1701, localhost:1443, just about every damn port number I can think of. No joy. So what the devil am I doing wrong??? -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

5 16

stfx.eu down
by Sven Van Caekenberghe Dec. 22, 2018

Dec. 22, 2018

Hi, This evening I somehow broke my stfx.eu server while doing an ubuntu dist upgrade (an old AWS EC2 machine). This means several websites / web services hosted by that machine are down, most notably mc.stfx.eu (hosting several of my packages) and ws.stfx.eu (used for shared smalltalk workspaces). A couple of Zinc tests will also fail. For source code access, all my public repos exist both in an up to date form on GitHub (http://github.com/svenvc) as well in the original form in SmalltalkHub (http://smalltalkhub.com/#!/~SvenVanCaekenberghe) or SS3. The main problem there is that the distributed ConfigurationsOf and Catalog entries will still point to the original. This is not a problem with git's BaselineOf definitions. Although the machine will no longer boot, I managed to mount the original volume on another instance so I can still access the whole filesystem. This will make it possible to eventually recover most services. But this will take time as these things never happen when it is convenient. It will give me an opportunity to modernise the setup though, which is good. Sorry for the inconvenience. Sven

3 4

Re: [Pharo-users] [Moose-dev] glamorous toolkit: v0.4.0
by Tudor Girba Dec. 21, 2018

Dec. 21, 2018

Hi, Thanks for detailing your thoughts. Indeed, I know about your application. Whatever you can do with the current GT you will be able to do with the new one. Except that for the new one you will be able to do extra things. Here are a few: - You can build and share documents that embed those inspector views. This can be useful for reporting or sharing diagnostics with your users. - Because the underlying rendering engine is much more powerful, you can express modern and interfaces that integrate with the rest of the environment smoothly. - You likely have to deal with log files that might get large. First, the new editor allows you to smoothly work with such files. But, you can go well beyond this. Imagine that you build a tooling that produces the same editor only the text is interactive, and you might even embed visual artifacts right in the text to bridge the gap between what you would see in a typical console. For example, this tweet shows the new Transcript used to debug an animation. For every animation frame, we output the text corresponding with the frame and we insert the graphical preview corresponding to that step. You look at GT from the point of view of an end-user. You likely like the fact that you could mold the environment to your context and that you could do this incrementally. It happens that the same principles and tools can be applied to the whole programming, and once you do that, you actually can fundamentally change the act of programming. In fact, the same thing applies to the old GT: we built the new GT using that version and we believe that this allowed us to work much faster than if we would have used more traditional tools. The new GT pushes the envelope significantly further. So, that is why we are excited about that perspective, but even if you do not spend much time programming in Pharo, you can still take advantage for the user point of view as described above :). Is this answer better? Cheers, Doru > On Dec 21, 2018, at 4:59 PM, Luke Gorrie <luke(a)snabb.co> wrote: > > On Thu, 20 Dec 2018 at 10:58, Tudor Girba <tudor(a)tudorgirba.com> wrote: > The goal of the new GT is to propose a completely reshaped programming experience that enables moldable development. You will find the concepts from the old GT in the new world as well. For example, the Inspector is extensible in similar ways and the API is similar as well. > [...] > Does this address the concern? > > I am not sure yet :). > > Programming is not our main use case for GT. We are using GT as an object inspector (etc) for examining diagnostic data. We have a Smalltalk application that's similar to GDB and we are using GT as the front-end. > > In our world we use the Inspector and the Spotter but all of the Smalltalk programming views are hidden. GT is "molded" to be a diagnostic tool *instead of* a programming environment. Specifically, our main use case is inspecting/debugging the operation of a JIT compiler written in C. We have Smalltalk code to load binary coredumps from the JIT, decode them using DWARF debug information, and represent the application-level compiler data structures as Smalltalk objects. This way we can use GT to browse generated code, cross-reference profiler data, examine runtime compilation errors, etc. > > The "old" GT is awesome for this. I feel like this application is also very much in the spirit of the "moldable tools" thesis. Lots of diagnostic workflows ultimately boil down to drill-down inspecting and/or searching. > > I don't know where we stand with respect to the "new" GT though. I am talking about diagnostics, you are talking about programming. I am talking about zeros and ones, you are talking about feelings. I am maintaining a stable application, you are talking about rewrites. I am having a hard time whether I should be switching to the new GT in the immediate future, or waiting another year or two for it to mature, or planning to stick with the old GT. > > Hints would be appreciated :) > > I reiterate that I think you guys are doing fantastic work - some of the most interesting work in the programming universe to my mind. I hope that this discussion is useful for at least understanding the thought process of some users / potential users. > > Cheers! > -Luke > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.feenk.com "Being happy is a matter of choice."

1 1

PetitParser release: v2.1.0
by Julien Dec. 21, 2018

Dec. 21, 2018

Hello, This email to announce that a new minor release of PetitParser (1) has been published on GitHub (v2.1.0). Here is the change log: Summary ----------- - Each package has its tests separated in a separated package. - Cleaned baseline, made it more modular. - Created more groups to let people load the part of the project they want. - Some cleaning in `PetitParser` package. - Integrated PetitPreprocessor and PetitParserExtensions in the project as separated groups Changelog ----------- #31 Extract PPTextHighlighter into a separated package. #21 Add contribution guidelines #13 Update README with new groups #9 Fix CI configuration #19 A TODO comment in PPMemoizedParser>>#parseOn: might need to be fixed cleaning #11 Inconsistent method classification #15 Split tests in their own packages cleaning #22 PetitPreprocessor is missing some extensions #3 Use `>>>` notation for examples inside method #8 PPStream>>#column: has commented code that should be removed #7 PPCharSetPredicate and PPContextMemento need to be commented #1 Replace 'Oops' error message with a meaningful message #4 PPContext>>#on:stream: should be removed #2 Integrate PetitParserExtensions package from Smalltalkhub #5 Integrate PetitPreprocessor package from Smalltalkhub Thanks to Cyril Ferlicot for his help. Cheers, Julien --- Julien Delplanque Doctorant Ã lâUniversitÃ© de Lille http://juliendelplanque.be/phd.html Equipe Rmod, Inria BÃ¢timent B 40, Avenue Halley 59650 Villeneuve d'Ascq NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40

1 0

MongoCursor>>execute raising 'Unexpected responseTo in response'
by Sebastian Sastre Dec. 21, 2018

Dec. 21, 2018

Hi All, Holger... Iâve seen this today: http://forum.world.st/MongoCursor-gt-gt-execute-and-MongoTalk-changes-td488… <http://forum.world.st/MongoCursor-gt-gt-execute-and-MongoTalk-changes-td488…> After talking with some people in the Pharo chat group at Discord about this erratic error Iâm having with MongoTalkâs MongoCursor . Once it happens, the stream stays open and Mongo says isValid true but no other operations can be executed. Iâve loaded MongoTalk with: Metacello new githubUser: 'pharo-nosql' project: 'voyage' commitish:'1.?' path: 'mc'; baseline: 'Voyage'; load: 'mongoâ. in a Pharo 6.1 image. Did this Unexpected responseTo happened again to you? nextRequestID has the code you mention in the issue: nextRequestID ^requestID := requestID + 1 bitAnd: 16r3FFFFFFF Do you have any further hint on why the issue? Thanks! Sebastian

2 1

How to log Teapot activity
by horrido Dec. 20, 2018

Dec. 20, 2018

Is there a way to log server activity (to Transcript?) with Teapot? Without ZnSecureServer. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

2 1

Re: [Pharo-users] [Moose-dev] Re: glamorous toolkit: v0.4.0
by Tudor Girba Dec. 20, 2018

Dec. 20, 2018

Hi Luke, I am happy this looks exciting :). About the confusion part: The Glamorous Toolkit we are working on right now is a complete new world built on a complete new graphical stack that does is not based on the existing stack that ships with Pharo. It is not an evolution. It is a leap. The goal of the new GT is to propose a completely reshaped programming experience that enables moldable development. You will find the concepts from the old GT in the new world as well. For example, the Inspector is extensible in similar ways and the API is similar as well. But, in the new world, we are bringing the concept much further. For example, Documenter provides a whole new kind of a tool that can mold to unify multiple workflows (like data notebooks, code documentation, or tutorials) right in the IDE. Coder provides the infrastructure for manipulating code that can mold its shape as you type. Transcript allows you to embed various widgets to transform the otherwise dull experience of a console into a live one. Behind the scenes GT comes with several engines. The Examples engine enables example-driven development which also bridges the gap between testing and documentation effort, especially when combined with Documenter. Releaser is able to release deeply nested projects. Phlow offers an engine that shares similarities with Glamour. Completer provides moldable completion. Visualizer offers a couple of visualization engines such as Mondrian. All of these are possible because of the underlying graphical stack made of Sparta/Bloc/Brick. All in all, we believe that the new GT enables a new way of programming. Individual features can be attractive, but our goal is to reshape the development experience. Does this address the concern? Cheers, Doru > On Dec 19, 2018, at 2:09 PM, Luke Gorrie <luke(a)snabb.co> wrote: > > On Fri, 14 Dec 2018 at 05:13, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Please do let us know what you think .. and, of course, what you feel. > > I'm feeling excited and confused :). > > Excited because I love seeing all these new demos streaming out and I'm itching to put new capabilities to work. > > Confused about the roadmap. How does this "new" Glamorous Toolkit relate to the "old" one that I learned about last year from the Moldable Tools thesis? Is this a new version or a complete rewrite? Is it backwards compatible or completely reimagined? Is adopting the new version a seamless process or is porting required? Are frameworks like Glamour still there behind the scenes or were they replaced? etc. > > > <gt-documenter-magic-markup.gif><gt-0-4-0.png>_______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.feenk.com "Things happen when they happen, not when you talk about them happening."

1 0