Well, this is only a partial solution and a little risky. You need to guarantee that the underlying data has not changed since the page was rendered; otherwise there will be inconsistent state between what the back-end thinks is on the page and what is actually there, which could lead to bizarre behavior if the user starts using the facets to browse.
Note that you can already tell exhibit not to bother displaying many items, which keeps the dom rendering down; you are only in trouble if you have a facet with a huge number of values. And I think the frame buffer approach is the right one here: only render into the dom those facet values that will actually appear in the scroll... Ivan Zhidov wrote: > One way of improving the intensity of opening an exhibit with many > entries is to forgo DOM creation altogether by posting a page with > already pre-generated DOM but I still want to have the search > functionality enabled so I cannot take exhibit js library out of the > page but exhibit in turn goes out and tries to render the data and if > it doesn't find a source in the page (if datasource reference was > taken out) it replaces pre-rendered content with empty space. Is > there a way to force exhibit not render DOM and rely on the existing > DOM? Exhibit can still load the data but should rely on the existing DOM. > > Ivan > _______________________________________________ > General mailing list > [email protected] > http://simile.mit.edu/mailman/listinfo/general > _______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
