search

geekcheng / simile-widgets

Automatically exported from code.google.com/p/simile-widgets
0 stars 0 forks source link

EXHIBIT: Allow for static default HTML for accessibility, search engines, and faster startup #109

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
I sometimes like the dynamicness of Exhibit, but most of the pages I intend
to use Exhibit on 1) are slow changing and 2) need to be accessible. I've
used the noscript trick described on
<http://simile.mit.edu/wiki/Exhibit/How_to_make_Exhibit_search_engine_%22friendl
y%22&gt;,
and it sort of works.

However, I don't see why, in principle, we can't have the regular exhibit
start up with a static view that is modified on demand when the user
twiddles a control. This would also really speed up start up display as the
initial view wouldn't have to be generated.

Obviously, this would require always synching the inital state of the page
when you change the data...but all the solutions *already* require that.

I guess it isn't a *blocker* for me, but the <noscript> version leaves some
detrius on the page from the dynamic version, so there's really no way I
can use it on my real home page.
All.

Original issue reported on code.google.com by GabrielR...@googlemail.com on 3 Apr 2009 at 6:22

GoogleCodeExporter commented 9 years ago 
Allow for static default HTML for accessibility, search engines, and faster
startup.
sometimes like the dynamicness of Exhibit, but most of the pages I intend
to use Exhibit on 1) are slow changing and 2) need to be accessible. I've
used the noscript trick described on
<http://simile.mit.edu/wiki/Exhibit/How_to_make_Exhibit_search_engine_%22friendl
y%22>,
and it sort of works.

However, I don't see why, in principle, we can't have the regular exhibit
start up with a static view that is modified on demand when the user
twiddles a control. This would also really speed up start up display as the
initial view wouldn't have to be generated.

Obviously, this would require always synching the inital state of the page
when you change the data...but all the solutions *already* require that.

I guess it isn't a *blocker* for me, but the <noscript> version leaves some
detrius on the page from the dynamic version, so there's really no way I
can use it on my real home page.

Original comment by GabrielR...@googlemail.com on 3 Apr 2009 at 6:34

GoogleCodeExporter commented 9 years ago

Original comment by stefano.mazzocchi@gmail.com on 3 Apr 2009 at 9:24