XUL Explorer:UseCases/Extension Testing: Difference between revisions

Jump to navigation Jump to search
Line 111: Line 111:
<tr>
<tr>
<td>Need more explanation about each step, since it is very subtle right now (dialog titlebar). Mark Finkle recommended a wizard.</td>
<td>Need more explanation about each step, since it is very subtle right now (dialog titlebar). Mark Finkle recommended a wizard.</td>
<td style="background-color:red;text-align:center;">High</td>
<td style="background-color:green;text-align:center;">Done / High</td>
<td>Mostly done. Just finishing localizing the parts that I have changed.</td>
<td>
*A wizard has been completed. There is one shot for intro, 3 shots for executable/profile/root, and a window for confirmation. Maybe this is too much? Looking for suggestions!
*Just finished localizing the parts that I have changed.</td>
</tr>
</tr>
<tr>
<tr>
<td>Pass “profile path” and “firefox path” to extensionTestManager, rather then extensionTestManager try to find these itself</td>
<td>
<td style="background-color:orange;text-align:center;">Medium</td>
Pass “profile path” and “firefox path” to extensionTestManager, rather then extensionTestManager try to find these itself
<td>Not Completed</td>
</td>
<td style="background-color:green;text-align:center;">Done(?) / Medium</td>
<td>
*this has sort of been done. Rather then trying to find out the executable/profile path in XE, it has been moved to the more logical place. The wizard. It passes back stuff. We like stuff.
</td>
</tr>
</tr>
<tr>
<td>Need to get rid of that rdf library</td>
<td style="background-color:yellow;text-align:center;">Low</td>
<td>This is bothering the heck out of me. I shouldn't be using a 700 line rdf library and use it just once. But that would mean understanding RDF, which still isn't explained all that well, and even worse to try and develop with it.
<tr>
<tr>
<td>''Future suggestion'' : install other extensions to help debug the current extension. For example, add venkman support if it is not already present.</td>
<td>''Future suggestion'' : install other extensions to help debug the current extension. For example, add venkman support if it is not already present.</td>
78

edits

Navigation menu