Hey @micha I’m thinking of changing if-tpl so that the conditional isn’t specified in :pred. So that where once the structure was:

(if-tpl :pred truth
  (true-tpl)
  (false-tpl))

(if-tpl truth
  (true-tpl)
  (false-tpl)

hey, so I just noticed that I can do (div :class “foo”) or (div { :class “foo” } ) equally well

is that so I can pass hash maps to my custom elements and pass them through to the core elements?

actually, I’ll just ask about what I’m looking at

if i want to do defelem that just wants to set some values but passes the rest through, what should I do?

e.g. (defelem html-range [{:keys [min max step]} opts] (input :type “range” :min min :max max :step step))

so i could do that to get a little range slider, but then I don’t get to do things like :class any more

really the only thing I want to set is :type “range”, everything else should just pass straight through

what’s the best way to do that?

and on an unrelated note, how is automated testing done for hoplon?

and if it isn’t, would anybody be opposed to me writing tests using travis and https://github.com/semperos/clj-webdriver?

@micha: I think i fixed a gnarly race condition (don’t even know what was causing or how to reliably reproduce) by making things “more abstract"

good advice, i think

if defelem doesn't accept a map, you could always use something like mapply

https://github.com/weavejester/medley/blob/master/src/medley/core.cljc#L136

(defelem html-range [opts _] (mapply input (assoc opts :type "range")))

and testing with webdriver is completely fine, although not sure how travis would matter here

@thedavidmeister: ^

@dm3: well is there currently something running builds other than travis?

@dm3 thanks for the mapply tip, i’ll try it out tomorrow

https://circleci.com/, https://drone.io/ - haven't tried those though

I mean for testing that will match closest to the real thing Webdriver is best

how you run it is secondary

i’ve tried circleci, it chokes on boot and runs out of memory

i’ve used drone in the past, it wasn’t as flexible or integrated with other systems as travis

alsooo, i already have travis working for a hoplon based project

so, i suggested it as I’ve already got some code snippets i can reuse

sure whatever works

@thedavidmeister: you could do (defelem html-range [attrs opts] (input (assoc attrs :type "range")))

which leverages the fact that defelems happily accept a map as the first arg

well, i suppose i’ll pick that up again tomorrow

cya all

I was wondering how to get around the lazy UI loading problem in a Hoplon way. I have a number of things in a list that have a Header and a Content. Headers get rendered all at once and content is fetched asynchronously. Each Item has a content-ref that gets resolved via an ajax call. It's kind of like how Castra mkremote works, only I have cells defined dynamically inside the element (as I understand mkremote only works for static state/`error`/`loading` cells). I was thinking of something like:

(let [content (cell= (content/resolve (:content-ref item)))]
  (div ...))

so I did the following:

(defn object-cell [object-id-cell]
  (with-let [result (cell (or (get @objects @object-id-cell) :in-progress))]
    (do-watch object-id-cell
              (fn [_ object-id]
                (if object-id
                  (get-object result object-id) ;this does AJAX if necessary
                  (reset! result :in-progress))))))

@dm3: so mkremote returns an rpc function, right?

and you call that function to make a rpc call

what that rpc function returns is a jquery promise

so suppose you have something like

(def doit (mkremote ...))

in your code you can do things like

(-> (doit arg arg) (.fail #(...)) (.done #(...)))

this is in addition to the global state, error, and loading cells

this is crucial for error handling, for example

so I'd do (cell= (-> (doit (:ref another-cell)) (.done #(...)))) ?

no, no cells there

although you will probably want to be swapping or resetting cells inside your fail/done/always callbacks

but if I need this to run when another-cell changes?

if you need what to run?

the doit

oh that's a different thing

(cell= (when other-cell (doit ...)))

or you can add a watch on another-cell

seems that's what I did in the above

just didn't understand the castra code properly

thanks

Hi, I am having some troubles getting an autocomplete functionality in a hoplon app

tried jqueryui autocomplete and selectize, but with not luck, I am suspecting I do something completely wrong

here's my code

(defmethod do! :selectize [elem _ opts] (.selectize (js/jQuery elem) (clj->js opts)))

then

(select :class "form-control" :id "doc-from-lang" :selectize {:options languages})

have you seen https://github.com/hoplon/demos/tree/master/jquery-selectize ?

yeah, well that one uses a hoplon wrapper, which is on clojars, but vanished from github

I am thinking there is no big deal to use selectize directly

the thing is, my do! method gets called, and throws no error, but there is no effect visible

there must be something I am missing here...

https://github.com/hoplon/hoplon/tree/cccca2fdd0c4708b39465f5a04f08ffa69cfbee2/contrib/jquery.selectize

https://github.com/hoplon/hoplon/blob/cccca2fdd0c4708b39465f5a04f08ffa69cfbee2/contrib/jquery.selectize/src/hoplon/jquery/selectize.cljs.hl

i think your problem is that .selectize needs to be called after other things run

after the element is in the DOM already, for sure

you'll notice line 14 in the file i linked to

https://github.com/hoplon/hoplon/blob/cccca2fdd0c4708b39465f5a04f08ffa69cfbee2/contrib/jquery.selectize/src/hoplon/jquery/selectize.cljs.hl#L14

it's doing the .selectize asynchronously

after all the dom building is finished

which ensures that the element you're selectizing is in the dom when .selectize is called

that's why your thing isn't having any affect i think

you're calling selectize() before the element is in the dom

hmm

ok, let me try hoplon contrib then

I wasn't aware that hoplon contrib source was part of hoplon

the links from clojars are broken

thanks

unfortunately hoplon contrib is dead-ish

supplanted mostly by cljsjs, altho there were things it did that cljsjs doesn't, like auto css concatenation

ERROR: No such namespace: hoplon.jquery.selectize

that was [io.hoplon/jquery.selectize "0.1.2"]

ok, so can I use selectize like this?

(defmethod do! :selectize [elem _ opts] (with-init! (.selectize (js/jQuery elem) (clj->js opts))))

or do I need to defelem?

that should work

the defelem just has different affordances, like control over children... which maybe you don't need