Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Unicode conversion (attention all devs)
rickg22:
We've finished converting the SDK and SRC to Unicode!
And I converted the "small" plugins to unicode, too!
Now it's time for the big ones: Compiler, Debugger, CodeCompletion.
(See http://forums.codeblocks.org/index.php?topic=687.msg4442#msg4442 for more details).
takeshimiya:
Just a note about the outdated wxString wxWidgets documentation, at the beggining it warns:
"Also please note that in this manual char is sometimes used instead of wxChar because it hasn't been fully updated yet. Please substitute as necessary and refer to the sources in case of a doubt."
The latest wxWidgets documentation updated from CVS is always here (tip: bookmark it :wink:):
http://www.lpthe.jussieu.fr/~zeitlin/wxWindows/docs/
Another fact is that sometimes the documentation is outdated because ISN'T autogenerated by Doxygen or any autodocumentation system, it's written in LATEX.
But there was some discussion at the wx-mailing-list about porting it to Doxygen. So this is the reason of why the documentation is always outdated in some things.
takeshimiya:
A question about CVS (I know little to nothing of CVS):
All of this changes will be in a new VERSION_1 CVS branch, but, when all the _T() conversion thing is finished,
it will be easily merged in the latest CVS-HEAD branch? Or all of this work will have to be rewritten??
I'm hoping that CVS-merge is smart :D
tiwag:
--- Quote from: takeshimiya on August 07, 2005, 02:08:40 pm ---it will be easily merged in the latest CVS-HEAD branch? Or all of this work will have to be rewritten??
I'm hoping that CVS-merge is smart :D
--- End quote ---
CVS is smart - at least when the same lines of code haven't already been changed in HEAD too - then it asks for user intervention to solve the conflict.
rickg22:
--- Quote from: tiwag on August 07, 2005, 02:49:38 pm ---CVS is smart - at least when the same lines of code haven't already been changed in HEAD too - then it asks for user intervention to solve the conflict.
--- End quote ---
Yeah, like making you edit manually all the lines in question :lol:
My proposed solution is this:
Branch: HEAD
--------------------------------------------------------- HEAD
|
|
| Branch: VERSION_1_0
| ------ SNAPSHOT ------------------- UNICODE
I had added a SNAPSHOT_DDDDDD tag (and CVS better had not messed with it! :shock: ) for all the changes beforethe UNICODE conversion. All those files have a specific version.
The CVS HEAD branch hasn't seen much changes recently, anyway - so they probably have exactly the same version number than those branhced (with one or two exceptions maybe).
If they have the same version, copy the respective file from the latest VERSION_1_0 to HEAD.
Ta-da! :D
Or does CVS do this already? :?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version