RE: WinSVN: Initial questions

> > I wouldn't want a non-open-source windows client, even if the
> cost is only
> > incurred for builds.
>
> The client itself could be open source, you just won't be able to
> compile it yourself if you don't have a license for qt.
>
> Look at it from this point of view:
> 1.) you write a free (open source, whatever) GUI for un*x systems, using
> Qt.
> 2.) you get a license for windows platform, and voila, you can
> distribute the _same_ GUI client for windows as well. The folks who
> already have a license for qt/windows can of course download the
> source and build the beast themselves.
>
> Besides, how much is VB more open-source then this? Personally, I don't
> have any MS devel environments installed...

Depending on how you look at it, VB is as open-source or more so than the Qt scenario.

To build the VB client from sources, you will need VB (it's being built under VB6), which is a commercial package. Just as to rebuild the COM object, you'll need Visual C++ most likely, as I'll be using a COM framework of theirs called the Active Template Library (ATL). However, you won't need anything besides the development environment in order to build them -- all the sources themselves will be included as part of the package.

Mark Murphy
mmurphy@collab.net
Received on Sat Oct 21 14:36:16 2006