Clojurians
#lumo
<
2017-05-04
>

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

anmonteiro00:05:47

hrm on a first attempt Prepack fails on the generated Lumo JS

anmonteiro00:05:59

can’t really say why as their output is pretty cryptic

dominicm07:05:47

Keep documented your attempts

hlolli09:05:44

anyone had the idea as well of trying to use lumo to clojurescriptify? https://github.com/substack/node-browserify/wiki/list-of-transforms nothing should hinder that right?

anmonteiro14:05:13

Actually managed to get it to work

anmonteiro14:05:29

I think my phone pasted the link twice :thinking_face:

dominicm14:05:34

That's awesome

dominicm14:05:42

@anmonteiro that happens if you're on a spotty connection

dominicm14:05:51

Any idea on how much difference it makes to the code?

anmonteiro14:05:17

Not much because all it matters is the snapshot in the end

anmonteiro14:05:07

But there might be runtime perf gains to be had

dominicm15:05:21

@anmonteiro sure, but hoping to apply it to other projects. Good to have number ideas roughly for them. :stuck_out_tongue:

jonpither16:05:21

hi - how do I use lumo.classpath?

jonpither16:05:01

nm, @dominicm helped me with a path

jonpither16:05:15

funky funkage

anmonteiro16:05:01

@jonpither is anything not straightforward in the API?

anmonteiro16:05:09

I’m always looking for feedback

jonpither16:05:57

Is it documented? It was odd I couldnt call it inside the lumo repl, but could from inside a cljs ns. I guess this is a known semantic?

anmonteiro16:05:16

that sounds weird

anmonteiro16:05:35

I can definitely (require '[lumo.classpath :as cp])

anmonteiro16:05:56

@jonpither not documented yet, sorry, working on it

jonpither16:05:09

Ok need to check my setup. Was defo running 1.4.1 but let me reexamine

anmonteiro16:05:13

you can always (dir lumo.classpath) and use doc

jonpither16:05:56

Just migrated to a pub, but will try later and report back.

cfleming23:05:27

Is it possible to install older versions of lumo via homebrew?

anmonteiro23:05:39

I don’t know how to do that

anmonteiro23:05:48

I’ve only ever succeeded at installing the latest

cfleming23:05:01

Ok, thanks - I’ll try from git.

anmonteiro23:05:03

what’s your problem?

cfleming23:05:45

For the SDK change in Cursive, I’d like to try the --version flag in a version that didn’t support it (1.2.0, AFAICT) so that I can detect that error message and warn the user they need to upgrade.

cfleming23:05:58

I just tested it here, but I’m on 1.1.0 and I got the infinite loop bug.

anmonteiro23:05:27

other than that the error will be the same as if you do lumo --askjbfkuasj

cfleming23:05:50

Thinking about it, even if that bug is fixed in 1.2.0, I’d be making that check for one single version (1.2.0) so perhaps it’s not worth it.

anmonteiro23:05:19

are you actually working on adding Lumo support to Cursive now? :slightly_smiling_face:

cfleming23:05:21

Since previous versions have the infinite loop. I guess I’m going to have to deal with that anyway.

cfleming23:05:19

I was just continuing some investigations, but it’s a bit of a yak shave right now. I’m trying to build my latest version and I use a lumo script there now, and working on the script in Cursive without support is a PITA so I got sidetracked :slightly_smiling_face:

anmonteiro23:05:14

hopefully a good rabbit hole to go down to :slightly_smiling_face:

cfleming23:05:06

Yeah, fingers crossed :slightly_smiling_face: