define "directly" I clicked on clojure.org. I don't see the link. I stared at the page for a good 30 seconds. I don't see a "links" section. . . . maybe it's there and I'm bad at reading. Ah it's inline in the getting started dialog. In my opinion, that wiki link ought to be prominently displayed on the left, maybe even above rationale . . . .in fact, stick the rationale on the wiki page as the preface to the "book" . . . in fact stick the whole page on the wiki page . . . .and at that point why not just have the wiki on clojure.org. Trust me. I'm a newby, and Tim is being insightful in making a single, quick reference goto place for information on the subject of clojure . . . .a most curious thing to have be confusing given that there's a website on the topic, clojure.org.
I'm going to memorize clojure.org. Much harder will it be to memorize, go to clojure.org, then "getting started", then "wiki" . . .and then . . . hmmmmm no link so search what? . .. I dunno, go back to this thread . . .read read . . .ah yes, here it is, "By Example". So I can search on By Example, or I can find this thread. finally I'm there. Not Tim's fault. And I'm glad he's doing it. Consider this feedback and opinion. You are getting a data point on how one person thinks (or fails to think). On Tue, Jan 13, 2009 at 11:42 PM, Nick Vogel <voge...@gmail.com> wrote: > It is, that article is part of the wiki linked to directly from > clojure.org. > > > On Tue, Jan 13, 2009 at 11:12 PM, e <evier...@gmail.com> wrote: > >> i know that will be awesome for me. I just wish clojure.org was the only >> place I had to go to get stuff like that. Why not wikify it all there? >> >> >> On Tue, Jan 13, 2009 at 9:12 PM, GS <gsincl...@gmail.com> wrote: >> >>> >>> On Jan 14, 1:12 am, Timothy Pratley <timothyprat...@gmail.com> wrote: >>> > I've written small wiki article which dives right into the look and >>> > meaning of common Clojure constructs with examples. Personally I find >>> > I learn best by examples and when starting out they were hard to find, >>> > whereas formal descriptions were there but rather cryptic when you >>> > don't understand the context. My intention is to provide an initial >>> > understanding of how programs look, what they mean, and what can be >>> > accomplished because of their features... from which someone would >>> > then move to one of the more complete articles and references. >>> > >>> > http://en.wikibooks.org/wiki/Clojure_Programming/By_Example >>> > >>> > I hope someone finds it useful :) >>> >>> That's really good, Tim. I hope you continue with it :) AFAIC, just >>> about every function in core, set, zip and xml needs to be documented >>> by example. I'm just not smart enough to read the API docs of a lot >>> of functions and understand how to use them. >>> >>> Some efficiency could be gained by demonstrating several functions at >>> once, clearly labeling them. An example without much thought: >>> >>> (Heading) map, range >>> >>> (map sqr (range 1 10 2)) ; after defining sqr >>> >>> Cheers, >>> Gavin >>> >>> >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
