paulrouget / firefox-jsterm Goto Github PK

When an object has many fields one hits Tab repeatedly or uses autorepeat to scan them. But if you go to far it's hard to backup. I suggest Shift+Tab to step backward through the completion list.

When entering an object on its own, JSTerm does not recognize the object syntax and shows an error instead. As a REPL it should recognize the object and simply return it.

{ a: 'b', c: 'd' } // error: SyntaxError: invalid label

Compare this with Node’s behaviour which is the correct one:

> { a: 'b', c: 'd' }
{ a: 'b', c: 'd' }

This is a feature request more than a bug.

Navigation between the control elements can be a useful way of moving around between the JSTerm and the Web Console.

Examples (use cases):

Example 1.

Game canvas with resize event captured, on the JSTerm you change the window size "resize to 300 300" then you want to move to the Web Console to check on your variables, right now you can only do "console open" assuming its not already open, on which your only option is to click on the web console input field.

Image 1

Image 2

Example 2.

Again related to resize, once you resized you decide you want to change some properties on the of your html so you open the inspector "inspect body" if focus was passed to the style inspector we could potentially write the rules with the keyboard then navigate back to the JSTerm to either close the inspector and keep resizing or do another changes

Image 1

Proposed key bindings:

a combination of either this could work

Move forward: Command + option + ]
Move backwards: Command + option + [

Can we use Backbone.js to structure stuff & separate data and how it looks like here?

Errors:

Error: NS_ERROR_FILE_NOT_FOUND: Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIXPCComponents_Utils.import]
Source file: chrome://jsterm/content/jsterm.js
Line: 4

Error: TypeError: iframeWindow.JSTermUI is undefined
Source file: resource://gre/modules/XPIProvider.jsm -> jar:file:///E:/Piotrek/pliki%20program%C3%B3w/FirefoxDeveloper/Data/profile/extensions/[email protected]!/bootstrap.js
Line: 34

Error: TypeError: JSTermUI is undefined
Source file: chrome://jsterm/content/jsterm.xul
Line: 1

A statement that evaluates to undefined or null won't output anything. It might be hard to tell what's going on:

actual:

var x = document.getElementById("container");
x;
6; // 6

expected:

var x = document.getElementById("container");
x; // null
6; // 6

It is annoying to see the undefined after a declaration. Maybe it could just show if it's null?

it is not possible to install on FF19.02

Seen under Nightly 18.0a1 (2012-09-23), JSTerm 2.0 Released August 31, 2012.

I tried several times to copy the issues URL but it's not working. First I though Copy didn't work in general but now I see it's only if you're selecting the URL or a substring of the URL.

In Firefox 18 and later, Web Console is changed to using remote debug protocol: https://bugzilla.mozilla.org/show_bug.cgi?id=768096

I installed on FF 18 edition but the console screen empty as well as can't write something.

We should bufferize print calls

Older versions of jsterm had an ":undock" command that allowed you to undock the jsterm window. It would be great to have that back in the current version.

When I install JSterm 2.3 on Aurora 20 and Nightly 21, I get these warnings:

