[wxWorkshop-dev] State of the Conversion to wxWidgets-2.6.1

[<wxw...@li...>]

Hi guys,

I think about Every weekend I'm going to send a State of the Conversion 
message to let you guys how things are progressing.....

Since I've been working on the wxWorkshop conversion to wxWidgets-2.6.1 
Unicode:

--I am now able to create libraries from the awtlay, diamond, wsutils, 
and xobject directories.  The files do compile and build in the diamond 
directory, however, I get many Warnings about deprecated C++ Header 
files.  I searched the Internet for a possible update to the diamond db 
source files, and found that the source & diamond db project have 
totally disappeared.  Later, when we are adding features to wxWorkshop, 
I would like to propose that the diamond db gets replaced by whatever 
database that the wxDB class will hook to, as well as deciding what a 
suitable Database will be.

--I am concentrating on the compiling/building for Linux, and I hope I 
have the Makefile.linux files generic enough to work on most Linux 
distributions.  For your reference, I am converting wxWorkshop to work 
on wxWidgets-2.6.1 (wxGTK), unicode version, compiled with g++ v3.4.4.

--I have changed the default Makefiles to now give a message directing 
the user to use one of the other Makefile.* files when making.  It is my 
hope that the other Makefiles for the other platforms will also be 
updated to work with their respective platforms.  Obviously, I'm 
developing using the Makefile.linux files.  And the original default 
Makefiles have been moved to Makefile.org files, so they can be used as 
well if needed.

--Plans for this coming week, to continue to convert the remaining 4 
directories to compile & build making the whole program.  From here it 
gets more difficult as I am running into issues with Deprecated 
functions that have no direct replacement in wxWidgets-2.6.1, and also 
there are some additional conversions I have to do to convert char types 
to wxString types, and wxStrings to ints, etc. that are not 
straightforward.  In My opinion, this just shows that when programming 
in wxWidgets, you do yourself a favor by sticking the wxWidgets types 
like wxChar and wxString, and only deal with chars, and arrays only as 
necessary.  This is the what I've done in the past with other wxWidget 
programs, and I note this approach works very well.

My Next Report will be next weekend.

Regards everyone,
--James Rasmussen
aka Spicerun