This stuff looks great, as always. A few questions (I'm sure some of
this will be in the coming documentation, but asking just in case):
1. I didn't see anything for event handling, is Pinot still the
preferred method there?
2. Is Pinot effectively being deprecated otherwise?
3. What is the preferred method for including these dependencies?
4. Does using jayq rule out advanced compilation?
5. Would you consider a wiki for documentation, editable by approved
members, or even public? The documentation on github and your branded
sites has been great, but it might be nice for many to have one
location to access overviews, tutorials, examples, and api
documentation for the "Chris Granger Collection", as well as easily
being able to see how all of these projects interrelate for web
development.
Thanks again, I'm looking forward to getting into this stuff deeper.
- Mark
I don't think the need is pressing, but the thought was more of down
the line, something that provides a big picture view, and can handle
multiple versions of noir/jayq/fetch/crate/monet/korma/etc, would be
very beneficial, and may be more work than one person wants to take
on. While all of these packages are great standalone, they also work
great together, and having one place where people can discover all of
the pieces available in this collection, where they fit in the web
development puzzle, and which pieces they would like to use might be
nice. And with respect to multiple versions, as more people are using
noir, et al, in production, and as these packages advance, there will
necessarily be multiple versions in use, and having the documentation
available for multiple versions may be necessary.
I was thinking something along the lines of clojuredocs.org, where
people can add examples and comments for the entire api, but really my
comment was more about planting the seed for something down the road.
- Mark
One possible extension of the One model would be to include on the
branding site an incubator page where people who have extended or
modified the examples can put up short descriptions/tutorials with
their own variations. That would allow Chris' work to benefit from a
little crowd-sourcing and be a potentially awesome resource.
Thanks for releasing this CLJS code, Chris. Already read most of it
and learned a lot.
Chris, thanks for the great work you've given us in the past months! I was eager to know your plans for the future of Noir + Pinot, especially in relation to ClojureScript One.jayq - Bringing back jquery to the _masses_ of ClojureScript developers! I was surprised when you said jquery is the most battle-tested library out there; but obviously, you must be right. Although GClosure is battle-tested in Gmail and other big-name Google applications, I understand you feel that jquery is much more battle-tested thanks to its usage in almost everything else that's displayed in our browsers nowadays. One thing I'm sure, though, is that Google absolutely needed advanced compilation a while back to be able to make Gmail's javascript footprint not blow IE6's limits. That said, I understand that you consider we generally don't have such constraints, and wouldn't be using ClojureScript in the first place if we had them. So in the end, I definitely relate to your thinking; jquery is inevitable nowadays and GClosure doesn't feel as approachable and usable. Moreover, if Google ever migrates Gmail and their other big apps to a GClosure-over-Dart, they will obviously stop investing in the GClosure-over-JS that we know today.