September 2017 - Pharo-users

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

Re: [Pharo-users] help needed regarding conversion of hex to binary

by Sven Van Caekenberghe

ByteArray readHexFrom: #[ 0 1 2 3 4 5 6 7 8 9 10 ] hex. > On 12 Sep 2017, at 14:47, Ben Coman <btc(a)openinworld.com> wrote: > > > > On Tue, Sep 12, 2017 at 2:55 AM, Casimiro de Almeida Barreto <casimiro.barreto(a)gmail.com> wrote: > Is there a (easy and ready) way to convert hexa to binary. I mean, convert data that was transformed > > x := myData asByteArray hex. > > back to binary? > > > > I thought I'd try what usually works... World > Tools > Finder > Examples > First to test what we know... > #(9 10 11 12) asByteArray . '090a0b0c' > results in #hex > > but the reverse... > '090a0b0c' . #(9 10 11 12) asByteArray . > doesn't show any result, > so perhaps there is no easy way. > > But this might give you a starting point... > hexString := #(9 10 11 12) asByteArray hex. > (NumberParser on: '16r', hexString) nextInteger asByteArray " ==> #[9 10 11 12]" > > cheers -ben

Sept. 12, 2017

Re: [Pharo-users] help needed regarding conversion of hex to binary

by Ben Coman

On Tue, Sep 12, 2017 at 2:55 AM, Casimiro de Almeida Barreto < casimiro.barreto(a)gmail.com> wrote: > Is there a (easy and ready) way to convert hexa to binary. I mean, convert > data that was transformed > > x := myData asByteArray hex. > > back to binary? > > > I thought I'd try what usually works... World > Tools > Finder > Examples First to test what we know... #(9 10 11 12) asByteArray . '090a0b0c' results in #hex but the reverse... '090a0b0c' . #(9 10 11 12) asByteArray . doesn't show any result, so perhaps there is no easy way. But this might give you a starting point... hexString := #(9 10 11 12) asByteArray hex. (NumberParser on: '16r', hexString) nextInteger asByteArray " ==> #[9 10 11 12]" cheers -ben

Sept. 12, 2017

Re: [Pharo-users] Accessor Creation in Nautilus Browser

by Rob Rothwell

On Tue, Sep 12, 2017 at 5:45 AM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > Hi Rob, > > On 12 September 2017 at 03:32, Rob Rothwell <r.j.rothwell(a)gmail.com> > wrote: > > Hello, > > > > Is there a way to create accessors for more than one instance variable > at a > > time with the Nautilus browser? > > > > "Class -> Refactoring -> Inst Var Refactoring -> Accessors" shows > available > > instance variables, but only one can be selected... > > > > Thank you, > > > > Rob > > Class -> Refactoring -> Class Refactoring -> Generate Accessors > > Ha! Thank you...my brain kept seeing "Class" and saying, "But I'm not ON the Class side!" Thanks again, Cheers, > Alistair > >

Sept. 12, 2017

Re: [Pharo-users] Pharo 6.1 debugger - suggestions break once, does funny things?

by Marcus Denker

> On 12 Sep 2017, at 12:44, Tim Mackinnon <tim(a)testit.works> wrote: > > That makes sense - but in a practical usability sense its broken - it doesnât give me a useful breakpoint to step through code where I expect. Should I raise a Fogbugz for this? > Yes, please add an issue. I wanted to see if I can improve the debugger for thisâ¦ Marcus

Sept. 12, 2017

Re: [Pharo-users] Pharo 6.1 debugger - suggestions break once, does funny things?

by Tim Mackinnon

That makes sense - but in a practical usability sense its broken - it doesnât give me a useful breakpoint to step through code where I expect. Should I raise a Fogbugz for this? Or should we just remove this feature if we canât do it right? Tim > On 12 Sep 2017, at 11:09, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > > 2017-09-11 1:26 GMT+02:00 Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>>: > While Iâm on a debugger tripâ¦ anyone else also notice that the Suggestions, Break once debug option acts weirdly? I seem to get a debugger but it halts several lines after where I have said, and if I start stepping the debugger seems to jump to funny places and show values that donât line up with what I know is happening? If I use Suggestions, Break it seems to work correctly (apart from the Step Through I mentioned in another thread). > > Tim > > > Thats because the "Break once" creates a MetaLink that when executing this Metalink it removes itself from the methode prior to the break-command. If now the debugger opens the method, it executes a context to a method that already had changed. (the actual method bytecode only exists in the current context). > > You can see the "real" bytecode of the contexts method if you select GTs bytecode view. >

Sept. 12, 2017