What you could do is to find the dom elements and attach callbacks to them directly to trigger events.
Would the
jsdeps approach suggested by @mkotsbak work for you?
I've responded to your other questions on the GitHub issue.
Widok's DSL is slightly more succinct. Judging from Udash's TodoMVC example you may still need to use jQuery to manipulate nodes.
@tindzk
@kindlychung I would also recommend you to have a look at MetaWeb which is a complete redesign of Widok. The goal is to address some conceptual issues and have a smaller core.
@drdozer still a SPA? Then like this?: http://widok.github.io/manual/widok-v0.2.2.html#multi-page-applications
Nothing new in sbt if you don't mind having all code available for all pages
Here is a routing example: https://github.com/widok/skeleton/blob/master/js/src/main/scala/io/widok/client/Application.scala This is a client side thing, nothing to do with server side routes
Why can't you do it like that?
Maybe all could point to the same application, and get the widok router to read physical page urls too
If size does not matter, I would say rather point to the exact same .js file (which could be cached by the client between each page)
And then read the url for the app to react properly according to the page
Or if you make your own Application class not extending JSApp you could launch it manually with parameters given from the html file
The sjs sbt plugin I think, or the compiler
So would I have to subclass View and over-ride
render(parent, offset) to run the relevant javascript?
and this will only work if the view is part of the page, so only if when you render a child, the parent is already added to the page
override def render(parent: Node,
offset: Node) = {
super.render(parent, offset)
js.Dynamic.global.window.setTimeout(registerAce _, 0)
}