I like openpgp_packet_* api and would like to see it exposed to the
user more. It allows a lot of flexibility in use of the library.
Whenever we want to do something a tiny bit complicated than invoking
methods of the global openpgp object, pain starts.
The current naming is just a bit irksome with the static openpgp_
prefixes and so on.
I'm mostly pushing my own solution to modularization because it allows
us to get exactly what we want. My module.js is less than 150 lines of
code - whatever features we need, they can be easily added.
Do we want modules defined by filenames? If so, I could add a hook to
the concatenation step.
What definition conventions do we want?
module('moduleName', function(otherModule) { ... ?
module('moduleName', { depends: ['otherModule'] }, function(require) {
var otherModule = require('otherModule') ?
What kind of user-facing interface?
A global openpgp object?
Do we provide the user with a callback fired when the library is
loaded or do they take care of it themselves?
_______________________________________________
http://openpgpjs.org
