any reagent benchmarks against om elm etc?

I’m reading the changelog for the upcoming release https://github.com/reagent-project/reagent/commit/348ac4aaf86dd120d0aa254dc06c5efa5991ce22 Anyone know what "Support [:> nativeComp {:foo "bar"}]” will mean?

> jstew: I feel all warm and tingly inside. I figured out how to make select2 work with reagent (albeit in a hacky way but it works)

@jstew you are sitting on top google closure library which has the bestest autocomplete made by human being.

why hacking into select2?!

@mike: unfortunately to make it work with an opinionated bootstrap theme that looks gross unless you use their components (Flat-UI)

closure library's ac should fit nicely with reagent.

It's not even for the autocomplete functionality.

select2 is pretty cool anyway

bloated.

what is a google closure library that can be used instead of select2?

http://google.github.io/closure-library/source/closure/goog/demos/autocompleterichremote.html http://google.github.io/closure-library/source/closure/goog/demos/autocompleteremote.html http://google.github.io/closure-library/source/closure/goog/demos/autocomplete-basic.html

and free advanced optimization.

at the very least you could go with http://jedwatson.github.io/react-select/

but it's not as nice as closure ac, IMO.

I had never heard about those

I can't really complain, select2 relies on jquery and has it's own API. Which is understandable considering that it wasn't designed with react or clojurescript in mind.

yeah, I don’t have issues with select2. Finding google closure alternatives isn’t so easy.

@jstew: what about the overhead? you're using clojurescript which comes with closure library stuff and then on top of that you'll have jquery.

i think the overhead isn’t a problem, the main focus is getting it built. If it isn’t built, you can’t worry about overhead anyway

damn, even googling for Automcomplete Remote Google Closure doesn’t return good results

that's because closure library is hugely underrated 😞

but you know what...

the input box that you just googled with...

that's the very same autocomplete by closure library.

There are not many entry level tutorials for the closure library and the docs aren't the greatest either.

it looks good, but for someone that is not familiar with the google closure ecosystem, it is difficult to find. While I don’t have to be familiar with jquery to find select2 and start using it.

I'm really surprised.

That's what I've been finding when I have to work with it. Luckily there are smart people in slack that I can get info from

clojurescript is shipped with closure library interface.

now that I know about closure’s autocomplete, I’ll investigate it some more, but really, the closure libraries and ecosystem is obscure

also, you're using reagent, which is based on react.

the last thing that you want to do is to go back to jqeury ui.

Honestly, the documentation for GCL is just bad, I can't really understand it (but same goes for documentation of most Java libraries).

what am I missing here?

clojurescript is also shipped with google guava, do I have to know that or be concerned with the libraries in google guava

@jaen I agree, but there is (only one) excellent book on it.

select2 is shipped with jquery, doesn’t mean I have to know every single library or utility in jquery

also look the github project, google started to take it seriously after many years of public inactivity.

it is also probably an opportunity to write good docs about google closure.

from personal experience, google documentation is horrible

the only one I’ve had a good experience with was Guice

@roberto please give that feedback in https://groups.google.com/forum/#!forum/closure-library-discuss

this is reference not docs http://google.github.io/closure-library/api/

I don;t know why google does this.

I'm really mad at them.

yeah, I just had to write an app that uses their spreadsheet API

reading through their docs was a nightmare

maybe they don’t care about good docs because they are more focused in getting internal use.

clojurescript is the only open source project that got closure library power right.

maybe they have better docs internally

which part of documentation is the problem?

the code itself is very very much documented.

Also re-com has a pretty nice select component. I've cannibalized it once to add multiple selection and was quite satisfied.

(and annotated)

I think this is exactly the problem

it's very easy to follow the code.

While understandable and commented code is good

it is not a substitute for documentation

It's easy to understand the code if you know where to start and what to look for.

just start from the demos.

i won’t go reading code (especially javascript code) when I’m on a deadline

it's not a jquery style code

i have never had to dig into jquery source code

closure library is made to be readable by a huge team.

I meant a jquery based ui component.

when I’ve had to read jquery code, it was mostly for educational purposes. But most of them are very well documented.

and yes, I agree, closure is superior, but if the docs are horrible, it won’t get much usage.

again, the api docs are excellent.

api docs don’t help

duh.

api docs are useful when you know what you are looking for

I can’t point a java newbie to the java api docs

doesn't clojurescript work with closure library out of the box?

it won’t help them

yes, and backbone works with jquery out of the box

maybe my impression is wrong.

so that's all you need.

so, if I use your analogy

someone coming to clojure, without any java experience

should be able to understand java code

var tcMovies = [
        "Mission Impossible", "Top Gun","Jerry McGuire","Rain Man",
        "Days of Thunder", "Risky Business","Interview With The Vampire",
        "Eyes Wide Shut","Far And Away", "Jerry Maguire","The Firm","Cocktail",
        "A Few Good Men","Legend","Taps", "The Outsiders","Losin' It",
        "Endless Love","The Color Of Money", "All The Right Moves",
        "Minority Report","Magnolia","Mission Impossible 2",
        "Mission Impossible 3","Vanilla Sky","Ghost Soldiers","Few Good Men A",
        "Color of Money The","Firm The","Mission Impossible II","Outsiders The",
        "Young Guns","Top Gun DVD","Days of Thunder DVD","Coctail",
        "Mission Impossible DVD","Fallen Angels Vol 1","Don't Look at Me",
        "Young Guns uncredited"];

    var ac1 = goog.ui.ac.createSimpleAutoComplete(
        tcMovies, document.getElementById('txtInput1'), false);
    var ac2 = goog.ui.ac.createSimpleAutoComplete(
        tcMovies, document.getElementById('txtInput2'), true);

this is all you need for ac.

how do you make something like tags that you can do in select2?

it has remote and rich remote, but no tags mode.

it should be easy with reagent.

that's the whole reason I'm trying to start with clojurescript.

closure library ui is verbose to extend.

I'm hoping react based components make it easy.

But how do you customise it?

Select2 has a lot of customisation

This doesn't seem to

what if I want a different matching algorithm?

it has an extensive matcher.

tag mode is just a visual trick. after entering, you just keep a list of elements with tags style.

yeah, select2 might be inferior code wise, but you can build something much faster by just reading the docs.

That is why just the apis don’t work as docs. You have to know about ‘matchers’.

https://github.com/rackt/react-autocomplete it's much easier with react.

for example

https://github.com/google/closure-library/blob/master/closure/goog/ui/ac/richremotearraymatcher.js

But you know about it

that react autocomplete looks better tho. Even the source code is much easier to understand than closure's

I wouldn't even know how to look for it

@jaen that was the point I was trying to make

When I wrangled with Google Closure Compiler I had to figure out what it's doing with trial and error

No docs at all

And it was really annoying

I donno guys,.. I've always enjoyed and learned a lot from closure library.

when I build a component on closure lib, I know it's rock solid, works down to ie 7.

if you cannot take my word, hear it from the man himself:

https://youtu.be/tVooR-dF_Ag?t=21m19s

@roberto: yeah, I agree with that point, when all you have is javadocs you don't really know where to start biting into the library. For a university project I was doing a Clojurescript frontend for a backend in Groovy. When I had to modify that for my convenience and there wasn't much docs besides API docs figuring out how the hell do I change data serialisation format took me literally hours.

yeah, people confuse api docs, tests and source docs for good documentation on HOW to use something.

The others are good if you want to know how something works.

most of the time I don’t care how something works, I just want to know how to use it.

I dunno, not saying Rich made a wrong decision building on GCC and GCL, the tree shaking thing is pretty awesome, but I think he might have the Java mindset - if there's Javadocs then it's awesomely documented and readily usable. I despise Java and Javadocs give me nothing in the way of understanding how to deal with something. I tried to use this once - http://oltu.apache.org/ - because all Clojure oAuth provider libraries were missing refresh tokens and this lib had it and I couldn't make head or tails of how to use it.

yeah, javadocs are good as a reference, which you need once you are familiar with a library. But if you are not familiar with it, javadocs are not much help.

it is like saying, if you want to learn OCaml, this should be enough http://caml.inria.fr/pub/docs/manual-ocaml/libref/

oracle has awesome java tutorials

tbh

Won't make me want to learn it anyway xD

https://docs.oracle.com/javase/tutorial/

it would be cool to get a full stack reagent app running on node

tmtwd: You mean like electron + reagent and clojurescript on the backend with node?

no

but thats kinda cool too

does anyone know how I could make a non-component function run after every react update?

i've got components running db transactions and I want to combine the transactions and only actually transact! them after the components are done rendering

maybe I could use a reaction and deref it in the main app component

@mpdairy: i think that would call your function BEFORE the components start rendering.

but assuming componentDidUpdate is called depth-first (parents called after children) maybe you could put your function at the top-level component

but that is an assumption of mine. i have no idea if it’s correct