On 2/28/07, David Huynh <[EMAIL PROTECTED]> wrote: > Johan Sundström wrote: > > On 2/28/07, David Karger <[EMAIL PROTECTED]> wrote: > > > >> I agree with Johan that it is good to keep the old forms---not because > >> the we need to be backwards compatible, but because those forms were > >> generally simpler than the new forms, so the right entry path for new > >> exibitors might be to use the old forms until they feel too limited and > >> they want the new forms. > > > > My thoughts exactly. (Though backwards compatibility doesn't > > particularly hurt, if it comes for free, IMO. And here, it just might, > > I think.) > > I agree, too. I just didn't have time.
Good. > I'm also thinking that we need to re-think about the exporters. Those > Copy and Copy All buttons are a little too intrusive and yet they don't > give enough control over the output (no settings to adjust). I think our re-thinking earlier discussed would be good enough; has any new needs or thoughts on the topic surfaced since? We should probably try to migrate what we end up with into the issue tracker, or (better still?) a development roadmap on the wiki, optionally surrounded with invitations for helpers eager to get us there quicker. Linking mails on the list on each topic, for additional context and discussion. If I had a helper, I'd put him on structuring up what good thoughts surface that nobody has the initiative to commit to the wiki. ;-) > >> Good, but I suggest changing the old > >> <div id="exhibit-browse-panel" ex:facets=".abc, .def"> > >> to > >> <div ex:role="exhibit-browse-panel" ex:facets=".abc, .def"> > >> because the move to ex:role makes sense. > > > > I was thinking of keeping the id so the change does not incur an > > additional performance hit (we can query nodes in documents by id > > using a speedy DOM native call, but have to traverse the entire > > document to find ex:role attributes). > > > > At least I assume that is what David's new code does now; I have not > > read through it yet, because it's a huge checkin that isn't unreadable > > in email form, and I'm hopeful I'll be able to wait for a fix that > > gets us a proper webside changeset browser first, and be up to speed > > in five minutes sharp. Apparently your new UROP Mason could get it > > done before long, if he only had the bits to set it up: > > > > http://simile.mit.edu/issues/browse/SIMILE-27 > > > > But there is merit to the thought. I think I'd prefer > > ex:role="facets-panel" though; I always have to think for a while to > > remember the right noun, whereas I always remember the ex:facets > > attribute. > > I'd vote for ex:role="exhibit-facetPanel" or ex:role="facetPanel", to > parallel with ex:role="exhibit-viewPanel" or ex:role="viewPanel". > > Let me check in the shortening of ex:role="exhibit-*" today. Johan, I'd > appreciate some help with getting the browse panel back... Sure; I'll re-add it, with backwards compat for id="exhibit-browse-panel" if available, and forwards support for ex:role="facetPanel" on its own. That will happen sooner with a Simile Trac installation, but probably within the next week otherwise (assuming I'll eventually get past the threshold of reading the gigantic commit unaidedly, if I really have to). -- / Johan Sundström, http://ecmanaut.blogspot.com/ _______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
