Re: [Pharo-users] Porting Transducers to Pharo

Hi esteban It was to manage namespace (from memory). Stef On Wed, Mar 21, 2018 at 2:29 PM, Esteban A. Maringolo wrote: > Hi Steffen, > > 2017-06-06 7:44 GMT-03:00 Steffen Märcker : >> I assumed so. I used file-outs only to get something working quickly. =)

Re: [Pharo-users] Porting Transducers to Pharo

I think I used FileOut30 and encodings were part of the adhoc fixing before loading into Pharo (using iconv certainly, but I don't recall) On 21 March 2018 at 14:29, Esteban A. Maringolo wrote: > Hi Steffen, > > 2017-06-06 7:44 GMT-03:00 Steffen Märcker : >

Re: [Pharo-users] Porting Transducers to Pharo

Hi Steffen, 2017-06-06 7:44 GMT-03:00 Steffen Märcker : > I assumed so. I used file-outs only to get something working quickly. =) > Properly published code will follow as soon as I am more familiar with code > management in Pharo. I'm coming back to this. What was the choosen

Re: [Pharo-users] Porting Transducers to Pharo

On 14 June 2017 at 17:21, Steffen Märcker wrote: > I played a bit with Iceberg in Pharo, managed to check out the repository, > and load Transducers-Core. As a bit of a surprise, multiple packages show > up in the SystemBrowser; one for each method category, e.g., >

Re: [Pharo-users] Porting Transducers to Pharo

Hi Phil, Tell me how it goes for you. I played a bit with Iceberg in Pharo, managed to check out the repository, and load Transducers-Core. As a bit of a surprise, multiple packages show up in the SystemBrowser; one for each method category, e.g., Transducers-accessing and

Re: [Pharo-users] Porting Transducers to Pharo

2017-06-08 15:37 GMT+02:00 Steffen Märcker : > In fact, I moved from Mocketry to DoubleAgents quite some time ago... =) It was greatly updated from VW version. (look for details here http://dionisiydk.blogspot.fr/2016/04/new-version-of-mocketry-30.html)

Re: [Pharo-users] Porting Transducers to Pharo

In fact, I moved from Mocketry to DoubleAgents quite some time ago... =) Am .06.2017, 23:04 Uhr, schrieb Denis Kudriashov : 2017-06-07 22:04 GMT+02:00 p...@highoctane.be : I read your note about DoubleAgents for the tests, well, yeah this one we do

Re: [Pharo-users] Porting Transducers to Pharo

Hi Phil, thanks a lot for your effort and valuable input. I am having a look at STIG for VW in the hope that I can set up a common repository for the VW and Pharo version. Though, the next days I won't work on the port, because I am quite busy at the moment. Tell me how it goes for you.

Re: [Pharo-users] Porting Transducers to Pharo

2017-06-07 22:04 GMT+02:00 p...@highoctane.be : > I read your note about DoubleAgents for the tests, well, yeah this one we > do not have. I read about it on the blog of its maker and it looked decent > indeed. > I think Mocketry can easily replace DoubleAgents but API is

Re: [Pharo-users] Porting Transducers to Pharo

Use Iceberg with Pharo6.0 There are techtalks videos about it. https://www.youtube.com/watch?v=AuZAFfWS34w=29s Phil On Wed, Jun 7, 2017 at 11:29 AM, Steffen Märcker wrote: > Hi Phil, > > that's great. I do have a GitHub account (merkste) but none at > SmalltalkHub. Is there

Re: [Pharo-users] Porting Transducers to Pharo

I wouldn't bother with SmalltalkHub at this point. Check Iceberg, it's the future: https://github.com/pharo-vcs/iceberg/ On 7 June 2017 at 11:29, Steffen Märcker wrote: > Hi Phil, > > that's great. I do have a GitHub account (merkste) but none at > SmalltalkHub. Is there a

Re: [Pharo-users] Porting Transducers to Pharo

Hi Phil, that's great. I do have a GitHub account (merkste) but none at SmalltalkHub. Is there a recommendable doc on how to use Git from Pharo? Best, Steffen Am .06.2017, 14:09 Uhr, schrieb p...@highoctane.be : Hi Steffen, I am willing to help you create the

