Hi, 
Guest
Pic
Sign In

maildev@lists.thunderbird.net

Thunderbird email developers

View all threads

Searching a developer for an AddIn migration to WebExtension

VS
Volker Schmid
Mon, Jan 8, 2018 3:52 PM

Hello,

For this question I was pointed to this mailinglist by Ryan from Thunderbird blog.

We developed and maintained a Thunderbird AddIn since years. Now, with the new WebExtension technique, it will no longer work in future Thunderbird releases soon.

I'm looking for a skilled developer who is able to re-develop the AddIn using WebExtension API. The problem is, that the AddIn is mainly working like this:

Sending process:

  1. Extract email content to filesystem (temp): body, attachments.
  2. Call a local executable to encrypt all into one encrypted container.
  3. Load an HTML default body.
  4. Re-assemble the email with default body and the new attachment (old ones to remove).
  5. Trigger sending.

Based on this, we also do some reconversion which is nearl ythe same:

  1. Extract encrypted attachment to filesystem (temp): body, attachments.
  2. Call a local executable to decrypt all into a temp folder.
  3. Parse results in filesystem (read some file and folder).
  4. Re-assemble a duplicate of the email with body and the attachments from resulting data.
  5. Modify subject (add some notice)

As you can see, there is filesystem access needed. And, as far as I understood, it is not possible to do such filesystem access with WebExtensions by default. So it has to be someone who knows the needed APIs in Thunderbird to be able to do so.

Of course, the existing AddIn source code is available and I'm able to help on any technical detail regarding the files and executables to run.

Is there someone who can do such development? Please contact me on "info (at) regify (dot) com" for further details and for any questions. We will pay by effort, thus you also may send me your hourly rate.

Thank you in advance!

Volker

Hello, For this question I was pointed to this mailinglist by Ryan from Thunderbird blog. We developed and maintained a Thunderbird AddIn since years. Now, with the new WebExtension technique, it will no longer work in future Thunderbird releases soon. I'm looking for a skilled developer who is able to re-develop the AddIn using WebExtension API. The problem is, that the AddIn is mainly working like this: Sending process: 1) Extract email content to filesystem (temp): body, attachments. 2) Call a local executable to encrypt all into one encrypted container. 3) Load an HTML default body. 4) Re-assemble the email with default body and the new attachment (old ones to remove). 5) Trigger sending. Based on this, we also do some reconversion which is nearl ythe same: 1) Extract encrypted attachment to filesystem (temp): body, attachments. 2) Call a local executable to decrypt all into a temp folder. 3) Parse results in filesystem (read some file and folder). 4) Re-assemble a duplicate of the email with body and the attachments from resulting data. 5) Modify subject (add some notice) As you can see, there is filesystem access needed. And, as far as I understood, it is not possible to do such filesystem access with WebExtensions by default. So it has to be someone who knows the needed APIs in Thunderbird to be able to do so. Of course, the existing AddIn source code is available and I'm able to help on any technical detail regarding the files and executables to run. Is there someone who can do such development? Please contact me on "info (at) regify (dot) com" for further details and for any questions. We will pay by effort, thus you also may send me your hourly rate. Thank you in advance! Volker
PK
Philipp Kewisch
Thu, Jan 11, 2018 8:33 AM

Hi Volker,

we are still miles away from having Thunderbird support WebExtensions, so there is no need to worry now.

While I believe it would be helpful to make a variant of WebExtensions available to Thunderbird, our current plan is to support legacy add-ons as long as possible.

If your add-on is listed on addons.mozilla.org we will get in touch with you to inform you in case more concrete plans emerge, you can also keep an eye on the blog.

Hope this clears up some of the confusion!

Philipp

On 8. Jan 2018, at 4:52 PM, Volker Schmid volker.schmid@regify.com wrote:

Hello,

For this question I was pointed to this mailinglist by Ryan from Thunderbird blog.

We developed and maintained a Thunderbird AddIn since years. Now, with the new WebExtension technique, it will no longer work in future Thunderbird releases soon.

I'm looking for a skilled developer who is able to re-develop the AddIn using WebExtension API. The problem is, that the AddIn is mainly working like this:

Sending process:

  1. Extract email content to filesystem (temp): body, attachments.
  2. Call a local executable to encrypt all into one encrypted container.
  3. Load an HTML default body.
  4. Re-assemble the email with default body and the new attachment (old ones to remove).
  5. Trigger sending.

Based on this, we also do some reconversion which is nearl ythe same:

  1. Extract encrypted attachment to filesystem (temp): body, attachments.
  2. Call a local executable to decrypt all into a temp folder.
  3. Parse results in filesystem (read some file and folder).
  4. Re-assemble a duplicate of the email with body and the attachments from resulting data.
  5. Modify subject (add some notice)

