On Sun, Dec 10, 2000 at 07:46:28PM -0500, Mark Murphy wrote:
> I wasn't planning on asking for CVS space for it until I had released the
> COM wrapper and had a functioning first version of the GUI. However, if you
> prefer, I can clean up what I have and post it now. It doesn't matter a ton
> to me -- it's merely a matter of timing.
I'm +1 on putting this into subversion/winsvn/ asap.
> I've written it in Visual Basic.
> <pause for groans>
> For rapid GUI development, nothing I've seen touches VB on Win32.
No groan here. I totally agree and would probably question anybody who
didn't consider writing a Windows GUI in VB.
[ it was a pain in the ass when I worked at MSFT. it was actually frowned
upon to ship VB-based GUIs(!) ... shipping product almost always had to be
written in C++ (GUI or not). some of the MSFT dev culture is just whacked ]
> I've created a GUI shell that has a better look than
> WinCVS and on par with SourceSafe and Perforce (IMHO -- you'll be able to
> judge for yourself shortly).
Kick ass. I'd like to see the VB in our CVS repository so that I could take
a look at what you did.
> I realize fully that VB is not the norm for Open Source development. It
> just makes no sense for me to try to do it in C++. It's also part of the
> reason why I'm planning on building the COM wrapper (in C++), in case
> somebody might want to build a C++ GUI sometime in the future.
Anybody that wants to complain about WinSVN being written in VB can take
their time and go rebuild it in C++. Unless they're willing, then they can
just shut the hell up :-)
Pick the tool for the job. Windows GUIs? VB.
> Give me your input on these two points, and I'll know how to proceed from
I'm quite fine with adding this to CVS and with VB. I'd like to see a few
more +1's on the CVS thing, though (e.g. what's Karl think?)
Greg Stein, http://www.lyra.org/
Received on Sat Oct 21 14:36:16 2006