Allow for options in message styles

NEW
Unassigned

Status

Instantbird
Conversation
--
enhancement
4 years ago
4 years ago

People

(Reporter: clokep, Unassigned)

Tracking

Details

(Reporter)

Description

4 years ago
*** Original post on bio 1585 at 2012-07-12 11:58:00 UTC ***

It has been discussed a few times that it would be nicer to have options in message styles instead of variants, this would allow people to further customize their styles without an insane number of variants (e.g. buddy icons on/off, different colors in Bubbles, with/without context messages; or something like that).

For reference, there is an Adium ticket about supporting this: http://trac.adium.im/ticket/1920

It's possible the add-on UI for inline preferences could be used, if message styles were moved to the add-on manager.

Comment 1

4 years ago
*** Original post on bio 1585 at 2012-07-12 12:14:39 UTC ***

> It's possible the add-on UI for inline preferences could be used, if message
> styles were moved to the add-on manager.
This is bug 953968 (bio 530).
*** Original post on bio 1585 at 2012-07-13 10:03:25 UTC ***

Maybe we should try to cooperate with Adium-developers here to find a solution that is both suitable to them and us? This is in the sense how the theme will be notified of the options, not how we provide the choices to our users in the UI!
*** Original post on bio 1585 at 2013-04-07 21:57:25 UTC ***

The Adium-bug is sitting there unchanged for three years now.
Maybe we could collect ideas of how we'd like to solve this or what we'd expect it to be capable of and then post a proposal in their bug?


Some ideas:
Different types of options, with labels, default values and ids for internal use (much like the advanced options for accounts):
* Booleans / checkmarks to enable/disable features
* Lists / Radio buttons to choose between mutually exclusive options.
* Color picker?
* ...


How to access them:
A new global JS object available in the context of the conversation, the fields should be easily accessible (e.g. as simple as "if (theme.showIcons) {...}", where "showIcons" would be the id of a boolean option that might be labelled "Show user icons" and e.g. defaults to true).
If something speaks against a new global object, maybe add it elsewhere? On "window" maybe?

Challenges:
* Localization
* Options UI

Other stuff:
* Maybe variants could still be around, for major changes of the theme instead options tweaking a few aspects? If yes, then it should be easy to tell from code which variant was chosen, in my opinion (e.g. if (theme.variant == "Red_Blue") {...})
You need to log in before you can comment on or make changes to this bug.