This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-10-22
Channels
- # bangalore-clj (2)
- # beginners (22)
- # boot (8)
- # cider (1)
- # cljs-dev (10)
- # clojars (1)
- # clojure (5)
- # clojure-austin (14)
- # clojure-conj (1)
- # clojure-dusseldorf (6)
- # clojure-france (3)
- # clojure-russia (11)
- # clojure-spec (3)
- # clojure-uk (2)
- # clojurescript (27)
- # datomic (4)
- # hoplon (68)
- # leiningen (7)
- # off-topic (1)
- # om (68)
- # onyx (12)
- # other-languages (1)
- # re-frame (19)
- # vim (2)
ok, I've got a problem and I'm too much of a noob to figure it out. š I'm trying to play around with the plotSVG demo. I created a new project, copied the chart.cljs.hl into it, giving it a multi-segmented ns (because the build complained about that in its original form). I made my otherwise stock index.cljs.hl file require it, and I went to boot it and it gives me: '''WARNING: Can't take value of macro cljs.core/use at line 88 /home/kevin/.boot/cache/tmp/home/kevin/0work/hoplon/aaa/n4o/nyg3lv/index.html.out/hoplon/svg.cljs WARNING: use already refers to: cljs.core/use being replaced by: hoplon.svg/use at line 88 /home/kevin/.boot/cache/tmp/home/kevin/0work/hoplon/aaa/n4o/nyg3lv/index.html.out/hoplon/svg.clj''' Now since that's a collision between two different libraries (I think) and not between any code in my project, what is the canonical way to deal with it? Fix it and issue a pull request? https://github.com/vigilancetech-com/aaa
Or just treat it like the warning that it is and ignore it hoping it will go away (and that I don't end up using that particular feature)?
What version of clojurescript are you running?
Ah so you are using the latest version I see, those are new core functions, they will need to be excluded
isn't this a problem with one library including another library and not excluding "use?"
Right use is now in core
I'm probably using a newer version of both
We need to exclude it in hoplon
so as just an intellectual curiousity, what is the best way to deal with such a thing? Is it a bug report?
Yep an issue on github or a PR
ok, and in the meantime, I guess should just hack the code on my local copy
If you wanted to hack it yourself you could also send us the PR with the change it's fairly minimal, also we need alpha17 in master tested :)
ok, thanks @flyboarder ! This ALSO will be mostly a new experience for me.
Hoplon is easy to hack on, boot develop
and make changes š
Just add use to line 2 of hoplon.svg
yeah, I'm learning that (in theory). It's all pretty abstract and the code is dense with meaning/function, but its slowly starting to sink into my thick head! I've tried to climb this hill several times before but then life happened and I never was able to use it enough for it to be second nature (unlike some other languages). This time is looking good though (thanks to a little help from my friends).
fascinating article on HN about the japanese legal system, http://www.japantimes.co.jp/community/2016/06/22/issues/japans-koseki-system-dull-uncaring-terribly-efficient/#.WArsKXUrKCh
koseki reminds me very much of cells (vs. events)
> Compared to āevent-basedā Official Documents (birth certificates, divorce decrees and so forth) that prevail in places like America, the koseki is more accurate. An American can use a marriage certificate to show he got married on a particular date in the past but would struggle to prove he is still married today. A koseki extract, on the other hand, can do just that.
one simply derefs the married?
cell
@vigilancetech I proposed your question in #clojurescript
@flyboarder about what is the best way to deal with the name collision?
im not sure since this is a core name probably rename hoplon use to svg-use like is done with html-meta
yes, for one's app, but if that library doesn't need "use" specifically, probably fine to just exclude it (although it might bite the unwary dev in that library in the future)
im not sure that use
can be excluded now with the latest version
since itās a namespace macro
well, it compiled without warning if that's any help
hey, when I get a message like these: >WARNING: header already refers to: hoplon.core/header being replaced by: hoplon.app-pages.indexDOT_html/ header at line 33 hoplon/app_pages/indexDOT_html.cljs WARNING: html already refers to: hoplon.core/html being replaced by: hoplon.app-pages.indexDOT_html/html at line 90 hoplon/app_pages/indexDOT_html.cljs does that mean the problem is in my file? I don't see anything under hoplon that looks like "app-pages"
my read is, it's compalining about def
s in your index.cljs.hl
claiming you created your own header
and html
definitions
yeah, renamed those š Probably not the best choice for names.
well, for one thing alpha17 is using javelin 3.8.4 but the newest version in clojars is 3.8.1 so it breaks for me (not saying that that's a bug, but its making it difficult; trying to change hoplon's build.boot to make it use 3.8.1)
that didn't work either: clojure.lang.ExceptionInfo: Could not find artifact hoplon: javelin:jar:3.8.1 in clojars (https://clojars.org/repo/)
@flyboarder should we do a alpha17 release? It's confusing having the readme saying that is released and not being on clojars.
@vigilancetech latest javelin is 3.8.4 on clojars -> https://clojars.org/hoplon/javelin
just realised i can compile garden css from a javelin cell straight into the dom
thatās pretty cool
(def styles (j/cell {}))
(defn set!
[& params]
(let [pairs (partition 2 params)]
(j/dosync
(doseq [[k v] pairs]
(swap! styles assoc k v)))))
(h/defelem css
[_ _]
(h/style
(j/cell= (->> styles.state/styles
(map second)
(filter identity)
(apply garden.core/css)))))
(garden.def/defrule logo :.logo)
(styles.state/set!
:logo (logo { :font-size (u/px* 2 styles.typography/base-font-size)
:line-height styles.typography/base-line-height}))
@vigilancetech: can you update the PR?
@alandipert koseki sounds like blockchain
@flyboarder I think the pr from @vigilancetech is fine, what should be changed?
@mynomoto thanks to @anmonteiro I think you are correct that the PR is fine.
@micha I hate to always be bugging you, but do you mind a quick review of pending PRās as @mynomoto stated there are a few people trying to test alpha17
no prob, I just dont want to be merging things without approval
I wonder about numbers as custom attributes. I imagine using to make a positioning system
@alandipert like (myelem 4 someval)
?
Or (myelem 16 9) to express aspect or something
Not like custom attributes blocked on it, but I wanna fiddle with it
that would be interesting for sure
I'm not able to upload My Clojure Project, it always declares that missing jar-file / repo
@jondejung do you have a public repo of the project you want to upload?
It would be easier to see what is the problem. Or you could put the contents of your build.boot
somewhere public and tell what command you are using.
1(set-env! 2 :resource-paths #{"src"}) 3 4(task-options! 5 pom {:project 'earthware/earthware-css 6 :version "0.1.0" 7 :description "test "} 8 speak {:theme "woodblock"}) 9 10(deftask build-jar 11 [] 12 (comp 13 (pom) 14 (jar))) 15 16(deftask install-jar [] 17 (comp 18 (build-jar) 19 (install)))