Debugging on Internet Explorer

[ambrose levi]

I created a web application using Cappuccino i was able to deploy it
on safari and firefox but could not get it to work on Internet
Explorer. Any possible solutions?

[Alexander Ljungberg]

Run it with the Internet Explore Javascript debugger and analyse the error preventing the app from loading. Make sure to use index-debug.html to make your code readable. Most of the time it will be something like a trailing comma in a list, or other IE specific Javascript quirks.

Alexander

> --
> You received this message because you are subscribed to the Google Groups "Cappuccino & Objective-J" group.
> To post to this group, send email to objec...@googlegroups.com.
> To unsubscribe from this group, send email to objectivej+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/objectivej?hl=en.
>

[ambrose levi]

Yes i've tried that but the debugger did not reveal any errors

On Jan 31, 12:15 pm, Alexander Ljungberg <stillf...@gmail.com> wrote:
> Run it with the Internet Explore Javascript debugger and analyse the error preventing the app from loading. Make sure to use index-debug.html to make your code readable. Most of the time it will be something like a trailing comma in a list, or other IE specific Javascript quirks.
>
> Alexander
>
> On 31 Jan 2012, at 16:49, ambrose levi wrote:
>
>
>

> > I created a .and firefox but could not get it to work on Internet

> > Explorer. Any possible solutions?
>
> > --
> > You received this message because you are subscribed to the Google Groups "Cappuccino & Objective-J" group.
> > To post to this group, send email to objec...@googlegroups.com.
> > To unsubscribe from this group, send email to objectivej+...@googlegroups.com.

> > For more options, visit this group athttp://groups.google.com/group/objectivej?hl=en.- Hide quoted text -
>
> - Show quoted text -

[Alexander Ljungberg]

Sometimes debugging Internet Explorer can be a bit of a pain. The brute force method is to comment out all of your code and verify the app starts. Then re-enable one piece at a time, checking that each one works, until you find the one that makes the app fail. Try to divide that failing piece up further, commenting out about half of it to see if it starts to work then, then half of the code where the error must be, etc. Eventually you'll get to a point where the error must be in just a few lines of code, where if you comment them out the app works, but if you leave them in it does not.

Study those lines for extra commas and so on until you see what's wrong or post it here.

Alexander

[ambrose levi]

Yes I have tried that and even made a simple "Hello World" application just to see if it would appear on Internet Explorer which it did.

[Alexander Ljungberg]

So what lines are the lines with the error?

Alexander