On Thu, May 29, 2003 at 05:25:20PM +0100, Mike Hearn wrote: > > >They are normally shipped with the app. So would we really need one >in Wine? > > > > I think one of the goals of wine is to implement all the functions > > of windows systems, for instance now i'm testing an application > > written in VB that uses both Winsock.ocx and mscomm.ocx (RS-232), > > and I would like to use as builtin libraries/"com libraries" as possible, instead > > of using a "closed ocx", in which i can't do anything if something > > fails...I know now exists some builtin programs like wine-Notepad or winemine, so > > i think, the next step is to develop builtin OCX...under > > wine license > > OK, that's fine, but be aware that: > > * notepad is there because some apps require it > * winemine is just a simple demo of how to write a WineLib app > > ie, Wine is NOT trying to replicate the entirety of Windows.
Err, we are trying that. And a standard winsock OCX falls under the "to be done" category for me. Ciao, Marcus
