this might not be right, but my understanding is that hoplon does compiling per-page

so yeah, it's faster to have some kind of dynamic routing under one page than lots of pages all compiling

as yet, i do not know what impact this has on SEO, if any, maybe @alandipert or @micha could give more details on that?

@mudphone @thedavidmeister if you look at the boot-hoplon task, once there are hl files detected, it goes through and compiles those to cljs then parses the cljs files, depending on your project size this can take a while

for this reason I am converting all my libraries to cljs to speed up build times

and I use .hl for the page macro

@flyboarder is it any faster/slower to use .cljs instead of .hl files for a given page?

e.g. (ns ^{:hoplon/page "index.html"} pages.index ...)

Yeah using a cljs file will always be faster

Else you always need an extra build task which will take time

@thedavidmeister ^

I find if I use .hl for the index page only and cljs for everything else I get a decent build time, then factoring components into smaller libraries cuts down on app level code which requires rebuilding

I am often running 4 builds at a time of multiple components

i do only have one .hl atm

if i move things into something on clojars, will that speed up my build times too?

moving things to separate projects limits the number of files/folder tracked

but that seems unnecessary

ah ok, i didn't now whether clojure still needed to compile dependencies

i assumed it would need to

Does anyone know if there is a way to get hoplon to play nice with an existing instance of jQuery? I have a site using clojurescript, and I was considering incorporating hoplon in order to add a new planned feature, but requiring hoplon in any namespace seems to clobber the existing jQuery and plugins that the site already uses. Is there anyway to get hoplon to use the pre-existing instance of jQuery rather than requiring its own?

@tjscollins you probably need to exclude the jQuery dependency when including hoplon

:dependencies '[[hoplon VERSION] :exclusions [cljsjs/jquery]]

@thedavidmeister @flyboarder thank you, I have much to think about now.

@dm3 That doesn't seem to do it. It's weird. Simply having

(ns theme.test
    (:require [hoplon.core :as h]))

how broken?

@dm3 I'm using a jQuery plugin to create a carousel. It works without hoplon loaded, and with hoplon loaded I get a nonresponsive mess. Basic jquery stuff seems to work, but the plugin is totally broken (plugin is slick, if that matters)

yeah, but where does it start to break in javascript? Hoplon doesn’t go and modify jQuery internals, so if you’re sure that you have the right jQuery version on the page - you should be good

@dm3 I'm not sure what you mean. Every looks right, except the carousel plugin. I just tried a few other parts of the site and that seems to be the only thing breaking.

are there any js errors?

None.

The plugin must be making some global assumption that hoplon breaks...but I have no idea what.

yeah, so if it works without the hoplon dependency

I’d try to 1. diff the loaded JS tree with/without Hoplon on the page with breakage

2. step through plugin initialization in JS to see if there’s anything obvious

@mudphone re: hoplon speed, in hoplon 7.0.0 there was a big improvement

or rather, 7.0.1 is the one you want