October 2019 - Pharo-users - lists.pharo.org

Re: [Pharo-users] OSProcess and CommandShell available on GitHub for Pharo users

by Sean P. DeNigris

Sean P. DeNigris wrote > ...to the GH README Also: - you can disable the GH issue tracker if you don't want reports there - you don't need the code subfolder (src) in the URL since you have project metadata ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Oct. 14, 2019

Re: [Pharo-users] OSProcess and CommandShell available on GitHub for Pharo users

by Sean P. DeNigris

David T. Lewis wrote > Alistair Grant and I, with the support of Feenk, have made GitHub > repositories > for OSProcess and CommandShell Thank you to all involved! David T. Lewis wrote > my own development work remains on squeaksource so I prefer > contributions there anyway It might be good to add that disclaimer and the location of the canonical repo to the GH README. Also, does anyone know whether, after loading from GH, one can make enhancements and then simply save to an MCZ repo? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Oct. 14, 2019

Re: [Pharo-users] Transcript: printString or asString

by Samuel Teixeira Santos

I like the way you put because it's a nice way to remember and to teach too. I'm just bit confusing, and I think this because Object Oriented it's not one of my strong skills, when you say when: "what this object converted *to a string means in my domain"* - what really means, specially about when you say *'domain'?* Could you give some example for this? Thanks

Oct. 14, 2019

Re: [Pharo-users] Transcript: printString or asString

by Sean P. DeNigris

arcanosam wrote > printString... v asString... There is something different about both? I will add that conceptually: - #printString = what a developer would want to see, e.g. in an inspector - #displayString = a string suitable for UI (i.e. in production) - #asString - while typically implemented to be the same as #printString, the meaning for me is a bit different, which is "what this object converted to a string means in my domain" That said, IMHO as a community we are not great about properly distinguishing these, especially #displayString. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Oct. 14, 2019

Re: [Pharo-users] Transcript: printString or asString

by Samuel Teixeira Santos

Thank you too Richard. Very interesting and elucidative. Regards to all.

Oct. 14, 2019

Re: [Pharo-users] Smallest docker image for pharo >=7 ?

by Norbert Hartl

Hi, > Am 14.10.2019 um 09:07 schrieb HernÃ¡n Morales Durand <hernan.morales(a)gmail.com>: > > Hi guys, > > Because I am lazy and want to avoid searching through all DockerHub repository pages... Do you know a Dockerfile to generate the smallest possible docker image for Pharo? Please have a look at https://github.com/pharo-contributions/Docker-Alpine <https://github.com/pharo-contributions/Docker-Alpine> This was the first step in unify work on this. Itâs based on alpine. It may need to be ironed out a bit as alpine has a different libc implementation. Further steps should include building a pharo minimal image to bring it down in size. 10 MB per docker image is theoretically possible. > > I am also interested in which stage you use to install packages into the image, and why? Do you copy the contained image into docker already built? or do you prefer install packages on building? (as done by pip -r requirements.txt) > Anyone using xpra binding from subuser [1]? > Anyone could make it work Pharo on Alpine since it uses different libc? > Building the docker image you can do either way. I have one public project where I provide the software as docker image. Doing this is easier when you build the pharo image inside the docker container. Because you can then use dockerhub [1] to build it. You just add your project there and it builds it and releases it. In our inhouse products I use building the image outside of the docker container. The process is building the product image then load the test code and test it and when everything is fine use the image and package as a docker image. I donât know subuser but using xpra will bloat the docker image because AFAIK it works over X11 which means you need those libraries in the docker container and in the pharo vm. What Iâm working on is to be able to connect a running docker container directly from my laptop and use TelePharo [2] on it. Norbert > Anyway sharing opinions would be also appreciated. > > [1] http://subuser.org/news/0.3.html <http://subuser.org/news/0.3.html> > > Cheers. > > HernÃ¡n > [1] https://hub.docker.com <https://hub.docker.com/>[2] https://github.com/pharo-ide/TelePharo <https://github.com/pharo-ide/TelePharo>

Oct. 14, 2019

Re: [Pharo-users] NVARCHAR and Glorp

by Sven Van Caekenberghe

Hi Tomaz, > On 11 Oct 2019, at 18:15, eftomi <tomaz.turk(a)ef.uni-lj.si> wrote: > > Dear all, > > I'm working on ADO database driver for Glorp by using Pablo's PharoCOM. The > structure of the driver is similar to Sven's P3DatabaseDriver and P3Client > (thanks, Sven for very clear architecture :-) ) and the work is progressing > quite nicely. I can connect to SQL Server, PostgreSQL and create tables, > insert and read data directly with ADO Connection and Recordset objects, and > with Glorp, too. In next days I'll do some more testing, including Oracle, > and publish the prototype on GitHub. The goal is not PostgreSQL, of course, > but to finally reach SQL Server, Oracle and possibly MS Access, at least > from Windows systems. Great to hear this, please keep us all posted of your progress. > One thing is bothering me though - SQL Server supports Unicode with NCHAR > and NVARCHAR types, and when using INSERT INTO with literal strings these > should be prefixed with N, like in > > N'This is a Unicode string' > > Does somebody remember whether Glorp can prefix the strings in that way when > constructing SQL statements? I checked all the constants and string > conversions under DatabasePlatform but haven't found anything related to > this kind of prefixing. I don't know for sure. Could you not add the N at the moment the string quotes are written ? What I do know is this: the interface between P3DatabaseDriver and P3Client is essentially an SQL string to execute. That SQL string was built by the Glorp machinery, so it must know about certain specifics (like string quoting and escaping, etc). Also, in Glorp's Login #database specification, a platform is set, like PostgreSQLPlatform. So I am assuming some platform specific delegation is happening (or could happen). I don't have a Glorp image ready, but there must be a way to find this out. That being said, I do foresee a problem for you. You are building a more general driver that can access several different platforms, you will need to make that explicit, else you won't be able to do something specific for SQL Server. HTH, Sven > Thanks and best wishes, > Tomaz > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Oct. 14, 2019

