On Mon, 19 Jun 2006, Wine Bugs wrote:
vitaliy@kievinfo.com changed:
What |Removed |Added
Status|RESOLVED |CLOSED------- Additional Comments From vitaliy@kievinfo.com 2006-19-06 14:11 ------- Again this is not a bug. There is nothing to fix because there is nothing that broke.
I disagree. If IE doesn't run, it's a bug. I would actually say that it's a major bug - IE is one the those core applications that users expects to work.
You are incorrect about "there is nothing to fix": Perhaps the source code is fine, but the documentation is certainly not. http://appdb.winehq.org/appview.php?versionId=469 even says:
"(to be continued because then it still doesn't run because of ole errors)"
Anyone is welcome to write up instructions on what to override and place them in appDB. Bugzilla is not the right place for that.
Why do you think Bugzilla cannot be used for tracking documentation bugs? There is a "wine-documentation" component and a "WineHQ Apps Database" component, if you think that wine-misc is totally wrong.
I would very much prefer is this bug could be left open until someone has managed to figure out what needs to be overridden to actually *run* IE.
Regards,
Try adding wine overrides for iexplore
Just my 2 cents, Vijay
On 6/20/06, Peter Åstrand astrand@cendio.se wrote:
On Mon, 19 Jun 2006, Wine Bugs wrote:
vitaliy@kievinfo.com changed:
What |Removed |Added
Status|RESOLVED |CLOSED------- Additional Comments From vitaliy@kievinfo.com 2006-19-06 14:11 ------- Again this is not a bug. There is nothing to fix because there is nothing that broke.
I disagree. If IE doesn't run, it's a bug. I would actually say that it's a major bug - IE is one the those core applications that users expects to work.
You are incorrect about "there is nothing to fix": Perhaps the source code is fine, but the documentation is certainly not. http://appdb.winehq.org/appview.php?versionId=469 even says:
"(to be continued because then it still doesn't run because of ole errors)"
Anyone is welcome to write up instructions on what to override and place them in appDB. Bugzilla is not the right place for that.
Why do you think Bugzilla cannot be used for tracking documentation bugs? There is a "wine-documentation" component and a "WineHQ Apps Database" component, if you think that wine-misc is totally wrong.
I would very much prefer is this bug could be left open until someone has managed to figure out what needs to be overridden to actually *run* IE.
Regards,
Peter Åstrand ThinLinc Chief Developer Cendio http://www.cendio.se Teknikringen 3 583 30 Linköping Phone: +46-13-21 46 00
On Tue, 2006-06-20 at 13:49 -0400, Vijay Kiran Kamuju wrote:
Try adding wine overrides for iexplore
This has been already tried of course. The problem is to find a good combination of native dlls to run IE (stock WineCVS let's you install it without problems now). You can see the current state of the How-To here: http://appdb.winehq.org/appview.php?versionId=469
If someone knows about the current minimal override required to run IE in win2k mode, I'll gladly add it to the How-to (because we have about one user a day and a bug a week for this damn IE ;-) ).
Tuesday, June 20, 2006, 11:27:04 AM, Peter Åstrand wrote:
On Mon, 19 Jun 2006, Wine Bugs wrote:
vitaliy@kievinfo.com changed:
What |Removed |Added
Status|RESOLVED |CLOSED------- Additional Comments From vitaliy@kievinfo.com 2006-19-06 14:11 ------- Again this is not a bug. There is nothing to fix because there is nothing that broke.
I disagree. If IE doesn't run, it's a bug. I would actually say that it's a major bug - IE is one the those core applications that users expects to work.
What would you say if I open a bug about "Windows doesn't work on Wine"? Or better yet, "Can not upgrade Wine to winxp".
You are incorrect about "there is nothing to fix": Perhaps the source code is fine, but the documentation is certainly not. http://appdb.winehq.org/appview.php?versionId=469 even says: "(to be continued because then it still doesn't run because of ole errors)"
This is _not_ a documentation. If you are not happy with something on appDB ask app maintainers to change that. Of course suggestions are welcome to what do you want to see there.
Anyone is welcome to write up instructions on what to override and place them in appDB. Bugzilla is not the right place for that.
Why do you think Bugzilla cannot be used for tracking documentation bugs? There is a "wine-documentation" component and a "WineHQ Apps Database" component, if you think that wine-misc is totally wrong.
Because that's exactly what appDB is for.
I would very much prefer is this bug could be left open until someone has managed to figure out what needs to be overridden to actually *run* IE.
I explained in the bug and will repeat here. Wine does not run windows. Wine runs windows applications. That's the main goal. The ultimate goal is to run every windows application without using any native component. That way Wine will be 100% replacement to windows. If you install any part of windows (per m$) you have to have windows licence.
I'm not saying that some one can not find a way to run ie on Wine. In fact I spent quite some time putting that "magic" list of overrides together. Now it's been removed because Wine has it's own replacement for ie whenever app needs that.
Vitaliy.
On Tue, 20 Jun 2006, Vitaliy Margolen wrote:
------- Additional Comments From vitaliy@kievinfo.com 2006-19-06 14:11 ------- Again this is not a bug. There is nothing to fix because there is nothing that broke.
I disagree. If IE doesn't run, it's a bug. I would actually say that it's a major bug - IE is one the those core applications that users expects to work.
What would you say if I open a bug about "Windows doesn't work on Wine"? Or better yet, "Can not upgrade Wine to winxp".
I would say that you are acting silly. "Windows" and "WinXP" is operating systems. IE is an application.
You are incorrect about "there is nothing to fix": Perhaps the source code is fine, but the documentation is certainly not. http://appdb.winehq.org/appview.php?versionId=469 even says: "(to be continued because then it still doesn't run because of ole errors)"
This is _not_ a documentation.
I think it is.
If you are not happy with something on appDB ask app maintainers to change that. Of course suggestions are welcome to what do you want to see there.
For Wine to succeed, we need to have a fruitful communication and cooperation between the code wine developers and the AppDb maintainers. Currently, neither the AppDb maintainers nor the core developers (as far as I know) knows how to run IE. If it's not a documentation bug, it is at least a common lack of knowledge, which might be useful to track.
I would very much prefer is this bug could be left open until someone has managed to figure out what needs to be overridden to actually *run* IE.
I explained in the bug and will repeat here. Wine does not run windows. Wine runs windows applications. That's the main goal. The ultimate goal is to run
If you want to keep pretending that IE is "Windows", fine with me. In my world, IE is an application.
"Peter Åstrand" astrand@cendio.se wrote:
I would very much prefer is this bug could be left open until someone has managed to figure out what needs to be overridden to actually *run* IE.
I explained in the bug and will repeat here. Wine does not run windows. Wine runs windows applications. That's the main goal. The ultimate goal is to run
If you want to keep pretending that IE is "Windows", fine with me. In my world, IE is an application.
The problem is that Microsoft calls IE an "OS component" which implies that it's a part of Windows. Vitaliy tried to explain it. That doesn't mean though that Wine shouldn't be able to run IE.
Vitaliy Margolen wrote:
Tuesday, June 20, 2006, 11:27:04 AM, Peter Åstrand wrote:
On Mon, 19 Jun 2006, Wine Bugs wrote:
vitaliy@kievinfo.com changed:
What |Removed |Added
Status|RESOLVED |CLOSED------- Additional Comments From vitaliy@kievinfo.com 2006-19-06 14:11 ------- Again this is not a bug. There is nothing to fix because there is nothing that broke.
I disagree. If IE doesn't run, it's a bug. I would actually say that it's a major bug - IE is one the those core applications that users expects to work.
What would you say if I open a bug about "Windows doesn't work on Wine"? Or better yet, "Can not upgrade Wine to winxp".
You are incorrect about "there is nothing to fix": Perhaps the source code is fine, but the documentation is certainly not. http://appdb.winehq.org/appview.php?versionId=469 even says: "(to be continued because then it still doesn't run because of ole errors)"
This is _not_ a documentation. If you are not happy with something on appDB ask app maintainers to change that. Of course suggestions are welcome to what do you want to see there.
Anyone is welcome to write up instructions on what to override and place them in appDB. Bugzilla is not the right place for that.
Why do you think Bugzilla cannot be used for tracking documentation bugs? There is a "wine-documentation" component and a "WineHQ Apps Database" component, if you think that wine-misc is totally wrong.
Because that's exactly what appDB is for.
I would very much prefer is this bug could be left open until someone has managed to figure out what needs to be overridden to actually *run* IE.
I explained in the bug and will repeat here. Wine does not run windows. Wine runs windows applications. That's the main goal. The ultimate goal is to run every windows application without using any native component. That way Wine will be 100% replacement to windows. If you install any part of windows (per m$) you have to have windows licence.
I'm not saying that some one can not find a way to run ie on Wine. In fact I spent quite some time putting that "magic" list of overrides together. Now it's been removed because Wine has it's own replacement for ie whenever app needs that.
If you are saying that Wine shouldn't actively try to support IE like other Apps, I very much regret this. As a part time web developer I have learned to hate IE very much, each and every bit of web code written has to be tested with it and I always had to go and find a Windows machine to do this. Supporting IE in Wine would help a lot of web developers to migrate completely to Linux.
Nearly every Laptop-user has a (maybe unwanted) license for some windows version, so these people (including me) are allowed to run IE on any OS they want.
And I think it good for Wine to have its own IE replacement too.
Just my 2 €cents.
Vitaliy.
Ulrich
Am Mittwoch 21 Juni 2006 10:41 schrieb Ulrich Dobramysl:
Vitaliy Margolen wrote:
Tuesday, June 20, 2006, 11:27:04 AM, Peter Åstrand wrote:
On Mon, 19 Jun 2006, Wine Bugs wrote:
vitaliy@kievinfo.com changed:
What |Removed |Added
----- Status|RESOLVED |CLOSED
------- Additional Comments From vitaliy@kievinfo.com 2006-19-06 14:11 ------- Again this is not a bug. There is nothing to fix because there is nothing that broke.
I disagree. If IE doesn't run, it's a bug. I would actually say that it's a major bug - IE is one the those core applications that users expects to work.
What would you say if I open a bug about "Windows doesn't work on Wine"? Or better yet, "Can not upgrade Wine to winxp".
You are incorrect about "there is nothing to fix": Perhaps the source code is fine, but the documentation is certainly not. http://appdb.winehq.org/appview.php?versionId=469 even says: "(to be continued because then it still doesn't run because of ole errors)"
This is _not_ a documentation. If you are not happy with something on appDB ask app maintainers to change that. Of course suggestions are welcome to what do you want to see there.
Anyone is welcome to write up instructions on what to override and place them in appDB. Bugzilla is not the right place for that.
Why do you think Bugzilla cannot be used for tracking documentation bugs? There is a "wine-documentation" component and a "WineHQ Apps Database" component, if you think that wine-misc is totally wrong.
Because that's exactly what appDB is for.
I would very much prefer is this bug could be left open until someone has managed to figure out what needs to be overridden to actually *run* IE.
I explained in the bug and will repeat here. Wine does not run windows. Wine runs windows applications. That's the main goal. The ultimate goal is to run every windows application without using any native component. That way Wine will be 100% replacement to windows. If you install any part of windows (per m$) you have to have windows licence.
I'm not saying that some one can not find a way to run ie on Wine. In fact I spent quite some time putting that "magic" list of overrides together. Now it's been removed because Wine has it's own replacement for ie whenever app needs that.
If you are saying that Wine shouldn't actively try to support IE like other Apps, I very much regret this. As a part time web developer I have learned to hate IE very much, each and every bit of web code written has to be tested with it and I always had to go and find a Windows machine to do this. Supporting IE in Wine would help a lot of web developers to migrate completely to Linux.
Well, not really
Internet Explorer on wine is not guaranted to render things like Internet Explorer on Windows. You can reduce the differences by using as much native dlls as possible(mshtml, shdocvw, dcom, ...), but there might still be differences.
If you run IE with the builtin dlls you have pretty much a Mozilla Gecko based Browser with the gui of IE. Just run the Acid 2 test in msie with builtin mshtml and compare the output to the rendering on Windows and the rendering in Firefox.
What I want to say is that one can't really use wine to see if pages render correctly in IE. However, I still think that IE should be installable and work with its native dlls(including mshtml and dcom), because it is helpful to check if a bug in another application is caused by shdocvw, mhtml and friends.
-
Dmitry Timoshkov -
Jonathan Ernst -
Peter Åstrand -
Stefan Dösinger -
Ulrich Dobramysl -
Vijay Kiran Kamuju -
Vitaliy Margolen