nanogui: Re: Reactivate


Previous by date: 11 Jul 2001 16:31:38 -0000 Re: Reactivate, John Zulauf
Next by date: 11 Jul 2001 16:31:38 -0000 -help, bobby_lai.wistron.com.tw
Previous in thread: 11 Jul 2001 16:31:38 -0000 Re: Reactivate, John Zulauf
Next in thread:

Subject: Re: [nanogui] Re: Reactivate
From: "Greg Haerr" ####@####.####
Date: 11 Jul 2001 16:31:38 -0000
Message-Id: <0a5101c10a26$52bae6a0$3aba46a6@xmission.com>

: WINE can be well
: leveraged to support just the the subset of Win32 needed by these
: plugins to be useful to IA devices.

I haven't stuck my head into this too far yet, but there seems to be
two parts to this problem.  The first part is emulating ActiveX's COM
layer, which works by having a "typelib" that specifies the function
method signatures so that the interface layer can build the called
function parameter layer on the stack and call the function through
the vtable entry point.  This is what the boys at KDE/Konq just finished
with some Wine patches.

The other part of the problem is linking the ref'd Win32 (and possibly
other) entry points in the loaded DLL to Wine or some other windowing
system.  If the loaded DLLs truly use just a subset of Win32 (like
for instance just Win32 GDI), then it could be feasible to run all this
on Microwindows as well (we would need a COFF loader for the
dynamic symbol resolving).  Or - a smaller subset of Wine, running
on X could be used.

Perhaps someone needs to run exehdr on Shockwave and other
DLLs to determine exactly what API calls they're making...

Regards,

Greg


Previous by date: 11 Jul 2001 16:31:38 -0000 Re: Reactivate, John Zulauf
Next by date: 11 Jul 2001 16:31:38 -0000 -help, bobby_lai.wistron.com.tw
Previous in thread: 11 Jul 2001 16:31:38 -0000 Re: Reactivate, John Zulauf
Next in thread:


Powered by ezmlm-browse 0.20.