On 3/4/07, David Huynh <[EMAIL PROTECTED]> wrote: > Try moving the <div ex:role="exhibit-collection"...> outside the view > panel div.
Sure; I'll play around more with that. I'd hope to find a converting-old-exhibits recipe that leads to something that is as close to the former page structure as possible. Not that our former user base is huge; there are probably "only" thousands in existence so far. > > 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. Good. :-) > >> 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. You can count on that; it's my personal main interest in Exhibit. Expect resistance to ideas that make that more difficult than it need be. ;-) I'm still mildly annoyed about not having access to id properties, for just such use cases. I work around it by duplicating id:s javascript-aidedly under another name for now when I need them (which is often, as it is what controls linkage between properties of merged data sets and at the very heart of mashups), though I don't understand what makes me need to. I have worked out some kind of meta-understanding of that it this some religious no-no of Semantic Web people, and try to adapt to working around it, but the fact remains that it is a hindrance to effective use of Exhibit for mashups. I have also stopped expecting answers about this, and considered maintaining patch sets or an eventual fork of Exhibit that does not guard id properties, but for now left them hanging at the work-arounds stage. (And forks are rarely a good idea for open source projects, so I'd vigorously prefer not to.) > By the way, you can now add (and I believe, remove) facets on the fly. Nice. I don't think I've had a use case for that yet; what I have wanted is an on/off switch for the ones I already have. Come to think of it, that might actually be easier to handle on the CSS layer, if we want to cut down on facet API:s (even if that sacrifices the nice on/off animation). > 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. Neat! A first move towards centralizing all the boilerplate code copied around all over the place, I gather? > 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 Sounds good. You'll be going (and present Exhibit), I presume? If so, I'll try to work it into my schedule too. -- / Johan Sundström, http://ecmanaut.blogspot.com/ _______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
