David R. Karger wrote: > Maybe it's time to start defining some object-oriented programming model > for exhibit. > What if we definedan "attribute handlers" architecture for new exhibit tags. > Any developer could write some javascript that registered a particular > method (function) on a particular new exhibit tag. > When exhibit encountered that tag while parsing, it would invoke the > method, passing in the object being constructed (view, facet, lens, > content) that included the tag, and also the argument associated with > the tag. > > So in your example below, you would register a tooltip-callback > function, which would be invoked whenever ex:tooltip appeared in a > facet, and get passed that object representing the facet and also the > value of the ex:tooltip attribute. > Could you give some specific examples (HTML code) on how this might work in facets, views, and lenses?
I generally try to limit custom code executed on these elements for one reason: it's very hard and unsafe to support the same when migrating to something like Backstage. David --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SIMILE Widgets" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/simile-widgets?hl=en -~----------~----~----~----~------~----~------~--~---
