In article <E1I6z6P-0002vi-2c@pecan.exetel.com.au>, "Paul" <pdeleeuw@deleeuw.com.au> writes:
What are the advantages of wxWidgets over the standard dialogue boxes that come with the development environment?
The Express edition of VS.NET doesn't include ATL/WTL or MFC, so you have no support for dealing with Win32 UI code at a class level. You only have access to the raw Win32 C function API and even then, only if you install the Platform SDK and configure it. However, dealing with dialog boxes and so-on through the raw Win32 API is very tedious and error-prone. Furthermore, the work you do on any dialog is only going to work on Win32 and you must recode the dialog again to have it work on the X11 code. wxWidgets wraps its own class API around the existing platform support, whether that platform is GTK on unix/X11 or Win32 on Windows. You write a single set of code that uses the underlying UI facilities on either platform. So wxWidgets *does* use the standard Win32 dialog boxes and so-on on Win32 and it uses the standard GTK dialogs on unix/X11.
Are you interested in any of the palette generation code?
Yes. By the time fractint is running on wxWidgets, it will be a good time to incorporate your palette editing dialog and its coloring mechanism. That's why I say it would be useful to have you prototype a palette editing dialog in wxWdigets that utilizes your algorithms. -- "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/>