Re: RFC: make JSExn non fatal and caught by Template.java

Brian Alliet wrote:

> On Mar 11, 2004, at 8:34 PM, Tupshin Harper wrote:
>
>> Right now, any template that has code that results in a JSExn 
>> effectively kills the application
>
>
> I think that is what we want. If a template application fails the 
> caller should know about it, right?
>
> -Brian
>
I don't think think the current behavior is desirable at all.
1) currently the app is left in an open but unresponsive state....not 
good from the end user's point of view. I think you can't even close the 
main window by normal means.
2) I can envision wanting to create an Ibex IDE within Ibex. To do that, 
you would want to be able to have the user type in a line of javascript, 
and evaluate it without fear of crashing the app.
3) It is very different than the behavior of a Web browser when 
confronted with faulty JavaScript, which is what most users prior 
experience will be.

-Tupshin