Status of ScalesXml development

[Scott Calvert]

Long time listener; first time caller.

My team and I are working on what we expect to be a large commercial system for handling HTML email content parsed into XML and sliced/diced/turned into julienne fries using Scales. I can see two things from the project's history:

1) chris-twiner has done some fine work here.

2) ScalesXml is a hobby side project that doesn't get consistent attention.

We'll be working on ScalesXml to fix any problems that come up for us. Presently we're starting work on Scalaz 7.1 comparability. We're probably building most of our architecture off of scalaz-stream and need to be able to keep up with Scalaz versions. chris-twiner's repo contains some scalaz-7 work in a feature branch as does rickeyvisinski-kanban's fork. We'll be looking into the build/test failures on those branches and either completing this work or we'll start fresh with 0.5.0-M1.

If anybody has advice for us as to the state of these Scalaz v7 updates we're all ears.

It's a priority for my employer and my team to respect the work the community has done here and to contribute in the most constructive ways possible. Any input on how to best serve the project and coordinate with existing contributors (especially chris-twiner) is appreciated.

Scott Calvert

Tripit

Principle Software Engineer

[Chris Twiner]

Hi Scott / All,

I'd be very appreciative of help and contributions and I'm grateful for the compliments.  The 2.11 patch for example is one that should have been shipped a while ago.

It's not 100% accurate that it's a hobby project, it's also used within a number of day-job projects.  I mention a percentage as it very much appears like that right now :-(

Long story short, as I have mentioned this elsewhere, I have had laptop issues (I only have train journey time, 1h15m to do scales dev), and indeed must send it off for repair yet again (4th time now). Unfortunately I have also needed the time to catch up on work in the last 6m.

I will get a new build out soon with the 2.11 patches followed by another build with asnyc enumerators and scala 7. Where soon is unfortunately defined by weeks.

Directionally I want to move away from iteratees, perhaps trying streams.  The number of hoops that force you out of the iteratees model in order to control pulling or asynchronous behaviour are simply too high and become too difficult to reason about.

As such if you have any joy in providing pull processes/combinators that can be paused / restarted in streams then I'll be a very happy camper.

Let me know if it makes sense to look at making a group repo and opening up maven publishing.

Cheers,
Chris

--
You received this message because you are subscribed to the Google Groups "scales-xml" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scales-xml+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Ilya Korniyko]

Hi, Chris

Any updates on a new build with 2.11 support? 

Regards, 

Ilya

[Chris Twiner]

Hi Ilya,

Funnily enough I was just about to send an email 😃

I released 0.6.0 M2 yesterday, basically async enumerators, 0.5 with Scalaz 7 and a 2.11 build.

Please let me know (with issue in github) if anyone has issues with the build and I'll get a patch out soonest.

I've also described the next milestones in the github tracker. M3 I'll try to do by next week (IterV in its own project). M4 may take quite a bit longer (Scalaz streams).

Cheers
Chris

[Chris Twiner]

Hi all,

M3 has been pushed.

Basically just splitting out IterV usage into separate modules.

The readme on the release branch gives the details.

As usual let me know if there are any issues.

Cheers,
Chris