What are good alternatives for hiccupdata->dom node, if I am migrating from an old dommy?

in cljs, how much can I .increment a number before it stops incrementing? (due to everything being a double in js)

@qqq I believe it is 2^53. Reference: See https://en.wikipedia.org/wiki/Double-precision_floating-point_format , in particular the sentence indicating that in the range from 2^52 and 2^53 you can represent integers, and then 2^53 to 2^54 being even integers. In short

(= (inc 9007199254740992) 9007199254740992)

Or, FWIW (inc cljs.spec/MAX_INT)

Would it be correct to say that Google Closure compiler won't even try to eliminate dead code from the libraries included via :foreign-libs+:externs?

@meta-meta

@metametadata that would be correct, yes.

@metametadata that's kind of what the "foreign" bit is about. Usually foreign libs are written in a different module system or none at all and thus can't be understood/disected by the compiler

If you have something that's in Closure's module format you can use :libs and get all the benefits (DCE, renaming etc.)

@martinklepsch got it, thanks a lot

@metametadata FWIW Closure won't even see :foreign-libs, only their externs

i'm trying to test a function that accesses a global JS variable and i'm looking for a way to set/mock that in the test. is there a way to write to global variables or change the access to them?

@fossifoo, e.g. (set! (.-xyz js/window) "xyz")

because js is single-threaded, you can just store the value, run the test, and restore its old value 🙂

thanks. that's what i tried. i got a parenthesis wrong 😉

This also works and is shorter: (set! js/xyz "xyz").

too much plain js, not enough lisp in the last few days 😉

yeah, that's actually what i use now 😉

have to defeat the urge to write a with-global-variable 😉

my main it's going to be the only point i'll take these in, no point, but....

but there is no "unset", so "delete", right?

oh, well, set!ing to js/undefined should be fine

@fossifoo I think the preferred way is to use goog.object/remove

There is also js-delete, but gobj/remove will tell you if the key was actually deleted.

but for "global" i don't have any object

js/global

Well I was thinking js/window, but deleting from window is apparently illegal in js itself.

disregard. carry on 🙂

actual: #object[ReferenceError ReferenceError: Can't find variable: global

seems like phantomjs doesn't like js/global

it provides window though

it's js/global in node, js/window in browsers I think

Hmm, it actually worked in my repl, but not in my console:

js/window
=> #object[Window [object Window]]
(set! js/window.a "foo")
=> "foo"
js/window.a
=> "foo"
(js-delete js/window "a")
=> true
js/window.a
=> nil

(in chrome) ^

hmmm. also still seems to be set in phantomjs after the delete

i guess i just go for overwriting it with undefined

should work everywhere in case i want to switch test environments 🙂

works good enough. thanks

I think I am going to make an SPA, for the first time in a while.

but it is not a business app and does not have a backend or a complex app state thing. so I'm afraid of using a full SPA framework

I feel like I mostly just need a good library for handling events and updating the dom

and do everything else the quick & dirty old fashioned way

am I wrong? what libraries are good for the events and dom stuff?

@gfredericks for updating the dom my preference has been reagent for a while

reactive atoms were you need them for ad-hoc state as necessary

okay so I can use that without having to like have an implementation of datomic in the browser and use datalog or anything like that

yup totally.

I imagine it has event handling as well

haven't looked into that as much. Most event stuff I've done with it I just hook directly into whatever js event I need

should I be figuring out how react works if I'm going to do that or can I pretend react is not there

I don't 100% understand how react works myself. or even like 80%. I mostly pretend it's not there

ok

thx

:thumbsup:

@gfredericks I’d recommend reading a little bit on react if you have not tried it ever, I think reagent docs assume that you know react in the first place. It’s very intuitive after that, though. Recommended

Is :serve-static really an option for the browser repl?

It's in the doc string, and it's defaulted to true in the opts. But that key doesn't appear to be read anywhere. It just reads :static-dir when setting up the server.

Furthermore, given the way the xpc connection is set up, I think you must serve static files to one extent or another.