This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-10-16
Channels
- # beginners (1)
- # boot (69)
- # carry (1)
- # cider (29)
- # cljs-dev (17)
- # cljsrn (100)
- # clojure (13)
- # clojure-austin (13)
- # clojure-brasil (1)
- # clojure-dev (1)
- # clojure-korea (3)
- # clojure-russia (3)
- # clojure-spec (20)
- # clojure-uk (5)
- # clojurescript (45)
- # cloverage (3)
- # datomic (5)
- # figwheel (1)
- # hoplon (198)
- # klipse (25)
- # lein-figwheel (2)
- # leiningen (3)
- # off-topic (35)
- # om (7)
- # om-next (2)
- # onyx (8)
- # proton (8)
- # re-frame (3)
- # untangled (1)
- # vim (13)
I’ve found when developing with Hoplon and other ClojureScript frameworks like re-frame with figwheel, that there are certain things you can do that totally bork up the system. For example, in Hoplon, accidentally dereferencing an input cell within the definition of a formula cell (cell= (inc @input-cell)) can cause this.
I’ve started thinking of it as the Blank Screen of Death
Curious what you guys call that state
and if there are any diagnostics that can be used to track down the problem
My current technique is to slowly back out changes until I get back in a state where stuff is rendering again 🙂
@keithsparkjoy do you have browser developer tools open? I believe there should be an error message there
Also, count me as another instant huge hoplon/UI fanboy. First time I felt comfortable with any sort of UI work, nevermind finding it fun
Thanks, @jjttjj. Embarrassed to say I'd not thought of that :) pretty new to cljs.
Yep, sure enough. I’ve been looking at the DOM inspector; hadn’t thought to look at the console.
@keithsparkjoy you arnt really supposed to do that in a cell=
@flyboarder: hah yep it was just an example of a mistake that leads to the bsod :)
Maybe spec could help avoiding that, checking for deref and throwing an exception, but I'm not sure.
@keithsparkjoy I've been finding it quite useful to print stuff (intermediate forms) to the console with (enable-console-print!) and (println) for debugging like spelled out in the clojurescript quickstart and hoplon tutorials
hoplon/ui
master now depends on hoplon/hoplon
responsive-layout-attributes-micha
branch for bound-fn
https://mynomoto.github.io/hoplon-klipse/ live coding a subset of hoplon in the browser. I'm trying and failing to make macros work on that. But the sample works, click on the number and it should increment. I'm pointing to forks of hoplon and javelin because I had to remove jvm related stuff to be able to use bootstrapped cljs.
@micha: i just realized, when building against the latest hoplon master + bound-fn, that castra assumes jQuery is already provided (for the promises)
i used the zones one for a bit, i found it to be kind of inconvenient, because then all te code needs to know whether to deref it in a special way or not
it looked liked that one was more advanced and could be wrapped to be equivalent to Michas, but I didn't go deep into either
does it give us some benefit (aside from extra machinery) that micha’s bound-fn doesn’t?
i only scanned it quickly, but it looks that the benefit of micha’s bound-fn is that it works with the existing clojurescript fns, rather than introducing new ones to accomplish similar things. the one i’m about to merge in seems simpler.
sorry guys should have squashed those
yeah i think the performance implications are negligible for typical ui event ahndling use case
if you have something that will fire many times per second you can always optimize by making explicit lexical bindings
ok so i think with alpha17 jquery has been completely factored out into a separate module
which is pretty awesome, good work @flyboarder !
@micha thanks for fixing boot-hoplon!
How do we feel about hoplon 7?
I haven't been able to test with work app yet but we can always do minor releases
@alandipert maybe hold off on hoplon 7 until I can get goog attribute provider updated?
then we can offer both for the next major
I'm game
It would be nice to orient the task and libs around the same number when we're ready, state of things kind of confusing currently
agreed, maybe increment boot-hoplon to v1? or v7 hahaha
I like this
Yeah one and the same
:thumbsup:
I don't remember why they were ever separate
That would be cool, then it can be excluded
to support compatibility with older setups where people just update the hoplon dep but have their own separate boot-hoplon dep
this is so exciting!
gotit, not the protocol ICustomAttribute
that’s still in the responsive-layout branch.
I will do up a wiki page today about attribute providers
i have a lot of gratuitous attribute machinery in ui right now that needs to be factored out, so they may be quite helpful.
basically the on! and do! methods now just fire browser behaviour and all other jquery references in core have been replaced with vanilla js, but you get original functionality back by including hoplon.jquery
in your (page)
which new boot-hoplon does for you so to the outside world nothing should be different except optionally dropping jquery if you want
there are also some new jquery specific things to solve a few problems like :data/*
:prop/*
where :attr/*
isnt technically correct
yeah i can stop sweating and take a shower now 😛
so for the past week it's just been in primer so i have to take a bath in a bucket every day
@micha omg thats like when I visit family in germany, their house is really old, you actually wash yourself with a wash cloth, because there is no water pressure
totally
yeah scarf was recently shut down here https://www.getscarf.com/
ah, that’s sad. we had a service like that here in boston for a while. i was one of their, ah, power users, you might say.
city slickers get to spend more time computing and less time fing around with mop buckets.
I started working out of our local startup incubator, micro services for real world is the way to go, not just for IT
@micha: i wonder if it would be worthwhile to, instead of using jquery, include a polyfill with castra so javascript promises can be used instead.
i’m making heavy use of them in one of my apps since, if webrtc is supported, so are they.
yeah there are also promise libraries that provide the same as the newer browser ones of course
of course, it the current configuration, it already is though since it relies upon it to provide the jQuery dep.
i do that myself anyway, because each application has a few types of removtes that i do different things with
it would be nice to chain in castra remote calls with other promises i’m getting back from webrtc remotes/peers.
brower apis like this one return promises now: https://developer.mozilla.org/en-US/docs/Web/API/MediaDevices/getUserMedia
speaking of disgusting things… instead of simply using json/javascript objects, this is the protocol browser vendors implemented as part of the webrtc apis to exchange connection information. https://tools.ietf.org/id/draft-nandakumar-rtcweb-sdp-01.html
f-35 saga seems even crazier
with computers and software, demands can take on infinite dimensions
the portholes thing i don't understand at all
i tried to shoot the saw out of the window of an 1114 at a range once
whole cabin filled with noxious smoke instantly
maybe the problem was my mindset lol
i was pretty amped tho
definitely rained on my parade
i guess there is a long tradition of tanks having ports like that tho
how did they do it and also breathe
maybe if i was actually shooting in bursts it wouldn't have been as badt
@alandipert: my favorite movie!
the webrtc discussion reminded me of it
webrtc: troop carrier, recon, tank
just when we think we’re starting to get one browser interface under control, they botch up another to keep us occupied.
much better