December 2021 - Pharo-users

Pharo-WebView

by TomaÅ¾ Turk

Dear all, Pharo-WebView package is now available on GitHub at https://github.com/eftomi/Pharo-Webview. Pharo-WebView is a package which implements a binding to webview dll library available at https://github.com/webview/webview in Pharo. Webview allows you to show HTML user interfaces in a native window, inject JavaScript code and HTML content into the window. It renders HTML originating via web requests or as a direct input. I tested it on Windows 64 bit in Pharo 64, I plan to do that on Pharo 32 and Linux, however I don't have access to Mac, so if anybody is interested, I'd be grateful :-) Best wishes, Tomaz

Dec. 16, 2021

Re: Platform studies

by Rafael Luque

Hi Offray, Maxwell's thesis seems exactly what I was asking for. Good luck with your proposal for ESUG. Thank you! El vie, 3 dic 2021 a las 18:42, Offray Vladimir Luna CÃ¡rdenas (< offray.luna(a)mutabit.com>) escribiÃ³: > Hi Rafael, > > Thanks for those provocative reading recommendations. > > On the use of Smalltalk or its derivations from a more sociotechnical > point of view I would recommend Maxwell's Tracing the Dynabook, a study of > technocultural transformations [1]: > > [1] > https://mutabit.com/repos.fossil/indieweb/uv/docs/es/miniwiki/grafoscopedia… > > Also on alternative tech stacks as a way to inhabit alternative futures, > recently I was presenting The Weekly Package (think in a Cuban Hulu/Netflix > alike of 1 terabyte of data of media working offline across all the island) > and how we mapped it by combining it with Pharo/GT, TiddlyWiki and Fossil: > > """ > > Because infrastructures organize/accumulate action and embed/transport > contexts, by choosing alternative tech stacks, we are enabling ourselves to > inhabit/explore alternative futures. ie by choosing techs like TiddlyWiki > instead of MediaWiki, Fossil instead of Git, Pharo instead of Python, > HedgeDoc instead of GooglDocs, and so on, and by arranging such > technologies on our own stacks and workflows, we are answering ourselves, > via prototyping, about alternatives to questions like: > > * How to organize and empower community learning and memory, particularly > in places with intermittent/low connectivity and diverse (mostly small to > medium) computing/storage/processing resources? > * How to inhabit the continuum between online/offline, > inter+personal/collective, synchronous/asynchronous, > documents/data/software? > * How to introduce meta-systems that enable us to change the > (media/digital) systems we inhabit? > > """ > > You can find a graph of The Weekly Package art metadata below and the > complete mail in [2]. > > [2] https://lists.riseup.net/www/arc/grafoscopio/2021-11/msg00000.html > > One of the things that wonders me is how context informs the development > of technologies and the communities around them, which, in time, informs > the presents and futures traversed by such communities-technologies > tandems. In the case of Smalltalk, I have seen it deployed time and again > in the context of academic, enterprise and research institutions. But in > our case, as Smalltalk, Pharo, GT deploys in a hackerspace other concerns > and approaches are taken, which in time mean exploring "alternalities" of > technologies in the present, more related with hacktivist, civic tech and > grassroots communities. (I will try to propose a talk in that sense for the > upcoming ESUG or the Smalltalk 50 years in Canada). > > Cheers, > > Offray > > > > On 29/11/21 8:46, Rafael Luque wrote: > > Hi all. > > I'm enjoying reading some books of the Platform Studies series by the > MIT Press (https://mitpress.mit.edu/books/series/platform-studies) > > Specifically, I'm reading "The future was here" about the Amiga and > "Racing the Beam" about the Atari VCS. What I like about these books is how > they try to study the relationships between the hardware and software > design of these computing platforms and the creative works produced on > these systems. The books study these media from the technical point of > view, but also deep into their social and cultural aspects. > > I'd like this kind of critical study about the Smalltalk platform. Do you > know about any book or research in this style? > > Thank you. > > ~ Rafael Luque > >

Dec. 13, 2021

Audio Capture in Pharo

by Evan Donahue

Hello, Does anyone know if it is currently possible to capture sound from the microphone in Pharo? I found this blog post that seemed to suggest that it wasn't possible in 2020: https://thepharo.dev/2020/11/17/how-to-play-sound-in-pharo/ Thanks, Evan

Dec. 12, 2021

UK Smalltalk User Group Meeting - Wednesday, December 29th

by Giovanni Corriga

