Yeah, I think your CSS analogy works. The XHTML side of things would map to Pivot's Component graph (which may or may not be built or instantiated using BXML files), and the stylesheets are like the CSS used to style them.
If you dig around in the relevant source, you might be able to rip out the code to just build your own named style map & typed style map (rather than using the static ones in Component) and then load and apply those styles as you required. You might need to extend or modify BXMLSerializer so that it uses your named/typed styles in preference to any global ones, and then you would use that custom BXMLSerializer to load your BXML file and apply the styles that you need on a file by file basis. (Or just have the BXMLSerializer look for a style file matching your naming convention, load that and use it when building the object graph) Chris On 23 March 2011 03:32, Bill van Melle <[email protected]> wrote: > Okay, so I guess the interesting part for what I'm thinking about is this > property styleName. It doesn't satisfy the desire to change a whole bxml > file without additional markup, but at least it's cleaner looking than what > I thought in my earlier speculation was needed. It also suggests to me that > I might be thinking about it the wrong way, and that some kind of > globally-managed styles might actually be more desirable. Sort of like how > css files are preferable to lots of markup in html. > > Thanks for your help. >
