Thanks everyone for the feedback. It was good to think about Johs comment that there also tends to be server-side document that define the server-side processing. We have so little of that in our current demos of our product that I hadn't considered it (the vast majority of action in our product happens in the client).
Martin - given that our tools are sort-of purpose built for our product, it might not be convenient to use them with other JS frameworks. You'd have to mess around with the directory structure - it might be possible. Our stuff will be available under an Open Source license. Note that the Couch stuff is only one (small) piece of an overall larger, full stack framework. We'll have a lot more to say in the next few weeks :-). Cheers, - Bill On Sun, Nov 15, 2015 at 1:22 PM, Johs. E <[email protected]> wrote: > Hi Bill, > I think your “couch-served apps” is a good candidate for a term to could > adopt as replacement for couchapps. > > I use "applications in CouchDB" rather than Couchapps. > An application in CouchDB to me is one or more design documents that > define the server side processing as well as define what modules to load > client side. > > johs > " > > On 15 Nov 2015, at 17:40, William Edney <[email protected]> > wrote: > > > > I know there are other products out there that do similar things to ours. > > Does the term 'Couch-served app' make sense to folks and should we be > using > > it this broader context or does someone have a better suggestion? > >
