- Pharo-users - lists.pharo.org

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

by Marcus Denker

> > > 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 ? > The problem is that for now we are running on Inria servers where logins are restrictedâ¦ for sure we will at some point move somewhere else. If that happens, we will make a call for help for sys admin related tasks. Marcus

Sept. 13, 2017

Re: [Pharo-users] DataFrame inspector issues

by Norbert Hartl

+1 Norbert > Am 13.09.2017 um 09:54 schrieb Stephane Ducasse <stepharo.self(a)gmail.com>: > > sure no stress. When it will be with a too large volume we will complain. > Ideally I would like DataFrame not to be part of PolyMath but of Containers > and that PolyMath uses Containers. > What is Containers: a Collection of datastructure that is managed in a > modular fashion. > I would like to remove from the image all the datastructure that are not used > and migrate them to Containers + tests + coverage + consistent documentation. > So that we can cherry pick the one we need. > > http://smalltalkhub.com/#!/~StephaneDucasse/Containers/source > > Stef > > > > Stef > >> On Tue, Sep 12, 2017 at 11:39 AM, Alistair Grant <akgrant0710(a)gmail.com> wrote: >>> On Tue, Sep 12, 2017 at 09:28:13AM +0200, Serge Stinckwich wrote: >>> >>> On Tue, Sep 12, 2017 at 9:22 AM, Alistair Grant <akgrant0710(a)gmail.com> wrote: >>> >>> Hi Everyone, >>> >>> ?Hi Alistair, >>> >>> I've started using DataFrame, it's great to have this functionality >>> easily available, and noticed a few issues with the inspector: >>> >>> 1. The inspector always shows row numbers and not the supplied name. >>> >>> 2. The last column label isn't displayed. >>> >>> >>> Where should I report issues? >>> https://github.com/PolyMathOrg/DataFrame/issues >>> >>> >>> >>> ?Thank you for your report.? >>> >>> ?At the moment, you can report issues here. I guess later, we will intregrate >>> DataFrame in the main PolyMath repository. >>> ? >>> >>> I have a patch that addresses the first issue, although I'm not >>> completely happy with it, and I'll take a look at the second issue. >>> >>> >>> ?This is maybe better to discuss about DataFrame? and other PolyMath issues >>> on the polymath mailing-list: https://groups.google.com/forum/#!forum/scismalltalk >>> >>> ?See you there !? >> >> Hi Serge, >> >> Thanks, I've joined the group and reposted the message there. >> >> I wrote: >>> If I remember correctly, there has been some discussion about making the >>> column widths draggable in the inspector. I would prefer to have a >>> context menu that is "size to fit". This could be potentially expensive >>> to calculate, so it would be user-initiated. >> >> I think this is more of a FastTable / GT issue than DataFrame, so maybe >> the discussion should stay here? (if anyone is interested :-)). >> >> Thanks, >> Alistair >>

Sept. 13, 2017

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

by Esteban Lorenzano

fixed. added also an autorestart job (checking every hour) Esteban > On 13 Sep 2017, at 09:22, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > 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

Re: [Pharo-users] DictionaryValueHolder question

by Peter UhnÃ¡k

On Wed, Sep 13, 2017 at 9:45 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > incomplete > I would use Announcement. > ValueAdded/ValueChanged/ValueRemoved are all announcements. P

Sept. 13, 2017

Re: [Pharo-users] DataFrame inspector issues

by Stephane Ducasse

sure no stress. When it will be with a too large volume we will complain. Ideally I would like DataFrame not to be part of PolyMath but of Containers and that PolyMath uses Containers. What is Containers: a Collection of datastructure that is managed in a modular fashion. I would like to remove from the image all the datastructure that are not used and migrate them to Containers + tests + coverage + consistent documentation. So that we can cherry pick the one we need. http://smalltalkhub.com/#!/~StephaneDucasse/Containers/source Stef Stef On Tue, Sep 12, 2017 at 11:39 AM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > On Tue, Sep 12, 2017 at 09:28:13AM +0200, Serge Stinckwich wrote: >> >> On Tue, Sep 12, 2017 at 9:22 AM, Alistair Grant <akgrant0710(a)gmail.com> wrote: >> >> Hi Everyone, >> >> ?Hi Alistair, >> >> I've started using DataFrame, it's great to have this functionality >> easily available, and noticed a few issues with the inspector: >> >> 1. The inspector always shows row numbers and not the supplied name. >> >> 2. The last column label isn't displayed. >> >> >> Where should I report issues? >> https://github.com/PolyMathOrg/DataFrame/issues >> >> >> >> ?Thank you for your report.? >> >> ?At the moment, you can report issues here. I guess later, we will intregrate >> DataFrame in the main PolyMath repository. >> ? >> >> I have a patch that addresses the first issue, although I'm not >> completely happy with it, and I'll take a look at the second issue. >> >> >> ?This is maybe better to discuss about DataFrame? and other PolyMath issues >> on the polymath mailing-list: https://groups.google.com/forum/#!forum/scismalltalk >> >> ?See you there !? > > Hi Serge, > > Thanks, I've joined the group and reposted the message there. > > I wrote: >> If I remember correctly, there has been some discussion about making the >> column widths draggable in the inspector. I would prefer to have a >> context menu that is "size to fit". This could be potentially expensive >> to calculate, so it would be user-initiated. > > I think this is more of a FastTable / GT issue than DataFrame, so maybe > the discussion should stay here? (if anyone is interested :-)). > > Thanks, > Alistair >

Sept. 13, 2017

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