Timestamp: 2013-01-31 10:28:52 AM
Warning: WARN addons.xpi: Error loading bootstrap.js for [email protected]: [Exception... "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIStringBundle.GetStringFromName]" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: resource://gre/modules/XPIProvider.jsm -> jar:file:///Users/jeff/Library/Application%20Support/Firefox/Profiles/b49h24eg.default/extensions/[email protected]!/bootstrap.js :: <TOP_LEVEL> :: line 19" data: no]
Source File: resource://gre/modules/XPIProvider.jsm -> jar:file:///Users/jeff/Library/Application%20Support/Firefox/Profiles/b49h24eg.default/extensions/[email protected]!/bootstrap.js
Line: 19

Timestamp: 2013-01-31 10:30:44 AM
Warning: WARN addons.xpi: Exception running bootstrap method startup on [email protected]: TypeError: toolDefinition is undefined
Source File: resource:///modules/devtools/gDevTools.jsm
Line: 69

The jsterm tab doesn't show up in the devtools panel:

After installing JSTerminal the code panel of the Inspector tab is always blank.
Fx 24.0

Hard to tell if I have the latest version, :help should print the version number of the addon. Or maybe a :version command.

Title is pretty much self-explanatory. I installed this addon both from xpi file available on github and addons page with no success. It works like a charm in FF 16.0.2 though, but not in my beloved early-bird aurora/nightly builds.

Hi!

Just installed this extension to try it out. However, I found something slightly confusing; not sure if that's something you can fix or if it's something to do with the Add-ons site.

Generally we always have to restart Firefox in order to get an add-on working. But in this case I got this beautiful and promising "No restart" sticker close to the title:

This got me superexcited as having to restart my browser always makes me delay the restart until I have finished with everything I was doing/reading/etc--so it could well be that I forget that I install the add-on and only remember about it like three days later.

Anyway, I installed it, and opened dev tools, and... nothing, JSTerm wasn't there.

I effectively had to restart the browser. Then I opened the dev tools and finally the terminal was there. I am using Firefox 20 (beta channel).

Thanks for the extension!

The behavior of version 2.4 is:

:coffee // error: SyntaxError: syntax error

JsTerm is looking great, but I think a killer feature of the webkit's dev tools is missing: the ability to inspect evaluated objects inline. Although it is possible with the panel, being able to do it inline is much more comfortable in my opinion (and most of my coworkers and friends agree)

There's a strange focus problem on my system and it's unusable.

For example, I hit Shift+F2, the toolbar appears, I type "help", hit enter and then I see something flash, it disappears and Firefox has lost focus.

Trying something that doesn't exist is even worse: I type the letters

t
te
tes

once I hit the 's', something flashses, the toolbar and firefox loose focus and even if I click there again the focus is automatically lost again. At that point I'm unable to even use backspace to delete "tes".

I don't know if this is a problem with jsterm, Firefox, Gnome-Shell or a combination of these. There have been some weird focus problems with Gnome-Shell 3.4 and Guake as well, see: http://guake.org/ticket/436

implement FDB - FirefoxDeBugger. Somewhat like GDB, that allows you to control the debugger from the JSTerm. In comparison to GDB, it should show the source that is debugged in a panel on the left-hand side, like the current property panel on the right-hand side.

Does that sounds useful?

Firefox Terminal V3 is a nice extension!
I have one small request though:
Can chrome://jsterm/content/orion.css be replaced with chrome://jsterm/skin/orion.css?
This allows themers such as me to style the terminal in the same style as the other window/devtool parts in "full themes".

I tried to open a static html file and recieved an error that a jQuery method was undefined, upon further research it looks like the $ namespace is being overridden by JSTerm :(.

> $
(function JSTH_$(aSelector)
  {
    "use strict";

    return aJSTerm.window.document.querySelector(aSelector);
})

This is actually really frustrating, any thoughts on this?

Now, when pressing TAB to show suggestions on bottom, object properties are in alphabetic order (at least it's looks that). It causes that some properties inherited from prototype such __defineSetter__, __defineGetter__,.. are first on the suggestions list while I think these properties aren't so important because are the same for every object.

My proposal: show first own properties, next inherited from prototype

When starting JSTerm, there's too much flickering.

I'm always switching from typing to using the mouse to click on objects to inspect them. A keyboard shortcut to access the last object would be sweet, and maybe it could focus the filter input.

It'd be useful to be able to copy values from the object inspector (right-hand value list from "[+]"). Currently I can hover a value to see it if it's too long for the field but how do I copy it e.g. to paste into the terminal?

jsterm looks to be a great tool, by the way!

It does delete a word, but when you continue typing the word reappears and the new characters are inserted after it.

I'm using Iceweasel 16.0a2 with Xfce on Debian, I think the Ctrl+W actually comes from Gtk and me having Emacs keys enabled.

So, all dev tools are quite shitty currently for non-js langs. Coffee is extremely useful as DOM manipulator because of its much shorter syntax and it will be cool to have it in console.

I hope jsterm will be able to innovate and i'll gladly contribute its support soon.

A console.log("foo") entry should print "foo".

We might want to support console.* calls from the page too.

The treeview implementation has been updated. We should use the variable view.