Hi!:
Could you explain to me what the Winsock Control is? We have a >winsock DLL implementation already.....
Winsock.dll is the Windows API to manage sockets, but Winsock control is a high-level library, provided with Visual Studio 6.0. It is mainly used by Visual Basic programmers, as it provides a very simple interface to send and receive data via TCP/UDP protocols. It provides some events (Connection, Data received, Data Sent...), and a easy way to send different data types (automatic conversion for unicode strings, for example)
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
OCXs are mainly for plugging into IDEs yes?
Well, some ocx yes, but Winsock.ocx has not any visible interface, and it can be used without IDEs, simply by calling the COM server
Thanks,
Daniel Campos
--- On Thu 05/29, Mike Hearn < mike@theoretic.com > wrote: From: Mike Hearn [mailto: mike@theoretic.com] To: danielcampos@myway.com Cc: wine-devel@winehq.com Date: 29 May 2003 14:47:32 +0100 Subject: Re: Bultin OCX?
One of the goals of this project would be replacing current native Winsock control by a "Bultin OCX". <br><br>Could you explain to me what the Winsock Control is? We have a winsock<br>DLL implementation already.....<br><br>> I've look at Wine Documentation<br>> ant it's simple to create a native DLL, but i've seen nothing <br>> about the possibility of creating a builtin OCX. Is there any way<br>> to do it? What about registry issues?<br><br>It is possible yes, but rather hard. OCXs are mainly for plugging into<br>IDEs yes? They are normally shipped with the app. So would we really<br>need one in Wine?<br><br>Also, such a thing would need to use the Win32 winsock api really, not<br>unix sockets.<br><br>thanks -mike<br><br><br>
_______________________________________________ No banners. No pop-ups. No kidding. Introducing My Way - http://www.myway.com
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.
Well, some ocx yes, but Winsock.ocx has not any visible interface, and it can be used without IDEs, simply by calling the COM server
If you want to write one then by all means go ahead, but I think it would be quite a bit of work. You'd want to use the winsock apis, as then your OCX can be reused on Windows and we keep all the code together.
thanks -mike
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
Err, we are trying that.
Hmm, you want to create an Explorer clone as well? MS Paint? What I meant was, it's not necessary to recreate every aspect of Windows the desktop. Windows the platform yes, maybe.
And a standard winsock OCX falls under the "to be done" category for me.
Ok, cool. I'd guess it's like MFC, nice to have but as apps usually ship with it, not critical. But if somebody is going to write it, then that's great :)
Hi,
On Thu, May 29, 2003 at 06:20:11PM +0100, Mike Hearn wrote:
Err, we are trying that.
Hmm, you want to create an Explorer clone as well? MS Paint? What I meant was, it's not necessary to recreate every aspect of Windows the desktop. Windows the platform yes, maybe.
Naah, probably not an Explorer clone (unless we need a special one to support Wine-specific features, that is, and even that could be done instead by asking a well-established Explorer clone to support these Wine enhancements...)
We're talking about *system* parts, and the relatively widely used Winsock OCX DEFINITELY falls under that category. (together with several other important OCXes in windows/system/)
And a standard winsock OCX falls uder the "to be done" category for me.
Ok, cool. I'd guess it's like MFC, nice to have but as apps usually ship with it, not critical. But if somebody is going to write it, then that's great :)
Yep, it's sort of an "enhancement", since the native Winsock OCX should hopefully work with our own builtin Winsock DLL, so no need to write something here and now. (although it'd be cool to have it here and now, of course!) However if this OCX does NOT work with our Winsock, then please yell immediately.
Andreas Mohr wrote:
Hi,
On Thu, May 29, 2003 at 06:20:11PM +0100, Mike Hearn wrote:
Err, we are trying that.
Hmm, you want to create an Explorer clone as well? MS Paint? What I meant was, it's not necessary to recreate every aspect of Windows the desktop. Windows the platform yes, maybe.
Naah, probably not an Explorer clone (unless we need a special one to support Wine-specific features, that is, and even that could be done instead by asking a well-established Explorer clone to support these Wine enhancements...)
Developing a Explorer clone has been on the roadmap for a while. ReactOS is working on one and I am hoping to see it in WINE one day if someone needs a good interface for --desktop mode.
Thanks Steven
-
Andreas Mohr -
danielcampos -
Marcus Meissner -
Mike Hearn -
Steven Edwards