I like the sound of these ideas very much.. Should we check the ability
to just run the apps, or the apps and any extensions or plugins they
might support?
I suppose the 2nd one would make more sense, cause thats why people use
firefox, to get more out of their browser, but it is a question in my
mind nonetheless.
Also, do we have any steady IE testers? It would be nice to find out if
any version of IE is currently working (registry hacks welcome), and
what would be needed to get it to work if not? The reason for this is
simple... Maxthon.
Tom
Dan Kegel wrote:
Say, if we're expecting people to use Wine for real
work, maybe we should start doing that ourselves.
Firefox-1.5 runs pretty well on Wine.
How many Wine developers use it on Wine as their main web browser?
Maybe we could raise that number from zero to somewhere
around ten, and flush out a couple bugs.
Speaking of flushing out bugs,
OpenOffice 1.1 was said to work well under wine
a couple years ago (though I don't think I ever saw it
do so myself). Sadly, although OpenOffice 1.1.5 seems
to install fine under current wine, it crashes quickly on
startup, so I guess we have a bit of work to do first.
The extra payoff would be being able to use
http://qa.openoffice.org/qatesttool/ to run OpenOffice's automated
test suite as an automated regression test for wine.
One complication in all this is having to teach yourself
to not automatically blow away your ~/.wine directory
when trying a new app!
OK, baby's waking up, time to go.
Cheers,
Dan
--
Wine for Windows ISVs: http://kegel.com/wine/isv
