Peter, nobody talked about waiting.
And your above mentioned products shows only one thing: all major browsers including FireFox do not support XForms out of the box. So it is not a common tool. Beside that, this should not matter the whole discussion.
XForm is a tool that runs on the browser, it is defined in XML, output can be XML and introduces a lot of nice features. I never asked about the meaning of Xml, XForms, etc, I asked about your ideas. I can imagine that you will use XForm on client side, otherwise you would not call it XForm module. I could copy XForm code inside a Text/Html module. I could even place that code inside this thread and if you are using Mozilla FireFox with the new Mozilla XForms extension istalled you would be able to use it.
THat is what you are looking for? I think no. So what do you want?
Every module has a definition. For example the xml module; purpose of the xml module is to load XML out of a File or URL and to XSL transform this Xml using a given stylesheet. The result gets integrated into the page output. Dotnetnuke stores the settings for the XML Source and the stylesheet.
What is your desired XForm DotNetNuke Module like? Discribe it, give a concrete definition. And please assume I know everything about XForm, Xml, WebServices etc. At least I am able to google...
Thanks,