78
edits
XUL Explorer:UseCases/Extension Testing: Difference between revisions
Jump to navigation
Jump to search
m
XUL Explorer:UseCases/Extension Testing (view source)
Revision as of 01:42, 18 May 2007
, 18 May 2007→What is left to do?
| Line 66: | Line 66: | ||
<td>Locate root directory of extension</td> | <td>Locate root directory of extension</td> | ||
<td>High</td> | <td>High</td> | ||
<td>Needed to write in text file. This is tricky because it should point to the same directory as application.ini, but where that file is isn't always relative to the current file. So we have a few options | <td>Done | ||
Needed to write in text file. This is tricky because it should point to the same directory as application.ini, but where that file is isn't always relative to the current file. So we have a few options | |||
* Go through each tab for a file named application.ini, and take it's document.title | * Go through each tab for a file named application.ini, and take it's document.title | ||
* Have the user locate by hand (but this shouldn't be saved to prefs.js | * Have the user locate by hand (but this shouldn't be saved to prefs.js | ||