console.js

11 messages Options
Embed this post
Permalink
smith () console.js
Reply Threaded More More options
Print post
Permalink
I've released a script that partially implements the Firebug Console API using FirePHP for server-side JavaScript. Right now it works on Jaxer.

See http://nlsmith.com/projects/console/

I would be interested in any comments or suggestions.

Thanks,

Nathan
Christoph Dorn () Re: console.js
Reply Threaded More More options
Print post
Permalink
I have updated the wiki: http://www.firephp.org/Wiki/Libraries/Jaxer

I'll be able to take a look at it in December. Traveling right now.

Have you received any feedback from the Jaxer community? When I had originally posted about the jQuery plugin it went completely un-noticed. It would be great to get some exposure and feedback from Aptana/Jaxer.

smith () Re: console.js
Reply Threaded More More options
Print post
Permalink
Christoph Dorn wrote:
Have you received any feedback from the Jaxer community? When I had originally posted about the jQuery plugin it went completely un-noticed. It would be great to get some exposure and feedback from Aptana/Jaxer.
A couple of people responded to my announcement on the Jaxer forums here: http://forums.aptana.com/viewtopic.php?t=7203

My script should be pretty solid once I fix a couple of Jaxer specific issues, though.

Thanks,

Nathan
smith () Re: console.js
Reply Threaded More More options
Print post
Permalink
This now works on ASP, AppJet, and as a Jaxer extension.

Also, it's the first Jaxer extension ever that's not made by Aptana. I got a free T-shirt out of the deal.

Nathan
Christoph Dorn () Re: console.js
Reply Threaded More More options
Print post
Permalink
Very cool. I'll keep an eye on this to see where it goes. I am planning on releasing a non-PHP specific extension next year.
Christoph Dorn () Re: console.js
Reply Threaded More More options
Print post
Permalink
In reply to this post by smith
Can I send you a login for the wiki so you can maintain the Jaxer page?
smith () Re: console.js
Reply Threaded More More options
Print post
Permalink
Sure, I'd love to.

Nathan

On Fri, Nov 21, 2008 at 8:07 PM, Christoph Dorn (via Nabble) <[hidden email]> wrote:
Can I send you a login for the wiki so you can maintain the Jaxer page?

Tofu () Re: console.js
Reply Threaded More More options
Print post
Permalink
Hello Everyone

I'm playing around with Jaxer and im trying to get some logmessages to the console. Somehow i'm not able to get the extension to run. I'm using the Aptana Studio inbuild Jaxer-Server and placed "Jaxer.console.js" in the local_jaxer/extension Folder in my Workspace but the Extension seems not to get loaded (Jaxer.console is undefined).

So i'm trying to use "console.js" as described on http://nlsmith.com/projects/console/. No error occures but also no messages show up in firebug. But when i look the the Response Headers of the page, i can see all those log-messages appended (i ran this page http://svn.nlsmith.com/console/trunk/jaxer/test.html):

