Re: Importing NW object into other documents

On 23-Sep-04, at 2:46 AM, Christian Boulanger wrote:

> Hi,
>
> I am working alot with pop-up windows instead of nW_windows since they 
> are much easier to debug (for example, I can read a PHP error message 
> whereas content loading in nW just fails without me knowing why).
<snip>

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.

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.

Anyway, just my $0.02

Michael


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