Try moving the <div ex:role="exhibit-collection"...> outside the view panel div.
> [snip] > > I primarily miss the very comfy and workable API we had for > instantiating an exhibit via Exhibit.create() right off an exhibit > json object, or a node id of an html table, an object describing a > jsonp feed and perhaps other means for loading the exhibit data. Most > of it was implemented by the _dwim_create method in > > > http://simile.mit.edu/repository/exhibit/tags/1.0.pre-ui-split/src/webapp/api/scripts/exhibit.js > > I was hoping it would be somewhat safe from being expunged, by being > very nearly documented and all. :-) > Sorry, I was trigger-happy with the delete button... :) I agree about the easy create call. I'll put that back. >> Keeping the Javascript configuration code is extremely important to me, >> too, since I also need to "sell" Exhibit to those who consider ex:* >> bastardizing HTML :-) >> > > It makes Exhibit based mashup writing substantially easier too. > Will you help me test that? I think it's easier to have a real "customer" for that feature, as I myself don't use it much, yet. By the way, you can now add (and I believe, remove) facets on the fly. The create function here http://simile.mit.edu/repository/exhibit/branches/2.0/src/webapp/api/scripts/component.js can create a component out of a configuration object. The component will take over the provided elmt. Or you can also use the other specific create* functions. I haven't tested them. I'd like to release Exhibit 2.0 before I go to WWW 2007 (May 8). We should start nailing down which features we absolutely want it in there. Let's coordinate through http://simile.mit.edu/wiki/Exhibit_Todos David _______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
