[tahoe-dev] help! how do I manage dependencies on JavaScript code?

[Greg Troxel]

  We have a half-baked idea of how to solve the JavaScript dependencies
  problem by making the visualizer code be a Secure Decentralized Cloud
  App. :-) Commit Brian's patches to Tahoe-LAFS which cause it to emit
  its download status report in JSON, but don't commit any of the actual
  JS visualization code nor jQuery nor protovis to Tahoe-LAFS. Then
  upload jQuery, protovis, and the visualizer code into the grid itself
  and link to it so that the user sees it whenever they look at the
  status page. Something like that. :-)

That is half-baked, because it only works on the pubgrid :-)

It's normal in software for all sorts of programs ('packages' in linux
and bsd) to depend on each other.  So are there already packages for the
things we want to depend on?  That seems like the right answer, although
it's in opposition to the 'just grab this one tarball' mentality.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20100903/b833dc32/attachment.pgp>