In article <4569E644.12856.1F0410@twegner.swbell.net>, "Tim Wegner" <twegner@swbell.net> writes:
Rich wrote:
OK, so I've got the code compiling. Now I just have a long list of undefined symbols :-).
Looks like you have gotten a tremendous amount done in a short time.
I was able to cheat by reusing what I had before. The source code hasn't changed much in the core functionality that I had refactored into the device interface.
We need to think carefully about where to go from here.
Agreed.
My suggestion is get all features working first, then systematically attack the cleanups you mentioned, though bring order to the defines may be necessary just to get thinbgs working.
I think we're in agreement on where to go from here. I know this has been discussed before, but refresh my memory on what's keeping the 16-bit code alive these days? :-) Are we interested in keeping a 'DOS only' version alive, even if its through a DPMI style flat memory model? Or are we truly ready to abandon DOS and embrace an event-driven window system model? The latter would really clean up the code substantially. Currently the I/O model is polling. The event stuff is jammed into the low-level keyboard I/O routines on the X11 and Windows ports so that when you check if a key has been pressed, the events get pumped. Having it truly be event driven would be a good refactor to do after the steps I've done this weekend. -- "The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download <http://www.xmission.com/~legalize/book/download/index.html> Legalize Adulthood! <http://blogs.xmission.com/legalize/>