On 3/3/07, David Huynh <[EMAIL PROTECTED]> wrote: > Johan Sundström wrote: > > These are my experiences trying to upgrade this exhibit: > > > > http://exhibit.ecmanaut.googlepages.com/choir-events.html#basic > > > > from tags/1.0.pre-ui-split, to branches/2.0, at: > > > > http://ecmanaut.googlepages.com/choir-2.html#basic > > Got a 404...
Note to self: never do anything before breakfast. :-) http://exhibit.ecmanaut.googlepages.com/choir-2.html#basic > >> <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> > > > > Check (putting them inside the div, in my case). > > > > I preferred the old default facet panel names propagated from the type > > info for the data type featured in the facet over getting an empty > > label when no ex:facetLabel is provided. Being able to override with > > ex:facetLabel could be useful at times, though. > > Agreed. Laziness it was. That would be easy to fix... > > >> - Change <body ex:ondataload="window.exhibit = > >> Exhibit.create('President');"> to > >> > >> <body> > >> <div ex:role="exhibit-collection" ex:itemTypes="President"></div> > >> > > Check. While it's nice that we don't have to write any javascript code > > any more to set up an Exhibit object, I'm not happy to see that all > > support code making it possible (and even easy) to do it from > > javascript too isn't there any more. (Or maybe it's just hidden away > > somewhere?) > > It's there, but hidden away and perhaps incomplete. In 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. :-) > 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. > >> <div ex:role="exhibit-logo" ex:color="abc"></div> > > > > Check. Not knowing which colour was the old default, I stuck with your > > suggestion. :-) A later upgrade tutorial might suggest going with > > whatever used to be the case if you, like me, hadn't specified one. > > You don't need ex:color ... and I think the default is Silver. It's amazing, the kind of things that don't occur to me before breakfast. :-) > > My init() code which pre-selected a facet ("events in the future:yes") > > died too, but we should make APIs for that, rather than me poking in > > the innards of the browser engine object which no longer exists > > anyway. > > Will do. Great! -- / Johan Sundström, http://ecmanaut.blogspot.com/ _______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
