tonymec wrote:Yes, all those ideas sound good to me.
Have You any recommendations for me how to construct this basic support of SeaMonkey?
Because I don't really want to duplicate the browser.js and messenger.js code into seamonkey.js.
Or I shouldn't care about this? Just copy the code to make titlebar customizing work, and file another bug to refactor / rewrite this customizing stuff into a reusable one ( SM would use both browser- and messenger specific code).
tonymec wrote:Once we start customizing the title in different ways in different windows, we will need some way to keep them apart, of course. I suggest keeping nightly.templates.title as a default for all windows with customizable title (for compatibility with previous versions) and then use nightly.templates.title.browser, nightly.templates.title.mailnews as overrides. These would not have a default, and would fall back to the value of the other option when undefined (but setting them to the empty string would "remove" the default value setting for that window). What do you think? This would provide for extensibility.
That would be nice.
tonymec wrote:About the options, IIUC at the moment the only way to set them is about:config (or the Thunderbird Config Editor). I suppose that if the number and complexity of the options keep growing, at some (indeterminate future) point a Preferences UI will have to be added. I don't think this is urgent, but let's keep it in view.
While using nightly.templates.title.browser and nightly.templates.title.mailnews, how about setting them?
Should I improve options.xul, or it's script to distinguish those preferences?
For example if the options.xul were able to answer "what type of window called me?"
then the browser.js could use nightly.templates.title.browser, the messenger.js could use nightly.templates.title.mailnews and seamonkey.js would use both preference.
Hm? Or leave users alone with about:config and an other filed bug?