I prefer option #2 too.
Is there an existing document that describe the interface of netserv/libmwn?
I would like to be able to understand what's the amount of work to hook Wine
to netserv/libmwn.
Stephane.
> -----Original Message-----
> From: Gavriel State [mailto:[EMAIL PROTECTED]]
> Sent: Monday, March 27, 2000 5:38 PM
> To: Oleg Noskov
> Cc: Andrew Lewycky; Ming Poon; Jeff Tranter; Toufic Milan
> Subject: Re: WINE<->Samba integration
>
>
> The licensing isn't a problem, since WINE is under a BSDish
> license, and soon to switch to
> the X11 license. What's much more questionable is how we can mix
> WINE code with QT code:
> can windows handled by WINE co-exist in the same process as QT's windows?
>
> If not, we have two possible approaches:
> 1) Make a seperate process that handles UI for browsing, etc,
> and have WINE talk to it
> through a socket.
> 2) Rewrite netserv/libmwn to be completely independant of the
> underlying GUI system
> (ie: have them weak link to another library that provides
> UI). That way, we could
> do a direct WINE UI for browsing and password entry in
> addition to a KDE UI. Doing
> something like this will help the transition to KDE 2.0, and
> will make GNOME-based
> usage possible as well.
>
> I'd definitely favour option (2), as it gives us the most
> flexibility. It will require
> more work, though.
>
> -Gav
>
> Oleg Noskov wrote:
> >
> > Well, at present time libmwn depends on some KDE core libraries
> and on ccqt library (Corel's
> > version on Qt 1.4x). Looks like if WINE team is interested in
> using netserv/libmwn, we should
> > consider extracting UNC mapping/wrapping code from libmwn and
> making it a completely separate
> > library (currently libmwn contains LOTS of other stuff needed
> by Corel File Manager). But
> > before we do that, we need a decision to be made by all
> interested parties that this is
> > exactly the way that we want to go. Also, licensing issues need
> to be clarified because
> > currently netserv/libmwn is CPL and we cannot mix GPL code with
> CPL code.
> >
> > Thanks,
> > Oleg
> >
> > Andrew Lewycky wrote:
> >
> > > > Netserv/libmwn are working great in Corel Linux and can be
> used by WINE.
> > > >
> > > > If WINE is running not in Corel Linux, it is still possible
> to use all of this, provided
> > > > netserv is launched by some script or application before
> all the UNC-related activity
> > > > begins.
> > > >
> > > > (For instance, I have Corel File Manager running in my
> RedHat-based NetWinder computer
> > > > and it is using all the abovementioned functionality).
> > > >
> > > >
> > > > Netserv/libmwn are distributed under CPL.
> > > >
> > > > Please contact me if you have any questions/concerns.
> > > >
> > > > Thanks
> > > >
> > > > Oleg Noskov
> > > > [EMAIL PROTECTED]
> > >
> > > Would you consider putting together debian package sfor netserv and
> > > libmwn? Ideally, kde-corel would depend on these packages. In the mean
> > > while, we can just have the netserv and libmwn "replace" (in the sense
> > > of the dpkg replace control field) kde-corel.
> > >
> > > Andrew Lewycky
> > > [EMAIL PROTECTED]
> > > x1846
> >
> > --
> > The free Corel LINUX OS Download is NOW available! Check it
> out at http://linux.corel.com
>
> --
> Gavriel State
> Engineering Architect - Linux Development
> Corel Corp
> [EMAIL PROTECTED]
> --
> The address in the headers is not the poster's real email
> address. Do not send
> private mail to the poster using your mailer's "reply" feature.
> CC's of mail
> to mailing lists are OK. Problem reports to
> "[EMAIL PROTECTED]".
> The poster's email address is "[EMAIL PROTECTED]".
>
>