September 2018 - Pharo-users

Re: [Pharo-users] TextEditor

by Hilaire

Hello HernÃ¡n, Thanks to point Rubric which I did not know until now. Any doc/pointer about this new boy in town? What is the differences with the TextEditor? Can the text contains arbitrary Morph? I am exploring the idea of an infinite roll with text, code and morph. Hilaire Le 21/09/2018 Ã 00:19, HernÃ¡n Morales Durand a Ã©critÂ : > StandardWindow new > addMorph: ( > RubScrolledTextMorph new > withLineNumbers; > appendText: '/path/to/file' asFileReference contents) > fullFrame: (0@0 corner: 1@1) asLayoutFrame; > openInWorld. > > Cheers, > > HernÃ¡n -- Dr. Geo http://drgeo.eu

Sept. 21, 2018

Re: [Pharo-users] MIDI IO

by Guillermo Polito

Hi Manuel, I don't know the state of the Midi Plugin, but for sure it would not be difficult to make some bindings to an existing library with uFFI. Check for example http://jedi.ks.uiuc.edu/~johns/projects/midid/ Guille On Fri, Sep 21, 2018 at 1:34 PM Manuel Leuenberger <leuenberger(a)inf.unibe.ch> wrote: > Hi, > > I am currently investigating how to work with audio in Pharo, especially > how to hook up Pharo to my synths or DAW using MIDI. I found that there is > an old MIDI plugin for the VM, but apparently it has been discontinued due > to OS changes ( > http://forum.world.st/Mac-OS-Cocoa-MIDI-Plugin-td4893691.html) Is there > any setup that works for MIDI IO on OSX using Pharo 6/6.1? > > Cheers, > Manuel > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Sept. 21, 2018

MIDI IO

by Manuel Leuenberger

