The most important thing currently unimplemented is (IMHO) the uncomplete
typelib support (the Invoke function of IDispatch). This makes the use
of eg. ocx's without a native oleauth.dll impossible. (This is a quite big
part since it would need the typelib marshaller.)
A second thing is the IStorage implementation. The creation of temporary
storage was incomplete the last time I needed it ;-).
Both problems you can easely show with hh.exe.
Ciao
Juergen
> > I have been looking for information about COM and DCOM support
> > under WINE and haven't been able to find anything. I have looked
> > through the documentation section and have done some web
> > searches but haven't found anything. I am an experienced
> > COM/DCOM/CORBA developer and would be willing to assist in
> > the development efforts, but I would like to know what, if
> > anything, has been done so far.
>
> Hi Chris,
>
> The COM that is in WINE currently works pretty well,
> overall. For example, an app I am currently debugging
> is basically completely written as COM objects, and it
> works fine. There are certainly things that are missing,
> for example out of process and remote servers are not
> supported yet, a lot of functions are only stubs, I'm sure
> other people on this list can point other things out to you.
> A good way to find problems is to grep files for FIXME and stub.
> Also, DCOM support doesn't exist at all, as far as I know.
>
> I don't think anyone is currently working on COM/DCOM at
> the moment in WINE... So, if you would be willing to
> help out, that would be great! In the source tree, most
> of the COM stuff is in dlls/ole32/compobj.c
>
>
> -James
>
>
> --
> James Hatheway
> Software Designer - Macadamian Technologies, Inc.
> [EMAIL PROTECTED] ~ http://www.macadamian.com
>
> "Nothing is a problem once you debug the code."
>
>
>
>
>
