All, thanks for your responses. There's an important point that I
forgot in my first email which explains what I hope to get from WINE.
We don't just want to grab static screenshots, we ultimately want to do
appsharing in Flash, almost like X Windows or terminal server type
stuff, except
Mike McCormack wrote:
Augustus Saunders wrote:
As for what we hope to accomplish, well, it might seem like
massive overkill to try using WINE, but it's the only
plausible way I've come up with. Basically, we want to
substitute all the graphics/windowing/GDI etc so that we can
record all the
Augustus Saunders wrote:
As for what we hope to accomplish, well, it might seem like massive
overkill to try using WINE,
but it's the only plausible way I've come up with. Basically, we want
to substitute all the
graphics/windowing/GDI etc so that we can record all the
painting/rendering into
I've been avidly following WWN for some time now, and now
that other people have brought up this topic (using WINE
dlls on Windows), I wanted to jump in. (I'm not subscribed,
so please CC me on any response) My employer is vaguely
considering pursuing a product idea, depending on 1) how
--- Augustus Saunders [EMAIL PROTECTED] wrote:
I appreciate any feedback anybody has. Thanks-
It wont work for DirectX. Wine directX structures and implementation is
incompatible with Windows
currently. Normal Win32 dlls work fine.
Thanks
Steven
Augustus Saunders wrote:
As for what we hope to accomplish, well, it might seem like
massive overkill to try using WINE, but it's the only
plausible way I've come up with. Basically, we want to
substitute all the graphics/windowing/GDI etc so that we can
record all the painting/rendering into
Hi Rolf,
--- Rolf Kalbermatter [EMAIL PROTECTED] wrote:
Why would you need the .local file? Has there anything changed in XP or
2003 which would
prefer Windows or system DLLs over local DLLs in the same directory as
the calling executable?
I always was under the impression that the
Steven Edwards [EMAIL PROTECTED] wrote:
I think it would be good in testing Wine/ReactOS vs Windows for Winelib
applications developers.
You can make a dummy file in your application directory called
application.exe.local to force
Windows to use the dlls in the local directory. So say you have
Has anybody else thought of using DLLs (like ReactOS' dlls) as a
compatibility
layer to different Windows versions?
I.e. when you distribute your Windows app, you also throw in a bunch of DLLs
that implement lots of functionality you aren't sure exists on your
target otherwise.
(Windows 2003
Hi,
--- Jakob Eriksson [EMAIL PROTECTED] wrote:
Has anybody else thought of using DLLs (like ReactOS' dlls) as a
compatibility
layer to different Windows versions?
I think it would be good in testing Wine/ReactOS vs Windows for Winelib
applications developers.
You can make a dummy file in
10 matches
Mail list logo
