clojure-cookbook/clojure-cookbook

This is the home of O'Reilly's Clojure Cookbook - http://clojure-cookbook.com

clojure-cookbook's Issues

Polyglot Clojure <-> Java projects

The main road for Clojure developers is to code in Clojure and to optionally depend on some external Java based libraries/ frameworks. Clojure with its built-in Java interoperability makes this very easy.

In an enterprise Java environment, where introduction of new technologies such as Clojure might face some resistance due to risk considerations, a possible solution is to pick one component, code it in Clojure, and keep the rest in well known Java land. A Java interface, implemented in Clojure, and used from Java, requires an elaborate build setup.

contributor agreement pages aren't working at the moment

Filling out the form at http://www.clahub.com/agreements/clojure-cookbook/clojure-cookbook leads to the error page consisting of the text, "We're sorry, but something went wrong."

Possibly alternate arrangements should be made for CAs until that signing form can be fixed.

Recipe: Get tweets using the Twitter API

There should be an example of using Clojure to consume the Twitter API.

Potential updates for the Local I/O file list recipe

Here is a list of updates I'd like to make to the Get files from a directory recipe

• Threading macros in this recipe do not need parens wrapped around every single arg step.
• There is a keyword and few other bits of "cody" outside of a code block that could be wrapped in +s
• The file path splitting here is not actually platform agnostic, it'd be best to rely on something coming out of #76 to solve this.

Recipe: How to read a stack trace

How to read a stack trace to figure out which form (which may be deeply nested) is failing.

Add asciidoc toolchain help in README.md

Editing the raw asciidoc source is a frustrating way to preview one's own recipes. I managed to get asciidoc running and generating HTML copies of this book locally for editing purposes, but the following hints, perhaps added to the README, would be helpful:

1. clojure syntax highlighting. This required a bunch of googling around but I was eventually able to get this to work.
2. PDF generation. Some things[1] would be easier to check/preview/test if we could make our own PDFs. I still haven't gotten this to work with asciidoc/docbook.

I'm willing to help out on this one but could use help with (2).

[1] footnotes

Fix how simple-statistics call-outs render

Presently the ASCIIDoc callouts in the simple-statistics recipe are messed up in draft book renderings.

Make them not messed up.

(This one is probably most do-able for @levand or myself–that is unless you are able to compile the book.)

Idea: Parsing command line arguments

Problem: You want to parse command line arguments and use them in your command line application.

Connect to and query a datomic database

Idea: Setting up a development environment in vim

Starting with a fresh install of vim, what's a good setup to have? fireplace, nailgun etc

Problem: Specifying library versions??

A lot of problems can be practically solved by referring to third party libraries. The twitter api is an example of this.

We can specify versions within each recipe, but I wonder if we shouldn't just mention the library versions in the description and where people can grab the latest release.

Thoughts?

Idea: data validation

I was thinking of creating a recipe for a pattern I use to validate input by applying a vector of validation functions and reducing to a set of booleans. Not sure where that would belong in the structure of the book, though. Any Ideas? Speaking of ideas, I can't seem to add a label to this issue. Looks like I have to be an existing contributor?

Chapter Idea: Practical uses for core.logic

How about a chapter about practical use cases for core.logic?

Recipe: Parsing CSV in Clojure

Parsing CSV formatted files is incredibly common, we should show a good example of it.

Cross reference examples using file-seq with "Get files from a directory"

There are currently a few recipes in the Local I/O chapter that utilize file-seq with clojure.java.io/file to get a list of files from a directory. Any such recipes should include an AsciiDoc Internal Cross Reference from those recipes See Also section to the Get files from a directory recipe.

The reference will look something like this:

===== See Also

* <<sec_primitives_strings_re_find>> for testing a string for the
  presence of a pattern.

and the target recipe will look like this:

[[sec_primitives_strings_find_replace]]
==== Performing Find and Replace on Strings

Build a join query across multiple Datomic databases from a single peer

Recipe (math): Add standard deviation to existing statistics recipe

Idea: Setting up a development environment in LightTable

