From user-return-4936-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Fri May 22 17:32:54 2009 Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 93886 invoked from network); 22 May 2009 17:32:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 22 May 2009 17:32:52 -0000 Received: (qmail 67915 invoked by uid 500); 22 May 2009 17:33:04 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 67839 invoked by uid 500); 22 May 2009 17:33:03 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 67829 invoked by uid 99); 22 May 2009 17:33:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 May 2009 17:33:03 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ben324@gmail.com designates 209.85.218.170 as permitted sender) Received: from [209.85.218.170] (HELO mail-bw0-f170.google.com) (209.85.218.170) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 May 2009 17:32:54 +0000 Received: by bwz18 with SMTP id 18so2087762bwz.11 for ; Fri, 22 May 2009 10:32:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=xywLkhXMpIJ4deJJeKhdzN2LfknoBXuh5U/ReFcEzOM=; b=rhlHt+r/Q0RI9Fi8KeAbfn7WHYFa/TYgQzwPHednotmxADwibN0+LLp1ea5iuZeVqj JPWymsRyVqVSq6vDXPclrdYMcfI+AlmGSFEeZ8L3aRs4S+thU1RlLAii/DBPRAiO3A7A 9yDrB1DTOG/SBwO8Bl1Chp7sFiSzQ4q3UAUT0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=oyjlviBpcjQVAVqoYd/J0tyQHqEVMlA6EdDDZM8fDGji8fdpsbZ8WQ0lRjkI7s0A0J TQKjzVFSICk+NHV7n3cM7tpQfYl55YEB/3386olbuE46cXfiU1NdVNsataicPu4bcGTJ 2M103DoXgM0zOAO8RGFRheRRyqGuQ0vTkCWJ4= MIME-Version: 1.0 Received: by 10.204.117.203 with SMTP id s11mr3782933bkq.153.1243013554176; Fri, 22 May 2009 10:32:34 -0700 (PDT) In-Reply-To: References: <1B75DD93-C2D3-442D-A10E-6926910F4255@apache.org> Date: Fri, 22 May 2009 13:32:34 -0400 Message-ID: Subject: Re: I'd like a dish of JavaScript Awesome, please! From: Ben Browning To: user@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org I'm not working on this to be a futon replacement or any other grand goal - it just looked like a fun thing to do. There are lots of unsolved problems and I'd love some discussion around potential solutions: Authentication - right now I punt and just log you in as a fake user. I saw some discussion on getting cookie-based auth in CouchApp and we'd probably need something similar to have a usable auth system. Filesystem implementations - I really have two ideas here. The first is to make every CouchApp on a given database(can I do cross-database? probably...) a Project in the Bespin world. Then, all the app's attachments would appear as editable files in the dashboard. The second part is to have regular CouchDB docs appear as files enabling you to edit docs, views, etc with nice javascript syntax highlighting. My next main focus is getting at least one of these two options fully functional for CRUD stuff. Dojo vs jQuery - Bespin uses Dojo for all its javascript. There are a few nice CouchDB helper functions written in jQuery. Should I just include both or make a special port of those helpers to Dojo? Thanks for all the positive feedback. I've got a Slicehost box sitting idle so I'll try to carve out some time to install trunk CouchDB and push my Bespin stuff there for people to play with. Then, as I make code updates, you can just couchapp clone or use couchdb replication to keep your local copy updated. Ben On Fri, May 22, 2009 at 12:27 PM, Benoit Chesneau wrote: > 2009/5/22 Paul Davis : >> Benoit, >> >> Once its a couchapp we can look at integrating it into the >> distribution and what not. It would be awesome to have something as a >> default install, but there are all those questions about licensing and >> what not. As always, these questions are always easier once we have >> code to look at. > > mmm I didn't think about integrating in official couchdb which would > be dificult indeed considering the license. And the fact that it works > only with mozilla. I thought more about a line we add to local.ini > like > > _couchapps = {couch_httpd_misc_handlers, handle_utils_dir_req, > "/somewhere/couchapps"} > > Wich isn't really difficult and would allow to distribute it as a > plugin. Just a talk. That's just for me this is more like futon rather > than a couchapp. > >> >> And depending on what the lawyer type people say, this could be the >> motivation to get that fancy dancy public app hosting node so people >> can see what its like to install an app via replication. >> > > agree. > > - benoit >