add 'Tahoe Explorer' (JavaScript-based UI) to Tahoe #1000

New Issue

tahoe-lafs · 2010-03-17T01:54:55Z

davidsarah commented

2010-03-17 01:54:55 +00:00

Toby Murray has written a JavaScript front-end called "Tahoe Explorer", which looks very promising -- particularly from the point of view of solving [security problems with the existing WUI]query:status!=closed&keywords~=capleak, as well as potentially better usability and performance. (It's not often you get to improve all of those at the same time!)

I don't think this should be added just as a 'contrib' package; it is liable to bitrot that way.

The original code was dependent on Cajita, which would have required solving some (minor) licensing issues#comment:7, but it turns out that this dependency is easily removed.

Of more concern is that the code has no unit tests. We need to decide how to test JavaScript code (there are several possibilities including JSUnit and Windmill; I'll open another ticket about that).

Toby Murray [has written](http://allmydata.org/pipermail/tahoe-dev/2010-March/004137.html) a JavaScript front-end called "Tahoe Explorer", which looks very promising -- particularly from the point of view of solving [security problems with the existing WUI]query:status!=closed&keywords~=capleak, as well as potentially better usability and performance. (It's not often you get to improve all of those at the same time!) I don't think this should be added just as a 'contrib' package; it is liable to bitrot that way. The original code was dependent on Cajita, which would have required solving some (minor) [licensing issues](/tahoe-lafs/trac-2024-07-25/issues/6057)#comment:7, but it turns out that this dependency is easily removed. Of more concern is that the code has no unit tests. We need to decide how to test JavaScript code (there are several possibilities including [JSUnit](http://www.jsunit.org) and [Windmill](http://www.getwindmill.com); I'll open another ticket about that).