|
From: Malcolm N. <m.n...@wa...> - 2008-09-28 09:51:22
|
Hi All, Since we are moving to wxWidgets, should we also move the help file to wxHelp format? This has my vote, since we need to generate help for all platforms. Also, assuming we are, I would suggest that the help is written as we go along, ensuring that we can correctly link to subjects as we move along. I assume that we can re-use a lot of information from the old help file, replacing screen shots as we go for example. We need to ensure that context help works as expected also. Do we support the "What's this" help under windows? Or do we insist that the program works exactly the same on all platforms? The images for the new look (as used by wxdevcpp) need to be located and added to svn. I would also suggest giving this theme a different name and allowing the user to select between the images currently within the folder "new look" and those we actually use for the new look in wxdev. Are we going to go the sizer route for dialog design? This gets my vote, as well as turning on wxDefaultPosition/wxDefaultSize in the designer, it makes the dialogs look better when designed with sizers. We need to decide on a standard Astyle style for our code. I assume we all have a preference as to how we like our code to look, so we need to agree on a standard from the beginning. I have looked at Sof.T's SkinDoc2 project, and it looks as though the form designer there could be used to replace our designer. (Ed could you tell me the difference between the old designer and the new designer - does it suffer from the same problem we do where it grows beyond the confines of the screen and becomes unmanageable- need scroll bars for example? Just some food for thought Mal |