Johan, since you're thinking about generic importation into exhibit, let me suggest that the true "exhibity" way to do this would not be through javascript calls to calls like loadGoogleSpreadsheetData but through enrichment of the html tags in an exhibit. For example, regarding David's spreadsheet importer, I'd argue that the exhibity way to have a google spreadsheet would be to avoid javascript and instead in the head of the exhibit have something like <link href="http://spreadsheets.google.com/pub?key=pLvsUS-CftHo21r-0xjKvVA"; type="google-spreadsheet" rel="exhibit/data" />
(or perhaps ...ex:importer=google-spreadsheet) Johan Sundström wrote: > On 1/19/07, Alf Eaton <[EMAIL PROTECTED]> wrote: > >> In a similar vein, how feasible would it be to build an Exhibit from >> Flickr's JSON output? >> > > Very feasible indeed. Ditto any of Yahoo's other APIs (all or at least > mostly all JSONP capable today, for all I know). I have been thinking > about devising a more generic way of binding JSONP services to > Exhibit. With a few examples about for what people want to use it, and > more importantly, with people eager to adopt and play with it, it will > come sooner rather than later. > > A likely outcome is a built-in generic JSON data binding API, with a > few comfortable "pre-packaged" entrances like > loadGoogleSpreadsheetsData. > > _______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
