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...
> [...]
>
>> - 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>
>>
> 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
http://simile.mit.edu/repository/exhibit/branches/2.0/src/webapp/api/scripts/exhibit.js
look for configure and configureFromDOM. Actually, hmm, I just spotted a
bug looking at it :-(
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 also seems like ex:itemTypes="Event" is ignored; I see all item
> types listed now in the tabular view.
>
>
>> - Change <body ex:exhibitLogoColor="abc"> to
>>
>> <body>
>> ...
>> <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.
> 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.
> Lens links in tabularview error out on
>
> lensRegistry has no properties
> http://simile.mit.edu/repository/exhibit/branches/2.0/src/webapp/api/scripts/ui.js
> Line 194
>
> now. My facets are not clickable any more, but most likely due to my
> not having figured out where to put the <div
> ex:role="exhibit-collection" ex:itemTypes="Event"></div> to have
> Exhibit render the view into the same DOM node it used to. I tried
> putting it last in my former exhibit-view-panel.
>
Will look once your new URL is back up...
David
_______________________________________________
General mailing list
[email protected]
http://simile.mit.edu/mailman/listinfo/general