Hi, I am currently investigating how to work with audio in Pharo, especially how to hook up Pharo to my synths or DAW using MIDI. I found that there is an old MIDI plugin for the VM, but apparently it has been discontinued due to OS changes (http://forum.world.st/Mac-OS-Cocoa-MIDI-Plugin-td4893691.html <http://forum.world.st/Mac-OS-Cocoa-MIDI-Plugin-td4893691.html>). Is there any setup that works for MIDI IO on OSX using Pharo 6/6.1? Cheers, Manuel

Sept. 21, 2018

Deprecation guide for methods, classes and packages

by Torsten Bergmann

Hi, >From Bug #20900/ PR 1818 it looked like it is not really clear on how to "deprecate" correctly. Therefore I summarized and wrote a short guide following what we contributors used as best practice so far. Also read [1], [2] and [3] and check some of the deprecation settings in the Pharo settings browser. Just open SettingsBrowser and search for "Depre". I write this mail to "pharo-dev" with CC: "pharo-users" list - because of common interest. But comments and replies should please go to "pharo-dev" so we do not disrupt the thread too much. Thanks! Please review what I wrote and ideally we can put the text or a link to it as "Deprecation guide" into the documentation / wiki / ... on GitHub afterwards. Hope this helps a little bit. Thanks T. [1] https://en.wikipedia.org/wiki/Deprecation [2] https://www.peteruhnak.com/blog/2015/08/06/transforming-deprecated-code-wit… [3] https://pharoweekly.wordpress.com/2016/06/17/automatic-deprecation-refactor… ------------------------------------------------------------------------------------------------------------------------------ In any Pharo version we have a special package hosting deprecated methods and classes. This allows smooth migration for Pharo users as code should still load and runs to some extent - but deprecation warnings and possibly a helping hand (in form of automatic code transformations) could be given to support migration. As we currently work on Pharo7 there is a "Deprecated70" package in the image hosting deprecated methods and classes intended to be removed for Pharo 8. When Pharo 7 is released the users can easily spot the deprecations - also because they are striked through (more on this below). When Pharo 8 iteration starts the "Deprecated70" will be replaced with an empty "Deprecated80" package. DEPRECATING METHODS =================== If you deprecate a METHOD use #deprecated: message and switch it to be an extension method in *Deprecated70*. If the method could be replaced by calling another method then dispatch the call to the new method and ideally provide a transformation so next time the old method is called the sender method is automagically rewritten and could be adopted/migrated: oldMethod "An old method we do not use anymore. But luckily there is a replacement." self deprecated: 'Please use #newMethod instead' transformWith: '`@receiver oldMethod' -> '`@receiver newMethod'. ^ self newMethod So if there is a method like foo self oldMethod sending the old deprecated method it will be migrated to foo self newMethod as soon as foo, the oldMethod and the transformation is called. If the automatically migrated method is under version control (Monticello or git) you will easily see that #foo was modified. In case there is no replacement for a method you would like to deprecate then it is best to throw an error when it is used: veryOldMethod "A very old method hopefully nobody uses. So we do no provide a replacement." self deprecated: 'The method #veryOldMethod is deprecated without any replacement'. ^ self error: 'Do not use #veryOldMethod anymore' Note that the method is striked through in the Pharo system browser in both cases to show that it should not be used anymore. In the standard image calling a deprecated method is logged on the Transcript and flagged with a warning dialog. This should help users and maintainers of external packages to easily spot when they still use deprecated code. You can change these settings in Pharo Settings Browser under Tools -> Debugging -> Deprecation Handling. DEPRECATING CLASSES =================== If you deprecate a CLASS implement #isDeprecated on class side to return true and move it to package "Deprecated70" Ideally write in the class comment why it is deprecated and if there is a replacement class what to use instead Object subclass: #OldClass instanceVariableNames: '' classVariableNames: '' package: 'Deprecated70-OldTag' and comment to explain the reasons: OldClass comment: 'Use NewClass instead'. and implement in class side method category 'testing' isDeprecated "We do not need this class anymore" ^true Note that the class is striked through in the system browser. DEPRECATING PACKAGES ==================== If you deprecate a PACKAGE then rename it with "Deprecated" in the name. Let the class side of the package manifest (typically a subclass of PackageManifest within the package) als return #isDeprecated with true. In the class comment of the package manifest (which also serves as package comment) explain why the package is deprecated and if there is a replacement or not. Example: your package name is "OldPackage-Core", so the new name is "OldPackage-Deprecated-Core". Create a manifest or use the existing one. A Manifest should be a subclass of PackageManifest and should be categorized within a 'Manifest' tag. PackageManifest subclass: #ManifestOldPackageCore instanceVariableNames: '' classVariableNames: '' package: 'OldPackage-Deprecated-Core-Manifest' and comment to explain the reasons: ManifestOldPackageCore comment: 'This package is not useful anymore. Check NewPackage for replacement'. and implement in class side method category 'testing' isDeprecated "We do not need this package anymore" ^true Note that the manifest class and the package is striked through in the system browser. Be aware that a deprecated package might be removed completely already in the next Pharo major version iteration.

Sept. 21, 2018

Re: [Pharo-users] Sending emails

by Jeff Gray

After trawling through some of the older posts it sounds like an external mail handling service may be the way to go, or I just stick with Gmail. There are some quite generous email services that give in the region of 10,000 mails a month for no charge. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Sept. 21, 2018

Re: [Pharo-users] TextEditor

by HernÃ¡n Morales Durand

StandardWindow new addMorph: ( RubScrolledTextMorph new withLineNumbers; appendText: '/path/to/file' asFileReference contents) fullFrame: (0@0 corner: 1@1) asLayoutFrame; openInWorld. Cheers, HernÃ¡n 2018-09-20 15:06 GMT-03:00 Hilaire <hilaire(a)drgeo.eu>: > Hello, > > How can I get a text editor window? > > I can't make sense of the TextEditor class, and its comment is not helpful. > > What is the logic behind? > > Thanks > > Hilaire > > -- > Dr. Geo > http://drgeo.eu > > >

Sept. 20, 2018

Sending email

by Jeff Gray

Hi all, I can use the ZdcSecureSMTPClient to send emails from a Gmail account but I have tried to do the same from a Microsoft live account without success. It times out on the connection. Do I just need to work out what's wrong or is there an easier, better way to send mails from a pharo application? -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Sept. 20, 2018

Sending emails

by Jeff Gray

Hi all, I can use the ZdcSecureSMTPClient to send emails from a Gmail account but I have tried to do the same from a Microsoft live account without success. It times out on the connection. Do I just need to work out what's wrong or is there an easier, better way to send mails from a pharo application? -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Sept. 20, 2018

Re: [Pharo-users] Pharo 6 snap package

by Offray Vladimir Luna CÃ¡rdenas

Hi, Another project that have save us from installation pains on several heterogeneous environments while giving workshops (including machines with several Linux flavors and Mac OS X, but not Windows) is Nix[1]. There is even a package for Pharo[2]. [1] https://nixos.org/nix/ [2] https://nixos.org/releases/tmp/release-nixos-unstable-small/nixos-18.09pre1… Cheers, Offray On 9/7/18 10:07 AM, Guillermo Polito wrote: > Hi all, > > Nope, I'm not maintaining my package. I was experimenting with it at > some point (2 years ago?) and then saw somebody else started with a > more complete solution so I've not continued working on it. > > Personally, I've experienced the same sandboxing problems stated by > Alistair, plus the fact that at that moment Snap was not working in > *nixes other than Ubuntu made me put my energy somewhere else. > > Three points more: > Â - for those that do not know exactly what we are talking about, snap > is "new" a packaging tool used in ubuntu. I strongly believe that we > could use some kind of tool like this for the VM, but not for image > (which are mutable). > Â - it could maybe make more sense to package the pharo launcher? ;) > Â - rather than snaps, I'd put my 2cents on a solution > likeÂ https://github.com/probonopd/appimagekit/. I've been following it > for two years and it has a lot of movement and getting mature. > > On Fri, Aug 24, 2018 at 6:18 PM Alistair Grant <akgrant0710(a)gmail.com > <mailto:akgrant0710@gmail.com>> wrote: > > Hi Hannes, > > On Fri, 24 Aug 2018 at 06:36, H. Hirzel <hannes.hirzel(a)gmail.com > <mailto:hannes.hirzel@gmail.com>> wrote: > > > > Hello Alistair > > > > Thank you for the detailed answer. I understand that at the moment > > going for a Pharo snap package does not seem to be useful. > > > > In particular as a Pharo installation may reside in a directory with > > everything included. > > So different Pharo installations may reside in different > directories. > > Yep.Â Especially if using the in-development version of Pharo > (currently 7), I find it useful to pair images and VMs. > > > > I think where snap still might come is for solutions which require > > more than a particular Pharo installation. > > > > For example I could think of combining a particular Pharo > version with > > a particular Jupyter notebook installation into a snap which could > > lead to aÂ web based 'Dynabook' solution. > > That was one of the things that attracted me to snaps originally, I > use sqlite in my daily environment, so included it in the Pharo snap. > > > > I am also looking forward to Guille's answer. > > +1. > > Cheers, > Alistair > > > > Regards > > Hannes > > > > On 8/23/18, Alistair Grant <akgrant0710(a)gmail.com > <mailto:akgrant0710@gmail.com>> wrote: > > > Hi Hannes, > > > > > > On Wed, 22 Aug 2018 at 17:20, H. Hirzel > <hannes.hirzel(a)gmail.com <mailto:hannes.hirzel@gmail.com>> wrote: > > >> > > >> Hello > > >> > > >> Are there plans to do a Pharo 6.1Â snap package in the upcoming > > >> months? (Ubuntu 18.04.1) > > > > > > I haven't been thinking about it really, because: > > > > > > - The big attraction for me was the ability to easily run 32 > bit Pharo > > > on a 64 bit OS without installing all the dependencies.Â But > now that > > > 64 bit Pharo is stable that driver has largely gone. > > > - The sandboxing is quite limiting for a development > environment, so > > > if you want to run commands on the localhost you end up doing > > > something like ssh'ing the command to localhost. > > > - The snap runtime environment is still quite immature - I've > had to > > > deal with bugs in snapd, the gtk desktop interface, loading 32 bit > > > executables, etc. > > > - The snapcraft build environment is still evolving, so I have > to keep > > > up with the changes. > > > - I was originally compiling the 32 and 64 bit VMs as part of the > > > build process, but that is problematic as the 32 and 64 bit > libraries > > > tend to interfere with each other making the build process > unstable. > > > - You can't run multiple versions of a snap on one system, e.g. we > > > can't have Pharo 6 and Pharo 7 installed simultaneously under > the one > > > snap name (pharo).Â I tried to register Pharo7 so pharo could > be the > > > GA version (6), but never got a response. > > > > > > I was listening to an Ubuntu podcast just this week where one > of the > > > hosts tried installing 4 packages via snaps and ended up going > back to > > > debian packages for 3 of the packages due to problems, so it > obviously > > > still isn't mature. > > > > > > I realise that every software package has its own issues, I'm sure > > > someone from the snap community could find parallel issues > with Pharo, > > > but it wasn't where I wanted to be spending all my time. > > > > > > If someone wants to take it over, I'm more than happy to pass > it on > > > (although it isn't building at the moment due to changes in > > > snapcraft). > > > > > > If there is enough interest I'll try and update it to run > Pharo 6.1. > > > > > > If Guille is actively maintaining his package, maybe we should > move to > > > that (I haven't looked at it). > > > > > > Cheers, > > > Alistair > > > > -- > > Â Â Â > > > > Guille Polito > > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > French National Center for Scientific Research - _http://www.cnrs.fr_ > > > *Web:* _http://guillep.github.io_ > > *Phone: *+33 06 52 70 66 13 >

Sept. 20, 2018

Re: [Pharo-users] Query on Pharo syntax

by Offray Vladimir Luna CÃ¡rdenas

I learned something for sure from this exchange. Thanks Peter and Ben for this public conversation. Cheers, Offray On 9/10/18 7:56 PM, Ben Coman wrote: > Its a very interesting and elegant aspect of PharoÂ > and I'm sure there are others at different parts of their journey > learning Pharo > who learnt something new from your question.Â > > cheers -ben > > On Tue, 11 Sep 2018 at 03:13, PBKResearch <peter(a)pbkresearch.co.uk > <mailto:peter@pbkresearch.co.uk>> wrote: > > Thanks Ben â itâs all clear now. Thanks also to Esteban, who > spared my blushes by answering direct! > > Peter Kenny > > Â > > *From:*Pharo-users <pharo-users-bounces(a)lists.pharo.org > <mailto:pharo-users-bounces@lists.pharo.org>> *On Behalf Of *Ben Coman > *Sent:* 10 September 2018 19:56 > *To:* Any question about pharo is welcome > <pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org>> > *Subject:* Re: [Pharo-users] Query on Pharo syntax > > Â > > Â > > On Tue, 11 Sep 2018 at 02:44, PBKResearch <peter(a)pbkresearch.co.uk > <mailto:peter@pbkresearch.co.uk>> wrote: > > Hi All > > Â > > This is an idiot question, I should know the answer, but I > have looked around and canât find relevant documentation. Iâm > not asking for a full answer, just a pointer as to where to > start looking. > > Â > > I have seen from examples in this forum that an expression > like the following: > > Â > > paras collect: [para| para prettyPrinted] > > Â > > can be written more concisely as: > > Â > > paras collect: #prettyPrinted > > Â > > which obviously works when I try it. It doesnât seem to fit in > with the definition of #collect:, which requires a block as > argument. Where can I find the relevant definition, either in > method comments or in some general manual? Can the notation be > extended, > > Â > > Its not special notation.Â Just a normal object (a Symbol) passed > via a normal message. > > Â > > for example to #select: - obviously with an argument which > returns a Boolean? Can it be used with a method which requires > an argument, e.g. as myArray collect: (#myMethod: arg)? Are > there any other extensions? > > Â > > Any help gratefully received. > > Â > > Peter Kenny > > Â > > Full answer ;) > > Its a combination of the following two methods... > > Â > > Collection >> collect: aBlockÂ > > Â Â Â Â Â Â Â Â Â Â Â Â Â Â | newCollection | > > Â Â Â Â Â Â Â Â Â Â Â Â Â Â newCollection := self species new. > > Â Â Â Â Â Â Â Â Â Â Â Â Â Â self do: [:each | newCollection add: (aBlock value: > each)]. > > Â Â Â Â Â Â Â Â Â Â Â Â Â Â ^ newCollectionÂ > > Â > > Symbol value: anObjectÂ > > Â Â Â Â Â Â Â Â Â Â Â Â Â Â ^anObject perform: self. > > Â > > When /aBlock/ is a symbol, that symbol is performed on /each/ element. > > And looking atÂ #select:Â , yes it works the same...Â > > Â > > Collection >> select: aBlockÂ > > Â Â Â Â Â Â Â Â Â Â Â Â Â Â | newCollection | > > Â Â Â Â Â Â Â Â Â Â Â Â Â Â newCollection := self copyEmpty. > > Â Â Â Â Â Â Â Â Â Â Â Â Â Â self do: [ :each |Â > > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â (aBlock value: each)Â > > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â ifTrue: [ > newCollection add: each ]]. > > Â Â Â Â Â Â Â Â Â Â Â Â Â Â ^newCollection > > Â > > cheers -ben >

Sept. 20, 2018