As you can see, there is filesystem access needed. And, as far as I understood, it is not possible to do such filesystem access with WebExtensions by default. So it has to be someone who knows the needed APIs in Thunderbird to be able to do so.

Of course, the existing AddIn source code is available and I'm able to help on any technical detail regarding the files and executables to run.

Is there someone who can do such development? Please contact me on "info (at) regify (dot) com" for further details and for any questions. We will pay by effort, thus you also may send me your hourly rate.

Thank you in advance!

Volker

Maildev mailing list
Maildev@lists.thunderbird.net
http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net

Hi Volker, we are still miles away from having Thunderbird support WebExtensions, so there is no need to worry now. While I believe it would be helpful to make a variant of WebExtensions available to Thunderbird, our current plan is to support legacy add-ons as long as possible. If your add-on is listed on addons.mozilla.org we will get in touch with you to inform you in case more concrete plans emerge, you can also keep an eye on the blog. Hope this clears up some of the confusion! Philipp > On 8. Jan 2018, at 4:52 PM, Volker Schmid <volker.schmid@regify.com> wrote: > > Hello, > > For this question I was pointed to this mailinglist by Ryan from Thunderbird blog. > > We developed and maintained a Thunderbird AddIn since years. Now, with the new WebExtension technique, it will no longer work in future Thunderbird releases soon. > > I'm looking for a skilled developer who is able to re-develop the AddIn using WebExtension API. The problem is, that the AddIn is mainly working like this: > > Sending process: > 1) Extract email content to filesystem (temp): body, attachments. > 2) Call a local executable to encrypt all into one encrypted container. > 3) Load an HTML default body. > 4) Re-assemble the email with default body and the new attachment (old ones to remove). > 5) Trigger sending. > > Based on this, we also do some reconversion which is nearl ythe same: > 1) Extract encrypted attachment to filesystem (temp): body, attachments. > 2) Call a local executable to decrypt all into a temp folder. > 3) Parse results in filesystem (read some file and folder). > 4) Re-assemble a duplicate of the email with body and the attachments from resulting data. > 5) Modify subject (add some notice) > > As you can see, there is filesystem access needed. And, as far as I understood, it is not possible to do such filesystem access with WebExtensions by default. So it has to be someone who knows the needed APIs in Thunderbird to be able to do so. > > Of course, the existing AddIn source code is available and I'm able to help on any technical detail regarding the files and executables to run. > > Is there someone who can do such development? Please contact me on "info (at) regify (dot) com" for further details and for any questions. We will pay by effort, thus you also may send me your hourly rate. > > Thank you in advance! > > Volker > > > _______________________________________________ > Maildev mailing list > Maildev@lists.thunderbird.net > http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net
VS
Volker Schmid
Thu, Jan 11, 2018 10:06 AM

Hello Philipp,

thanks, but now I'm even more confused :( Due to public information, the legacy addons stop working from version 57:

https://wiki.mozilla.org/Thunderbird/Add-ons_Guide_57

Citate:
"Mozilla core have disabled "legacy" add-ons (not based purely on WebExtensions) in Firefox 57. Because this type of add-on is not supported from mozilla 57 any more, many interfaces have been removed from Mozilla core."

This are clear words. Even if it is still enabled in 57 to 59, due to the time planing, version 60 will be released in May 2018 and by this, our AddOn will stop to work? No much time until then...

https://de.wikipedia.org/wiki/Mozilla_Thunderbird#Versionstabelle

Does your message mean that you think we can stay with the current AddIn for a longer time than this?

But we need to switch to WebExtensions in the near future, anyway. Therefore, I'm still looking for a developer. Even if the project starts a few weeks or even months later.

Volker

Hello Philipp, thanks, but now I'm even more confused :( Due to public information, the legacy addons stop working from version 57: https://wiki.mozilla.org/Thunderbird/Add-ons_Guide_57 Citate: "Mozilla core have disabled "legacy" add-ons (not based purely on WebExtensions) in Firefox 57. Because this type of add-on is not supported from mozilla 57 any more, many interfaces have been removed from Mozilla core." This are clear words. Even if it is still enabled in 57 to 59, due to the time planing, version 60 will be released in May 2018 and by this, our AddOn will stop to work? No much time until then... https://de.wikipedia.org/wiki/Mozilla_Thunderbird#Versionstabelle Does your message mean that you think we can stay with the current AddIn for a longer time than this? But we need to switch to WebExtensions in the near future, anyway. Therefore, I'm still looking for a developer. Even if the project starts a few weeks or even months later. Volker
JK
Jörg Knobloch
Thu, Jan 11, 2018 5:47 PM

