Posted by Christian Klauser on 2007-06-18 17:01 CET
(In reply to: Re: Want to sell copies of Champ? posted by Hans Salvisberg on 2007-06-18 02:54 CET)

>> I'm not sure this is a problem. Running off a message loop was the Win16/Win32 programming paradigm, but Champ successfully worked around that to provide its own sequential model. .NET hides the message loop even more, but it's still there, and I believe it could be wrapped again. Yes, Windows Forms wraps around the message loop and it can still be accessed directly. >> Much bigger issues for a port to .NET are its reliance on WIN16 GDI and on multiple inheritance. System.Drawing is a wrapper around GDI+ which in turn wraps around plain GDI. I'm not very familiar with Champ's architecture but the limitations of interfaces definitely will become a problem when reproducing Champ's API. (There are times when I wish C# would at least support mixins) >> Worrying about speed is exactly the kind of mistake that we made back then when we decided to implement Champ on the WIN16 API. Besides, there is no pixel-by-pixel drawing, unless you explicitly use putpixel(). Everything else uses basic graphics primitives such as lines, circles, and bitblts. At school we almost exclusively draw point-by-point/pixel-by-pixel because often the actual task is to find the points/pixels such primitives consist of. I have to admit though, that most of what we are told to draw doesn't involve a lot of computation. >> Might you be interested to work on a New Champ? Absolutely. But I have to emphasize that I have never ever programmed against the WIN32 API. All I know is the .NET base class library.

Email: (hidden)