Content-Type: text/html
Content-Length: 176
X-Wf-1-1-1-9: 64|[{"Type":"GROUP_START","Label":"Unimplemented"},"Unimplemented"]|
X-Wf-1-1-1-17: 53|[{"Type":"WARN"},"console.dump() is not implemented"]|
X-Wf-1-1-1-16: 54|[{"Type":"WARN"},"console.table() is not implemented"]|
X-Wf-1-1-1-15: 54|[{"Type":"WARN"},"console.count() is not implemented"]|
X-Wf-1-1-1-14: 59|[{"Type":"WARN"},"console.profileEnd() is not implemented"]|
X-Wf-1-1-1-5: 48|[{"Type":"INFO"},"Multiple strings separated 6"]|
X-Wf-1-1-1-6: 24|[{"Type":"LOG"},"Debug"]|
X-Wf-1-1-1-7: 24|[{"Type":"WARN"},"Warn"]|
X-Wf-1-1-1-19: 30|[{"Type":"LOG"},{"a":1,"b":2}]|
X-Wf-1-1-1-8: 26|[{"Type":"ERROR"},"Error"]|
X-Wf-1-1-1-18: 25|[{"Type":"GROUP_END"},""]|
X-Wf-1-1-1-1: 31|[{"Type":"LOG"},"Hello world!"]|
X-Wf-1-1-1-2: 37|[{"Type":"LOG"},"Hello world! 4 4 4"]|
X-Wf-1-Structure-1: http://meta.firephp.org/Wildfire/Structure/FirePHP/FirebugConsole/0.1
X-Wf-1-1-1-3: 38|[{"Type":"LOG"},"Hello 4! How gosit?"]|
Set-Cookie: JaxerSessionId%24%24127.0.0.1%3A8000=123185464298303194584308018853; path=/
X-Wf-1-1-1-4: 28|[{"Type":"LOG"},"Hello 42!"]|
Pragma: no-cache
Cache-Control: no-cache, must-revalidate,post-check=0, pre-check=0
X-Wf-1-Plugin-1: http://meta.firephp.org/Wildfire/Plugin/FirePHP/Library-FirePHPCore/0.2.0
X-Wf-1-1-1-20: 248|[{"Type":"ERROR","Line":37,"File":"http://127.0.0.1:8000/Test/test.htm"},{"lineNumber":37,"fileName":"http://127.0.0.1:8000/Test/test.htm","message":"Oh no!","stack":"Error(\"Oh no!\")@:0\n@http://127.0.0.1:8000/Test/test.htm:37\n","name":"Error"}]|
X-Wf-1-1-1-23: 38|[{"Type":"INFO"},"console is enabled"]|
X-Wf-1-1-1-24: 38|[{"Type":"LOG"},"This should be here"]|
X-Wf-1-1-1-21: 26|[{"Type":"INFO"},"t: 4ms"]|
X-Wf-1-1-1-22: 39|[{"Type":"INFO"},"console is disabled"]|
X-Wf-Protocol-1: http://meta.wildfirehq.org/Protocol/JsonStream/0.2
Expires: Fri, 23 May 1997 05:00:00 GMT
X-Wf-1-1-1-10: 55|[{"Type":"WARN"},"console.assert() is not implemented"]|
X-Wf-1-1-1-11: 52|[{"Type":"WARN"},"console.dir() is not implemented"]|
X-Wf-1-1-1-12: 55|[{"Type":"WARN"},"console.dirxml() is not implemented"]|
X-Wf-1-1-1-13: 56|[{"Type":"WARN"},"console.profile() is not implemented"]|
Server: Jetty(6.1.11)

200 OK

I run Firefox 3.0.5 with Firebug 1.3.0 and FirePHP 0.2.1 on Windows.
Do you have any Idea why this aint working?

Greetings, T.
Tofu () Re: console.js
Reply Threaded More More options
Print post
Permalink
Bad boy, bad boy. Should have read the other Post in the forum first. Found the solution in this post: http://n2.nabble.com/No-messages-in-Firebug-Console-td842774.html.

The Net-Tab was deactivated. Everything is working fine now with "console.js".
Sorry for the troubles.

Cheers, T.

PS: Any Ideas for the Extension Problem? ;-)
Christoph Dorn () Re: console.js
Reply Threaded More More options
Print post
Permalink
I have not used the jaxer extension myself. You'll have to ask Nathan for help.
smith () Re: console.js
Reply Threaded More More options
Print post
Permalink
In reply to this post by Tofu
T,

I swear it worked when I released it :).

I just tried it on my Mac and Linux server and Jaxer isn't loading the extension at all when it is (re)started. I'll look into it and get it fixed.

When Jaxer starts you should see a trace on the Jaxer log: *** Jaxer.console.js attached

Let me know what happens if you try some of the sample Jaxer extensions. I'll give it a try when I get some time.

BTW, sorry for the late response, my RSS reader just sent it to me today for some reason.

Thanks,

Nathan