December 2017 - Pharo-users

Thanks All.
by Ian Ian Dec. 26, 2017

Dec. 26, 2017

After some looking into it I believe Mongo Voyager is the easiest given the current options. Too bad Gemstone limits usage after a given number of Gems. Too bad ObjectDB does as well. Thanks all. :) On Dec 25, 2017 12:00 PM, <pharo-users-request(a)lists.pharo.org> wrote: > Send Pharo-users mailing list submissions to > pharo-users(a)lists.pharo.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.pharo.org/mailman/listinfo/pharo-users_ > lists.pharo.org > or, via email, send a message with subject or body 'help' to > pharo-users-request(a)lists.pharo.org > > You can reach the person managing the list at > pharo-users-owner(a)lists.pharo.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Pharo-users digest..." > > Today's Topics: > > 1. Re: Object Persistence (Hilaire) > 2. Re: Object Persistence (Joachim Tuchel) > 3. Re: Object Persistence (Torsten Bergmann) > 4. Re: Object Persistence (Stephane Ducasse) > > > ---------- Forwarded message ---------- > From: Hilaire <hilaire(a)drgeo.eu> > To: pharo-users(a)lists.pharo.org > Cc: > Bcc: > Date: Mon, 25 Dec 2017 12:08:08 +0100 > Subject: Re: [Pharo-users] Object Persistence > Fuel (present in the image) is nice, but not compatible from one image > version to another one. > > Hilaire > > > Le 25/12/2017 Ã 10:43, Ian Ian a Ã©crit : > >> Hi All, >> >> Thoughts of a purely OO nature? >> >> :) >> > > -- > Dr. Geo > http://drgeo.eu > > > > > > > ---------- Forwarded message ---------- > From: Joachim Tuchel <jtuchel(a)objektfabrik.de> > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Cc: > Bcc: > Date: Mon, 25 Dec 2017 12:54:10 +0100 > Subject: Re: [Pharo-users] Object Persistence > Wasnât there an attempt to port Magma over from Squeak? That would sound > like a nice alternative. Or Gemstone, of course. > > > Am 25.12.2017 um 10:43 schrieb Ian Ian <icjohnsoia(a)gmail.com>: > > > > Hi All, > > > > Thoughts of a purely OO nature? > > > > :) > > > > > > ---------- Forwarded message ---------- > From: Torsten Bergmann <astares(a)gmx.de> > To: pharo-users(a)lists.pharo.org > Cc: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Bcc: > Date: Mon, 25 Dec 2017 14:13:37 +0100 > Subject: Re: [Pharo-users] Object Persistence > Hi, > > with Voyage you can already use easy persistence in an OO way - with tiny > (P)UnQlite up to Mongo. > > Check https://github.com/pharo-nosql > > Or you use Gemstone. > > For a full Magma version on Pharo: > I doubt that will happen as Chris Muller was and still is more oriented > towards Squeak as > development platform. He is the author of Magma and beside the port it > would cost him > (or anyone who would do such a port) more effort to maintain another Pharo > specific version. > > But maybe a Pharo client for a Squeak based Magma server is possible - > with a Voyage wrapper. > > Bye > T. > > > Gesendet: Montag, 25. Dezember 2017 um 12:54 Uhr > > Von: "Joachim Tuchel" <jtuchel(a)objektfabrik.de> > > An: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org> > > Betreff: Re: [Pharo-users] Object Persistence > > > > Wasnât there an attempt to port Magma over from Squeak? That would sound > like a nice alternative. Or Gemstone, of course. > > > > > Am 25.12.2017 um 10:43 schrieb Ian Ian <icjohnsoia(a)gmail.com>: > > > > > > Hi All, > > > > > > Thoughts of a purely OO nature? > > > > > > :) > > > > > > > > > > > ---------- Forwarded message ---------- > From: Stephane Ducasse <stepharo.self(a)gmail.com> > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Cc: > Bcc: > Date: Mon, 25 Dec 2017 16:01:15 +0100 > Subject: Re: [Pharo-users] Object Persistence > the author of omnibase told me that he always wanted to port it to > Pharo. But may be someone should do it. > There is also VOSS that is open source even if GPL that could be > ported to pharo but this is an effort too. > > Stef > > On Mon, Dec 25, 2017 at 10:43 AM, Ian Ian <icjohnsoia(a)gmail.com> wrote: > > Hi All, > > > > Thoughts of a purely OO nature? > > > > :) > > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.pharo.org > http://lists.pharo.org/mailman/listinfo/pharo-users_lists.pharo.org > >

