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.
However, just to ensure that we aren't backward compatible :) I think it is good to adopt some of david's conventions to modify the old forms. See below. Johan Sundström wrote: > On 2/27/07, David Huynh <[EMAIL PROTECTED]> wrote: > >> I have just refactored the Exhibit 2.0 development branch to support >> more flexible layouts, e.g., >> >> http://simile.mit.edu/repository/exhibit/branches/2.0/src/webapp/examples/CSAIL-PIs/CSAIL-PIs.html >> > > Great! > > >> Make the following changes if applicable to your html files and your >> exhibits should work again: >> >> - Remove <div id="exhibit-control-panel"></div>. It's no longer supported. >> > > If it ever was. ;-) > > >> - Change <div id="exhibit-browse-panel" ex:facets=".abc, .def"></div> to >> >> <div ex:role="exhibit-facet" ex:expression=".abc" ex:facetLabel="Abc >> or whatever"></div> >> <div ex:role="exhibit-facet" ex:expression=".def" ex:facetLabel="Def >> or whatever"></div> >> > > Would you be against me re-adding support for the old format too (by > having it construct above contents from its ex:facets attribute, if > found on an empty div of the right id, detected old style)? > 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'd say this should be done by "desugaring" the above into an html fragment containing the new syntax, in case the response to the new syntax changes later. separate question: why "exhibit-facet" instead of just "facet"? The fact that we are in namespace ex: makes it obvious this is exhibit stuff. In general, seems like exhibit-foo could reduce to foo. > I find it a lot more tractable, for the many cases where strewn-about > facets are not wanted -- less typing, fewer decisions, easier to > change order of things, add or drop facets, no chasing about the > entire page source code to find them. > > >> - Change <body ex:exhibitLogoColor="abc"> to >> > > Ditto this feature coming back in the above scenario, if perhaps more > appropriately on the browse-panel itself. Making it comfy to get the > logo is probably the best or only way to ensure it shows up at all. > > >> You can use more than one view for a single collection. Just don't put >> them inside a view panel component. >> > > Multiple views ok, recursive not. Got it. :-) > > >> David >> P.S. Oops, I just remember I haven't fixed the exporters... >> > > Heh. :) > > _______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
