Whither msxml?

[Dan Kegel]

For the past two years, I've helped UCLA's cs130 by pointing
them at an area of Wine that needs improvement
and helping them get patches submitted.
For Winter 2007, I'm considering having them focus on msxml3.

So I'm starting to look at bugzilla (see my previous message)
and dig up demo apps and articles that might help us
understand where wine's msxml needs to go.
Man, oh, man are there a lot of pages about msxml out there.
If anyone has tips on sore spots with Wine's msxml, please
let me know.

A few random notes:

MSDN on msxml:
http://windowssdk.msdn.microsoft.com/en-us/library/ms763742.aspx

I see the spec file for msxml3 has a bunch of stubbed ordinals.
Anyone know what they are?

Can Wine handle the "msxml3 jumpstart" demo app from year 2000 yet?
http://msdn.microsoft.com/library/en-us/dnmsxml/html/sax2jumpstart.asp

Or the "msxsl.exe" wrapper app?
http://www.microsoft.com/downloads/details.aspx?familyid=2fb55371-c94e-4373-...

"Programming The SAX2 3.0 Using MSXML" (examples in vb6)
http://xml.sys-con.com/read/40210.htm

"MSXML, It's Not Just for VB Programmers Anymore" (examples in perl)
http://www.perl.com/pub/a/2001/04/17/msxml.html

"Python & XML"
http://safari.oreilly.com/0596001282

Here's a page that seems to show how to use msxsl and
explains differences between msxml3 and msxml4:
http://www.perfectxml.com/articles/xml/XSLTInMSXML.asp

msxml3 examples:
http://www.perfectxml.com/articles/xml/msxml30.asp

"A C++ Template Wrapper for the XML SAX API"
http://www.ddj.com/showArticle.jhtml?articleID=184401778

etc. etc.
- Dan

[Vijay Kiran Kamuju]

Hi

our msxml idl flles are not in sync with psdk idl files.
especially it still doesnot have SAX defines.
And XML DSO definitions. (this is a bit compilicated).
As msxml.idl includes xmldso.idl in PSDK headers.
And msxml2.idl defines them in the idl file itself.
As there are some incompatibilities with msxml2 and msxml3 (esp guids)
But in the wine implementation, Mike wnet for a simplified approach
with the msxml idl implementation.
To reuse msxml.idl functionality in msxml2.idl, by including it.
But we should not do that, if we want to support older versions of msxml.
We should redo the idl's first inorder, to get msxml implemented correctly.

Thanks,
VJ

On 9/23/06, Dan Kegel  wrote:
> For the past two years, I've helped UCLA's cs130 by pointing
> them at an area of Wine that needs improvement
> and helping them get patches submitted.
> For Winter 2007, I'm considering having them focus on msxml3.
>
> So I'm starting to look at bugzilla (see my previous message)
> and dig up demo apps and articles that might help us
> understand where wine's msxml needs to go.
> Man, oh, man are there a lot of pages about msxml out there.
> If anyone has tips on sore spots with Wine's msxml, please
> let me know.
>
> A few random notes:
>
> MSDN on msxml:
> http://windowssdk.msdn.microsoft.com/en-us/library/ms763742.aspx
>
> I see the spec file for msxml3 has a bunch of stubbed ordinals.
> Anyone know what they are?
>
> Can Wine handle the "msxml3 jumpstart" demo app from year 2000 yet?
> http://msdn.microsoft.com/library/en-us/dnmsxml/html/sax2jumpstart.asp
>
> Or the "msxsl.exe" wrapper app?
> http://www.microsoft.com/downloads/details.aspx?familyid=2fb55371-c94e-4373-...
>
> "Programming The SAX2 3.0 Using MSXML" (examples in vb6)
> http://xml.sys-con.com/read/40210.htm
>
> "MSXML, It's Not Just for VB Programmers Anymore" (examples in perl)
> http://www.perl.com/pub/a/2001/04/17/msxml.html
>
> "Python & XML"
> http://safari.oreilly.com/0596001282
>
> Here's a page that seems to show how to use msxsl and
> explains differences between msxml3 and msxml4:
> http://www.perfectxml.com/articles/xml/XSLTInMSXML.asp
>
> msxml3 examples:
> http://www.perfectxml.com/articles/xml/msxml30.asp
>
> "A C++ Template Wrapper for the XML SAX API"
> http://www.ddj.com/showArticle.jhtml?articleID=184401778
>
> etc. etc.
> - Dan

[Huw Davies]

On Sat, Sep 23, 2006 at 05:52:51AM -0700, Dan Kegel wrote:
> If anyone has tips on sore spots with Wine's msxml, please
> let me know.

Hi Dan,

There are lots of things that need to be done in msxml3:

Currently we have implemented some of the DOM methods, most of these
are part of the IXMLDOMNode interface (node.c) - you'll still see a
lot of stubs in there.  Most of the additional methods for the
interfaces derived from IXMLDOMNode (see eg IXMLDOMText in text.c)
also need filling out.  Hopefully the infrastructure for DOM is pretty
much laid out however.

There's currently no SAX support, so that could be another area of
fruitful work.

Some of the helper apis like IXMLHTTPRequest would also be fun.

We also don't have a plan for msxml4, so some design decisions
regarding this should be made at some point.

Huw.