Hi, I've attached a few patches against the latest? (yesterday's) CVS.
I've left IOElement still only allowing an Xframe thread and for NS4. Was there a special reason for this? I know in NS4 it's needed as it can't post from an ilayer form? Though it looks like NS4 is only allowed to do a get? Does anyone have a perl port of the SODA stuff? I'd like to learn more about datasource etc. Thanks for the demo's Raymond. Very helpfull to aid in my understanding of new features. Needed a dynlayer_dom.js patch (attached). OK now for TabManager. It's ready over the weekend I hope: It's a pain as some browsers don't generate key events for all required keys. So I propose the basic functionality for all broswers is: 1) for moving in same tabgroup - numeric keypad left / right 2) for moving between tabgroups - numeric keypad up / down 3) for selecting the current tab/dynlayer/widget - space key This is the worst case for NS4 on Windows - NS4 on Linux will require a special fix as some keys only generate events onkeyup and others onkeydown :( To the above functionality there will be available for browsers that generate the key events. 1) left / right arrow keys and shift+tab / tab 2) up / down arrowkeys 3) enter key This is the best case for IE as the default use of the tab can be stopped with e.preventDefault() - Netscape will require a special fix to force focus when using the tab key. I'll leave special fixes commented out in the code so are there if needed! ----- Kevin.
dynapi3x-patchfiles.zip
Description: Zip compressed data
