hi, anyone here using natal/ambly on ios?

Should I use cljs.reader/read-string or js/parseInt to convert numeric user input after sanitization to an integer?

I would suggest the latter as read-string can read many more things than you may want to allow/accept.

Hi

Brace yourself - here comes a stupid question.

I understand we are not quite there yet, but still: What needs to be done to get an nrepl server running in node?

this will probably sound stupid (today is not my best day …) but is there something like an inserted sorted set in cljs?

what would the "inserted" part do?

@cfleming: btw, the sooner you can get to Socket REPL support the better

turns out ClojureScript doesn’t need to do anything at all, the clojure.core.server is generic enough

5 lines of code

Amazing

(Thinking about mobile :) )

@mfikes well this is about starting REPL servers, so you won’t be able to do that on mobile

Ok

Maybe one use case for Socket REPL is to wrap Ambly so Cursive can drive it.

@mfikes: yep that’s the primary use case, tooling

this gives us a unified simple way to talk to Clojure & ClojureScript REPLs

you can start as many as you want in the same JVM process etc. etc.

Cool. I need to put some thought into cleaner initialization of Ambly with respect to its discovery “choose device” phase.

@dnolen for tooling to work we'd need :repl/attach. is that already supported? can't find it

ah nevermind .. just using one node/repl-env anyways

the keyword driven API is weird. did I miss the dev discussion on socket REPL?

@thheller: yeah it’s been going on for at least 6 months or something

since before 1.7.0

unlikely to see further changes I suspect at this point but you can check in with @alexmiller

@dnolen: Sweet. Socket REPL works just fine with Ambly. I’ll write up a short blog post note on it. No surprises… good thing is that the discovery phase works fine over the socket.

nice!

That was easy: http://blog.fikesfarm.com/posts/2015-11-11-ambly-and-socket-repl.html

nice british socket

@mfikes that was quick

Thanks to @alexmiller (or whoever was involved), that was trivial

yep I thought I would have to do something special but happily we just adopted the clojure.main approach earlier this year

now all this stuff just composes

hmm just a few things come to mind

but I have to test some stuff

can't get this stuff to run

ClojureScript Node.js REPL server listening on 54882 java.lang.AssertionError: Assert failed: (or (file? x) (url? x) (string? x))

@dnolen: Excellent we are going to converge on a good general setup. So exciting.

re: Socket REPL

one concern that comes to mind is that there is no framing of messages

can't differentiate between out, err or eval result

things are once again targetted at humans not tools

@thheller: no it’s targeted at composition

irrespective of humans or tools

there’s already examples of how to get the nREPL style stuff out of this design if that’s your cup of tea

but nREPL has demonstrated how uncomposable that stuff actually is

yeah just concerned that the REPL is still built on RPC semantics

clojure can do that just fine since you have blocking for everything

eg. require can block

node/browser-repl that is async

still a tools needs to be able to identify that require finished

in clojure you get an exception if something goes wrong

cljs that exception is async

I think you’re missing the point

this is just communication over a socket

who cares about async or not async

REPL’s can arbitrarily nest over standard IO

nothing says you cannot send EDN frames to clojure.core.server or whatever

the point is you can layer that stuff over something primitive

trying to get something primitive out of a fancy thing like nREPL is a disaster

totally agree that nREPL isn't great

and nothing like it will be

ship the smallest composable thing, people can layer over whatever they need

sounds kinds of like … the Internet

well .. most things have protocols

but I get your point .. socket REPL is just a socket. the rest is up to the tool

@dnolen: I’m trying out om.next, using the quick start. Seems like I have to require om.core to use js/ReactDOM.render but the quick start examples don’t. Is it just me? (I’m almost at the point where I’ll use add-root! so I expect I won’t need om.core for long.) … and thanks for the great stuff!

@boz you probably have something wrong with your deps

@boz also there is an #C06DT2YSY specific channel

Cool @shaunlebron is topping HN with Parinfer

wow Parinfer feels like magic

😄

Wow, looks neat, considerably better than having to remember paredit shortcuts. Now someone just needs to get it into Cursive : D

Given the pace @cfleming works…. that might be sooner than most would think.

Oh cool, working on it for Atom? Noice.

the Atom extension is mostly working; you can try it out right now

let me know if you run into anything

Nice. I’m a bit of a Clojure n00b, but I’m not grokking paredit, so I’ll give it a spin.

you are precisely the target audience for Parinfer then

Haha awesome

@dnolen: Cool, it’s on the post-conj shortlist

Parinfer looks really nice, I’ll have to take a look at how it works.

@cfleming: sweet!

nice; I’m a total smartparens/paredit nerd but this is obviously so much better ux

And it doesn’t really mess with splice &c

What about slurp and barf within a single line? I guess you would still need hotkeys for that, right?

@ordnungswidrig: from the example on the project’s page it looks like inserting and deleting parens can automagically trigger a slurp/barf

Yes but not necessarily where I want it in a long line?

it determines where to slurp to based on where you choose to insert a closing paren

and it does a similar operation based on where you choose to delete an opening paren

I was thinking about (+ a b) => (+ (or a 1) b)

parinfer: (+ |a b) insert [ => (+ (a b))

I see when I insert the ) it corrects it

ordnungswidrig: wait, why does that do ( instead of [

I’m generating some cljs sources and got an interesting problem. Some names clash with cljs.core stuff: "WARNING: update already refers to: cljs.core/update being replaced by: …" I would like to use :refer-clojure :exclude, but how to reliably know list of symbols defined in cljs.core? so I can mention only clashing ones. Clojure’s :refer-clojure :only would solve my problem beautifully, but it does not seem to be supported under clojurescript 😞

ideas?

Is there a solution for compiling Scss with Lieningen or Figwheel, or somethin?

@lucaska: https://github.com/bluegray/lein-scss ??

I’ve never used it

never used scss

Cool, thanks!

I hope it helps

I had decent luck with that on a project a couple weeks ago

@kevinmershon: So it would auto build it, and inject the resulting css with figwheel?

I don't think I got figwheel to watch for changes, no. I was running a second terminal with lein recompiling scss to do it if I remember correctly. Not as clean as it should be

Yeah, I guessed that was the way to use it, but definitely seems clunky. Thanks though.

Ah no, I was using lein-sass 0.3.7 not lein-scss.

Might still be the same haha

I’m not super familiar with Leiningen/Figwheel yet, so I dunno what is possible, but not many front end devs write pure CSS anymore…at least not in my experience.

My best guess would be to use figwheel's :notify-command and add your sass/scss path to the watched folders

is there a way to slurp json files at build time in clojurescript?

@puppybits: you could write a macro that uses slurp, e.g. https://groups.google.com/forum/#!searchin/clojurescript/slurp/clojurescript/zfnK8Wxg-bM/-V8WZ2sxWlQJ

thanks

So, are these slack channels and the corresponding irc ones mirrored?

to answer my question: it appears not. bummer.

I can’t get externs to work on my project. I want to export some functions that are on the window. how do I do that

I think we should consider this: https://ekmartin.com/2015/slack-irc/

Don't want to leave those old-timers in our dust

Can any of our admins make installing that bot happen?