Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 39365 invoked from network); 27 Jan 2011 10:05:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 27 Jan 2011 10:05:48 -0000 Received: (qmail 39970 invoked by uid 500); 27 Jan 2011 10:05:46 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 39533 invoked by uid 500); 27 Jan 2011 10:05:43 -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 39525 invoked by uid 99); 27 Jan 2011 10:05:42 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Jan 2011 10:05:42 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of rasmussen.bryan@gmail.com designates 209.85.214.180 as permitted sender) Received: from [209.85.214.180] (HELO mail-iw0-f180.google.com) (209.85.214.180) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Jan 2011 10:05:36 +0000 Received: by iwn37 with SMTP id 37so1870906iwn.11 for ; Thu, 27 Jan 2011 02:05:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=jXnYdqz7skRiWr72JUxDRME1lQy4Ym8wLTfOd8Pe0Wo=; b=WcK75OmyZHfyV/fQ9kQNVUzTFuxKU6budAluey+P5bSXCrpwYMx+E+XECS+YAe8Pyx T6FRw7jCpvUhQVI/qWiRhaitPDPIF37KqCypFMMEuMzKNGBM8WUgABDBM2TSvavsD50D YYmSewndBe2nhIHgnWSlUE5KwrLFovSDyvDQw= 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=CBN9A0uZ/XuXAcHL5iuFwHHNyPM7I6PrR9yojOJQDuuIP6E8qUdN33jXVGJk+BEPYk 0240W/4dX+sdjDFS3gf/TrVvIKwzEKvUAEizq9Vq1GLT38AdVAX1hx2xqMwRdkjzEL43 ML+3PnlaVxFHhb8TckehLuPXTilGk4BLz4nCM= MIME-Version: 1.0 Received: by 10.42.178.70 with SMTP id bl6mr1926367icb.28.1296122714848; Thu, 27 Jan 2011 02:05:14 -0800 (PST) Received: by 10.42.240.68 with HTTP; Thu, 27 Jan 2011 02:05:14 -0800 (PST) In-Reply-To: References: <3932D9F0-B92E-4B02-B37C-A71A89549EC6@mac.com> <6D65615D-89C8-42A2-A648-4234837CBE15@me.com> Date: Thu, 27 Jan 2011 11:05:14 +0100 Message-ID: Subject: Re: native support for url-shorteners and qr codes? From: bryan rasmussen To: user@couchdb.apache.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Hi, I would just like to say as a couchdb newbie I would like some sort of show functions libraries... Best Regards, Bryan Rasmussen On Thu, Jan 27, 2011 at 10:41 AM, Wout Mertens wrote: > QR generator in Javascript + Canvas: > http://www.cipherbrain.be/wp/posts/main/2010/05/canvas-qr-code.html > > QR generator via Google Charts API: > http://code.google.com/apis/chart/docs/gallery/qr_codes.html > > Either of these is trivial to put in design documents or show functions. > > Wout. > > On Jan 27, 2011, at 4:21 , Keith Gable wrote: > >> That's what I'm suggesting. QR codes can store data that's meaningful >> in a ton of different ways to different people (URLs, contact info, >> serial numbers, etc.). There ought to be a QR code function in the >> client-side JavaScript standard library (I don't use CouchDB for >> CouchApp functionality so I don't use show functions or anything... >> not sure how the client does any of that), but it would be up to you >> to define what goes in it. There's not a "standard" way that CouchDB >> could output the QR code and make everyone happy. >> >> On Wed, Jan 26, 2011 at 6:02 PM, Nikolai Teofilov wrote: >>> I am on manufacturing field and I am about to integrated the QR codes a= s a part of the production system for tracking the URL to the document in t= he data base that keep information about the product with 2D-barcode scanne= rs. There is API for generating uuid-s and I thought would be nice to have = some of the url features as utility APIs integrated. >>> But actually you are right it is application logic and could be easily = implemented as a show function in a couchapp. >>> >>> >>> Begin forwarded message: >>> >>>> Date: 26. Januar 2011 23:31:04 MEZ >>>> Subject: Re: native support for url-shorteners and qr codes? >>>> Source: user@couchdb.apache.org Archives >>>> Author: Keith Gable >>>> >>>> On Wed, Jan 26, 2011 at 3:46 PM, Benoit Chesneau = wrote: >>>>> On Wed, Jan 26, 2011 at 10:00 PM, Nikolai Teofilov wr= ote: >>>>>> I'm just curious why not ship couchdb with native support for url sh= orteners and >>>> qr codes. This might be very helpful. >>>>> >>>>> why native support ? >>>>> >>>> >>>> +1. >>>> >>>> My 2 cents follow: >>>> >>>> CouchDB is a database... You wouldn't SELECT QR_CODE() FROM users >>>> WHERE id =3D '1234' or SELECT BITLY_URL('appid', 'secret') FROM articl= es >>>> WHERE id =3D '1234'. >>>> >>>> Also, assume that CouchDB is able to figure out the self-referential >>>> URL for an object. Is that what you want in the QR code? If the >>>> document describes a person, wouldn't you want the QR code to have >>>> their contact info in it? Or if you're in manufacturing and the >>>> document describes a product, wouldn't you want the QR code to have >>>> tracking information, like what machine made it, when, and so on? >>>> >>>> It's application logic - put it in the application layer.. which >>>> could, in the case of a CouchApp, also be in JavaScript, but it could >>>> just as easily be your Ruby app or your shell script... >>>> >>>> -- >>>> Keith Gable >>>> A+ Certified Professional >>>> Network+ Certified Professional >>>> Web Developer >>>> >>>> >>>> Read more=E2=80=A6 >>>> >>> >>> >> >> >> >> -- >> Keith Gable >> A+ Certified Professional >> Network+ Certified Professional >> Web Developer >> > >