Hi! ~~~ As Felix wrote we are currently restructuring the project to fit into a common goal. I would like to suggest the following directory structure:
plugins/ - Plugin API and subdirectories containing the plugin code plugins/chrome/ - Plugin for chrome (current state) webmail/ - Generic WebMail API (here We have to define a generic API to be implemented by all webmail integrations) webmail/gmail/ - Current gmail integration code src/ - Main source folder for the openpgp implementation (keyring, message, private / public key) src/ciphers/ - Generic openpgp crypto interface src/ciphers/asymmetric/ - DSA, RSA, Elgamal src/ciphers/symmetric/ - AES, blowfish, CAST5, DES, twofish src/ciphers/hash/ - Hash algorithms (sha*, ripe-md160, md5) src/compression/ - Compression methods (currently none; ZIP, ZLIB Bzip2) src/encoding/ - Encoding libs (base64, ascii armor format, emsa / eme pkcs1) src/packet/ - Openpgp packet implementation src/type/ - Openpgp type objects (MPI, keyId, s2k) src/util/ - Debugging, type conversion (string <-> array), checksum calculation lib/ - Libraries lib/rfc822/ - I'm currently working on a RFC822 Message parser which i use to parse message in gmail doc/ - Documentation (currently i use JavaDoc) config/ - Generic configuration API for all plugins. A use would be able to choose on the used plugin which webmail integration is to be used. Build targets would be the plugins for the browser. The src folder is structured like the current version of gpg4browsers js/ folder containing the openpgp implementation. Please give some input. I may violate some common practice on github. regards, carsten -- Recurity Labs GmbH | Carsten Wentzlow http://www.recurity-labs.com | [email protected] Wrangelstrasse 4 | Fon: +49 30 69539993-0 10997 Berlin | Mobil: +49 163 7007430 Germany | PGP: AF3F 4C6C F80A 7C76 7DDE | 39BF 83DD 3803 E163 4F45 HRB 105213 B, Amtsgericht Charlottenburg, GF Felix Lindner _______________________________________________ http://openpgpjs.org
