On Thursday, August 13, 2015 at 4:00:34 AM UTC-7, Axel Hecht wrote: > I do see value in creating views(?) with data associated to them, just > so that folks don't need to repeat argument passing a few times.
I believe that that's exactly what we're thinking about. :) The way I think about it is that we could have multiple views per context (while currently we have 1-1), and each view could have it's own ctxdata (so maybe view data)? For example, document's View would have it's data, while webcomponents view (while sharing the l10n context) would provide it's own data. I can then see how a navigation bar could in the future have it's own data etc. > I can see a similar aspect in allowing l10n data to be associated with > any parent element of a localizable html element, too. The benefit of > not enforcing this to be global is that you can actually put l10n data > onto things like contacts cards, and have multiple per document. Yeah, I like it. I would like to tinker more with this thought, but I can imagine sth like: <element l10n-view-args=""> <h1 l10n-id="foo"></h1> </element> where foo has access to viewArgs defined on the element. zb. _______________________________________________ tools-l10n mailing list [email protected] https://lists.mozilla.org/listinfo/tools-l10n