On 11/01/2018 11:06, Volker Schmid wrote:

"Mozilla core have disabled "legacy" add-ons (not based purely on WebExtensions) in Firefox 57. Because this type of add-on is not supported from mozilla 57 any more, many interfaces have been removed from Mozilla core."

And the text goes on to say:

However, Thunderbird 57-59 and Seamonkey still support these add-ons if the appropriate modifications are done to adapt to the changed interfaces. In general, Thunderbird is adding WebExtension support (bug 1396172) while maintaining "legacy" add-ons and hybrid add-ons.

OK, I'll change this to 57-60 and beyond.

Jörg.

PK
Philipp Kewisch
Thu, Jan 11, 2018 6:59 PM

I’m going to write a blog post to clarify our stance, but as Jörg mentioned legacy add-ons will continue to be supported and there is no action required now.

Philipp

On 11. Jan 2018, at 6:47 PM, Jörg Knobloch jorgk@jorgk.com wrote:

On 11/01/2018 11:06, Volker Schmid wrote:
"Mozilla core have disabled "legacy" add-ons (not based purely on WebExtensions) in Firefox 57. Because this type of add-on is not supported from mozilla 57 any more, many interfaces have been removed from Mozilla core."

And the text goes on to say:

However, Thunderbird 57-59 and Seamonkey still support these add-ons if the appropriate modifications are done to adapt to the changed interfaces. In general, Thunderbird is adding WebExtension support (bug 1396172) while maintaining "legacy" add-ons and hybrid add-ons.
OK, I'll change this to 57-60 and beyond.
Jörg.

Maildev mailing list
Maildev@lists.thunderbird.net
http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net

I’m going to write a blog post to clarify our stance, but as Jörg mentioned legacy add-ons will continue to be supported and there is no action required now. Philipp > On 11. Jan 2018, at 6:47 PM, Jörg Knobloch <jorgk@jorgk.com> wrote: > >> On 11/01/2018 11:06, Volker Schmid wrote: >> "Mozilla core have disabled "legacy" add-ons (not based purely on WebExtensions) in Firefox 57. Because this type of add-on is not supported from mozilla 57 any more, many interfaces have been removed from Mozilla core." > And the text goes on to say: > > However, Thunderbird 57-59 and Seamonkey still support these add-ons if the appropriate modifications are done to adapt to the changed interfaces. In general, Thunderbird is adding WebExtension support (bug 1396172) while maintaining "legacy" add-ons and hybrid add-ons. > OK, I'll change this to 57-60 and beyond. > Jörg. > _______________________________________________ > Maildev mailing list > Maildev@lists.thunderbird.net > http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net
PK
Philipp Kewisch
Thu, Jan 11, 2018 7:02 PM

Ok, “nothing” may be wrong, but you don’t have to migrate to WebExtension APIs

On 11. Jan 2018, at 7:59 PM, Philipp Kewisch kewisch@thunderbird.net wrote:

I’m going to write a blog post to clarify our stance, but as Jörg mentioned legacy add-ons will continue to be supported and there is no action required now.

Philipp

On 11. Jan 2018, at 6:47 PM, Jörg Knobloch jorgk@jorgk.com wrote:

On 11/01/2018 11:06, Volker Schmid wrote:
"Mozilla core have disabled "legacy" add-ons (not based purely on WebExtensions) in Firefox 57. Because this type of add-on is not supported from mozilla 57 any more, many interfaces have been removed from Mozilla core."

And the text goes on to say:

However, Thunderbird 57-59 and Seamonkey still support these add-ons if the appropriate modifications are done to adapt to the changed interfaces. In general, Thunderbird is adding WebExtension support (bug 1396172) while maintaining "legacy" add-ons and hybrid add-ons.
OK, I'll change this to 57-60 and beyond.
Jörg.

Maildev mailing list
Maildev@lists.thunderbird.net
http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net

