-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi Fabio,
On 01.02.12 18:06, Fabio Pietrosanti (naif) wrote: > Hi all, > > i have received a notice that Enigmail is moving to (partially or > fully) Javascript: > http://www.mozdev.org/pipermail/enigmail/2012-January/014667.html > > Patrick, get on the OpenPGPJS Mailing list > http://list.openpgpjs.org, if we can establish some cooperation! > > Which is the current strategy of enigmail regarding Javascript > uses? > > Alex, Sean, what do you think? Enigmail is a front-end to GnuPG; it does not make directly use of any OpenPGP library. I'm working on replacing parts of Enigmail written in C++ with JS-ctypes. JS-ctypes is a Mozilla-specific extension to JavaScript, that allows to access C-library functions from within privileged JavaScript (similar to python ctypes). After I'll have completed this move, Enigmail will still use GnuPG, but call it via a different mechanism than now. The benefit for me is that I won't need to recompile Enigmail for every Thunderbird release -- which is currently every 6 weeks(!). I'm not aiming at replacing GnuPG with a JavaScript implementation of OpenPGP, therefore I don't see how I could possibly help with openpgpjs. - -Patrick -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBTyl0/8k25cDiHiw+AQiuFQgA0nDvrcZzMInsK0s7NQX6lTmLeg41fNlx OGugq/8TnqTMvNo7/8pOdbI3M1qtzCUZaKkp8g4rRea8fKCUtgy09YW/To/3da4Z y9oIkl/ya+ZafwSNDj3Mo5nvpJ17z594hS7Qc8Lx3eF/gUFtSiIE7Njs/0aXwNMJ PLeSo6M3CCPUIm3Dd/pJcvYbMtGMUDVHbEiHmFsY/vTg8hIJ/c3RVHkqEQTJmfT+ QVXCnX/4eO8pjTntQb0bPrknIFw7/iyNuTgRzLG9FcISfPs0CdOqNYj2sy4sfAaa om7ZB2T6HH3YfwvYoUu4Ps7eneux/MJ4z9bx6YFsi3u181y633addA== =V1J0 -----END PGP SIGNATURE----- _______________________________________________ http://openpgpjs.org