2 3

Strange 'Connection closed while waiting for data.' Zinc error
by Yuriy Tymchuk Dec. 26, 2017

Dec. 26, 2017

Hi, Iâm trying to hack something with Pharo 6.1 and Phillips Hue[1] (they have a simple REST API). When I try to do a GET request with Zinc like this: ZnClient new url: 'http://192.168.0.115:80/api/1028d66426293e821ecfd9ef1a0731df/lights/'; get I get a âConnectionClosed: Connection closed while waiting for dataâ exception. The service provides a JSON response that I can get without a problem by using a web browser or curl. Also if I try to access fewer data (e.g. adding /1 to the url, so it gets only one resource) I donât get the exception. What is even more strange, when I resume the exception I get the desired response i.e. this works: [ ZnClient new url: 'http://192.168.0.115:80/api/1028d66426293e821ecfd9ef1a0731df/lights/'; get ] on: ConnectionClosed do: [ :ex | ex resumeUnchecked: ex defaultResumeValue ] Of course I cannot share the server that is on my local network for resting, but maybe anyone knows it there are any known issues with Zinc, or if there are ways for me to debug the issue further. Cheers. Uko [1]: https://www.developers.meethue.com

3 5

Iceberg URL regex not matching how I would expect it to?
by Ian Ian Dec. 25, 2017

Dec. 25, 2017

Hi All, I am having trouble setting up iceberg to access my repository via ssh. On the command line I assess it via: git clone user@server.com:/proj/proj.git and all works as expected. When adding trying to add the same repository to iceberg I get a parseUrl error thrown from class IceScpRemote. While debugging I see the following regex: matcher := '(ssh\://)?([\w\-]+@)?([\w\-.]+)(\:[\d]+)?(\:|/)/?([\w\-]+)/([\w\-]+)(\.git)?' asRegex. which parses username@server.com:/directory/proj.git. However fails to parse: username@server.com:/dir1/dir2/proj.git The corrected version is as follows: matcher := '(ssh\://)?([\w\-]+@)?([\w\-.]+)(\:[\d]+)?(\:|/)/?(([\w\-]+)/)+([\w\-]+)(\.git)?' asRegex. Questions: Is this by design? of the top of your head: If I use the corrected version am I going to run into other issues? NB: I am using 64 bit Pharo 6.0 Update: #60520 Thanks in advance,

2 1

Getting Iceberg Commits Back to Github
by Evan Donahue Dec. 24, 2017

Dec. 24, 2017

Hi, Once I have cloned my github repository and committed changes locally, how do I actually get those changes back to github? I went to synchronize repository > push > publish all, and it has a loading bar for a few seconds that says "pushing local commits to origin," but github reflects no changes. ssh -T confirms that github recognizes my key, and I'm using a stable pharo 7 from within the last week or so. Any help would be appreciated. Thanks, Evan

1 0

NeoCSVWriter: how to output an empty quoted field
by jtuchel＠objektfabrik.de Dec. 24, 2017

Dec. 24, 2017

