Nikolay Sivov writes:
> I don't, you're right =). So you mean just add empty msxml4, register
> it as windows does and forward object
> creation to functional module?
Pretty much, yes.
--
Alexandre Julliard
julli...@winehq.org
On 2/3/2010 01:26, Alexandre Julliard wrote:
Nikolay Sivov writes:
No need to care of differences between version for a start, will be
ideally not to check for version at all.
And yes, winexml should be superset of course.
You don't want a winexml if it can be helped at all. Non-sta
Nikolay Sivov writes:
> No need to care of differences between version for a start, will be
> ideally not to check for version at all.
> And yes, winexml should be superset of course.
You don't want a winexml if it can be helped at all. Non-standard dlls
should be avoided. Just implement one of
On 2/2/2010 20:28, Reece Dunn wrote:
On 2 February 2010 16:19, Nikolay Sivov wrote:
Hi.
Wine currently has only one module for MSXML parser - msxml3. Since the
third one v4 and v6 are already out.
There is also an msxml 5. This is only available via Office 2003/2007,
and is installe
On 2 February 2010 16:19, Nikolay Sivov wrote:
> Hi.
>
> Wine currently has only one module for MSXML parser - msxml3. Since the
> third one v4 and v6 are already out.
There is also an msxml 5. This is only available via Office 2003/2007,
and is installed by that. See http://support.microsoft.com
Hi.
Wine currently has only one module for MSXML parser - msxml3. Since the
third one v4 and v6 are already out.
Judging from file size I don't think native modules reuse some code
between them, instead it looks like a completely
independent builds.
What Wine's policy should be about that? Is
