Connect with us: facebook twitter rss

Backlink/Extension Manager

One of the most notable things we've done with our FireFox extension is what we call the extension manager or the backlink manager. This was made possible because we went back to our codebase and took our sweet time rewriting it. The result is an application residing within FireFox that is more reliable and stable than its predecessors. The extension manager is not a replacement to keeping and maintaining an account with us. Its sole purpose is to shed some light and at the same time provide a measure of control over the inner workings of the extension's processes. Whereas the predecessors were marred by occurrences of phantom reports and hidden routines, the new and improved FireFox extension cuts that down to a minimum by letting you know what it's working on or if it's working on anything at all. Granted that the perfect code doesn't yet exist, there will be a few kinks here and there and on those occasions, we greatly value your feedback. To begin with, you may get to the extension manager through the right-click context menu along with our other entries, or through the extension manager link in the popover when generating reports.

The extension manager can be accessed through the context menu or through a link in the pop-over.
The extension manager can be accessed through the context menu or through a link in the pop-over.

 

The extension manager provides a list of all the reports that have run, is running, or is queued. These are differentiated into "steps" as marked under the progress column.

- Step 1 means the report has been successfully recognized by the tool and is currently queued pending the completion of a running report. If there are multiple reports in step 1, then the report that will be tackled next will be picked randomly. If no report is in the step 2 designation, then there shouldn't be any report in step 1. A report is being generated by our FireFox extension
A report is being generated by our FireFox extension.

Another report is requested while a report is still running.
Another report is requested while a report is still running.

- Step 2 denotes that report is currently running and is usually accompanied by a progress estimate. Only one report may be in step 2 at any given time. A queued report automatically starts upon completion of the previous report.
A queued report automatically starts upon completion of the previous report.

- Step 3 marks all reports that are no longer being worked on, this could either mean its finished or it was cancelled. The manager showing 3 reports in varying steps of completion.
The manager showing 3 reports in varying steps of completion.

The one thing you have to remember is that the extension manager is what could be called the controller for our tool which in turn resides within FireFox… it's bound by the same rules set by and for FireFox. Keeping a lot of reports in the tool would naturally mean FireFox will need more memory. Given that this is not an essential part of FireFox, it has low priority so when the internal Garbage Collection routines of FireFox kick in, the reports that you ran that's being kept track of the tool could fall prey to those. In which case, a reload from the extension manager could fail and it would have to be downloaded from our server. The best use is to keep saving reports in our interface, and keep deleting reports on the extension manager to keep our tool's footprint within FireFox on the low side. The delete feature within the extension manager works two ways. Firstly, reports that are in step 1 or step 2 gets cancelled if they are deleted from the manager, they then take on the step 3 designation. When in step 3, deleting the report then removes it from the tool's memory. The extension manager showing a cancelled report.
The extension manager showing a cancelled report.

Though the extension manager is a spartan tool for our app in FireFox, the potential for more functionalities to getting tacked into the manager is boundless. What would you like to see added within the extension? Speak up in the comments below, or contact us through the usual page.