Closed yakir12 closed 8 months ago
Well, if you use an explicit app, you should also call it in thepage macro
How exactly, is it in the docs somewhere? apologies if so.
help?> @page
@page(url, view)
Registers a new page with source in view to be rendered at the route url.
Usage
@page("/", "view.html")
btw, I'm only using an explicit app because I need to define js_methods
. Is there another way of accomplishing that...?
It's a general pattern: All New Reactive API macros can be called with an explicit model type in the first position
@methods "
f1: function() {console.log('Hello')}
f2: function(name) {console.log(name)}
"
@methods MyApp "
f1: function() {console.log('Hello')}
f2: function(name) {console.log(name)}
"
there's one exception with the @page
macro:
@page("/", ui)
@page("/", ui, model = MyApp)
We should put that in the docs somewhere ...
I think we can close this now.
Consider this MWE where an image is continuously updated in the background and continuously queried by the client:
The resulting window is empty:
although, if I navigate to
frame
manually I can see the frame:and the console states that:
versions: