AndrewTheArt wrote:Well, no offense to Chris, but the last few updates haven't included the addition of new features. Mostly, big fixes and small enhancements to previous features has been the trend.
That is why it is high time to port it.
Maybe it is, and maybe it isn't.
I just did a brief mental exercise in what a port would involve, and it boils down to:
1. Learning the whole Linux GUI API (for which ever window manager Chris decides to support).
2. Rewriting the entire GUI.
3. Removing any GUI functionality that may not be supported under Linux.
4. Learning an entire new sound hardware interface API.
5. Rewriting the entire sound hardware interface.
6. Removing any sound hardware interface functionality that may not be supported under Linux.
7. Throwing out the whole plug-in architecture (which I understand most of GWs internal functionality is based on) and reworking it from scratch.
8. Dealing with the myriad of bugs that such a comprehensive rewrite of the entire program would inevitably throw up.
9. Stalling all current and projected development on the Windows version while this is going on.
10. Having to maintain two separate codebases in the future.
Now, this is based on about half a minute of thinking about what would be involved, so no doubt there's quite a bit I've missed here.
Net result is that GW would end up becoming a
vastly inferior program, just to get it supported on Linux for a minority who prefer a native version over running it under WINE.