mackenzie wrote: > On Aug 13, 9:02 am, David <[email protected]> wrote: > >> I wanted to inquire as to the status of Backstage in terms of where it >> stands in the development process. Thank you. >> > Yes, Backstage has languished, but mainly because it's a very complicated > thing to do right. > My day job was keeping me a lot more busy than I thought... :-)
> Backstage was a proof-of-concept prototype, so really we need to start fresh > (I think David H. would agree) and it looks like a big project. > Yes, it is a big project and it was designed for existing exhibits to scale almost seamlessly just by switching the API from the exhibit-api.js URL to a backstage-api.js URL. But it seems that there is also demand for institution / enterprise use, which has totally different requirements. > That said, there's a huge need for it by everyone I've talked to, and here at > MIT, so I'm trying to get it started up again (or funded, or both). Any ideas > appreciated, > For medium-sized data sets (say, 1,000 to 20,000 items, 10 properties per item), Backstage's use of Sesame should work just fine. Facets and basic views (thumbnail, tile, tabular) should be easy. Simple lenses should also be easy--Backstage does support custom lenses. The challenges lie in more complex views like timelines and maps, which Backstage as currently implemented doesn't support. David --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SIMILE Widgets" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/simile-widgets?hl=en -~----------~----~----~----~------~----~------~--~---
