Re: Importing NW object into other documents

>
> The reason it fails is that the nw window widget depends on you 
> including a JavaScript file at the end of the content called 
> 'content_load_finished.js' or some such thing. If you were to have 
> access to the error templates for PHP (I'm no PHP guru, maybe this 
> isn't possible) and include this js file at the end of them, then you 
> would get the PHP errors to display in the dynamic content loading 
> window widget.

That is a good suggestion. PHP's error handling is miserable (at least 
in the 4.x version), and I have never gotten around to try to use them. 
But what you suggest is possible.

> As to your other suggestion about defaulting to opener.parent if the 
> nw environment can't be found, I'm not sure how feasible that is. I 
> don't think it would work as there are too many assumptions in the 
> code that deal with page scope and what widgets are created in it. If 
> you were to start mixing widgets for two different windows in the one 
> widget registry, I think it would just lead to too much confusion.
>
You are probably right. I wasn't so much thinking about the parent 
window widgets but rather access to the prototypes and the framework, so 
that I could create widgets in the new window without having to reload 
the whole framework.

There are other debugging advantages of pop-up-windows, such as that you 
can easily view the page source code which is more difficult with nW 
windows. But I imagin that I can go back to nW windows once the 
processes that run in particular windows don't have to be debugged any 
more..

Thanks,

Christian

_______________________________________________
The netWindows developers list: [email protected]
http://netwindows.org/mailman/listinfo/devel_netwindows.org