Michael C. Harris wrote: > > An implementation question (or four); what would themes advertise in > their XML ? A variable to fill ? A selector of some kind, like a CSS > ID ? What advantage would having them in the XML give us, as opposed > to a standard function call to, for example, hardpoints() ? >
The advantage to having it in the theme's XML is that you can know about the places to which a theme supports output before activating the theme. Our interface could highlight the hardpoint names that are in use. For example, the listing for a theme named Aardvark could look like this: Theme name: Aardvark [Activate] Supported Hardpoints: *sidebar* footer ?header? "*sidebar*" would be bold (or something) indicating that your current theme outputs data to that hardpoint. "?header?" would be red (or something) indicating that the data output to the "header" hardpoint will have no place to go in this theme. Or something useful like that. The key point being that if you rely on what functions are called to know what hardpoint names are available in the theme, then it becomes difficult to know what they are without activating the theme first. Owen --~--~---------~--~----~------------~-------~--~----~ 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/habari-users -~----------~----~----~----~------~----~------~--~---
