Hey, I am thinking about using hoplon for the client side of a side project. Does anyone know where does hoplon stand in terms of speed compared to other alternatives? (reagent, om, react)

we've built large applications with it, and speed was not a problem

cool, I was curious because from what I know hoplon does not use virtual-dom

hoplon doesn't need one, because javelin doesn't propagate unnecessary changes at the data layer

so it just naturally performs the minimum number of dom manipulations, whithout any need for things like that

nice, thanks for the help

🍻

@flyboarder: thanks! will investigate

so, i turned my 2 pages (index and styleguide) into two defelem

then I did this

(u/outer-dom
  (u/the-header)
  (cell= (if is-index
            (index/index)
            (style-guide/style-guide))))

I’m getting some serious negative performance issues (looks like garbage collection maybe?)

but i see the issues even when is-index is not changing (the URL fragment is not changing)

I think I don’t understand something >.<

speaking to what @micha said earlier: "hoplon doesn't need one, because javelin doesn't propagate unnecessary changes at the data layer"

I had thought that the cell= would have zero performance impact as long as is-index does not change

the problem is probably me 😉

ok, i think the problem was actually my crazy pseudo-route-cell

nope, swapped to route cell

still seeing it 😞

I used :toggle to "switch" between pages

or rather views in a SPA

@dm3: that’s a nice tip for handling display

i’m still not quite sure why it’s needed though

not sure either

thinking about it - it's idiomatic in react world to just do if this a() else b()

and it will remove the elements from DOM after diffing if the the condition changes

i saw there is a PR up for an if-tpl

no idea if that helps

ah, yes, if-tpl would be the proper way to do an if that depended on a cell

as you are returning a cell of dom elements to outer-dom

I'm confused why it even renders for you

magic

well i guess i’ll do a short writeup of my experiences on that PR then

hey, does hoplon have a way to handle delegation of events to elements outside a loop-tpl?

a cell in scope for both elements is a way

you mean like, i click on something in the loop-tpl, and you want that to cause something to happen outside the loop-tpl?

i mean like, i have 100 elements created by the loop-tpl

and each one has 5 event handlers

in jquery i can just delegate one event handler to an ancestor

rather than have 500 event handlers

is 500 event handlers slow? or do you find delegating events cleaner

i’m in the habit of delegating

i don’t know what is slow though @alandipert

😞

something was slow

and inconsistently too, which made me think of gc

you should see that in devtools profile

pretty easily

well, when i profiled, it said it spent most of its time in jquery event adding

sooo

i should have ss

definitely good to find what's slow and work from there

for now i’m going to go with display:none;

but i’m going to keep an eye on if-tpl and try again if/when that gets in

Hello @alandipert. I finally got the chance to test form validation with formula, and couldn't make it work. Here is what I have :

I can't turn is-form-valid? to true

any idea?

seems to have a problem with form-postal-valid?

problem solved. Made a typo somewhere else in my code

Thanks again for make-validator!

@thedavidmeister: I would also recommend sticking with :toggle for now, i believe there is also a cond-tpl in the works, which is probably more along the lines of cell based app views, im currently using a regex match over route-cell to handle nested views

@leontalbot: saw just ni time to also see you fixed :thumbsup:

the if-tpl macro uses the same mechanism as you're currently using with :toggle, except it removes things from the dom instead of hiding them

it doesn't do anything different with event handlers or anything

@thedavidmeister: you could use delegated handlers in loop-tpl, no?

why wouldn't that work?

@micha: should the snippet @thedavidmeister posted on https://clojurians.slack.com/archives/hoplon/p1458204887000228 work at all? Having a Cell of DOM elements passed as children to another element?

yes but then you are destroying and rebuilding that thing every time

so you need to manage memory then, or make sure the thing in the cell is a pure function

loop-tpl avoids all that complexity by using a pool of elements

yep, thanks

guess that was his problem

the cell= method will remove the children from the dom, but it can't make sure they get garbage collected

you'd need to do that manually if you have stateful things in there

this would be a Hoplon anti-pattern then

too easy to generate garbage

yeah i avoid it wherever possible

hey guys how's this sound for a pattern for a hoplon app that uses sente to do a lot of WS communication. Basically I'm sending a of messages to the server, most of which are responded to asynchronously. I have a 3 cells that are just lists of events: incoming-messages on which all incoming messages are conj'd, outgoing-messages, which messages are conj'd onto, and then a formula cell actually sends them to the server, and then user-inputs, a list of all user-input events. Then all ui components take as arguments formula cells that are some subset of these event streams, ie it will filter the incoming messages to just what it needs to display, and also take the actual event stream cells they may need to add an event to.

It's working ok so far I think, but my home-brewed architecture ideas have not generally worked great in the past so i worry a bit 😛

seems like it should work, I'm doing something conceptually similar but not through cells