David, sorry, Wine's not likely to be able to run Corel Draw X3 without several months worth of work, and nobody's focusing on it at the moment. - Dan
Thank you for the reply, Dan, a reply is appreciated.
I must write that I am surprised by this response - your website seems to be asking for help at all levels. I am not quite convinced that months of work is needed (mainly because corelDRAW version 11 works); but maybe you know something I do not - the main point of my posting, of course. Largely, I was asking for policy information; i.e., *what* to do, not *how* to do it, which I feel I can handle.
Good Luck with the project.
dajo
On 28/09/2007, David Outteridge dajo@frii.com wrote:
Thank you for the reply, Dan, a reply is appreciated.
I must write that I am surprised by this response - your website seems to be asking for help at all levels.
Help *is* needed at all levels.
Wine needs testers to test their favorite applications and report bugs. Without the bug reports, the developers don't know (or will miss) regressions or features that are not supported in Wine yet.
It is also a good idea to add an entry to the AppDB (and possibly to the equivalent one over at www.codeweavers.com for the CrossOver version of Wine). This helps the developers know where to focus their attention to get the best coverage. Note that this does not mean that because your application is not popular it will not be fixed.
This is where people like you can come in and help improve the support for running Windows applications on Wine.
I am not quite convinced that months of work is needed (mainly because corelDRAW version 11 works); but maybe you know something I do not - the main point of my posting, of course.
In general, applications that run on Windows 98 or earlier should (in theory) run without problems. The more recent the version of Windows an application wants to use, the less likely it will run, or run well. Newer versions of an application will tend to take advantage of newer features in Windows and start requiring more recent versions, increasing the chances that it will run into areas that are not implemented, or partially implemented in Wine.
For example, the latest version of Wine has added support for side-by-side manifests for installing different versions of a DLL with the same name. This was introduced in Windows XP and is required by newer applications. Also, GDIPlus - an extended drawing interface - was also introduced in XP and has only recently been partially supported in Wine.
The effort to support iTunes 7 took several months to complete, even though earlier iTunes were working. So getting CorelDraw 13 to work is likely not to be an easy task. Once the program installs, there are likely to be regressions with CorelDraw itself.
Largely, I was asking for policy information; i.e., *what* to do, not *how* to do it, which I feel I can handle.
I would suggest raising bug reports for each issue that you encounter as this will help developers track the problems that CorelDraw 13 has on Wine.
Also, try and help maintain the application on the Wine AppDB and CodeWeavers application support page.
And keep testing!
HTH, - Reece
Hi David,
On 28.09.2007 17:28, David Outteridge wrote:
Thank you for the reply, Dan, a reply is appreciated.
I must write that I am surprised by this response - your website seems to be asking for help at all levels. I am not quite convinced that
Yes, any help is appreciated and you can help as well.
months of work is needed (mainly because corelDRAW version 11 works); but maybe you know something I do not - the main point of my posting,
Dan knows more, but AFAIK the X3 version uses some interfaces which are not implemented yet. That's the problem with quite a few new applications, but in due time they will be supported. Besides that, having past versions of an application working fine under Wine unfortunately has nothing to say about newer versions of that app. Sometimes, application internals change so much that it takes literally a year or more to support a newer version. Look at MS Office for example. One more thing: It may or may not be easier to get CorelDRAW 12 to install and run first, perhaps some of the issues you have to fix there also help for the X3 version.
of course. Largely, I was asking for policy information; i.e., *what* to do, not *how* to do it, which I feel I can handle.
Looking at your first mail, I see you indeed dived into the code and accomplished something. My suggestion would be to post a separate mail (if possible, with a proposed hack/patch) with a descriptive subject for every issue you run into. Such mails are generally replied to more often (because of the descriptive subject) than mails with the subject line of this thread. Another hint: You wrote that you used comp.emulators.ms-windows.wine for questions, however that newsgroup is AFAIK a one-way gateway from mail to news, i.e. 98% of the members of that mailing list did NOT see your message.
Good Luck with the project.
Thanks!
Regards, Carl-Daniel
David Outteridge wrote:
Thank you for the reply, Dan, a reply is appreciated.
I must write that I am surprised by this response - your website seems to be asking for help at all levels. I am not quite convinced that months of work is needed (mainly because corelDRAW version 11 works); but maybe you know something I do not - the main point of my posting, of course. Largely, I was asking for policy information; i.e., *what* to do, not *how* to do it, which I feel I can handle.
If you're having trouble installing CorelDraw, then add a bug to http://bugs.winehq.org attaching a +msi debug log, making sure that a bug doesn't already exist for the version and bug you're reporting. Developers may then put hints into the bug as to where to look for next.
A good place to start out helping the Wine project by coding is by writing tests for untested APIs. There are also some todo lists on the website that may give you some pointers as to what to code on in order to start learning about the Wine codebase.
-
Carl-Daniel Hailfinger -
Dan Kegel -
David Outteridge -
Reece Dunn -
Robert Shearman