Gehigarriak
![[Warning]](https://addons.thunderbird.net/static/img/developers/test-warning.png?b=b00ed3ed-652d8172)
Baimenak
Gehigarri honi buruz
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.
Auto Resize Image is a Thunderbird add-on which allows to resize inline and attached images while composing email messages.
The main purpose is to:
- reduce size of image files (emails > 5 Mb are generally blocked by ISPs);
- give the image convenient dimensions for it to be visible directly in email client without using scrollbars.
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), swedish (sv-SE), icelandic (is-IS), dutch (nl-NL), german (de-DE)
* Inline images (directly inserted into mail body) and attachment images are handled.
* Supported image formats are: JPEG, PNG, BMP and GIF. JPEG and PNG formats are natively supported whereas BMP and GIF formats are converted to PNG format.
Nb: Resized BMP and GIF image files keep original extension (.bmp or .gif), even if they are encoded using PNG format.
* A toolbar button is added to composing window and allows to resize images. Its behaviour can be user-defined:
- resizing of inline images;
and/or
- resizing of attachment images.
* The toolbar button offers a quick settings menuitem to set main settings directly.
* An interactive mode allows to set on-the-fly main settings (dimensions, jpeg quality, name) for each image when resizing.
This mode offers also to keep current settings as settings for all other resizings through the session or to crush default settings.
* Exif data can be read from the file and the Exif orientation information can be used to get the native orientation of the image.
* Settings dialog offers full control on how images are resized: inline and/or attachment images can be resized when:
- sending now;
- sending later;
- sending in background (a feature actually in development, have a look to this page for more information);
- saving message as draft;
- saving message as template;
- auto saving as draft.
For each mode, it's also possible to specify if undo is possible or not, and if resizing should be skipped if any image has already been resized (generally using dedicated custom button).
* Resized attachment images can be displayed with a user-chosen style in attachments pane (color, italic and/or bold).
* Resizing can be undone: it allows to roll back resized images to original versions. This is a real 'undo': resized images are replaced by original images.
* If message is saved in mailbox (draft, template, send later, etc.) it's still possible to resize or unresize images once the message is edited again. Nb: For attachment images undoing resizing is not possible.
* Images embedded into received messages which are replied to or transferred are handled as if they've just been added to the message.
* Images added through a http(s) link are handled.
* Images can be reduced and/or enlarged regarding user-defined maximum and minimum width and height (Nb: Dimensions ratios are not altered).
* Only images which satisfy dimensions criteria (larger than maximum dimensions and smaller than minimum dimensions) are modified. Other images are kept unchanged.
* Images to resize can be filtered via filename criteria: regarding a user-defined list of patterns, image files can be included or excluded; regular expressions can be enabled or disabled for pattern definition.
* Images to resize can be filtered via format criteria (JPEG, PNG, BMP, GIF) based on file extension.
* Resized images can be renamed using a user-defined pattern. This feature is smarter enough to avoid doublons.
Renaming pattern can contain some meta-data like:
- original filename;
- file extension;
- resized image number (= index of image file in resizing queue);
- height;
- width;
- current date (format is editable);
- current time (format is editable).
* Resizing can be enabled/disabled regarding recipients of the message being composed: user can define separated white and black lists of patterns which can control if compression is skipped or not regarding if one or all email recipients match given patterns.
* Images can be forced to jpeg or png format.
* Composer window status bar is used to display information to user. Embedded progress bar is also used during image resizing.
* Behaviour, associations and messages of settings dialog have been designed to improve accessibility for non-sighted people.
* 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.
Auto Resize Image is a Thunderbird add-on which allows to resize inline and attached images while composing email messages.
The main purpose is to:
- reduce size of image files (emails > 5 Mb are generally blocked by ISPs);
- give the image convenient dimensions for it to be visible directly in email client without using scrollbars.
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), swedish (sv-SE), icelandic (is-IS), dutch (nl-NL), german (de-DE)
* Inline images (directly inserted into mail body) and attachment images are handled.
* Supported image formats are: JPEG, PNG, BMP and GIF. JPEG and PNG formats are natively supported whereas BMP and GIF formats are converted to PNG format.
Nb: Resized BMP and GIF image files keep original extension (.bmp or .gif), even if they are encoded using PNG format.
* A toolbar button is added to composing window and allows to resize images. Its behaviour can be user-defined:
- resizing of inline images;
and/or
- resizing of attachment images.
* The toolbar button offers a quick settings menuitem to set main settings directly.
* An interactive mode allows to set on-the-fly main settings (dimensions, jpeg quality, name) for each image when resizing.
This mode offers also to keep current settings as settings for all other resizings through the session or to crush default settings.
* Exif data can be read from the file and the Exif orientation information can be used to get the native orientation of the image.
* Settings dialog offers full control on how images are resized: inline and/or attachment images can be resized when:
- sending now;
- sending later;
- sending in background (a feature actually in development, have a look to this page for more information);
- saving message as draft;
- saving message as template;
- auto saving as draft.
For each mode, it's also possible to specify if undo is possible or not, and if resizing should be skipped if any image has already been resized (generally using dedicated custom button).
* Resized attachment images can be displayed with a user-chosen style in attachments pane (color, italic and/or bold).
* Resizing can be undone: it allows to roll back resized images to original versions. This is a real 'undo': resized images are replaced by original images.
* If message is saved in mailbox (draft, template, send later, etc.) it's still possible to resize or unresize images once the message is edited again. Nb: For attachment images undoing resizing is not possible.
* Images embedded into received messages which are replied to or transferred are handled as if they've just been added to the message.
* Images added through a http(s) link are handled.
* Images can be reduced and/or enlarged regarding user-defined maximum and minimum width and height (Nb: Dimensions ratios are not altered).
* Only images which satisfy dimensions criteria (larger than maximum dimensions and smaller than minimum dimensions) are modified. Other images are kept unchanged.
* Images to resize can be filtered via filename criteria: regarding a user-defined list of patterns, image files can be included or excluded; regular expressions can be enabled or disabled for pattern definition.
* Images to resize can be filtered via format criteria (JPEG, PNG, BMP, GIF) based on file extension.
* Resized images can be renamed using a user-defined pattern. This feature is smarter enough to avoid doublons.
Renaming pattern can contain some meta-data like:
- original filename;
- file extension;
- resized image number (= index of image file in resizing queue);
- height;
- width;
- current date (format is editable);
- current time (format is editable).
* Resizing can be enabled/disabled regarding recipients of the message being composed: user can define separated white and black lists of patterns which can control if compression is skipped or not regarding if one or all email recipients match given patterns.
* Images can be forced to jpeg or png format.
* Composer window status bar is used to display information to user. Embedded progress bar is also used during image resizing.
* Behaviour, associations and messages of settings dialog have been designed to improve accessibility for non-sighted people.
* 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.
