On Wed, Feb 4, 2009 at 2:00 PM, antoniong <wineforum-user@xxxxxxxxxx> wrote: > > austin987 wrote: >> On 2/4/09, antoniong <wineforum-user@xxxxxxxxxx> wrote: >> >> > >> > austin987 wrote: >> > >> > > >> > > Tweaking an app to work both on Wine and Windows is *much* easier. >> > > >> > >> > Indeed, but then one needs a way to find out whether or not the app is >> > running using Wine. >> > >> >> No. They should test their app under Wine itself for bugs. >> -Austin > > > I think you misunderstand me. No, I understand you fine. > Sometimes people want to write an app that runs in principle using XP but they also want to make this app available for Linux users. The number of these users is lower so it is nor profitable to rewrite the app in a language that can be compiled for native running under Linux. > > > In these cases products products like Wine are great. One is able to run XP programms with a minimal amount of resource losses. So the user is happy and the manufacturer is ahppy. > > > The only problem is that there are situations where Wine does not react similar as native XP does. In such cases it is often easy to incorporate within the app 2 solutions. One the native XP way, one such so that Wine does the same thing. > > However it is necessary for the app to know whether it is running native XP or Wine. > > > Waiting for Wine to fix it would mean unnecessary waiting and very likely for a problem that is only contained within 1 particular situation. Right, but if the bug is fixed in Wine later on, then the app may behave unexpectedly. What if some windows machines have similar bugs (many often do). They won't receive that fix either. The proper thing to do would be detect the broken behavior and work around it, not detect Wine. But if you have a workaround, that should be the default behavior, so your app works the same in Windows and Wine. -- -Austin