Ok, “nothing” may be wrong, but you don’t have to migrate to WebExtension APIs > On 11. Jan 2018, at 7:59 PM, Philipp Kewisch <kewisch@thunderbird.net> wrote: > > I’m going to write a blog post to clarify our stance, but as Jörg mentioned legacy add-ons will continue to be supported and there is no action required now. > > Philipp > > > >> On 11. Jan 2018, at 6:47 PM, Jörg Knobloch <jorgk@jorgk.com> wrote: >> >>> On 11/01/2018 11:06, Volker Schmid wrote: >>> "Mozilla core have disabled "legacy" add-ons (not based purely on WebExtensions) in Firefox 57. Because this type of add-on is not supported from mozilla 57 any more, many interfaces have been removed from Mozilla core." >> And the text goes on to say: >> >> However, Thunderbird 57-59 and Seamonkey still support these add-ons if the appropriate modifications are done to adapt to the changed interfaces. In general, Thunderbird is adding WebExtension support (bug 1396172) while maintaining "legacy" add-ons and hybrid add-ons. >> OK, I'll change this to 57-60 and beyond. >> Jörg. >> _______________________________________________ >> Maildev mailing list >> Maildev@lists.thunderbird.net >> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net > _______________________________________________ > Maildev mailing list > Maildev@lists.thunderbird.net > http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net
JK
Jonathan Kamens
Thu, Jan 11, 2018 7:18 PM

Hi Volker,

My understanding as an add-on developer, which may be wrong and I hope
someone will correct me if so, is that it is premature to think about
converting Thunderbird add-ons to WebExtensions because many of the
Thunderbird-specific APIs used by Thunderbird add-ons are not yet
available to WebExtension add-ons.

The landscape is still changing rapidly, but at least for now, the
maintainers and developers of Thunderbird are focused on continuing to
support legacy add-ons, not on porting APIs to WebExtensions.

I think it's quite likely that if you try to port a TB add-on to
WebExtensions in "a few weeks or even months," you will discover that it
is simply impossible to do.

Please listen to what the people on this list are telling you: it is not
yet time to worry about doing such a port. They know what they're
talking about.

  jik

On 1/11/18 5:06 AM, Volker Schmid wrote:

Hello Philipp,

thanks, but now I'm even more confused :( Due to public information,
the legacy addons stop working from version 57:

https://wiki.mozilla.org/Thunderbird/Add-ons_Guide_57

Citate:
"Mozilla core have disabled "legacy" add-ons (not based purely on
WebExtensions) in Firefox 57. Because this type of add-on is not
supported from mozilla 57 any more, many interfaces have been removed
from Mozilla core."

This are clear words. Even if it is still enabled in 57 to 59, due to
the time planing, version 60 will be released in May 2018 and by this,
our AddOn will stop to work? No much time until then...

https://de.wikipedia.org/wiki/Mozilla_Thunderbird#Versionstabelle

Does your message mean that you think we can stay with the current
AddIn for a longer time than this?

But we need to switch to WebExtensions in the near future, anyway.
Therefore, I'm still looking for a developer. Even if the project
starts a few weeks or even months later.

Volker

Maildev mailing list
Maildev@lists.thunderbird.net
http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net

Hi Volker, My understanding as an add-on developer, which may be wrong and I hope someone will correct me if so, is that it is premature to think about converting Thunderbird add-ons to WebExtensions because many of the Thunderbird-specific APIs used by Thunderbird add-ons are not yet available to WebExtension add-ons. The landscape is still changing rapidly, but at least for now, the maintainers and developers of Thunderbird are focused on continuing to support legacy add-ons, not on porting APIs to WebExtensions. I think it's quite likely that if you try to port a TB add-on to WebExtensions in "a few weeks or even months," you will discover that it is simply impossible to do. Please listen to what the people on this list are telling you: it is not yet time to worry about doing such a port. They know what they're talking about.   jik On 1/11/18 5:06 AM, Volker Schmid wrote: > Hello Philipp, > > thanks, but now I'm even more confused :( Due to public information, > the legacy addons stop working from version 57: > > https://wiki.mozilla.org/Thunderbird/Add-ons_Guide_57 > > Citate: > "Mozilla core have disabled "legacy" add-ons (not based purely on > WebExtensions) in Firefox 57. Because this type of add-on is not > supported from mozilla 57 any more, many interfaces have been removed > from Mozilla core." > > This are clear words. Even if it is still enabled in 57 to 59, due to > the time planing, version 60 will be released in May 2018 and by this, > our AddOn will stop to work? No much time until then... > > https://de.wikipedia.org/wiki/Mozilla_Thunderbird#Versionstabelle > > Does your message mean that you think we can stay with the current > AddIn for a longer time than this? > > But we need to switch to WebExtensions in the near future, anyway. > Therefore, I'm still looking for a developer. Even if the project > starts a few weeks or even months later. > > Volker > > _______________________________________________ > Maildev mailing list > Maildev@lists.thunderbird.net > http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net > >
VS
Volker Schmid
Fri, Jan 12, 2018 7:23 AM

Hi,