Re: [Pharo-users] Porting Transducers to Pharo

Check https://medium.com/@i.oleks/interface-for-selecting-data-from-a-dataset-d7c6b5fb378f https://medium.com/@i.oleks/an-example-of-test-driven-development-c9ce033f05ef Loading a dataframe from a dataset and then using transducers for a transformation pipeline would be great. DataFrame is

Re: [Pharo-users] Porting Transducers to Pharo

Hi Steffen, I am willing to help you create the package in SmalltalkHub or Github based on your files/changeset. Do you have a github and/or SmalltalkHub account? Best, Phil On Tue, Jun 6, 2017 at 1:08 PM, Steffen Märcker wrote: > Hi! > > If the need arises, we could of

Re: [Pharo-users] Porting Transducers to Pharo - Name Clash

Hi, I found some name clash with the message #reduce: in Pharo. It is already declared in SequencableCollection. Additionally, Collection>>fold: just calls #reduce:, which makes the difference between folding and reducing a bit unclear. How should I handle this situation? I see the

Re: [Pharo-users] Porting Transducers to Pharo

Hi Phil, Coupling this with Olek's work on the DataFrame could really come handy. I am new to this list. Could you please elaborate? Cheers! Steffen On Mon, Jun 5, 2017 at 9:14 AM, Stephane Ducasse wrote: Hi Steffen > The short answer is that the compact

Re: [Pharo-users] Porting Transducers to Pharo

Hi! If the need arises, we could of course factor the compact notation out into a separate package. Good idea [...] I do not want to help promoting a syntax that alienates me (and others because other people reported the saem to me). I understand. Btw, I'd really, really appreciate if

Re: [Pharo-users] Porting Transducers to Pharo

I assumed so. I used file-outs only to get something working quickly. =) Properly published code will follow as soon as I am more familiar with code management in Pharo. Am .06.2017, 09:05 Uhr, schrieb Stephane Ducasse : We do not work with fileouts :) You should

Re: [Pharo-users] Porting Transducers to Pharo

Coupling this with Olek's work on the DataFrame could really come handy. Phil On Mon, Jun 5, 2017 at 9:14 AM, Stephane Ducasse wrote: > Hi Steffen > > > > The short answer is that the compact notation turned out to work much > better > > for me in my code, especially,

Re: [Pharo-users] Porting Transducers to Pharo

Hi Steffen > The short answer is that the compact notation turned out to work much better > for me in my code, especially, if multiple transducers are involved. But > that's my personal taste. You can choose which suits you better. In fact, > > 1000 take. > > just sits on top and simply calls

Re: [Pharo-users] Porting Transducers to Pharo

About NG this is strange but may be we were working on an old VW version. - I can help producing a nice document :) >> > > Do you mean like the booklets published over the last weeks? This would be > great. > yes now I do not want to help promoting a syntax that alienates me (and others because

Re: [Pharo-users] Porting Transducers to Pharo

We do not work with fileouts :) You should produce packages with also a configuration and published them on smalltalkhub or git and in the MetaRepository. You can also add package comments On Sat, Jun 3, 2017 at 10:29 PM, Steffen Märcker wrote: > Dear all, > > attached are

Re: [Pharo-users] Porting Transducers to Pharo

Hi Stephane & Damien! The short answer is that the compact notation turned out to work much better for me in my code, especially, if multiple transducers are involved. But that's my personal taste. You can choose which suits you better. In fact, 1000 take. just sits on top and simply

Re: [Pharo-users] Porting Transducers to Pharo

Hi Stephane! This is a great news. We need cool frameworks. I am really curious how well it will work for others. =) - There is a package on cincom store to support the migration from VW to Pharo. FileOuter something. The name escapes my mind now. We updated it last year to help porting one

Re: [Pharo-users] Porting Transducers to Pharo

If I recall correctly, there is an alternate protocol that looks more like xtreams or the traditional select/collect iterations. On 2 June 2017 at 21:12, Stephane Ducasse wrote: > I have a design question > > why the library is implemented in functional style vs

Re: [Pharo-users] Porting Transducers to Pharo

