September 2017 - Pharo-users

Re: [Pharo-users] About neoCSV

by Stephane Ducasse

I'm adding it to the doc On Tue, Sep 12, 2017 at 3:26 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Yes. > I read all the doc and is it there? > Because yes this is exactly what I was looking for. > > On Tue, Sep 12, 2017 at 9:14 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> I am not sure I understand 100% what you want, but consider this example: >> >> (NeoCSVReader on: 'foo bar baz >> 1 2 3 >> 11 22 33' readStream) >> separator: $ ; >> namedColumnsConfiguration; >> upToEnd. >> >> => an Array(a Dictionary(#bar->'2' #baz->'3' #foo->'1' ) a Dictionary(#bar->'22' #baz->'33' #foo->'11' )) >> >> Since you did not use $, but space I had to set that using #separator: >> >> #namedColumnsConfiguration uses the header as keys and reads dictionaries instead of arrays. >> >> Instead of #upToEnd you can also iterate with #do: >> >> Is this what you are looking for ? >> >>> On 12 Sep 2017, at 08:23, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >>> >>> Hi sven >>> >>> I have a question with NeoCVS >>> Do you offer the possibility to manage the data of one line based on >>> the description given by the first line >>> >>> Ex >>> >>> foo bar baz >>> 1 2 3 >>> 11 22 33 >>> >>> => >>> >>> res doWith: [:tag :data | >>> Transcript show: tag ; space ; show: data printString ;cr >>> ] >>> >>> foo 1 bar 2 baz 3 >>> foo 11 bar 22 baz 33 >>> >>> Stef >>> >> >>

Sept. 13, 2017

Re: [Pharo-users] DictionaryValueHolder question

by Stephane Ducasse

incomplete I would use Announcement. On Tue, Sep 12, 2017 at 3:46 AM, Rob Rothwell <r.j.rothwell(a)gmail.com> wrote: > Hello, > > Unlike the CollectionValueHolder, the DictionaryValueHolder only notifies > you that something has changed, rather than tell you what item has been > added or removed. Does anyone know if this is by design, or just > incomplete? > > If incomplete, what do you think about using the > ValueAdded/ValueChanged/ValueRemoved announcements and passing the > association in newValue/oldValue? > > Thank you, > > Rob > >

Sept. 13, 2017

Re: [Pharo-users] Gofer loads wrong version?

by Guillermo Polito

On Mon, Sep 4, 2017 at 1:01 PM, Herby VojÄÃk <herby(a)mailbox.sk> wrote: > Hello! > > As I need to load specific version of Glorp with my fix, and I did not > find out how to force-override it in my baseline, I tried to load it > post-the-baseline via Gofer: > > (Gofer new smalltalkhubUser: 'DBXTalk' project: 'Glorp') > package: 'Glorp'; > version: 'Glorp-HerbyVojcik.127'; > load. > > But it actually looks like this: [see attached bogusgofer.png]. > > OTOH, after the image loads the tests pass and monticello browser looks > like this: [see attached mbloaded127.png]. > > Am I doing something wrong? I am a bit afraid what is actually loaded / if > it won't break b/c of inconsistent state. >From my understanding, loading was right: - underlined in monticello means loaded - bold means not loaded - normal (not bold nor underlined) means ancestor of loaded version So I'd say you have effectively loaded Glorp-HerbyVojcik.127 in your system. Now, why in the progress bar somebody is loading the version 129? I'm not sure, maybe that's the metacello configuration? Or monticello needs that to calculate something with ancestors? Dunno... > > > Herby > -- Guille Polito Research Engineer 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. 13, 2017

Re: [Pharo-users] Who is maintaining of Artefact?

by Stephane Ducasse

Christian I'm interested by the transformation code since last year we did a migration and made sure that we can migrate again the code of Mobydic an open-source simulation system. The logic of our approach is in store NGFileouter or something like that. On Wed, Sep 13, 2017 at 7:58 AM, Christian Haider <christian.haider(a)smalltalked-visuals.com> wrote: >> von Stephan Eggermont >> >> On 12-09-17 11:11, Denis Kudriashov wrote: >> > Maybe it is similar as porting GLORP into Pharo. Somebody can comment >> on this process. >> >> The important point is that the original code is in another dialect, and the idea >> is not to fork, as the original maintainer develops it further. >> That means that it is not a one-time translation, but is a set of transformation >> rules and platform specific packages that is applied every time something >> changes on either side. > > Stefan, you are good :-)! > > Exactly! The full code transformation from VW to GS is described as a value, which gets interpreted by a generic code fileout machine. > A new version of the GS fileout can be generated at any time without human intervention. > A SystemChange (the name of the value class) could be interpreted in different ways. > > Currently, the transform is one way from VW to GS. > > I am very interested in changes people may do to the library, but for now, I will keep the master in VW and integrate contributions by hand. > I am sure that, if the need arises, there will be a way to deal with a two-way synchronization. But let's have a contribution first :-) > > Christian > >