Okay, thank you all for the clarification. From what I read I will have to check if we utilize functions that have been changed or removed in version 57 or later (especially nsILocalFile, as far as I can see). If they are updated/removed/replaced, the AddIn may work through the current year at least and we currently do not need to care about a WebExtensions version.

I am glad that we can continue to use the existing AddIn version. However, this triggers further questions, which I will ask in separate threads.

Thanks,

Volker

Am 11.01.2018 um 20:18 schrieb Jonathan Kamens:

Hi Volker,

My understanding as an add-on developer, which may be wrong and I hope someone will correct me if so, is that it is premature to think about converting Thunderbird add-ons to WebExtensions because many of the Thunderbird-specific APIs used by Thunderbird add-ons are not yet available to WebExtension add-ons.

The landscape is still changing rapidly, but at least for now, the maintainers and developers of Thunderbird are focused on continuing to support legacy add-ons, not on porting APIs to WebExtensions.

I think it's quite likely that if you try to port a TB add-on to WebExtensions in "a few weeks or even months," you will discover that it is simply impossible to do.

Please listen to what the people on this list are telling you: it is not yet time to worry about doing such a port. They know what they're talking about.

  jik

On 1/11/18 5:06 AM, Volker Schmid wrote:

Hello Philipp,

thanks, but now I'm even more confused :( Due to public information, the legacy addons stop working from version 57:

https://wiki.mozilla.org/Thunderbird/Add-ons_Guide_57

Citate:
"Mozilla core have disabled "legacy" add-ons (not based purely on WebExtensions) in Firefox 57. Because this type of add-on is not supported from mozilla 57 any more, many interfaces have been removed from Mozilla core."

This are clear words. Even if it is still enabled in 57 to 59, due to the time planing, version 60 will be released in May 2018 and by this, our AddOn will stop to work? No much time until then...

https://de.wikipedia.org/wiki/Mozilla_Thunderbird#Versionstabelle

Does your message mean that you think we can stay with the current AddIn for a longer time than this?

But we need to switch to WebExtensions in the near future, anyway. Therefore, I'm still looking for a developer. Even if the project starts a few weeks or even months later.

Volker

Maildev mailing list
Maildev@lists.thunderbird.net
http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net

Hi, Okay, thank you all for the clarification. From what I read I will have to check if we utilize functions that have been changed or removed in version 57 or later (especially nsILocalFile, as far as I can see). If they are updated/removed/replaced, the AddIn may work through the current year at least and we currently do not need to care about a WebExtensions version. I am glad that we can continue to use the existing AddIn version. However, this triggers further questions, which I will ask in separate threads. Thanks, Volker Am 11.01.2018 um 20:18 schrieb Jonathan Kamens: > Hi Volker, > > My understanding as an add-on developer, which may be wrong and I hope someone will correct me if so, is that it is premature to think about converting Thunderbird add-ons to WebExtensions because many of the Thunderbird-specific APIs used by Thunderbird add-ons are not yet available to WebExtension add-ons. > > The landscape is still changing rapidly, but at least for now, the maintainers and developers of Thunderbird are focused on continuing to support legacy add-ons, not on porting APIs to WebExtensions. > > I think it's quite likely that if you try to port a TB add-on to WebExtensions in "a few weeks or even months," you will discover that it is simply impossible to do. > > Please listen to what the people on this list are telling you: it is not yet time to worry about doing such a port. They know what they're talking about. > >   jik > > On 1/11/18 5:06 AM, Volker Schmid wrote: >> Hello Philipp, >> >> thanks, but now I'm even more confused :( Due to public information, the legacy addons stop working from version 57: >> >> https://wiki.mozilla.org/Thunderbird/Add-ons_Guide_57 >> >> Citate: >> "Mozilla core have disabled "legacy" add-ons (not based purely on WebExtensions) in Firefox 57. Because this type of add-on is not supported from mozilla 57 any more, many interfaces have been removed from Mozilla core." >> >> This are clear words. Even if it is still enabled in 57 to 59, due to the time planing, version 60 will be released in May 2018 and by this, our AddOn will stop to work? No much time until then... >> >> https://de.wikipedia.org/wiki/Mozilla_Thunderbird#Versionstabelle >> >> Does your message mean that you think we can stay with the current AddIn for a longer time than this? >> >> But we need to switch to WebExtensions in the near future, anyway. Therefore, I'm still looking for a developer. Even if the project starts a few weeks or even months later. >> >> Volker >> >> _______________________________________________ >> Maildev mailing list >> Maildev@lists.thunderbird.net >> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net >>
Empathy v1.0   2025 ©Harmonylists.com