Добавки
![[Внимание]](https://addons.thunderbird.net/static/img/developers/test-warning.png?b=b00ed3ed-652d8172)
Права
Относно добавката
TB v68 compatibility note:
There is no plan to move the addon to the TB v68 "standards", and here is why:
- Mozilla itself has decided not to work on compatibility developments and leave "that" to the addon developers.
I don't know how much a mozilla developer is paid, but speaking for myself the sum of the contributions i have ever received for 6 free addons during almost 10 years are a figure with 3 digits max...
- Besides the fact Mozilla leaves us doing the "dirty work", they are not even able to provide detailed information about how to make the old addons compatible with their new standards.
I mean a relevant guide, not an information note explaining that the addons should be restartless, turned into webextensions and so on, and not even giving an example.
- That is not the first time that Mozilla is acting as if addons developers and the community was not important.
I have had already several bad experiences in the past when my addons got broken just because Mozilla changed something which used to work without even thinking about compatibility or giving information.
- I'm tired of all this, and as i have another real job to afford my bills, i'm not ready to make all that effort for so few consideration.
- It already took me thousands and thousands and thousands of hours to develop my addons, working everyday on making them the more stable and practical possible. Why would i do twice something which worked pretty well?
- All my addons are Mozilla-licensed (~ free softwares), so sources are open for all developers which would be interested to follow the new Mozilla standards.
I think i made this work the best professional i could, so my code is well structured and full of comments. If you do so, sending me a simple "thank-you" email would be greatly appreciated.
- All my addons are already compatible with TB v60. Are there so much interest to move to TB v68?
Do you change your toaster every year just because there are new ones on the market? I don't.
- The choice is between v68 without addons or v60 with addons. Your call.
Subject Manager is a Thunderbird add-on which allows to manage subjects of composed emails.
The main purpose is to store user-defined subjects and offer a convenient way to insert them into subject field.
Features are the following:
* All platforms are supported. Tested versions are:
- Windows: XP sp3 (x86), Seven Pro sp1 (x64);
- Linux: Mandriva 2011-2 (x86);
- Mac: OS X 10.7 / Lion (x64).
* Available languages are: french (fr-FR), english (en-US), russian (ru-RU), swedish (sv-SE).
* A toolbar button is automatically added next to 'Attach' button into composer window at first run. If the button is not displayed (or has been removed), it should be available when editing and customizing toolbar.
* A list of main commands and user-defined subjects is available in a 'Subjects' button near native 'Subject' field. Picking a subject from the list inserts it automatically into 'Subject' field. This list is also available in 'Subject Manager' toolbar button context menu.
* Available subjects are defined freely by user. Moreover, if advanced mode is enabled, a subject can contain some meta-data like current_date, current_time, counters, etc. which are parsed automatically when subject is inserted into subject field.
* A default subject can be set to be automatically inserted as soon as compose dialog is opened.
* 'Subjects' button can be located at the right of native 'Subject' field or can replace native 'Subject' label. 'Subjects' button can also be enabled or disabled.
* Subject textbox allows autocompletion related to subjects list (TB >= v3 only). From settings dialog, autocompletion feature can be enabled/disabled, set as case-sensitive/case-insensitive.
WARNING: Autocompletion is not compatible with spellchecking, so enabling autocompletion disables spellchecking.
* Current subject of email can be added to subjects list via context menu of toolbar button.
* Current subject can be cleaned from automatically-generated prefixes such as "Re:", "Fwd:", etc. via context menu of toolbar button. Prefixes to remove are defined in settings dialog.
* When cleaning subject from automatic prefixes it's possible to keep only the first one. This first prefix can also be replaced by a user-defined one. 2 replacement strings can be defined: 1 for 'reply' prefix, 1 for 'transfer' prefix.
* Settings dialog allows to manage subjects list: add, remove, reorganize or sort naturally subjects.
* The add-on provides a 'debug mode' which writes information into embedded error console (see Tools > Error Console).
* Error and warning messages are also written into error console (regardless debug mode is enabled or not).
If for any kind of reason the add-on seems not to work properly, open error console and look for messages regarding add-on which could give you information about the issue (all messages are prefixed by add-on name).
If the issue is reproducible and you think it's an add-on bug:
1. Enable debug mode and enable 'Log messages in a file'.
2. Click on 'Export settings' to create settings file.
3. Proceed again (messages will be saved in debug log file').
4. Contact us and report us relevant and maximum information regarding the issue:
- screen captures of each step of the action which leads to the issue
- screen captures of each settings tab
- settings file
- debug log file
NB: Incomplete issue reports will not be answered.
Contact (bug reports, features request, etc.): [email protected].
NB: Usage support email will not be answered.
There is no plan to move the addon to the TB v68 "standards", and here is why:
- Mozilla itself has decided not to work on compatibility developments and leave "that" to the addon developers.
I don't know how much a mozilla developer is paid, but speaking for myself the sum of the contributions i have ever received for 6 free addons during almost 10 years are a figure with 3 digits max...
- Besides the fact Mozilla leaves us doing the "dirty work", they are not even able to provide detailed information about how to make the old addons compatible with their new standards.
I mean a relevant guide, not an information note explaining that the addons should be restartless, turned into webextensions and so on, and not even giving an example.
- That is not the first time that Mozilla is acting as if addons developers and the community was not important.
I have had already several bad experiences in the past when my addons got broken just because Mozilla changed something which used to work without even thinking about compatibility or giving information.
- I'm tired of all this, and as i have another real job to afford my bills, i'm not ready to make all that effort for so few consideration.
- It already took me thousands and thousands and thousands of hours to develop my addons, working everyday on making them the more stable and practical possible. Why would i do twice something which worked pretty well?
- All my addons are Mozilla-licensed (~ free softwares), so sources are open for all developers which would be interested to follow the new Mozilla standards.
I think i made this work the best professional i could, so my code is well structured and full of comments. If you do so, sending me a simple "thank-you" email would be greatly appreciated.
- All my addons are already compatible with TB v60. Are there so much interest to move to TB v68?
Do you change your toaster every year just because there are new ones on the market? I don't.
- The choice is between v68 without addons or v60 with addons. Your call.
Subject Manager is a Thunderbird add-on which allows to manage subjects of composed emails.
The main purpose is to store user-defined subjects and offer a convenient way to insert them into subject field.
Features are the following:
* All platforms are supported. Tested versions are:
- Windows: XP sp3 (x86), Seven Pro sp1 (x64);
- Linux: Mandriva 2011-2 (x86);
- Mac: OS X 10.7 / Lion (x64).
* Available languages are: french (fr-FR), english (en-US), russian (ru-RU), swedish (sv-SE).
* A toolbar button is automatically added next to 'Attach' button into composer window at first run. If the button is not displayed (or has been removed), it should be available when editing and customizing toolbar.
* A list of main commands and user-defined subjects is available in a 'Subjects' button near native 'Subject' field. Picking a subject from the list inserts it automatically into 'Subject' field. This list is also available in 'Subject Manager' toolbar button context menu.
* Available subjects are defined freely by user. Moreover, if advanced mode is enabled, a subject can contain some meta-data like current_date, current_time, counters, etc. which are parsed automatically when subject is inserted into subject field.
* A default subject can be set to be automatically inserted as soon as compose dialog is opened.
* 'Subjects' button can be located at the right of native 'Subject' field or can replace native 'Subject' label. 'Subjects' button can also be enabled or disabled.
* Subject textbox allows autocompletion related to subjects list (TB >= v3 only). From settings dialog, autocompletion feature can be enabled/disabled, set as case-sensitive/case-insensitive.
WARNING: Autocompletion is not compatible with spellchecking, so enabling autocompletion disables spellchecking.
* Current subject of email can be added to subjects list via context menu of toolbar button.
* Current subject can be cleaned from automatically-generated prefixes such as "Re:", "Fwd:", etc. via context menu of toolbar button. Prefixes to remove are defined in settings dialog.
* When cleaning subject from automatic prefixes it's possible to keep only the first one. This first prefix can also be replaced by a user-defined one. 2 replacement strings can be defined: 1 for 'reply' prefix, 1 for 'transfer' prefix.
* Settings dialog allows to manage subjects list: add, remove, reorganize or sort naturally subjects.
* The add-on provides a 'debug mode' which writes information into embedded error console (see Tools > Error Console).
* Error and warning messages are also written into error console (regardless debug mode is enabled or not).
If for any kind of reason the add-on seems not to work properly, open error console and look for messages regarding add-on which could give you information about the issue (all messages are prefixed by add-on name).
If the issue is reproducible and you think it's an add-on bug:
1. Enable debug mode and enable 'Log messages in a file'.
2. Click on 'Export settings' to create settings file.
3. Proceed again (messages will be saved in debug log file').
4. Contact us and report us relevant and maximum information regarding the issue:
- screen captures of each step of the action which leads to the issue
- screen captures of each settings tab
- settings file
- debug log file
NB: Incomplete issue reports will not be answered.
Contact (bug reports, features request, etc.): [email protected].
NB: Usage support email will not be answered.
