Something that I've always wondered - why is ClojureDocs not updated? I've
never tried to contribute to it - is it particularly difficult? Is it
impossible for users to add support for new Clojure versions? If so, who
runs it? Could it be turned over to the community?
On 11 September 2013 17:55,
I've just picked up on this thread but I've spent quite a bit of time
barking up this tree.
There are three repos that power the old version of the site
https://github.com/zk/clojuredocs - the Rails 2 frontend
https://github.com/zk/clojuredocs-analyzer - the clojure analyzer that
extracts data
Having clojuredocs updated would be a fantastic thing. As a website,
it's really nicely done, and very usable. But, it will become
increasingly irrelevant if it remains out of date.
Even better would be to have clojuredocs support additional libraries,
perhaps with some selector so that the
+1
On Sep 11, 2013, at 10:42 AM, xavriley wrote:
I've just picked up on this thread but I've spent quite a bit of time barking
up this tree.
There are three repos that power the old version of the site
https://github.com/zk/clojuredocs - the Rails 2 frontend
Hey all,
Lee Hinman (dakrone) is the current primary maintainer. There was a good
discussion about clojuredocs last year at the conj unsessions and I think
the primary driving note that came out of that was that it would be useful
to have the concept of version in the database (that is,
2013/9/11 Alex Miller a...@puredanger.com
I talked to him recently about the state of clojuredocs. I know he's been
pretty busy lately with a new job. I believe he thinks the service API and
doc extractor are in pretty good shape. The major areas that need work are
figuring out how to store
On Wednesday, September 11, 2013 1:55:45 AM UTC-4, Steven Degutis wrote:
One of my assumptions was that people don't use wikis simply because
it's Yet Another Account to sign up for, {snip}
I don't think that's it. Public wikis can be alright if assiduously
maintained... Ok, I'll stop
Here are some thoughts about versioning and examples that were driving
my github-wiki idea:
- Incompatibilities between Clojure versions are getting fewer and smaller.
- This suggests that jumping from 1.4 to 1.6 will probably be a lot
smaller than a jump from 1.2 to 1.3.
- This implies that
Hi everyone,
I'm interested in jumping into this project. Lee and others have already
written some great tools and an API for importing and searching
documents--it's mostly a matter of building a web app that uses them. You
can find them in the Clojuredocs group https://github.com/clojuredocs
Thanks :)
By the way, it's probably *not* a good idea to use this github-wiki
version of clojuredocs. Everyone's still using clojuredocs.org, and we
don't want to scatter data (examples, etc) between two websites.
My reason for posting this was to hear the community's thoughts on
this alternate
On Sunday, September 8, 2013 4:07:33 AM UTC-4, Steven Degutis wrote:
https://github.com/sdegutis/clojuredocs/wiki
{snip}
Thoughts?
Hi Steven,
This is a nice piece of work. Thank you.
Some thoughts:
* Wikis are difficult to keep nice. And, seemingly contradictory to that,
it's
All very good points.
One of my assumptions was that people don't use wikis simply because
it's Yet Another Account to sign up for, so this being hosted on
github would be a much lower barrier-to-entry for contributing
examples. But I'm not sure that's a valid assumption for anyone
besides just
That's really cool! Was always wondering if there's gone be something like
that ever.. Gonna be visiting often! Wish also that it'd be near
clojuredocs in search results if you google like clojure parse, but
that'a a different effort, I suppose.. keep up!
воскресенье, 8 сентября 2013 г.,
ClojureDocs.org is pretty awesome, I think I use it nearly every day,
especially for the Examples and See Also sections. But sometimes I've
been wishing it had Clojure 1.5.1 support. For example, I think as-
and cond- would have been easier for me to pick up had there been
entries for these with
I use clojuredocs daily and would definitely benefit from it being as
up-to-date as possible. I wasn't even aware of those two macros you listed,
which is a bummer and a good indication that a replacement might be
warranted.
I'd be happy to use your wiki as a day-to-day reference, or we can
15 matches
Mail list logo
