Eliminate "couchapp" support?

[Chas Emerick]

In the process of my experimenting with supporting the CouchApp idioms for organizing views and assets on disk, I implemented a very limited form of disk <=> CouchDB synchronization in Clutch, in the com.ashafa.clutchapp namespace. However, since then, the CouchApp concept and its canonical python implementation[1] has matured and expanded — IMO, anyone building CouchApps, or using its idioms for organizing data to be synchronized to/from CouchDB, should be using it instead.

I've long since stopped using and sadly neglected the implementation of it in Clutch, and I'd like to simply drop it from the Clutch API.

Any objections?

- Chas

[1] http://couchapp.org/

[pepijn (aka fliebel)]

As long as there is a better alternative, no objections.

If you set the language of the design doc to clojure, can you just
stuff Clojure source files into Couchapp?

You wrote a method to get ClojureScript views into Couch, is that
suitable to push Clojure as well?

Pepijn

[Chas Emerick]

Yes, I would think .clj files on disk would get sync'd up via the official couchapp toolchain.

The changes made in 0.3.0-SNAPSHOT unify the idioms for working with view server code in Clutch, regardless of language; aside from the :language and other options you might pass along, the same view-server-fns macro is used.

- Chas

[Chas Emerick]

FYI, the latest 0.3.0-SNAPSHOT and the corresponding branch in git[1]
no longer contain the cluchapp namespace.

The lack of tears and gnashing of teeth seems like all the clearance I
needed. :-)

- Chas

[1] https://github.com/ashafa/clutch/tree/0.3.0