>Sounds good. I would like to handle the UI part. The only problem I have
>with wxWindows is that I'll have to learn Win32/wxWindows instead of
>relying on the MFCs. Should cope, though.
Dylan,
wxWindows wraps all the UI stuff nicely, you shouldn't need to do any
Win32 in that area of the project. Also, wxWin is not too hard to learn.
Just have a look at some of the numerous example projects. I'd suggest
using the PNG or minimal sample as a starting point, as that's the one I
already got to compile. Look at some others to see how you do line-drawing
etc. using a wx DC.
>While on the subject of graphics, will we build in double-buffering for all
>graphics?
Maybe I get this wrong, but I think a single buffer would be more than
enough. HyperCard has one buffer for smoother redraws. But it would be best
if you got your code to draw nicely and with little flashing without
buffering. No problem with adding buffering later on, but usually one
writes faster and better code if one doesn't _rely_ on buffering.
>I will really have to have a look at HyperCard b4 I start
>antthing!!!
Yeah, I think that'd be a good choice :-) One thing we'll have to take
care of is that e.g. roundrect buttons have their corners rounded the same
way etc. Also, you have to add support for colors, that is, your code
should be able to draw the outline of a button using a different color than
the text, the contents, or the shadow. We need to take HC into the colored
dimension here.
Cheers,
-- M. Uli Kusterer
------------------------------------------------------------
http://www.weblayout.com/witness
'The Witnesses of TeachText are everywhere...'
--- HELP SAVE HYPERCARD: ---
Details at: http://www.hyperactivesw.com/SaveHC.html
Sign: http://www.giguere.uqam.ca/petition/hcpetition.html
