Well with the last two posts, this solves the issue of remote linking stylesheets. That is as long as one is willing to tag all the changes from the default style with "!important" -- ancestor, could you set Brief to automatically replace the default stylesheet if the import command is invoked? That would beat the heck out of marking "!important" to all changes from the default style...
Look at this suggestion like a compromise. You still get the intended editor functions (thanks for mentioning we can open brief-custom-style.css from our profile's chrome to speed up CSS editing) and advanced CSS stylesheet themers would be able to do advanced CSS editing without having to constantly invoke "!important" for every line they change.
Oh and by the way, you meant "@import url(*path to stylesheet here*);". For best importing results, store your custom stylesheet in your profile's chrome folder (this way you can do "@import url(/*stylesheet name here*.css); ). Oh and I see you moved feedview.css to your profile's "extensions/brief@mozdev.org/defaults/data" folder. Unless you're going to put the updated styleshet on your site, I'm still going to continue suggesting a quick link to the feedview.css from the CSS editor or Brief's options.
People (newbie and veteran alike) will still need to see what all options are available for tweaking. ;)
Re: New mechanism of customizing the appearance of feeds
Well with the last two posts, this solves the issue of remote linking stylesheets. That is as long as one is willing to tag all the changes from the default style with "!important" -- ancestor, could you set Brief to automatically replace the default stylesheet if the import command is invoked? That would beat the heck out of marking "!important" to all changes from the default style...
Look at this suggestion like a compromise. You still get the intended editor functions (thanks for mentioning we can open brief-custom-style.css from our profile's chrome to speed up CSS editing) and advanced CSS stylesheet themers would be able to do advanced CSS editing without having to constantly invoke "!important" for every line they change.
Oh and by the way, you meant "@import url(*path to stylesheet here*);". For best importing results, store your custom stylesheet in your profile's chrome folder (this way you can do "@import url(/*stylesheet name here*.css); ). Oh and I see you moved feedview.css to your profile's "extensions/brief@mozdev.org/defaults/data" folder. Unless you're going to put the updated styleshet on your site, I'm still going to continue suggesting a quick link to the feedview.css from the CSS editor or Brief's options.
People (newbie and veteran alike) will still need to see what all options are available for tweaking. ;)