This is off-topic for m.layout, so I'm setting followup-to.
Bryan W. Taylor wrote:
From a marketing point of view, the internal corporate network seems to me like a much larger potential mindshare opportunity. If you can get a company to choose mozilla as part of its architeture for its internal systems then it goes on a whole bunch of desktops. A company can require its use internally, while it might be very hesitent to do so on the internet.
Mozilla Foundation has actually talked to many enterprise companies, both "I/T end user" and ISV or I/T supplier, including those that have supported XForms -- including those who helped fund the development of the spec in the w3c process. The consistent answer is "no".
Most companies have Windows desktop fleets and use IE, and they would not switch to Mozilla just for XForms support. We've talked to dozens of such companies. Those who care about XForms make up the small, not obviously growing XForms plugin market.
On the topic of intranet vs. Internet features:
Mozilla web browsers are general-purpose user agents. They contain more than enough "fat" compared to other browsers, and they are routinely criticized for their size (download, on-disk, in-virtual-memory, ...). There is no way [EMAIL PROTECTED] can justify, e.g., MNG's hundreds of kilobytes for ~300 known uses of .mng on the web. XForms is in even worse shape.
But as I've repeated too many times, especially to you, if someone wants to step up, implement XForms well, and own the code, Mozilla will take it as an extension. A plurality of drivers would even include it by default if it were sufficiently small [TBD, certainly 30K on top of common XML and HTML forms infrastructure is small enough for me].
Optional enterprise extensions are the way to go, and a potential money-maker to boot.
/be _______________________________________________ mozilla-layout mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-layout
