E3 has modified E2's error handling, becoming more strict. For example,
if your exhibit links to a non-existent data file, E2 will ignore it and
proceed, while E3 will halt without rendering any other data. See e.g.
http://people.csail.mit.edu/karger/Exhibit3/demos/nobelists/broken-nobelists.html
This is probably a good step for exhibit developers, kind of like strong
typing/forcing you to eat your vegetables. But I think it's a problem
for more casual users of exhibit. Especially since the resulting error
messages in the javascript console are highly uninformative. Browsers
work hard to recover from as many syntax errors as possible, and I think
exhibit should too.
As a way to offer both options, I propose adding a "strict" option to
the exhibit api (<script src="exhibit-api.js?strict=true") which will
cause the fast fail behavior currently in E3, but to have the default be
for exhibit to proceed when possible, like E2 did.
thoughts?
--
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.
