This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-08-31
Channels
- # admin-announcements (9)
- # announcements (2)
- # beginners (16)
- # boot (18)
- # cider (22)
- # cljs-dev (10)
- # clojure (154)
- # clojure-denmark (5)
- # clojure-dev (5)
- # clojure-nl (2)
- # clojure-russia (13)
- # clojurescript (161)
- # cursive (3)
- # datomic (9)
- # editors (5)
- # emacs (25)
- # hoplon (57)
- # immutant (19)
- # instaparse (1)
- # ldnclj (2)
- # liberator (19)
- # off-topic (7)
- # re-frame (12)
- # reagent (10)
ClojureScript now has as many contributors as Clojure despite being significantly younger. Keep 'em coming
I gotta go run an errand, but after that, I can try using a script, removing cljsbuild from the equation.
Wait! Issue seems to be with cljs 1.7.122. 1.7.48 works just fine with 1.8.0-alpha4.
@ghadi, @bronsa : ClojureScript 1.7.107 and 1.7.122 break when using >= Clojure 1.8.0-alpha3.
Anyone know why codox might choke on clojurescript? It’s dumping a significant number of "WARNING: Use of undeclared Var” lines
@dnolen: clojure isn't exactly a project I'd base my "acceptable number of contributors" expectancy off of
@dnolen: OTOH I see cljs has almost 50% more commits then clj, that I consider impressive and kudos to you
Dan Motzenbecker created a nifty command line tool Natal, which sets up a ClojureScript React Native app for you via a single command, like
natal AwesomeApp
https://github.com/dmotz/natal@zentrope yeah I can reproduce the error, looks like a (clj) compiler bug. I'll investigate
@bronsa Clojure's contribution numbers are significantly different from other serious language projects that people actually use for real work.
@tel: I do not recommend Codox for documentation. ClojureScript for JSDoc is rapidly improving. Hopefully YUIDoc can be the standard solution in the near future
@zentrope: managed to find a minimum reproducible example, http://dev.clojure.org/jira/browse/CLJ-1809 if you want to keep an eye on it
can you just throw yuidoc at the output dir somehow and get it to generate docs, that doesn’t seem to work naively
Is there already a nice threejs wrapper in ClojureScript? My search’s coming up empty… but then again I also had a hard time finding the threejs Clojurescript playground which I did know existed.
There seems to be the three-year-old https://github.com/jasapp/cljsthree
Is anybody using prismatic/schema in CLJS? If I want to, can I strip out any schema usage/data in advanced compilation to make a small build? Or would I have to write such a wrapper (macros)?
@rauh, you should be able to disable it (search for set-compile-fn-validation! here: https://github.com/Prismatic/schema)
that's how it would work in clj at least, dunno about cljs
Yeah that's what I used in clj. But I mean: I can see that the s/defn
(etc) attaches the schema as meta data. If it's never used, does clojurescript strip it out (and all of schema)?
Would be an interesting usecase for custom :closure-defines
ah, you're worried about space, not runtime performance
not sure, my guess it it'll end up in the build but won't make a big difference (you'd have to measure it, however)
@bhauman: So I think the problem may be that when I save a CSS file once, it shows up twice in the notifications: https://www.dropbox.com/s/5zpxktph11bllhb/Screenshot%202015-08-31%2007.41.53.png?dl=0
Ultimately I would like to be, but not in this case - just editing a straight css file, adding/removing a single char
@sgrove: also I'd be interested to see the actual script that that includes the file initially
Hrm, I thought the actual file path “/resources/public/css” vs the http url path “/css” might be a problem, but looks like it’s loading it fine (and the current behavior is what I would expect)
@bhauman: I’m happy to help - is there anywhere I should look? I was trying to track down if the same file was getting reported twice (maybe calling (set ..)
as a quick hack) to watchtower
@sgrove: I'd like to look at it there maybe something that I changed in this last release that is causing a problem
@sgrove: yeah that is strange though. I wonder if your css paths overlap or something.
@sgrove: I'm just guessing now. But again I'm going to make sure that they are unique.
There should only be one, but I do have a reference to figwheel in my profiles.clj, I’ll remove that and double check
@sgrove: if you reload the app in the browser and then try the css changes, does it work
Alright, in chromium, with only a single fresh build, changing a css file causes the browser to be notified and the new nifty cljs logo to show, an additional <link>
tag is inserted into the head, then the previous <link>
tag is removed, but no CSS changes take place. Right-click open-resource-in-a-new-tab shows the css file indeed has the change
Yup, that was it - I’ve been experimenting with styles-in-code and some stuff there, so I had a <style>
tag with @import
directives, that was overridding the link file in the <head>
@sgrove: just released 0.3.9-SNAPSHOT if you want to see if weasel is compatible with it
I think we’re good to go - I saw one SO, but can’t repro at all now (tried lots of different ways), and everything seems to be working smooth
@bhauman: If I'm loading 2 CSS files (screen and print, generated from garden), figwheel should be blinking up the logo twice, right? It does it in both 0.3.8 and 0.3.9-snapshot. Moving to 0.3.9-snapshot and will let you know if I run into any problems.
@sgrove: hmmm let me know if it happens again. Both figwheel and weasel (browser.repl) are patching goog.base I tried to make it so that it can happen in any order.
@shaun-mahood: only one blink per message from the server and the server is probably only sending one message
@bhauman: ok, I'll play around with things and see if I can figure out what's happening - sometimes getting one blink, sometimes 2, sometimes none.
@shaun-mahood: sounds like when the files are getting detected. Look at the messages in the dev console are the css files grouped?
@bhauman: there are 3 different messages I'm getting for different edits - notified of file changes, loaded these files, and loaded CSS files. It looks like it's related to how cursive saves the files, the double blink looks like it only happens when cursive sends things ungrouped.
@bhauman: I'm still getting css updates (which load and change the styles) that don't come with a blink - figwheel does give the "loaded css files" message.
Yeah, it may be garden - seems to happen when I am moving between a garden file and a non-garden file, get one message sent from cursive and one from garden
@bhauman: Ok, just confirmed that both 0.3.8 and 0.3.9-snapshot have the same no blink "loaded css files" message. If you care about fixing it I'm happy to help, but it doesn't bother me otherwise. Mainly want to test the new snapshot
@bhauman: I think so - I'm using it to test my print stylesheet right now, and the print preview is updated when I make the changes. Not sure how else to check.
@shaun-mahood: does the link tag change after reload?
@shaun-mahood: I'm just wondering if your styles are doing something strange to hide the notification
like a race condition where the print style takes to the page and overrides the screen style for a second
so if I throw YUI Doc at a :optimizations :none cljs project it doesn’t really pick up any definitions. JSDoc does a bit better, but it’s still kind of weird
@bhauman: The link tag does change after reload. I did have a style to hide the figwheel notification on the print stylesheet, took it out and still have the same thing happening.
If I throw it just at my own project’s output directly then it actually picks up nothing at all
@bhauman: Strangely, if figwheel gets the message right after another message it blinks the notification twice, but if it comes on it's own there is no notification. I'll see if I can replicate it in a new project with just figwheel and garden.
I find this article interesting http://glenmaddern.com/articles/css-modules — wondering if people have played with such approaches in ClojureScript
Also there’s a #C06DTLT5X channel in here! 👍
@bhauman: I can only reproduce the problem when there are 2 separate garden builds, pointing to 2 separate .clj files, where one of the stylesheets is brought in with media="print"
@shaun-mahood: yeah I didn't plan for that type of flow. I can se why its a problem.
Even then it is sporadic
@shaun-mahood: this could be fixed I guess, if you want to file an issue, just need to handle the asynchrony better for css file loads
@bhauman: I'm leaning towards the side of not worrying about it, since it seems to only be an issue of the figwheel loading display. I can file an issue and provide a sometimes-reproducible case, if you think it's important enough to work on.
@shaun-mahood: it would be nice to record it. Not hard to fix I don't think.
@bhauman: Ok, will file away
@shaun-mahood: thanks
is anyone using a datepicker with om?
is there a concise css guide someone could point me to? I just wanted to put 2 elements next to each other and see there's a whole science around, well, everything regarding css
@bhauman: : yeah, inline-block, floats... reading around for 30 minutes, it's ridiculous! You'd expect to be able to simply define stuff like this in a declarative language
I mean if someone said tables you knew how to put 2 things next to each other in 5 minutes. No need to go read a book about it
btw. today I was studying CSS grid layout, and I thought my head just gonna explode: http://www.w3.org/TR/2015/WD-css-grid-1-20150806/
I just put a div with a given height in, the absolutely position the other stuff inside it. Works great.
@zentrope: that's a fixed size then though isn't it. I mean how will it show when you make the browser window small? How will it show on a smartphone?
tables are great, didn’t want to write source-code layouter for my editor, so I let browser do all the hard work via deeply nested tree of tables, like a boss 😜
@xifi: You can "position: fixed" the div as well, so that it will grow relative to the window.
@zentrope: so now I also need to look that up 😄 Didn't anyone abstract over this yet?
For, say, a nav bar across the top, div.nav-bar {position: fixed, top: 0, left: 0, right: 0, height: 30px}
The sign-out div will always be pinned to the right edge, the nav-bar to the top, left and right, etc, etc.
It’s like C++ or Scala. Everyone boils it down to a sub-set language they can manage.
@xifi: I’m not sure how approachable it is for beginners but I really enjoy working with http://basscss.com
anybody have experience with emacs+cider browser repl "No such namespace" for files in the same src directory?
specific example is my comment here: https://github.com/plexus/chestnut/issues/110#issuecomment-129286134
the style and scope of the namespace error changes based on the various versions of clojurescript / cider / nrepl, so it's been really nasty to work with
fwiw I've also made profiles.clj fixed based on https://gist.github.com/tclev/04bca1350b4157a0abc4
last month I resorted to a workaround by downgrading to clojurescript 0.0-2511
, lein-cljsbuild 1.0.3
, lein-figwheel 0.2.1-SNAPSHOT
, weasel 0.4.2
@martinklepsch: looks quite nice, a bit big for starters, but a reasonable attempt
@xifi big as in code size?
@martinklepsch: big as in modules and definitions