Timothee Cour

since there's nothing karax specific about `&` or `toCstring` or whatever name should be used, and since stdlib already has toCstring procs defined, I feel a stdlib module (std/cstrings? std/cdollars?)...

## workaround for example 1 ```nim n.dom => ev.currentTarget # or v.target ``` see https://developer.mozilla.org/en-US/docs/Web/API/Event/currentTarget for more details on these ## workaround for example 2 ``` callback_getVNodeById('elementsArea').dom => document.getElementById("elementsArea") ```

@araq is there any situation where `StyleAttr` is preferable to `toCss` (introduced in https://github.com/karaxnim/karax/pull/158) ? `toCss` is easier to use IMO because it's easier to go back and forth between...

> You probaly need to make toCss a compiletime operation. then maybe it's time to merge https://github.com/nim-lang/Nim/pull/15528 (const now works with ref types) ? There are so many use cases...

@zah I've found livereload to work well with karax; curious what are pros and cons of browsersync compared to livereload

We should revisit this now that https://github.com/nim-lang/Nim/pull/14979 was merged; I also am curious whether shadow dom could simplify some aspects of karax (including encapsulation of DOM and css) some links:...

EDIT: `cloneNode` is needed to insert same DOM Node twice, see https://stackoverflow.com/questions/20203143/how-to-insert-the-same-html-element-twice ```nim # workaround import karax / [kbase, vdom, kdom, karax, karaxdsl] import js/jsffi var elem = document.createTextNode("hello world")...

> The only thing that Jester is being used for is for parsing a route and extracting information in the route. then maybe that API can be added to stdlib...

agreed; if you have a working PR that avoids creating a div with verbatim, then https://github.com/karaxnim/karax/pull/160 can be closed

@eidheim How about this? * https://stackoverflow.com/questions/22424715/boostasio-with-boostunique-future ``` boost::unique_future result = timer.async_wait(use_unique_future) .then([](boost::unique_future future){ std::cout