LightTable (http://www.lighttable.com/) is alpha, but even in this early stage outperforms regular editors (be it emacs, vim, sublime, ...) in terms of developer productivity.

Build a WAR archive from a web application

Idea: platform agnostic file path splitting

It is a tad bit tricky to correctly split file paths in Java. Write a recipe covering an adequate technique (See pedestal's app-tools for an example.)

Add recipe for pulling apart a composite data structure - i.e., destructuring (composite data)

Understanding destructuring in clojure is extremely important for writing concise code and understanding idiomatic clojure code. It would be useful to add a recipe for destructuring vectors, maps, and strings to the composite data section.

Use OAuth to log in to a Clojure webapp

Most webapps need a login. OAuth is a common choice. We should have an example of this.

Make CONTRIBUTING.md or README.md more clear about what recipes already exist

For instance, the "strings" section of primitive-data is not very vocal about existing.

Optimally this extra information might make it clear how complete a section is.

Recipe: Build dynamic, data-driven charts & graphs in ClojureScript

Interactive charts and graphics are all the rage; we should have an example of how to build them from Clojure data on a ClojureScript page

Use a message queue for communication between members of a cluster

Recipe (strings): Escaping character literals

How do I do it properly?

Potential updates for the Local I/O file copying recipe

Here is a list of updates I'd like to make to the Copy a file recipe

• Use AsciiDoc callouts for safe-copy example. (This may be a bit difficult for others until we get better instructions for rendering.)
• Possibly include an example of using Reader/Writer with clojure.java.io/copy
• Discuss possible implications of buffer size being what it is. What does this mean when using the function.
• Make Fixup link to "Reading and writing files" on L70 a proper AsciiDoc link. ([[sec_....]] and <<sec_...>> pairs)

Idea: I'd like lots of examples of development pipelines and ways to debug error messages

I've documented what I'm asking for thoroughly on HackerNews here: https://news.ycombinator.com/item?id=5869422

For a more in depth example of what I struggle with, check out this SO question I asked: http://stackoverflow.com/questions/16901836/how-do-i-get-better-feedback-from-clojure-errors

Idea: Pedestal Recipe

I'd be happy to give this a shot. Do you think it's stable enough to get its own recipe?

Idea: Web scraping example with a few different libraries

My idea is to provide some trivial html and then scrape it the same way with at least Enlive and Laser.

The example would be as short and simple as possible, intended to show you how to load the html with each library and let you compare their syntax. I have to look up these semantics every time I switch between these libraries.

Recipe: Converting between strings, symbols and keywords

Idea: mention REPL-driven development

It'd be great to sum up REPL driven development a la my Clojure/west talk Editing Clojure Effectively with Emacs. I will do this in the near future, but if someone else wants to tackle this let me know.

This recipe should be cross linked with the Exploring Clojure section.

Idea: Coding a transactional database using Clojure reader literals

See this blog post by @malcolmsparks

http://blog.malcolmsparks.com/?p=67

Question: Can I post my work on my blog

Hi,

a little question, just to be sure and to don't mess around.

If I write recipe for you, then there are any problems if I publish my own recipes on my own blog ?
O'Reilly is fine with that ?

Idea: read a single keystroke from the console

As covered in this SO post and others: http://stackoverflow.com/questions/13435541/reading-unbuffered-keyboard-input-in-clojure?lq=1

I might take this one if nobody else wants it ASAP.

Idea: read (parse)/write binary data files

If someone will +1, I can provide a recipe under local-io.

Deploying a system using Pallet

Connect to and query a relational database

Send data using edn as wire format

De/serializing Clojure data <=> edn and using it in a web context, as a data storage format, etc. would be useful.

Idea: Local IO XML

I have started to put together read/write of XML for addition to the local io chapter. If that sounds like a good idea you can put this one to in-progress and I'll will keep working on it.

Idea: Extend native java types!

Extend Java native types. For example, we could add an isPalindrome? method to java.lang.String via extend-type:

user=> (defprotocol Palindrome
  #_=>   (isPalindrome? [this]))
Palindrome
user=> (extend-type String
  #_=>   Palindrome
  #_=>   (isPalindrome? [this] (let [base-string (-> this
  #_=>                                          (clojure.string/replace #"[,.! ]" "")
  #_=>                                          .toLowerCase)]
  #_=>                               (= base-string
  #_=>                                  (clojure.string/reverse base-string)))))
nil
user=> (def test-string "A man, a plan, a canal. Panama!")
#'user/test-string
user=> (class test-string)
java.lang.String
user=> (isPalindrome? test-string)
true

What about image ?

Should we include images if necessary ?

There are dimension that we need to stay in ?

Chapter idea: Fun Problems

The current proposed chapters look pretty comprehensive. However, one Chapter that I find missing is "Fun Problems". These are problems that are just fun to solve. Example recipes in this chapter could be various kind of algorithmic problems or puzzles or other misc. stuff which are fun to solve. Like:

• Knight Tour on a chess board
• 8 Queen's problem on a chess board
• Various logic puzzles
• Some of the problems at http://projecteuler.net/problems

I could contribute many of such recipes for this chapter. e.g. Look at some of the problems I have solved in python at https://github.com/nangia/funproblems and in clojure at https://github.com/nangia/funwithclojure. While there is no detailed documentation that I have put in on github yet, I can write up detailed recipes for the book to explain how these can be solved.

Thanks and regards,

Sandeep
http://in.linkedin.com/in/sandeepnangia/

CONTRIBUTING.md should include instructions on recipe dependencies

As per the discussion in #54 CONTRIBUTING.md should include instructions on how to introduce a library dependency to a recipe both in its own project.clj (this may necessitate fleshing out the sub-project story) as well as how to tastefully mention this possibly versioned dependency to the recipe text itself.

Support both `recipe.asciidoc` and `recipe/recipe.asciidoc`-style recipes.

Presently a recipes ASCIIDoc file must live under a sub-folder per recipe (i.e. my-recipe/my-recipe.asciidoc). It should be possible to exclude the sub-folder for simple recipes (i.e. my-recipe.asciidoc)

Idea: Example use cases for each of the concurrency primitives

When to use agents/ refs etc

Idea: Manipulate lists of non-trivial data

For example, compare lists of time-slots. A time-slot being an arbitrary length of time defined by a point in time and a duration. The recipe could show how to find overlaps of time slots (say for a scheduling system) via intersections of the times in multiple lists. Another manipulation could be to find open time slots (as in a booking system).

The point being would be to show the utility of the union/difference/intersection/etc functions, but not just on plain/simple lists. The above example is complex enough to not be trivial.

Idea: Publish a library in clojars with lein

I believe is necessary to show how to publish a library using lein in clojar

credits need to go here too, thought.
https://github.com/technomancy/leiningen/blob/stable/doc/TUTORIAL.md#publishing-libraries

Deploy a system using Chef

Edit a bitmap image

Java (and by proxy, Clojure) is capable of low-level graphics manipulation. Including an example of this would be interesting.