[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [sc-dev] [win32] discard SCSpawn?

Sounds fair to me, MFC kind of sucks anyway.

I'll use this as an opportunity to point out that the Qt toolkit is now available under the GPL license on all supported platforms.. so we could actually consider a cross-platform GUI solution.


----- Original Message ----- From: "Christopher Frauenberger" <frauenberger@xxxxxx>
To: "SuperCollider developers list" <sc-dev@xxxxxxxxxxxxxxx>
Sent: Monday, December 12, 2005 9:13 PM
Subject: [sc-dev] [win32] discard SCSpawn?

Hi list,

I would like to discuss whether we should discard SCSpawn as the way of starting scsynth on windows. As far as I can see it has some pro and contras:

Pro SCSpawn:
* nice graphical interface providing all options and showing devices available
* remembers settings in registry

Contra SCSpawn:
* depends on MFC libraries
* not consistent with the startup method on osx

The main argument against it here imo is that it depends on MFC. Microsoft now released the Visual Studio C++ Express edition, which is a free version of MS Visual Studio that uses the same compilers and the same IDE, but does not include MFC. If we could get rid of SCSpawn and allow for setting the device by name through the ServerOptions it would be consistent with the way it works on osx. We could also print all available devices at startup to inform the user of her/his options.

This way, we would have a way of compiling SC3 on windows without relying on commercial tools...

what are your opinions?

sc-dev mailing list