@jumblerg Thanks! got it working with help from a snippet you gave me a while back

(defc model {:view :home})

(defc= view  (->  model :view))
(defc= route (->  view vector vector))

(defn change-view [model view]
  (assoc model :view view))

(defelem menu-button [{v :view :as attr} elems]
  (elem :click #(swap! model change-view v) elems)

(window :route route

    (menu-button :view :foo)
 
    (case-tpl view
       :home (home-view)
       :foo (foo-view))

Advanced compilation seems to be nuking my ability to call .getBBox on an SVGTextElement. What sorcery is involved in making that work?

maybe google closure externs are missing that?

Yep, headed down that road now.

there are some built-in externs for browser provided javascript types

Currently trying to figure out HTH to do that. 🙂 I think I’ve got it.

var SVGTextElement; SVGTextElement.prototype.getBBox = function() {};

That look right for an externs file?

Cool, that worked.

What a PITA. Hope that thing David was talking about makes all this easier soon.

I was just wondering about this

i'm curious about that

it looks like you would add type annotations

but js doesn't have interfaces

so you would need to know the concrete type

But I believe Closure does have interfaces of a sort.

https://github.com/google/closure-compiler/wiki/Structural-Interfaces-in-Closure-Compiler

yeah but externs are only useful for non-GCL code

otherwise you don't use externs, you just compile the js along with the rest of your GCL compatible js

and it munges away

externs are for like jquery plugins or other random vanilla js code

the externs file is a sort of interface spec itself

@jumblerg Do you have a basic example of how the (pick) form elem is set up?

I've started playing with http://trigger.io, but when I copy index.html + index.html.js over, and compile for the ios simulator, it looks like I'm losing functionality relating to javalin. Any idea if this should work or if I'm missing something obvious?