From chouser at bluweb.com  Wed Sep  3 18:01:04 2003
From: chouser at bluweb.com (chouser@bluweb.com)
Date: Thu Sep  4 01:10:49 2003
Subject: [Jsconsole] Errors running jsconsole 1.1
Message-ID: <20030903220104.GF19403@mycroft.flatmonk.org>

JS Console looks like it would be very to me, so I'm hoping to get it
working.  I think I'm seeing the same problem as George Levasseur
<geolev at yahoo.com>, where the window comes up but nothing actually
works.

I have strict JavaScript on, so I see a series of warnings when I pick
"JS Console" out of the Tools menu:

    Warning: reference to undefined property this.K
    Source File: chrome://mozlib/content/lib/js/xpcom/connector.js
    Line: 14
    if(!this.K) this.K = constantSet;

    Warning: reference to undefined property this.loadSet[url]
    Source File: chrome://mozlib/content/lib/js/xpcom/scriptloader.js
    Line: 99
    return (this.loadSet[url] == undefined);

    Warning: assignment to undeclared variable itemNode
    Source File: chrome://jsconsole/content/gui/js/prefs/controller.js
    Line: 86
        itemNode = popupNode.childNodes.item(i);

These are just warnings, but then I get an exception:

    Error: uncaught exception: [Exception... "Component returned failure
    code: 0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH)
    [nsILocalFile.initWithPath]"  nsresult: "0x80520001
    (NS_ERROR_FILE_UNRECOGNIZED_PATH)"  location: "JS frame ::
    chrome://mozlib/content/lib/js/io/file/instantiator.js :: anonymous
    :: line 71"  data: no]

That line appears to be:

    this.handle = new this.constructor(path);

Any idea what's going on?

Thanks,
--Chris
From dfour at noos.fr  Thu Sep  4 11:50:26 2003
From: dfour at noos.fr (Fournier Daniel)
Date: Thu Sep  4 04:53:26 2003
Subject: [Jsconsole] Re: Errors running jsconsole 1.1
Message-ID: <3F56FCD2.5010305@noos.fr>

Thanks for pointing me those JavaScript strinct warnings.

The major bug recently introduced (in Windoz platforms only) has been
fixed in a new version posted today.

*******
WARNING
*******
Before reinstalling JS Console, do the following:

-- Quit Mozilla/Firebird;
-- Edit the prefs.js file in your Mozilla/Firebird user profile
directory removing all lines begining with jsconsole.mozdev.

Then install the last JS Console release and go.

Daniel



From geolev at yahoo.com  Thu Sep  4 20:45:51 2003
From: geolev at yahoo.com (George Levasseur)
Date: Fri Sep  5 01:23:36 2003
Subject: [Jsconsole] Re: Jsconsole post from geolev@yahoo.com requires
	approval
In-Reply-To: <3F4D9922.2070306@noos.fr>
Message-ID: <20030905024551.12880.qmail@web9701.mail.yahoo.com>

Hi Daniel,

Sorry for the slow turn around. 

I tried what you suggested and downloaded the latest
release. I was not able to find prefs.js anywhere in
the mozilla directory structure. 

Still have the same problem with latest build.

Might the fact that I don't have a prefs.js have
something to do with it?

