Hi David,
Wow, that sounds fantastic.
Regarding your mentioning of...
Regarding using Backstage on licensed/private data, it is possible to
install Backstage on your own server and tell Exhibit to use that
instance rather than a public Backstage service. The experiment right
now does not include that option, but there is no technical challenge
there. You actually might even want to run Backstage yourself and
connect it directly to a local Sesame store if your data is too large to
transfer as a JSON file.
I would be very interested in this functionality (the linking to a local
Sesame Store), I know in some ways this goes against your principles of
"light-weight" publishing. However I would have thought that it is only natural
that as the user demands more "advanced" functionality and customisation then
they might reasonable expect to have to do more than alter some parameters, or
even overload a function.
Though I fear I would be little or no help in terms of development, I would
gladly help in and way my time and ability allow (e.g. user testing).
N
_________________________________________________________________
Get Hotmail on your mobile, text MSN to 63463!
http://mobile.uk.msn.com/pc/mail.aspx
_______________________________________________
General mailing list
[email protected]
http://simile.mit.edu/mailman/listinfo/general
