Re: Debugging Javascript generated on the fly whre there is no stored Javascript file.

Rob

when I started with javascript I used alert to get variables displayed. Now
a days
I build in ... console.log('cache: ' + require.cache) in my code. The
value is then
display in the console in google tools.

There is another nice feature, alert wil give you [object object] if you
tries to display
an object (array or object) but console.log(myObj) will give you what is in
the object.

You may even use console.log(JSON.stringify(myObj, null, '\t')) to display
an object
in well formed JSON

console.log also won't stop processing of the script so the users dosn't
notice other
than if put into a large loop it will slow the page down.

On Fri, May 26, 2017 at 12:24 PM, Rob Dixon <robertsdixon@xxxxxxxxx> wrote:

Henrik,

Many thanks. I can see the HTML and Javascript that I generate but as soon
as I try to do anything, Chrome demands that I use Ctl+P to open a file.
The variable that I wish to watch is not in any file - it is generated by
my system.

Is there no one else using CGIDEV and generated HTML/Javascript that has
had a similar problem?



On 22 May 2017 at 10:23, Henrik Rützou <hr@xxxxxxxxxxxx> wrote:

If you call the CGI program from Crome and developer-tools active while

you

call the page
(start it with F12 just before you activate the page) you are able to see
what is sent to the
browser under "network" - click on any of the links and the will be both
the header and
what is received.

On Mon, May 22, 2017 at 10:50 AM, Rob Dixon <robertsdixon@xxxxxxxxx>
wrote:

Keith,

Many thanks but I generate the HTML and Javascript - it isn't stored
anywhere. I am using CGIDEV2 and the stored HTML is only very basic,

most

of it, including the <script> statement, being generated by my system.

This

allows great flexibility. I don't see how to get into debug mode.

Rob

On 20 May 2017 at 13:36, Keith McCully <keithmccully@xxxxxxxxx> wrote:

Hi Rob,
You could make a temporary test version of your setup.

Assuming the html is in IFS then copy your runtime source to a .js

file

there. Make sure you include a <script > reference to your temp file

in

the

html then it should appear in chrome debug.

Regards

Keith

sent from Android
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400)

mailing

list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.

--
Rob Dixon

www.erros.co.uk
www.boarstall.com
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400)

mailing

list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.

--
Regards,
Henrik Rützou

http://powerEXT.com <http://powerext.com/>
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.

--
Rob Dixon

www.erros.co.uk
www.boarstall.com
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.