Hi, I need to write a number of empty quoted fields in a CSV export. The receiving application will complain about missing quotes for empty text fields... (don't ask, I've done all the eye rolling for you already) My frst attempt was: writer addConstantField: '""'. But this doesn't write the quotes - I really don't see why, but it's the case. Also, adding writer addObjectField: [:a| '""']. doesn't really work, because it will literally add the double quotes between single quotes... (???) Do I really have to implement some method that returns an empty String on my business objects and use: writer addQuotedField: #justAnEmptyString. ? Am I missing some switch to enable quotes for empty quoted fields? My version of NeoCSVWriter on VA Smalltalk is not actually a current one... Joachim And, btw: Happy Holidays to all of you and a Happy new Year! -- ----------------------------------------------------------------------- Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de Fliederweg 1Â Â Â Â Â Â Â Â Â Â Â Â Â http://www.objektfabrik.de D-71640 Ludwigsburg http://joachimtuchel.wordpress.com Telefon: +49 7141 56 10 86 0Â Â Â Â Â Fax: +49 7141 56 10 86 1

2 3

Fuel transfer from Pharo 1.4 to Pharo 6.1
by Andreas Brodbeck Dec. 22, 2017

Dec. 22, 2017

Hi all, I have a long running Seaside/Pharo application which still runs perfect on Pharo 1.4. I want to step into the future and migrate to the newest Pharo 6.1. The application's persistence is just in the image, so my plan is to use Fuel to transfer the objects from Pharo 1.4 to Pharo 6.1. My first attempt: --- Using Fuel version 1.9.4 on both VMs. --- Class TimeStamp was missing, so I created it. --- I use a Fuel-migration for the renaming of "MethodContext" into the new "Context" class. But now I am stuck with FLMethodChanged errors. My investigation shows that there are unequal values for the method Context>>bytecodesHash when comparing Pharo 1.4 with 6.1. (BTW: Pharo 5 gives same values like 6.1). So, basically Fuel can not materialize the instances because the bytecode hash of all methods have changed, comparing 1.4 to 6.1. My feeling says that this could be a major problem for my plans to migrate from Pharo 1.4 to 6.1. Is there a chance to still load those instances with Fuel into the new 6.1 Pharo? Thanks! Andreas -- Andreas Brodbeck www.mindclue.ch

7 19

[ANN] Gemtalk Systems upgraded to Gold Membership
by Marcus Denker Dec. 22, 2017

Dec. 22, 2017

The Pharo Consortium is very happy to announce that Gemtalk Systems has upgraded to Gold Member status. About - Gemtalk Systems: https://gemtalksystems.com - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: http://association.pharo.org

2 1

[ANN] Pharo Consortium New Bronze Member: Object Profile
by Marcus Denker Dec. 21, 2017

Dec. 21, 2017

The Pharo Consortium is very happy to announce that Object Profile has joined the Consortium as a Bronze Member. About - Object Profile: http://objectprofile.com - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: - http://association.pharo.org

2 2

Hi, do I nowadays need any Id and psw, to log in smalltalk hub and others?
by Janko Korelc Dec. 21, 2017

Dec. 21, 2017

... as connection time out... Best Regards! Janko Korelc

2 1

Re: [Pharo-users] Irc
by Ian Ian Dec. 21, 2017

Dec. 21, 2017

