Its behaviour can be user-defined: - resizing of inline images and/or - resizing of attachment images. * A toolbar button is added to composing window and allows to resize images. gif), even if they are encoded using PNG format. Nb: Resized BMP and GIF image files keep original extension (.bmp or. JPEG and PNG formats are natively supported whereas BMP and GIF formats are converted to PNG format. * Supported image formats are: JPEG, PNG, BMP and GIF. Tested versions are: - Windows: XP sp3 (x86), Seven Pro sp1 (圆4) - Linux: Mandriva 2011-2 (x86) - Mac: OS X 10.7 / Lion (圆4) * 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. Features are the following: * All platforms are supported. 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. Auto Resize Image is a Thunderbird add-on which allows to resize inline and attached images while composing email messages. The choice is between v68 without addons or v60 with addons. 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. All my addons are already compatible with TB v60.
If you do so, sending me a simple "thank-you" email would be greatly appreciated. I think i made this work the best professional i could, so my code is well structured and full of comments.
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. 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. 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.
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. That is not the first time that Mozilla is acting as if addons developers and the community was not important. 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. 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 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. 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.
0 kommentar(er)
