printLine is not a function in chrome://omnibug/content/model.js:440

[janodvarko]

I have been testing your extension with Firebug 1.12
and I am seeing the following exception.

EXCEPTION in Events.dispatch loadedContext: TypeError: context.getPanel(...).printLine is not a function in chrome://omnibug/content/model.js:440

It breaks the functionality.

Honza

[simpsora]

Hi Honza,

Thanks for the bug report -- and sorry about that, I could have sworn I'd removed the reference to printLine().
In any case, I committed a fix a while ago, and pushed a new build out (0.5.456).

Cheers!

[janodvarko]

OK, good. Where I can get the XPI?

Btw. I tried to run from the source, but had some troubles e.g. missing install.rdf (its created in the build process), couple of files have path to another file (which is JS syntax error) .

Are there any recommended way how to develop (bug fix) the extension?

Honza

[simpsora]

Direct download links to the XPI are here:
http://www.rosssimpson.com/dev/omnibug-0.5.456.xpi
https://github.com/simpsora/omnibug/releases/download/omnibug-0.5.456/omnibug-0.5.456.xpi

There's a bit of documentation available here:
http://omnibug.rosssimpson.com/

To be honest, I've only recently open-sourced the project, and am in the process of re-thinking build and deployment steps. I plan on switching entirely to a grunt task to do build + deployments in the near future. I'd be interested to hear what build/deployment tools you've used for browser extensions.

In the meantime, if you update, go into the firefox directory and run ./build.bash site, an XPI will be created that's ready to go. I've just pushed a change to clean up the build scripts.

There is a bit of a known issue on Windows, in that a couple of JS files are actually symlinks to files in the common/ directory, and git can't really do symlinks on Windows. I've just removed those symlinks; the build script now copies the common JS into firefox/chrome/content/omnibug/ before doing the build.

Let me know if you need anything else!
Ross