Thanks Estoban. I'll check out discord. :) BTW, I am new to smalltalk. New to Pharo. Liking both! :) On Dec 21, 2017 8:45 AM, <pharo-users-request(a)lists.pharo.org> wrote: Send Pharo-users mailing list submissions to pharo-users(a)lists.pharo.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.pharo.org/mailman/listinfo/pharo-users_lists.pharo.org or, via email, send a message with subject or body 'help' to pharo-users-request(a)lists.pharo.org You can reach the person managing the list at pharo-users-owner(a)lists.pharo.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Pharo-users digest..." Today's Topics: 1. Re: Active IRC Chanel (Esteban Lorenzano) 2. Re: Iceberg, Git and Package version (Esteban Lorenzano) 3. Re: Iceberg, Git and Package version (Esteban Lorenzano) 4. Hi, do I nowadays need any Id and psw, to log in smalltalk hub and others? (Janko Korelc) 5. Re: Iceberg, Git and Package version (Vitor Medina Cruz) ---------- Forwarded message ---------- From: Esteban Lorenzano <estebanlm(a)gmail.com> To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Cc: Bcc: Date: Thu, 21 Dec 2017 11:10:55 +0100 Subject: Re: [Pharo-users] Active IRC Chanel > On 21 Dec 2017, at 08:27, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > >> On 21 Dec 2017, at 04:34, Ian Ian <icjohnsoia(a)gmail.com> wrote: >> >> Hi All, >> >> Is there an active IRC Chanel? > > No. There is (or was) an inactive one. > > >> Read somewhere (can't remember) that there is one labeled #pharo. Is this true if so may I ask on which server it resides? >> > > > I guess it is still there, it was on freenode I think. > > The Discord chat is quite active. For me it works much better than IRC. Maybe I had just a bad IRC > client, but it never was a nice experience. yes. I donât understand why, but #irc channel never worked while discord works pretty well and is very active. I meanâ¦ at the end, discord is no more than a glorified irc, but wellâ¦ one works and the other donât :) Esteban > > Marcus ---------- Forwarded message ---------- From: Esteban Lorenzano <estebanlm(a)gmail.com> To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Cc: Bcc: Date: Thu, 21 Dec 2017 11:22:59 +0100 Subject: Re: [Pharo-users] Iceberg, Git and Package version On 20 Dec 2017, at 19:51, Vitor Medina Cruz <vitormcruz(a)gmail.com> wrote: Hello, How are packages versions computed in Iceberg? I am looking at the Metacello documentation at 'Deep in Pharo', it says I can define dependencies at package level and it uses the following format to identify versions: <dev_name.versionNumber>; which I think is a pattern used by Monticello, right? However, I can't figure what is the equivalent (if any) in Iceberg. Thanks in Advance, Vitor Hi Vitor, Package versions do not have any sense on iceberg, where what has sense is the âprojectâ version. All packages point to a commit in repo. This is to say, you do not load single package in iceberg but you load a repository version (which is the commit). Thatâs why you use Metacello expressions like this: Metacello new repository: âgithub://someuser/someproject:sometag'; baseline: âBlahâ; load. and in your baselines, when you include another project you do spec baseline: âBlahâ with: [ spec repository: âgithub://someuser/someproject:sometag' ]. cheers! Esteban ---------- Forwarded message ---------- From: Esteban Lorenzano <estebanlm(a)gmail.com> To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Cc: Bcc: Date: Thu, 21 Dec 2017 12:02:54 +0100 Subject: Re: [Pharo-users] Iceberg, Git and Package version On 21 Dec 2017, at 11:03, Vitor Medina Cruz <vitormcruz(a)gmail.com> wrote: Then in a Metacello configuration should I reference the hash git commit or a tag in a version method? For example, an extract from Deep in Pharo: ConfigurationOfCoolToolSet>>version02: spec > <version: '0.2' imports: #('0.2-baseline' )> > spec for: #common do: [ > spec blessing: #beta. > spec > package: 'CoolToolSet-Core' with: 'CoolToolSet-Core-AlanJay.1'; > package: 'CoolToolSet-Tests' with: 'CoolToolSet-Tests-AlanJay.1'; > project: 'CoolBrowser default' with: '1.3'; > project: 'CoolBrowser Tests' with: '1.3â]. > the thing is: you donât use configurations with iceberg projects, you use baselines. Esteban In this case 'CoolToolSet-Core-AlanJay.1' would be changed by 'CoolToolSet-Core-<git_hash>'? On Wed, Dec 20, 2017 at 6:09 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > In iceberg you can specify > - latest version when you do not specify anything > - a version (but it should be a git tag so you should save you code > with a tag - iceberg does not support it right now but you can do it > with git) > - the hash of your git commit. > > Does it answer your question? > Stef > > > On Wed, Dec 20, 2017 at 7:51 PM, Vitor Medina Cruz <vitormcruz(a)gmail.com> > wrote: > > Hello, > > > > How are packages versions computed in Iceberg? > > > > I am looking at the Metacello documentation at 'Deep in Pharo', it says I > > can define dependencies at package level and it uses the following > format to > > identify versions: <dev_name.versionNumber>; which I think is a pattern > used > > by Monticello, right? However, I can't figure what is the equivalent (if > > any) in Iceberg. > > > > Thanks in Advance, > > Vitor > > ---------- Forwarded message ---------- From: Janko Korelc <dazajn.korelc(a)gmail.com> To: pharo-users(a)lists.pharo.org Cc: Bcc: Date: Thu, 21 Dec 2017 13:50:11 +0100 Subject: [Pharo-users] Hi, do I nowadays need any Id and psw, to log in smalltalk hub and others? ... as connection time out... Best Regards! Janko Korelc ---------- Forwarded message ---------- From: Vitor Medina Cruz <vitormcruz(a)gmail.com> To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Cc: Bcc: Date: Thu, 21 Dec 2017 11:43:23 -0200 Subject: Re: [Pharo-users] Iceberg, Git and Package version > Package versions do not have any sense on iceberg, where what has sense is > the âprojectâ version. All packages point to a commit in repo. > Oh, I suspected that, but was unsure :) the thing is: you donât use configurations with iceberg projects, you use > baselines. > Now I got lost, I had understand that a ConfigurationOfXXX is my project definition and that Iceberg is just the Pharo VCS (in substitution of monticello). Iceberg is now my project? How do I configure my dependencies, groups and versions? The Metacello documentation in Deep in Pharo is deprecated for Iceberg? cheers, Vitor On Thu, Dec 21, 2017 at 9:02 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > On 21 Dec 2017, at 11:03, Vitor Medina Cruz <vitormcruz(a)gmail.com> wrote: > > Then in a Metacello configuration should I reference the hash git commit > or a tag in a version method? For example, an extract from Deep in Pharo: > > ConfigurationOfCoolToolSet>>version02: spec >> <version: '0.2' imports: #('0.2-baseline' )> >> spec for: #common do: [ >> spec blessing: #beta. >> spec >> package: 'CoolToolSet-Core' with: 'CoolToolSet-Core-AlanJay.1'; >> package: 'CoolToolSet-Tests' with: 'CoolToolSet-Tests-AlanJay.1'; >> project: 'CoolBrowser default' with: '1.3'; >> project: 'CoolBrowser Tests' with: '1.3â]. >> > > the thing is: you donât use configurations with iceberg projects, you use > baselines. > > Esteban > > > In this case 'CoolToolSet-Core-AlanJay.1' would be changed by > 'CoolToolSet-Core-<git_hash>'? > > On Wed, Dec 20, 2017 at 6:09 PM, Stephane Ducasse <stepharo.self(a)gmail.com > > wrote: > >> In iceberg you can specify >> - latest version when you do not specify anything >> - a version (but it should be a git tag so you should save you code >> with a tag - iceberg does not support it right now but you can do it >> with git) >> - the hash of your git commit. >> >> Does it answer your question? >> Stef >> >> >> On Wed, Dec 20, 2017 at 7:51 PM, Vitor Medina Cruz <vitormcruz(a)gmail.com> >> wrote: >> > Hello, >> > >> > How are packages versions computed in Iceberg? >> > >> > I am looking at the Metacello documentation at 'Deep in Pharo', it says >> I >> > can define dependencies at package level and it uses the following >> format to >> > identify versions: <dev_name.versionNumber>; which I think is a pattern >> used >> > by Monticello, right? However, I can't figure what is the equivalent (if >> > any) in Iceberg. >> > >> > Thanks in Advance, >> > Vitor >> >> > > _______________________________________________ Pharo-users mailing list Pharo-users(a)lists.pharo.org http://lists.pharo.org/mailman/listinfo/pharo-users_lists.pharo.org

1 0