Re: [Pharo-users] Transcript: printString or asString

by Richard O'Keefe

days keysAndValuesDo: [:key :value | Transcript print: key; nextPutAll: ' has '; print: value; nextPutAll: ' days'; cr]. Transcript endEntry. works too and in some Smalltalks is easily the most efficient approach, as it does not construct any strings you have no other use for. In Pharo, however, there is a reason to prefer Transcript nextPutAll: (key asString, ' has ', value asString, ' days', String cr). The reason is that in Pharo 7, Transcript is an instance of *ThreadSafe*Transcript, and each public operation like #nextPut: or #print: locks the stream. In fact we have show: anObject self critical: [self print: anObject; endEntry]. print: anObject self nextPutAll: anObject asString. nextPutAll: aString self critical: [stream nextPutAll: aString]. ^aString cr self nextPut: Character cr. nextPut: aCharacter self critical: [stream nextPut: aCharacter]. ^aCharacter So the code I exhibited second (using #nextPutAll:) locks the Transcript *once* ensuring that nothing else can be written between 'days' and cr, whereas both versions you exhibited have a timing window between #show: and #cr where another Smalltalk process could write something. But you are asking about the difference between #asString and #printString. So look up the definitions! In a Playground, type asString and then Ctrl-m (for iMplementors). We see almost at once that Object>> asString ^self printString so that for numbers there is NO difference between the two (except a little bit of overhead for #asString). But we also see String>> asString ^self Symbol>> asString "complicated code logically equivalent to" ^String withAll: self Just for grins, the following interaction was with GNU Smalltalk. st> #January asString 'January' st> #January printString '#January' st> 31 asString '31' st> 31 printString '31' Pharo does exactly the same. On Sun, 13 Oct 2019 at 23:51, Samuel Teixeira Santos <arcanosam(a)gmail.com> wrote: > > Hi folks. > I'm starting in Pharo studies by FUN Mooc. > In Week 03, on An Overview of Essential Collections there is the example below: > > | days | > days := Dictionary new. > > days > at: #January put: 31; > at: #February put: 28; > at: #March put: 31. > > days keysAndValuesDo: > [ :k :v | Transcript show: k asString, ' has ', v printString, ' days' > ; cr ] > > The code in blue I change for > > days keysAndValuesDo: > [ :k :v | Transcript show: k asString, ' has ', v asString, ' days' > ; cr ] > > And works too on Playground. > > There is something different about both? There is someone better than other? > > Thanks in advance, > > > Samuel T. Santos

Oct. 14, 2019

Re: [Pharo-users] Smallest docker image for pharo >=7 ?

by Pierce Ng

On Mon, Oct 14, 2019 at 04:07:49AM -0300, HernÃ¡n Morales Durand wrote: > Because I am lazy and want to avoid searching through all DockerHub > repository pages... Do you know a Dockerfile to generate the smallest > possible docker image for Pharo? > Anyone could make it work Pharo on Alpine since it uses different libc? Hi HernÃ¡n, Please see following links: - https://github.com/pharo-contributions/Docker-Alpine - https://hub.docker.com/r/pierceng/pharovm-alpine - https://hub.docker.com/r/pierceng/pharo7-alpine - https://www.samadhiweb.com/blog/2019.07.20.alpine.pharo.minimal.html - https://www.samadhiweb.com/blog/2019.08.11.minimizing.pharo.html The Alpine-based VM can be made smaller by removing unused/irrelevant modules. Image-wise, currently I am using Pharo 7 minimal, which is just under 30MB, and that forms the lower bound of the Pharo image size. However there is also the Pharo Candle effort that aims to make really small images, which I hope to try out soon. > I am also interested in which stage you use to install packages into the > image, and why? Do you copy the contained image into docker already built? For Pharo, I start with the regular or minimal image, then load my packages. For Docker, I first build a container image for the VM only. Using that I build a new container image from the Pharo image and other required files. > [1] http://subuser.org/news/0.3.html Interesting. I use Firejail for big programs such as Chromium. Pierce

Oct. 14, 2019

Smallest docker image for pharo >=7 ?

by HernÃ¡n Morales Durand

Hi guys, Because I am lazy and want to avoid searching through all DockerHub repository pages... Do you know a Dockerfile to generate the smallest possible docker image for Pharo? I am also interested in which stage you use to install packages into the image, and why? Do you copy the contained image into docker already built? or do you prefer install packages on building? (as done by pip -r requirements.txt) Anyone using xpra binding from subuser [1]? Anyone could make it work Pharo on Alpine since it uses different libc? Anyway sharing opinions would be also appreciated. [1] http://subuser.org/news/0.3.html Cheers. HernÃ¡n

Oct. 14, 2019