George
> 
> Hi George,
> 
> There is probably a script error somewhere in JS
> Console, when it 
> launches, but it is not thrown in my environment
> (either on Windows or 
> Linux). So I need more details.
> 
> The fact that none of the contextual menu commands
> are working could 
> mean that this error comes when preferences are
> scanned.
> So first edit your prefs.js file (in your Mozilla
> profile dir) and 
> delete all lines begining with:
> 
> user_pref("jsconsole.mozdev
> 
> You have to do this when Mozilla is NOT running.
> 
> Reinstall JS Console, once more ;-), and launch it,
> then close it and 
> quit Mozilla (to have a new fresh version of your
> prefs.js file).
> Go back to your prefs.js file and send me a copy of
> the JS Console 
> preferences branch (all lines begining with
> "user_pref("jsconsole.mozdev").
> 
> I hope I will be able to make a diagnostic.
> 
> Another usefull way to find the error would be to
> look at Mozilla 
> jsconsole dump (from Tools menu) to see if there is
> some error report.
> If so send it to me.
> 
> Cheers,
> 
> Daniel
> 


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
From dfour at noos.fr  Fri Sep  5 09:19:00 2003
From: dfour at noos.fr (Fournier Daniel)
Date: Fri Sep  5 02:22:01 2003
Subject: [Jsconsole] Re: Jsconsole post from geolev
In-Reply-To: <mailman.1049.1062730134.16927.jsconsole@mozdev.org>
References: <mailman.1049.1062730134.16927.jsconsole@mozdev.org>
Message-ID: <3F582AD4.8010604@noos.fr>

Hi George,

You DO have a prefs.js file (otherwise, Mozilla couldn't work).

This file is located in the Mozilla user directory, under the directory
of the profile you use.

For instance, if you launch Mozilla using the "dev" profile, prefs.js
file will have the following path:

c:\\windows\Application Data\Mozilla\Profiles\dev\abcdefgh.slt\prefs.js

where the "abcdefgh.slt" directory is different for every Mozilla
install, so for your install it could be e.g. "zervhdft.slt".

You MUST NOT modify prefs.js when Mozilla is running: Mozilla updates it
before quiting, so any modification would be lost.

You MUST edit this file as indicated in my previous post to have JS
Console work correctly: the prefs.js file has wrong paths for the JS
Console user and store files prefs and installing a new JS Console
release doesn't overwrite the previous prefs.


If you don't want to edit this file directly, you have an easy workaround:

************************************************************
Type in the "about:config" URL in the Mozilla location bar.
Scroll to the "jsconsole.mozdev.code.url" pref.
Clicking this line with the right button, choose the "modify" entry in
the context menu displayed.
In the input box which pops up, replace the forward slash ("/") before
"jsconsoleuser.js" by a double backward slash ("\\") and click OK.

Do the same for the "jsconsole.mozdev.store.code.url" pref and the the
forward slash before "jsconsolestore.js".
************************************************************

Relaunch JS Console: it will work ;-)


Best regards,

Daniel




From dfour at noos.fr  Fri Sep  5 09:19:47 2003
From: dfour at noos.fr (Fournier Daniel)
Date: Fri Sep  5 02:22:48 2003
Subject: [Jsconsole] Re: Jsconsole post from geolev@yahoo.com requires
	approval
In-Reply-To: <mailman.1049.1062730134.16927.jsconsole@mozdev.org>
References: <mailman.1049.1062730134.16927.jsconsole@mozdev.org>
Message-ID: <3F582B03.2040404@noos.fr>

From geolev at yahoo.com  Sun Sep  7 07:15:31 2003
From: geolev at yahoo.com (George Levasseur)
Date: Mon Sep  8 01:14:03 2003
Subject: [Jsconsole] It worked!
Message-ID: <20030907131531.12495.qmail@web9702.mail.yahoo.com>

Thanks Daniel,

That did the trick! Will now run it through its paces.


Thanks for the help.

George

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
From geolev at yahoo.com  Sun Sep  7 08:15:00 2003
From: geolev at yahoo.com (George Levasseur)
Date: Mon Sep  8 01:14:03 2003
Subject: [Jsconsole] Getting started
Message-ID: <20030907141500.1180.qmail@web9708.mail.yahoo.com>

Hi Daniel,

I'm trying to get started with jsconsole and I guess I
don't understand how it is suppose to work. In the
Code panel I typed the following code snippet:

var str = "Hello world";
__SETOUT__( str );

When I Run it, I get...

************************ 2003-09-07 10:19:55.921
************************

SyntaxError: syntax error

Is there more setup I need to perform?

Thanks,

George

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
From dfour at noos.fr  Mon Sep  8 08:24:58 2003
From: dfour at noos.fr (Fournier Daniel)
Date: Mon Sep  8 01:28:07 2003
Subject: [Jsconsole] Re: Getting started
In-Reply-To: <mailman.1161.1062944289.16927.jsconsole@mozdev.org>
References: <mailman.1161.1062944289.16927.jsconsole@mozdev.org>
Message-ID: <3F5C12AA.9050401@noos.fr>

Hi George,

No there is no more setup now :-)

But there is a nasty Midas bug when pasting functions from JS Console 
API as you do :-(

The workaround (till I find a better way to fix that) is simple:
remove the spaces around str to have:
__SETOUT__(str);

Then it will be correctly evaluated.

May be should I remove directly the spaces in the pasting command, but I 
put them to have the possibility to select the "string_OUTPUT" argument 
with a double click. This is because if there is no spaces Mozilla 
select all the function statement, i.e. "__SETOUT__(string_OUTPUT);", 
which is probably you're not wishing.

To get started with JS Console have a look at the Manual (click the 
question mark button in the window statusbar.
You should notably read the Limitation page.

Cheers,

Daniel