- Pharo-users - lists.pharo.org

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

Re: [Pharo-users] DictionaryValueHolder question

by Peter UhnÃ¡k

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

Re: [Pharo-users] About neoCSV

by Sven Van Caekenberghe

I guess #namedColumnsConfiguration is relatively recent [oct 2015] (although it is just a convenience method, the underlying technology was already there), so it is probably not part of the external docs. > > On 12 Sep 2017, at 15:26, 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. 12, 2017

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

by Ben Coman

On Tue, Sep 12, 2017 at 5:38 PM, Christian Haider < christian.haider(a)smalltalked-visuals.com> wrote: > Moin, > > > > the port is almost done. Then I will add documentation and publish the > code under MIT licence. > > > > Including the code used to port the library from VW to Gemstone using a > novel approach. > > > > The heard of the âPDF engineâ is the type system which allows the > assignment of Smalltalk classes to raw PDF objects. > > In the new version, the PDF types are decoupled from the Smalltalk > classes, so that classes can be renamed freely (i.e. adding prefixes). > Thats great news Christian. Pharo's lack of namespaces and your desire to avoid prefixing classes made me wonder how to keep VW and Pharo ports synchronised - which added friction to my minor attempt to port it to Pharo. > > > I think that porting the new version to Pharo (and VA and â¦) has gotten > much easier. > > I hope that someone would take the challenge J. > I'm busy with other things for a while, but I'll add it back on my list of things to look at. cheers -ben > > > Cheers, > > Christian > > > > > > *Von:* Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] *Im > Auftrag von *Denis Kudriashov > *Gesendet:* Dienstag, 12. September 2017 11:12 > *An:* Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > *Betreff:* Re: [Pharo-users] Who is maintaining of Artefact? > > > > Look at slides PDFtalk for Gemstone > <https://www.slideshare.net/esug/pdftalk-for-gemstone> from last ESUG > about porting it to Gemstone (which is done). > > Maybe it is similar as porting GLORP into Pharo. Somebody can comment on > this process. > > > > 2017-09-12 11:04 GMT+02:00 H. Hirzel <hannes.hirzel(a)gmail.com>: > > Looks like a worthwhile exercise > > PDFTalk https://wiki.pdftalk.de/doku.php > > "The syntax is covered comprehensively, which means that any PDF file > can be read and any PDF object can be written in a conforming way. > > Typical PDF objects are dictionaries of which many are specialized as > Smalltalk objects. > > The library code is annotated with the original descriptions and > definitions from the specification, so that learning about PDF itself > is well supported. " > > I wonder what the main issues would be when porting this to Pharo. > > --Hannes > > > On 9/12/17, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > There is also PDFTalk from Christian Haider > > https://wiki.pdftalk.de/doku.php. > > But it needs to be ported into Pharo. > > > > 2017-09-11 21:03 GMT+02:00 Alejandro Infante > > <alejandroinfante91(a)gmail.com>: > > > >> Hi! > >> I would like to explore having support for Unicode characters. I want to > >> help for it. > >> > >> Who is the right person to talk about it? > >> > >> Cheers! > >> Alejandro > >> > > > > >

Sept. 12, 2017

Re: [Pharo-users] About neoCSV

by Stephane Ducasse

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. 12, 2017

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

by Stephane Ducasse

super! Stef On Tue, Sep 12, 2017 at 11:38 AM, Christian Haider <christian.haider(a)smalltalked-visuals.com> wrote: > Moin, > > > > the port is almost done. Then I will add documentation and publish the code > under MIT licence. > > > > Including the code used to port the library from VW to Gemstone using a > novel approach. > > > > The heard of the âPDF engineâ is the type system which allows the assignment > of Smalltalk classes to raw PDF objects. > > In the new version, the PDF types are decoupled from the Smalltalk classes, > so that classes can be renamed freely (i.e. adding prefixes). > > > > I think that porting the new version to Pharo (and VA and â¦) has gotten much > easier. > > I hope that someone would take the challenge J. > > > > Cheers, > > Christian > > > > > > Von: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] Im Auftrag von > Denis Kudriashov > Gesendet: Dienstag, 12. September 2017 11:12 > An: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Betreff: Re: [Pharo-users] Who is maintaining of Artefact? > > > > Look at slides PDFtalk for Gemstone from last ESUG about porting it to > Gemstone (which is done). > > Maybe it is similar as porting GLORP into Pharo. Somebody can comment on > this process. > > > > 2017-09-12 11:04 GMT+02:00 H. Hirzel <hannes.hirzel(a)gmail.com>: > > Looks like a worthwhile exercise > > PDFTalk https://wiki.pdftalk.de/doku.php > > "The syntax is covered comprehensively, which means that any PDF file > can be read and any PDF object can be written in a conforming way. > > Typical PDF objects are dictionaries of which many are specialized as > Smalltalk objects. > > The library code is annotated with the original descriptions and > definitions from the specification, so that learning about PDF itself > is well supported. " > > I wonder what the main issues would be when porting this to Pharo. > > --Hannes > > > On 9/12/17, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: >> There is also PDFTalk from Christian Haider >> https://wiki.pdftalk.de/doku.php. >> But it needs to be ported into Pharo. >> >> 2017-09-11 21:03 GMT+02:00 Alejandro Infante >> <alejandroinfante91(a)gmail.com>: >> >>> Hi! >>> I would like to explore having support for Unicode characters. I want to >>> help for it. >>> >>> Who is the right person to talk about it? >>> >>> Cheers! >>> Alejandro >>> >> > >

Sept. 12, 2017