For our December meeting, Florin Mateoc will show us JsSqueak ( https://github.com/fmateoc/JsSqueak ), a JavaScript implementation of (JavaScript compiled) Squeak. Whereas SqueakJS or TruffleSqueak are implementations of the Squeak stack VM which run the Squeak bytecodes, JsSqueak compiles all the Squeak code to JavaScript (including the VM plugins), it exports the image state as one big JavaScript storeString, and then loads them, and runs the JavaScript implemented minimal VM (mostly primitives) and the JavaScript-translated Squeak methods as one combined JavaScript application. The compiled JavaScript application can be run either in a browser or in Node.js While JavaScript, especially with its newest additions, is a very powerful language, which allows us to implement most Smalltalk-specific features (e.g. processes/green threads are implemented using generator functions and recursive yield* for all invocations, DNU is implemented using proxies and proto manipulation, the Smalltalk parallel class hierarchy is implemented using JavaScript classes with static properties and their parallel prototypes hierarchy, weak classes are implemented using JavaScript WeakRef instances in their (weak) slots), one obvious challenge is implementing contexts. Since we compile Squeak classes to JavaScript classes, Squeak methods to JavaScript methods (and class-side Squeak methods to static JavaScript methods), the code runs on the native JavaScript call stack, and we do not have a mapping between the JavaScript function activations and reified contexts. Nevertheless, it turns out that, by providing specialized implementations for various aspects that are implemented using contexts/stack walking in Squeak, we can actually run almost all Squeak code as-is. Florin Mateoc ( https://fmateoc.js.org/ ) is an electronics engineer who has always loved programming and who has actually only ever worked as a software engineer. Florin has worked as a professional Smalltalk programmer in Enfin (later called ObjectStudio), VisualAge, VisualWorks, and a little bit as a hobbyist in Squeak. This will be an online meeting from home. If you'd like to join us, please sign up in advance on the meeting's Meetup page ( https://www.meetup.com/UKSTUG/events/282445345/ ) to receive the meeting details. Donât forget to bring your laptop and drinks!

Dec. 9, 2021

Re: An Emacs <-> Pharo bridge (unidirectional at first)

by gettimothy

Excellent. When (!) I finish the large project I am on, I will probably turn to this. Thanks for the thread. ---- On Thu, 09 Dec 2021 07:53:14 -0500 Sven Van Caekenberghe <sven(a)stfx.eu> wrote ---- > On 8 Dec 2021, at 22:24, Mathieu Dubois via Pharo-users <mailto:pharo-users@lists.pharo.org> wrote: > > gettimothy wrote: > > https://github.com/ahungry/geben > > that is the protocol emacs/php uses. Dbg . > > iirc, there is another standard for code browsing, highlighting, etc. > > If i find it I will ping you. > > Are you talking about LSP (https://en.wikipedia.org/wiki/Language_Server_Protocol) ? This also already exists for Pharo: https://badetitou.fr/projects/vscode-pharo/2021/12/02/with-gtk/ https://marketplace.visualstudio.com/items?itemName=badetitou.pharo-languag… Sven

Dec. 9, 2021

Re: An Emacs <-> Pharo bridge (unidirectional at first)

by Sven Van Caekenberghe

> On 8 Dec 2021, at 22:24, Mathieu Dubois via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > gettimothy wrote: > > https://github.com/ahungry/geben > > that is the protocol emacs/php uses. Dbg . > > iirc, there is another standard for code browsing, highlighting, etc. > > If i find it I will ping you. > > Are you talking about LSP (https://en.wikipedia.org/wiki/Language_Server_Protocol) ? This also already exists for Pharo: https://badetitou.fr/projects/vscode-pharo/2021/12/02/with-gtk/ https://marketplace.visualstudio.com/items?itemName=badetitou.pharo-languag… Sven

Dec. 9, 2021

Re: An Emacs <-> Pharo bridge (unidirectional at first)

by gettimothy

YES!Â (: I do not know this, but I suspect that with those two things, smalltalk will be able to be developed in and designed in any IDE. That would do wonders for mind-share on the language itself. Thank you for finding that. cheers. ---- On Wed, 08 Dec 2021 16:24:06 -0500 Mathieu Dubois via Pharo-users <pharo-users(a)lists.pharo.org> wrote ---- gettimothy wrote: https://github.com/ahungry/geben that is the protocol emacs/php uses. Dbg . iirc, there is another standard for code browsing, highlighting, etc. If i find it I will ping you. Are you talking about LSP (https://en.wikipedia.org/wiki/Language_Server_Protocol) ?

Dec. 9, 2021

Re: InstanceVariables

by Norbert Hartl

> Am 08.12.2021 um 22:56 schrieb Richard O'Keefe <raoknz(a)gmail.com>: > > Other programming languages use terminology like slots, > fields, data members, ... > > The keyword 'instanceVariableNames:' is used because the > string that follows contains the names of the variables, > not the variables themselves. To experience that go into settings (under the âPharoâ menu item) search for âslotsâ. You will get this If you open a new system browser it looks like this Collection << #SmallDictionary slots: { #keys . #values . #size }; tag: 'Dictionaries'; package: 'Collections-Unorderedâ which resembles the slots representation better. Hope this helps and not raise confusion even more. Norbert

Dec. 9, 2021

Re: InstanceVariables

by Richard O'Keefe

If you are coming from a Pascal background, instance variables of an object correspond to fields of a record. They are called instance variables - because they are variables - that belong to INSTANCES of a class (object) as opposed to class variables - which are variables - that belong to the CLASS itself and are thus shared by all instances. Other programming languages use terminology like slots, fields, data members, ... The keyword 'instanceVariableNames:' is used because the string that follows contains the names of the variables, not the variables themselves. One thing to note is that in Smalltalk all instance variables (fields, slots, whatever) are PRIVATE. These are not the names of accessor methods, although there may be accessor methods with the same spelling. On Tue, 7 Dec 2021 at 05:32, <danhunfeldz(a)mail.com> wrote: > Object subclass: #Test > instanceVariableNames: 'var1 var2' > classVariableNames: '' > package: 'MyTest' > > I was struggling with instanceVariableNames even though they show up under methods. Perhaps I'm just slow, but it wasn't until last night when I was reading on Object Pascal and there was an example: > > type > TProjector = class(TTelevision) > Brightness, Temperature: Integer; > procedure Focus(Length: Single); > end; > > Then it finally clicked with me that "var1" and "var2" under instance variables in Smalltalk would be like the method "Focus" in Object Pascal. Is that correct, or am I still not getting it? > >

Dec. 8, 2021

Re: An Emacs <-> Pharo bridge (unidirectional at first)

by duboismathieu_gaas＠yahoo.fr

gettimothy wrote: > https://github.com/ahungry/geben > > that is the protocol emacs/php uses. Dbg . > > iirc, there is another standard for code browsing, highlighting, etc. > > If i find it I will ping you. Are you talking about LSP (https://en.wikipedia.org/wiki/Language_Server_Protocol) ?

Dec. 8, 2021