15
edits
| Peter Wilson (talk | contribs) mNo edit summary | Peter Wilson (talk | contribs)  | ||
| Line 100: | Line 100: | ||
| XBL lets you bind anonymous generated content to arbitrary XML elements. It supports CSS styling scoped to the generated content, introduction of generated containers between the bound element and its children, inheritance of attributes, dynamic update, and other cool stuff. It would be cool if we could reuse this very large hammer as part of a template system. | XBL lets you bind anonymous generated content to arbitrary XML elements. It supports CSS styling scoped to the generated content, introduction of generated containers between the bound element and its children, inheritance of attributes, dynamic update, and other cool stuff. It would be cool if we could reuse this very large hammer as part of a template system. | ||
| Peter Wilson. Please forgive me if I am stating the obvious. For all the talk of templates there is none of presentation,validation and collation. Is it possible to have a variant of XBL which can map template variables to xbl properties and visa-versa for use in content generation? This could operate in addition to regular xbl. This would allow bindable mappings for any datatype: dates, numbers currencies etc. This type of xbl would not generate any content. Thus, this could be made to work in trees where xbl widgets are not allowed. If template variables hold the internal form of the data (eg. int date double etc.) the sort service could also collate correctly. I may be wrong but I think everything is currently converted to strings in a predetermined manner (if not nsMsgDBView performs some serious contortions to sort its data) . This may also be a way of implementing more complicated template rules based on computed values. To sum up: use xbl to present, validate, collate, compute and synthesize values.  | |||
| ---- | ---- | ||
edits