78
edits
XUL Explorer:UseCases/Extension Testing: Difference between revisions
Jump to navigation
Jump to search
XUL Explorer:UseCases/Extension Testing (view source)
Revision as of 02:10, 16 May 2007
, 16 May 2007timeline
MarkFinkle (talk | contribs) No edit summary |
(timeline) |
||
| Line 31: | Line 31: | ||
#Wait for firefox to be closed | #Wait for firefox to be closed | ||
#delete extensions/extension_id | #delete extensions/extension_id | ||
= Timeline = | |||
This is a timeline of what is left to do and when I should have that done | |||
==What is left to do?== | |||
<table style="width:100%" border="1"> | |||
<tr> | |||
<th>Task</th> | |||
<th>Priority</th> | |||
<th>Status</th> | |||
</tr> | |||
<tr> | |||
<td>Auto-locate Firefox profiles and Firefox executable</td> | |||
<td>Low</td> | |||
<td> | |||
* This is probably a more difficult and time consuming feature to do, since it depends on the platform and where to check. | |||
* Nice to have feature, but I will leave it to the end if I have time</td> | |||
</tr> | |||
<tr> | |||
<td>Read values from prefs.js</td> | |||
<td>Medium</td> | |||
<td> | |||
* Done | |||
* Save information so app doesn't have to auto-locate executable/ask user each time</td> | |||
</tr> | |||
<tr> | |||
<td>Pick files (firefox executable)/directories (profile directory)</td> | |||
<td>High</td> | |||
<td>Done</td> | |||
</tr> | |||
<tr> | |||
<td>Locate root directory of extension</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 | |||
* 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 | |||
I am leaning towards option #1</td> | |||
</tr> | |||
<tr> | |||
<td>locate extension id</td> | |||
<td>High</td> | |||
<td>Read application.ini/install.rdf, but how?</td> | |||
</tr> | |||
<tr> | |||
<td>create text file/directory</td> | |||
<td>Medium</td> | |||
<td>Create a directory/text file. I don't think this will be difficult at all</td> | |||
</tr> | |||
<tr> | |||
<td>Launch Firefox</td> | |||
<td>Medium</td> | |||
<td>Not sure how to do this yet</td> | |||
</tr> | |||
<tr> | |||
<td>Wait for Firefox to close and delete file/directory</td> | |||
<td>High</td> | |||
<td>Important, but not sure how to do this either. If I figure out how to launch Firefox, there will probably be an easy way to catch when it is closed.</td> | |||
</tr> | |||
</table> | |||
==Estimated Time of Delivery== | |||
I have had a hell of a time finding the title of another tab (when I did a “Save All” functionality), and I gave up. So finding the root directory will probably take half a day. Locating the extension id will probably take the other half. | |||
Creating a text file and directory, I don't suspect will take very long. Maybe 2 hours at most. | |||
Launching firefox and waiting for it will probably take a full day. | |||
So two days? Meh, I'll make it Wednesday. | |||