(well it says you use cats-effect on the front page, but I guess it must be imported into the project in some indirect way)
Ah cool the sbt
dependencyTree tells me it is colibri that colibri that imports it.... (nice tool)
ok, so I guess the latest http4s-dom uses cats-effects 3.x whereas colibri is using 2.6.1
I personally only use a single websocket connection in my project, but if I ever need to talk to a rest api it's probably a good choice
For The Solid Project we write apps for the web thought of as one giant hyper-data RESTful system. Clients follow links from one server (Pod) to another to build up UI elements. So even though websockets are also used, we really need streaming http libraries.
I have written my server in Akka but I think having akka on the client would be a bit heavy on the client. So that means I need to learn another set of libraries on this. Cats-effect seemed indeed like a good thing to try out, and as you say it is widely used...
I have some kind of problem when I use
this happens on chrome but not on firefox.
I was searching for some solutions on google but I have some
Any idea please. :-)
onInput the focus on element input is loss more or less, because the element is showing is focused but the cursor is loss.this happens on chrome but not on firefox.
I was searching for some solutions on google but I have some
Observer connecting on this element so I don't quite get the solution.Any idea please. :-)
this my code:
val onChangingValueTxt =
SyncIO(
onInput
.value
.transformLifted( (e: Observable[String]) =>
e
.distinctUntilChanged
.withLatestFrom(hdlFieldActive){ case (txt: String, (field: String, currentValue: JsonValue)) =>
val currentValue2: JsonValue = Try {
wrapValue(txt, currentValue)
} match {
case Success(value) => value
case Failure(exception) => JsonNull
}
(field, currentValue2)
}
) --> hdlChangingValue
) val mountCellFocusSelectContent = Observer.create[(dom.Element, String, String)] { case (elem, inputType, idTxt) =>
if (idTxt == elem.id) {
val txt = if ( inputType == "input" ) elem.asInstanceOf[html.Input] else elem.asInstanceOf[html.TextArea]
Try {
val range = dom.document.createRange
val sel = scalajs.dom.window.getSelection
sel.removeAllRanges
range.selectNodeContents(txt)
sel.addRange(range)
} match {
case Success(value) =>
txt.focus
case Failure(exception) => alert("Hubo un error al convertir el valor del componente: line:102 from Grid3 " + exception.getMessage())
}
}
}
the solution seems is this:
$('#Search').focus(function() {
setTimeout((function(el) {
var strLength = el.value.length;
return function() {
if(el.setSelectionRange !== undefined) {
el.setSelectionRange(strLength, strLength);
} else {
$(el).val(el.value);
}
}}(this)), 0);
});
What would be the correct translation to Outwatch ?
the comment about the problem is this:
"It seems like the focus event is fired before the cursor is placed when you focus an input, a hacky workaround would be to use a setTimeout like so:"
"It seems like the focus event is fired before the cursor is placed when you focus an input, a hacky workaround would be to use a setTimeout like so:"
well I did this:
val mountCellFocusSelectContent = Observer.create[(dom.Element, String, String)] { case (elem, inputType, idTxt) =>
if (idTxt == elem.id) {
val txt = if ( inputType == "input" ) elem.asInstanceOf[html.Input] else elem.asInstanceOf[html.TextArea]
Try {
if (window.navigator.userAgent.indexOf("Chrome") == -1 || window.navigator.userAgent.indexOf("Safari") == -1) {
val range = dom.document.createRange
val sel = scalajs.dom.window.getSelection
sel.removeAllRanges
range.selectNodeContents(txt)
sel.addRange(range)
}
} match {
case Success(value) =>
txt.focus
case Failure(exception) => alert("Hubo un error al convertir el valor del componente: line:102 from Grid3 " + exception.getMessage())
}
}
}althought I don't know if is right. :-)
@busti That is a great question! Actually it is because dealing with an
Observable means, we need to handle a subscriptions: adding callbacks onMount and onDismount. Operating on an Observer, is great because you can just push things into an Observer without state. So, it is kind of a performance optimization to prefer Observer operations.
We do not have syntax extensions for
Source, Sink generally, because I felt, it would be too intrusive, when just working with Monix or scalarx or airstream natively. Maybe, just hide them under a syntax._-import? It is nicer too write. And that is an advantage of the Sink, Source archtiecture.
Ah, or a we just working on
Observable/Observer there?
EmitterBuilder kinda is like a wrapper in many cases, which makes it difficult to refactor in many cases, but I like the API it produces a lot.
I agree, syntax extensions for
Source and Sink would feel wrong because usually algebraic methods are members these days. I hope that's going to change with scala 3 and the extension keyword. No more .map on everything. Just a single global extension method for all functor instances.
But right now in colibri you are able to call member methods on observables
a.withLatest(b) and the method on the static object Observable.withLatest(a, b). While I think its fine to have both, outwatch tends to use them at random in some places and I believe it would make the code more readable to make that a little more consistent.
but I get this error:
not found: type Handler
[error] def cmpDate(hdl: Handler[Long]) =
if I search for the location I found it on this path:
import outwatch.reactive.handler.Handler
instead of this:
import outwatch.reactive.handlers.monix._
is it right to make the change ?
Hi @elyphas! Yes, we have actually deprecated
You are still able to render any kind of
Both are still available (monix and colibri handlers). Just deprecated.
Handler. To me, this concept feels too complex, that you indirectly create new instances of your stream-types (just with the help of a magic import). It just seems more straightforward to directly create your subjects with the library of your choice. The intent is much more clear.You are still able to render any kind of
Observable in your dom nodes.Both are still available (monix and colibri handlers). Just deprecated.
any idea why this code works perfectly, but if I put the class FrmClass on another file it doesn't?
class TestingOnClassSpec extends JSDomAsyncSpec {
class FrmClass {
val testClick = new Observer[String] {
def onNext(elem: String): Future[Ack] = {
Future {
println(elem)
Continue
}
}
def onError(ex: Throwable): Unit = { println(ex.printStackTrace.toString) }
def onComplete(): Unit = println("O completed Handler")
}
val but = button( idAttr := "cmdTestOnClass", "Save", cls := "myButton",
onClick.use("on the observer a class ----------") --> testClick
)
}
it should "be test the save button" taggedAs(ButtonTestingTest) in {
val frm = new FrmClass
for {
_ <- OutWatch.renderInto[IO]("#app", frm.but)
} yield {
val element = document.getElementById("cmdTestOnClass")
sendEvent(element, "click")
succeed
}
}
}something lacking me ?
thank you
@cornerman ; now there is full support to zio and monix is out ?