Re: Michael's validators integrated

Christian Boulanger wrote:
> The validator features sound great - but I haven't been able to get the test
> pages in CVS working - the problem is 
> 
> - the debugging console is in the way (you cannot even see the fields) -
> that is the case with most test pages by the way . I propose that the
> debugging console should be put in a seperate window in _all_ test pages

You can actually tell that debugging console where to align itself on 
the page (ie. lower right hand corner, upper left hand corner, etc.). 
You can see what param's you have to pass to it in console.js, it's 
actually quite well commented.

If you're using the nwWrapper.js file to launch your nw environment, you 
can just specify:

NWconfig["isProduction"]=true;

to hide the console. You can also specify an opacity value for the 
console so you can see through it to the content behind it. Take your 
pick of solutions.

> - even if I comment out the console,  when I enter some informationa and
> press the button, it alerts  "object object object object ...." 

You can thank me for the lame example test page. That's actually what 
it's suppose to print out. Each one of those Objects is an invalid 
component on the page. I'll make it print out somthing more usefull / 
interesting.

> Michael, can you write just a few lines how to use the widget
> programmatically? Thanks...
> 
> Christian 

Honestly, I've never tried to use the validators programatically. I've 
use the validator mechanism to format data on the fly (ie. when pumping 
data into our dynamic table widget) but never tried creating an input 
box dynamically and then adding a validator to it. I'll try and get an 
example of that implemented in the test page.


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