Sept. 13, 2017

Re: [Pharo-users] catalog.pharo.org - 503 service is temporarily unavailable

by Stephane Ducasse

Thanks a lot daniel for the report. On Wed, Sep 13, 2017 at 9:09 AM, Daniel BLANC <daniel.blanc(a)gmail.com> wrote: > Hi All, > > I don't know if you're aware of this but http://catalog.pharo.org/ returns > a 503 service is temporarily unavailable. > > BTW, If you need help for system administration, I'm willing to help and I > can dedicate some time to it. Is there someone I can talk to about this ? > > Thanks, > Daniel

Sept. 13, 2017

catalog.pharo.org - 503 service is temporarily unavailable

by Daniel BLANC

Hi All, I don't know if you're aware of this but http://catalog.pharo.org/ returns a 503 service is temporarily unavailable. BTW, If you need help for system administration, I'm willing to help and I can dedicate some time to it. Is there someone I can talk to about this ? Thanks, Daniel

Sept. 13, 2017

Re: [Pharo-users] Who is maintaining of Artefact?

by Christian Haider

> von Stephan Eggermont > > On 12-09-17 11:11, Denis Kudriashov wrote: > > Maybe it is similar as porting GLORP into Pharo. Somebody can comment > on this process. > > The important point is that the original code is in another dialect, and the idea > is not to fork, as the original maintainer develops it further. > That means that it is not a one-time translation, but is a set of transformation > rules and platform specific packages that is applied every time something > changes on either side. Stefan, you are good :-)! Exactly! The full code transformation from VW to GS is described as a value, which gets interpreted by a generic code fileout machine. A new version of the GS fileout can be generated at any time without human intervention. A SystemChange (the name of the value class) could be interpreted in different ways. Currently, the transform is one way from VW to GS. I am very interested in changes people may do to the library, but for now, I will keep the master in VW and integrate contributions by hand. I am sure that, if the need arises, there will be a way to deal with a two-way synchronization. But let's have a contribution first :-) Christian

Sept. 13, 2017

Re: [Pharo-users] Who is maintaining of Artefact?

by Stephan Eggermont

On 12-09-17 11:11, Denis Kudriashov wrote: > Maybe it is similar as porting GLORP into Pharo. Somebody can comment on this process. The important point is that the original code is in another dialect, and the idea is not to fork, as the original maintainer develops it further. That means that it is not a one-time translation, but is a set of transformation rules and platform specific packages that is applied every time something changes on either side. Stephan

Sept. 12, 2017

Re: [Pharo-users] Gofer loads wrong version?

by Herby VojÄÃk

Bump. Can you pls help me with how to load proper version / finding what is wrong here? As shown in replies, it loads two versions (eg. it seems it loads everything it finds in the repo). Herby Herby VojÄÃk wrote: > Hello! > > As I need to load specific version of Glorp with my fix, and I did not > find out how to force-override it in my baseline, I tried to load it > post-the-baseline via Gofer: > > (Gofer new smalltalkhubUser: 'DBXTalk' project: 'Glorp') > package: 'Glorp'; > version: 'Glorp-HerbyVojcik.127'; > load. > > But it actually looks like this: [see attached bogusgofer.png]. > > OTOH, after the image loads the tests pass and monticello browser looks > like this: [see attached mbloaded127.png]. > > Am I doing something wrong? I am a bit afraid what is actually loaded / > if it won't break b/c of inconsistent state. > > Herby

Sept. 12, 2017

Re: [Pharo-users] DictionaryValueHolder question

by Rob Rothwell

Hi Peter, Thank you very much for the clarification; I'll see what I can come up with! Take care, Rob On Tue, Sep 12, 2017 at 11:18 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > Hi Rob, > > this is by omission. Originally CollectionValueHolder didn't have it > either until I've introduced ValueAdded/ValueRemoved. So feel free to > incorporate it in a meaningful fashion to a DictionaryHolder. > > Peter > > On Tue, Sep 12, 2017 at 3:46 AM, Rob Rothwell <r.j.rothwell(a)gmail.com> > wrote: > >> Hello, >> >> Unlike the CollectionValueHolder, the DictionaryValueHolder only notifies >> you that something has changed, rather than tell you what item has been >> added or removed. Does anyone know if this is by design, or just >> incomplete? >> >> If incomplete, what do you think about using the >> ValueAdded/ValueChanged/ValueRemoved announcements and passing the >> association in newValue/oldValue? >> >> Thank you, >> >> Rob >> >> >> >

Sept. 12, 2017