Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Sep 19 2018 20:33
    tindzk commented #71
  • Sep 19 2018 20:33
    tindzk closed #71
  • Sep 19 2018 20:33

    tindzk on master

    Update SBT, Scala and dependenc… Merge pull request #71 from nig… (compare)

  • Sep 19 2018 07:35
    nightscape commented #71
  • Sep 19 2018 07:19
    nightscape synchronize #71
  • Sep 08 2018 11:04
    tindzk commented #71
  • Aug 13 2018 22:20
    nightscape opened #71
  • Jun 02 2017 06:31
    zoosky opened #70
  • Sep 16 2016 07:39
    mkotsbak opened #69
  • Sep 06 2016 20:39
    darkfrog26 commented #67
  • Sep 06 2016 20:16

    tindzk on ValidateCyclicalOptional

    (compare)

  • Sep 06 2016 20:15

    tindzk on master

    Added Channel.ValidateCyclical … Merge pull request #67 from Met… (compare)

  • Sep 06 2016 20:15
    tindzk closed #67
  • Sep 06 2016 20:15
    tindzk commented #67
  • Sep 05 2016 13:16
    darkfrog26 commented #67
  • Aug 07 2016 18:32
    fkz commented #64
  • Aug 07 2016 18:32
    fkz commented #64
  • Aug 07 2016 18:24
    fkz commented #62
  • Aug 07 2016 18:23
    fkz commented #62
  • Aug 07 2016 18:01
    fkz commented #62
Tim Nieradzik
@tindzk
Sorry, it's not available in the MetaRx version used by Widok
It was only added recently
Matthew Pocock
@drdozer
Getting this warning in a for comprehension
`withFilter' method does not yet exist on pl.metastack.metarx.ReadChannel[Boolean], using `filter' method instead
[warn]     parsed <- parseStatus if parsed
Tim Nieradzik
@tindzk
Ok, I never used for-comprehension with MetaRx. Looks like we have to define withFilter.
Matthew Pocock
@drdozer
I think it works without, but withFilter is meant to be a lower-overhead version that can avoid making a full instantiation of the monad
Tim Nieradzik
@tindzk
@drdozer I released v0.1.7 with support for withFilter
Matthew Pocock
@drdozer
@tindzk thanks - I'll give it a spin after lunch
can I drop 0.1.7 into widok by providing the updated dependency in my build.sbt, or do I need to wait for a widok update?
Tim Nieradzik
@tindzk
We will need to update the dependency in Widok's build file. I can do it later.
Marius B. Kotsbak
@mkotsbak
Nice. Maybe it is possible to start making 2.12.x builds too, if all deps are available?
Tim Nieradzik
@tindzk
I wanted to do it already, but unfortunately uPickle doesn't compile for 2.12 yet.
Marius B. Kotsbak
@mkotsbak
Ah ok
Matthew Pocock
@drdozer
I've got a Var bound to a text area input. It is firing an update on every interaction with the text area, including scrolling around with arrow keys. Is there a way to tell a Var to drop value firing events that are identical values with the previous value? A sort of 'only when changed' filter?
Tim Nieradzik
@tindzk
Yes, you can use distinct
Matthew Pocock
@drdozer
thanks, that works
Matthew Pocock
@drdozer
hi - something very wrong is happening with the reactives in my application
it seems like somewhere an entire log of past state is being replayed, getting cumulatively larger and larger
Matthew Pocock
@drdozer
OK, it looks like the repetitions are coming from a for comprehension
 for {
    txt <- dotTextDistinct
    url <- gvUrl
    parsed <- parseStatus if parsed
  } yield {
this seems to be invoking the body for some historical accumulation of the past values of txt, url and parsed
Matthew Pocock
@drdozer
ah - I wonder if flatmap is what's doing the nasty
so x.flatMap(T => ReadChannel[U]) will generate a new ReadChannel[U], each one closing over the value of Tit was geneated on. These are then all bound as down-stream consumers of x. When x fires, a new ReadChannel[U] is created. All the ReadChannel values then will fire in parallel as the U source fires, resulting in a whole load of parallel results getting spat out
Matthew Pocock
@drdozer
the comprehension desugars to:
  (dotTextDistinct).flatMap {
    case txt => (gvUrl).flatMap {
      case url => (((parseStatus).filter { case (parsed) => parsed })).map {
        case parsed => {
Matthew Pocock
@drdozer
OK, I've re-written this without any sugar using zip, filter and bind:
Felix Dietze
@fdietze
Probably interesting for everyone: I think we have a bit too many reactive dom libraries with the same goals: scala-js/scala-js#2843 What do you think?
Matthew Pocock
@drdozer
I was about to make things even worse by writing a finally-tagless abstraction over building DOM objects, with back-ends to the browser DOM and a virtual dom