I have a design question why the library is implemented in functional style vs messages? I do not see why this is needed. To my eyes the compact notation goes against readibility of code and it feels ad-hoc in Smalltalk. I really prefer square := Map function: #squared. take := Take number:

Re: [Pharo-users] Porting Transducers to Pharo

Hi steffen This is a great news. We need cool frameworks. - There is a package on cincom store to support the migration from VW to Pharo. FileOuter something. The name escapes my mind now. We updated it last year to help porting one application to Pharo. - I can help producing a nice document :)

Re: [Pharo-users] Porting Transducers to Pharo

To get the extension methods into the Transducers package, the following worked for me - edit the category to have the prefix '*Transducers-' 2710c2710 < !Number methodsFor: 'transforming' stamp: ' 2/6/17 15:38'! --- > !Number methodsFor: '*Transducers-transforming' stamp: ' 2/6/17 15:38'!

Re: [Pharo-users] Porting Transducers to Pharo

Dear all, thanks for the many suggestions. I didn't had time to test all import/export ways yet. But for now, I can report on two: 1) NGFileOuter Unfortunately It raised several MNUs in my image. I'll investigate them later. 2) FileOut30 (VW Contributed) I was able to file out the code

Re: [Pharo-users] Porting Transducers to Pharo

There is a package for that NGFileOuter or something like that on cincom store. We used it for mobydic code. On Wed, May 31, 2017 at 6:35 PM, Alexandre Bergel wrote: > If I remember correctly, there is a parcel in VisualWorks to export a file > out (Squeak format). > >

Re: [Pharo-users] Porting Transducers to Pharo

You can also give a try to use SIF (Smalltalk Interchange Format) https://github.com/peteruhnak/sif There is parcel file in VW subfolder, and docs here: https://github.com/peteruhnak/sif/blob/master/docs.md I've used it about year ago for some small code exchanges; but of course you will have

Re: [Pharo-users] Porting Transducers to Pharo

If I remember correctly, there is a parcel in VisualWorks to export a file out (Squeak format). @Milton, can you give a hand to Steffen? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >

Re: [Pharo-users] Porting Transducers to Pharo

I got stumped / life moved on… >From the top of my head, my port was working for the most part (the tests rely on a mocking library that should be ported as well; translating to either BabyMock2 or Mocketry seems possible on the surface but there is some impedance mismatch there between the

Re: [Pharo-users] Porting Transducers to Pharo

FileTree is the Pharo implementation of the Cypress format for packages, STIG is the implementation of Cypress for VW. The latest changes are available in , but it doesn't work out of the box. I'm interested in having a way to share code back and forth

Re: [Pharo-users] Porting Transducers to Pharo

Thanks for the encouraging response! First question: Which is the recommended (friction free) way to exchange code between VW and Pharo? Cheers! Steffen Am .05.2017, 16:22 Uhr, schrieb Alexandre Bergel : I second Sven. This is very exciting! Let us know when you

Re: [Pharo-users] Porting Transducers to Pharo

Hello Damien, I remember very well. How far did you get? Did you kick of a discussion on one of the Pharo lists? And did FileTree become a convenient way to exchange code between VW and Pharo? Best, Steffen Am .05.2017, 16:16 Uhr, schrieb Damien Pollet :

Re: [Pharo-users] Porting Transducers to Pharo

I second Sven. This is very exciting! Let us know when you have something ready to be tested. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On May 31, 2017, at 9:00 AM, Sven Van

Re: [Pharo-users] Porting Transducers to Pharo

As you know I experimented with that a while ago. My code is at http://smalltalkhub.com/#!/~cdlm/Experiments/source On 31 May 2017 at 15:00, Sven Van Caekenberghe wrote: > > > On 31 May 2017, at 14:23, Steffen Märcker wrote: > > > > Hi, > > > > I am the developer

Re: [Pharo-users] Porting Transducers to Pharo

> On 31 May 2017, at 14:23, Steffen Märcker wrote: > > Hi, > > I am the developer of the library 'Transducers' for VisualWorks. It was > formerly known as 'Reducers', but this name was a poor choice. I'd like to > port it to Pharo, if there is any interest on your side. I