Good suggestion about the categories. Making it browsable is important. A page that uses categories from the cheatsheet is easy to make. Adding categories/tags and auto-generating such a page is also doable.
Code contributions are welcome. I'm not attached to App Engine; I just used it to learn about the platform. The code could be modified to work with any storage backend. I'll be spending free time in the next few days writing real examples and seeing if anyone else follows suit. If it doesn't gain traction, or someone else has a better approach, adding fancy features and re- architecting is moot. Justin On Jul 2, 5:09 am, kredaxx <kred...@gmail.com> wrote: > On 2 Lip, 09:46, Justin Kramer <jkkra...@gmail.com> wrote: > > > > > > > Partly in response to this issue and partly to get my feet wet with > > Ring and friends, I spent the last few nights writing a proof-of- > > concept Wiki to collect structured Clojure usage examples: > > >http://clojure-examples.appspot.com/ > > > Here's a sample function page: > > >http://clojure-examples.appspot.com/clojure.core/contains%3F > > > I tried to come up with something that encourages a many-hands > > approach while maintaining structure and quality. There are plenty of > > missing features, but it should be easy for anyone interested to jump > > in and write some examples. It uses a modified version of Markdown for > > syntax. Content could be exported/parsed en masse relatively easily. > > > The source is on GitHub:http://github.com/jkk/clj-wiki > > > Does this seem like a worthwhile approach? > > > Justin > > Great! I was thinking lately of building something similar with the > same kind of approach. > > One suggestion: the core functions should be structured into > categories rather than listed alphabetically., that is for example: > > Maps > - fn1 > - fn2 > - fn3 > Vectors > - fn3 > - fn4 > - fn5 > Arithmetic > - fn6 > - fn7 > - fn8 > etcetera. > > (Similar to what is in the cheat sheet) > > This would eliminate the tersness and it would be much easier to find > a specific function (handy for newcomers to clojure) > > Other than that great job, I think it has big potential. It's clean, > and easy to contribute. I will surely add some examples later today. -- 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 Note that posts from new members are moderated - please be patient with your first post. 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
