Johan Sundström wrote: > [snip] >>> (I havent tied in the map functionality yet, since I didn't remember >>> how to do it at the time, so the final tab puts the Exhibit into an >>> eternal busy state, for the time being.) >>> >> In the location array, replace "name" with "id". Then in the map view, >> remove ex:start and ex:end and add ex:latlng="latlong". Hope that works! >> > > I ended up taking my time remodeling relations and doing a lot more in > the process, heavily tweaking things and messing about with the map > view code, and am sort of happy with the updated outcome: > > http://ecmanaut.googlepages.com/choir-events.html > > The multi-hop facets (.location.Stad here, for "city") behave a little > surprisingly; first, they don't exist at all, when the page has > loaded. Toggle something on and off, though, and they show up. > Hmm... You might have found a deep bug... Writing a multi-hop, group-able faceted browsing engine in Javascript was not trivial. :-)
> Unrelated side thought: I am starting to lean towards modeling all > data in English, to get presentation layer issues like CSS class names > and similar that don't violate W3C rules (I presume some browsers > might not like unicode names there, though I honestly haven't tried > the territory much). > I haven't tried international characters in CSS, either. I understand it's desirable to localize "label", "id", and "type" as well. At the same time, that would introduce another level of indirection, not just in the code but also in the documentation. I think let's keep that off until there are WYSIWYG tools for Exhibit (e.g., blog widgets). David _______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
