Code::Blocks - User contributions [en]

Developer documentation

2006-07-18T10:13:09Z

Peso: Add link to Launchpad

[[Category:Code::Blocks Documentation]]
[[Category:Developer Documentation]]
Articles for Code::Blocks developers.

* '''[https://launchpad.net/products/codeblocks/ Translation]'''
:Code::Blocks uses Launchpad to coordinate translation efforts.

* '''[[Coding style to use]]'''
:The source code formatting style used in the Code::Blocks' source.

* '''[[Creating a custom lexer for Code::Blocks editor]]'''
:How to add support for new syntax lighting schemes.

* '''[[Creating a patch to submit to BerliOS (Patch Tracker)]]'''
:Creating a diff file and then submitting it to the patch tracker.

* '''[[Unicode Standards]]'''
:Information about unicode standards and how unicode is handled in Code::Blocks' source code.

* '''[[Various development tips]]'''
:List of various development tips for Code::Blocks.

== Plugin development ==

* [[Creating a simple "Hello World" plugin]]
* [[Creating a Plug-in which modifies CB's Menus]]

* [[Research on doing a Plug-in for embedded help in CB]]

== Scripting ==

Using scripting to extend Code::Blocks' functionality

* [[Wizard scripts|Creating a new project wizard]]

Internationalization

2006-07-18T10:09:16Z

Peso: Categorize as developer documentation

[[Category:Code::Blocks Documentation]]
[[Category:Developer Documentation]]

This article is about how to realize and use localized C:B. All the works have been done under Windows XP SP2.

== Get the English POT file ==

The english POT file url is:

https://developer.berlios.de/patch/?func=detailpatch&patch_id=822&group_id=5358

I will update this file periodically. Of course, you can use the tool which I have created (see belown) to generate the POT file.

The content of the tool which is named as '''intl.bat''' is below:

rem ======= Begin of intl.bat =======

@echo off
wxrc src\resources\*.xrc -g -o src\src-xrc.cpp
wxrc sdk\resources\*.xrc -g -o sdk\sdk-xrc.cpp
wxrc plugins\astyle\resources\*.xrc -g -o plugins\astyle\astyle-xrc.cpp
wxrc plugins\classwizard\resources\*.xrc -g -o plugins\classwizard\classwizard-xrc.cpp
wxrc plugins\codecompletion\resources\*.xrc -g -o plugins\codecompletion\codecompletion-xrc.cpp
wxrc plugins\compilergcc\resources\*.xrc -g -o plugins\compilergcc\compilergcc-xrc.cpp
wxrc plugins\debuggergdb\resources\*.xrc -g -o plugins\debuggergdb\debuggergdb-xrc.cpp
wxrc plugins\defaultmimehandler\resources\*.xrc -g -o plugins\defaultmimehandler\defaultmimehandler-xrc.cpp
wxrc plugins\pluginwizard\resources\*.xrc -g -o plugins\pluginwizard\pluginwizard-xrc.cpp
wxrc plugins\todo\resources\*.xrc -g -o plugins\todo\todo-xrc.cpp

if not exist po md po

xgettext -C -n -k_ -o po\codeblocks.pot src\*.cpp src\*.h
xgettext -C -n -k_ -j -o po\codeblocks.pot src\wxAUI\*.cpp src\wxAUI\*.h
xgettext -C -n -k_ -j -o po\codeblocks.pot sdk\*.cpp sdk\*.h
xgettext -C -n -k_ -j -o po\codeblocks.pot sdk\as\bindings\*.cpp sdk\as\bindings\*.h
xgettext -C -n -k_ -j -o po\codeblocks.pot sdk\propgrid\src\propgrid\*.cpp sdk\propgrid\include\wx\propgrid\*.h
xgettext -C -n -k_ -j -o po\codeblocks.pot sdk\wxFlatNotebook\*.cpp
rem xgettext -C -n -k_ -j -o po\codeblocks.pot sdk\as\include\*.h
rem xgettext -C -n -k_ -j -o po\codeblocks.pot sdk\as\source\*.cpp sdk\as\source\*.h
rem xgettext -C -n -k_ -j -o po\codeblocks.pot sdk\wxscintilla\*.cpp sdk\wxscintilla\*.h
xgettext -C -n -k_ -j -o po\codeblocks.pot plugins\codecompletion\*.cpp plugins\codecompletion\*.h
xgettext -C -n -k_ -j -o po\codeblocks.pot plugins\codecompletion\parser\*.cpp plugins\codecompletion\parser\*.h
xgettext -C -n -k_ -j -o po\codeblocks.pot plugins\astyle\*.cpp plugins\astyle\*.h
xgettext -C -n -k_ -j -o po\codeblocks.pot plugins\astyle\astyle\*.cpp plugins\astyle\astyle\*.h
xgettext -C -n -k_ -j -o po\codeblocks.pot plugins\classwizard\*.cpp plugins\classwizard\*.h
xgettext -C -n -k_ -j -o po\codeblocks.pot plugins\codecompletion\*.cpp plugins\codecompletion\*.h
xgettext -C -n -k_ -j -o po\codeblocks.pot plugins\compilergcc\*.cpp plugins\compilergcc\*.h
xgettext -C -n -k_ -j -o po\codeblocks.pot plugins\debuggergdb\*.cpp plugins\debuggergdb\*.h
xgettext -C -n -k_ -j -o po\codeblocks.pot plugins\defaultmimehandler\*.cpp plugins\defaultmimehandler\*.h
xgettext -C -n -k_ -j -o po\codeblocks.pot plugins\pluginwizard\*.cpp plugins\pluginwizard\*.h
xgettext -C -n -k_ -j -o po\codeblocks.pot plugins\todo\*.cpp plugins\todo\*.h
xgettext -C -n -k_ -j -o po\codeblocks.pot plugins\xpmanifest\*.cpp plugins\xpmanifest\*.h
pause

rem ======= End of intl.bat =======

== The translation tool ==

Usually, we use the poEdit tool which can be downloaded [http://www.poedit.org/download.php here].

== Translating in poEdit ==

Rename codeblocks.pot into codeblocks.po. Use poEdit to open the file codeblocks.po. Change a few settings like:

[File]->[Preferences]->[Personalize]

[Catalog]->[Settings]->[Project info]->[Team/email/Language/Charset]

If Code::Blocks is compiled with Unicode, the charset should be set to utf-8; If Code::Blocks is compiled with ANSI, the charset should be set to your own language charset like gb2312, koi8-r etc.

After these settings are done, you can start translating. Don't be fooled, it's a hard work! During the process, of course, you can use your translation at any time.

== Create and use the .mo file ==

Pressing Ctrl+S in poEdit, you can get a *.mo file like codeblocks.mo which is what we need. To use codeblocks.mo, we just place it into C:\Program Files\CodeBlocks or C:\Program Files\CodeBlocks\share\CodeBlocks\locale\<lang>\LC_MESSAGES or C:\Program Files\CodeBlocks\share\CodeBlocks\locale\<lang>. My language is Chinese and I have installed C::B into E:\, so I place codeblocks.mo into E:\Program Files\CodeBlocks\share\CodeBlocks\locale\zh_CN.

If you want to use codeblocks.mo under Linux or Unix, you just place it into /usr/X11R6/share/locale/<lang>/LC_MESSAGES/. For example, I put it into /usr/X11R6/share/locale/zh_CN/LC_MESSAGES/ under FreeBSD.

Details about internationalization using wxWidgets can be found in the wxWidgets docs.

== Let Code::Blocks support your language ==

If you want Code::Blocks to support your language, you must modify the file \codeblocks\src\src\appglobals.cpp. In it, you can search for the word 'Chinese' to see the example. There are two vars about it:

const wxString langs[LANGUAGES_SIZE]
const int locales[LANGUAGES_SIZE]

== Troubleshooting ==

If you have any questions, you can send me a mail: zxpmyth at yahoo.com.cn.

Talk:Internationalization

2006-07-13T13:23:30Z

Peso:

[/index.php?topic=1022 This fairly long thread on the forum] has lots of people that wants to do translation. As the number of translators increase so do the need for coordination.

I would like to propose that CodeBlocks is registered with https://launchpad.net/ to centralise the translation.

If it is registered, this page should contain a link to the relevant page.

[[User:Peso]] 13-JUL-2006

Talk:Internationalization

2006-07-13T13:21:23Z

Peso: Suggest registration with launchpad.net

User:Peso

2006-07-13T13:19:54Z

Peso:

Hi.

I'm using CodeBlocks in my spare time to write an Abalone playing program.

Tools used:
* Windows, and some [http://www.colinux.org/ coLinux]
* [http://www.scintilla.org/ Scintilla] (I wish PFE still lived) / [http://www.gnu.org/software/emacs/ Emacs] (I wish I had learned VI first)
* C++ through [http://gcc.gnu.org/ GCC]. Actually [http://www.mingw.org/ MinGW] most of the time.
* [http://www.wxwidgets.org/ wxWidgets]
* [http://www.wxwidgets.org/wiki/index.php/WxIFM wxIFM]
* [http://www.gimp.org/windows/ GIMP]
* [http://www.gnu.org/software/autoconf/ Autoconf]
* [http://www.jrsoftware.org/isinfo.php Inno Setup]
* [http://groups.yahoo.com/group/abalone_prog/ abalone_prog] and [http://148009.aceboard.net/ Abalone Theory Forum]
* CodeBlocks

Regards,
Peer Sommerlund

User:Peso

2006-07-13T13:18:04Z

Peso:

Hi.

I'm using CodeBlocks in my spare time to write an Abalone playing program.

Tools used:
* Windows, and some [http://www.colinux.org/ coLinux]
* [http://www.scintilla.org/ Scintilla] (I wish PFE still lived) / [http://www.gnu.org/software/emacs/ Emacs] (I wish I had learned VI first)
* [http://gcc.gnu.org/ GCC], mostly [http://www.mingw.org/ MinGW]
* [http://www.wxwidgets.org/ wxWidgets]
* [http://www.wxwidgets.org/wiki/index.php/WxIFM wxIFM]
* [http://www.gimp.org/windows/ GIMP]
* [http://www.gnu.org/software/autoconf/ Autoconf]
* [http://www.jrsoftware.org/isinfo.php Inno Setup]
* [http://groups.yahoo.com/group/abalone_prog/ abalone_prog] and [http://148009.aceboard.net/ Abalone Theory Forum]
* CodeBlocks

Regards,
Peer Sommerlund

Template:Community:ImprovableArticles

2006-05-23T07:46:53Z

Peso: Add link to Building_From_Source

*[[Debugger scripts]] could use a brief step-by-step instruction so you don't have to read and understand the forum links.
*[[Building_From_Source]] could perhaps be better organized, see [[Talk:Building_From_Source]].
<div align="right">
<small>[https://wiki.codeblocks.org/index.php?title=Template:Community:ImprovableArticles&action=edit Edit]</small>
</div>

Talk:Installing Code::Blocks

2006-05-23T07:43:40Z

Peso: Fix link to category

There are several pages that give instructions on how to build codeblocks. I think this page should really be just a collection of links to all the specialised pages. Any opinions?

The build instructions can be found at [[:Category:Installation\Build_Instructions]].

A list of all pages (if some are not categorized properly) [[Special:Allpages]]

Here are a list of those that still live

Unix specific
* [[Compiling_Code::Blocks_in_Linux_(applies_to_all_distros)]]
* [[Compiling_Code::Blocks_in_RPM_based_distributions]]
* [[Compiling_Code::Blocks_in_Gentoo]]
* [[Compiling_Code::Blocks_in_FreeBSD]]
* [[Compiling_Code::Blocks_in_Mac_OS_X]]
Windows specific
* [[Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)]]
* [[Compiling_wxWidgets_2.6.1_to_develop_Code::Blocks_(MSW)]]
* [[Compiling_wxWidgets_2.6.2_to_develop_Code::Blocks_(MSW)]]
* [[Setting_the_WX_VER_variable]]

Some relevant info can be found
* [[Nightly_Cookbook]] --- zip is needed (this info is missing from the current page)

Peer Sommerlund, 2006-may-23

Using STLFilt with MinGW

2006-05-23T07:40:31Z

Peso: /* Links */ Instructions on how to link to a category

Welcome to the '''Sandbox''' where you can edit until your heart's content. Check out the 'edit' link at the top of this page to play around in here.

== Italic Text ==

Look at the ''italic text''.

== Bold Text ==

Look at the '''bold text'''.

== Lists ==

*Lists are easy.
**Really easy.

== Images ==

Some images....

[[Image:Chk.png]]
[[Image:Nop.png]]

== Links ==

Links to other pages, external sites. etc

Link to page in this wiki
[[Sandbox]]

Link with no title
[http://www.google.com]

Link with title
[http://www.google.com The Google Search engine]

Link to category (note the initial colon)
[[:Category:Installation\Build Instructions]]

To categorize a page, remove the initial colon like this: <nowiki>[[Category:Installation\Build_Instructions]]</nowiki>

Using STLFilt with MinGW

2006-05-23T07:35:00Z

Peso:

Welcome to the '''Sandbox''' where you can edit until your heart's content. Check out the 'edit' link at the top of this page to play around in here.

== Italic Text ==

Look at the ''italic text''.

== Bold Text ==

Look at the '''bold text'''.

== Lists ==

*Lists are easy.
**Really easy.

== Images ==

Some images....

[[Image:Chk.png]]
[[Image:Nop.png]]

== Links ==

Links to other pages, external sites. etc

Link to page in this wiki
[[Sandbox]]

Link with no title
[http://www.google.com]

Link with title
[http://www.google.com The Google Search engine]

Link to category
[[Category:Installation\Build_Instructions]] -- this doesn't work. How do you do this properly??
Like this: [[:Category:Installation\Build Instructions]]

Talk:Installing Code::Blocks

2006-05-23T06:06:34Z

Peso:

There are several pages that give instructions on how to build codeblocks. I think this page should really be just a collection of links to all the specialised pages. Any opinions?

The build instructions can be found at Category:[[Installation/Build_Instructions]]. (I'm not enough familiar with MediaWiki to be able to link properly to this page)

A list of all pages (if some are not categories properly) [[Special:Allpages]]

Here are a list of those that still live

Unix specific
* [[Compiling_Code::Blocks_in_Linux_(applies_to_all_distros)]]
* [[Compiling_Code::Blocks_in_RPM_based_distributions]]
* [[Compiling_Code::Blocks_in_Gentoo]]
* [[Compiling_Code::Blocks_in_FreeBSD]]
* [[Compiling_Code::Blocks_in_Mac_OS_X]]
Windows specific
* [[Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)]]
* [[Compiling_wxWidgets_2.6.1_to_develop_Code::Blocks_(MSW)]]
* [[Compiling_wxWidgets_2.6.2_to_develop_Code::Blocks_(MSW)]]
* [[Setting_the_WX_VER_variable]]

Some relevant info can be found
* [[Nightly_Cookbook]] --- zip is needed (this info is missing from the current page)

Peer Sommerlund, 2006-may-23

Using STLFilt with MinGW

2006-05-23T06:06:12Z

Peso: How do you link to a category?

Welcome to the '''Sandbox''' where you can edit until your heart's content. Check out the 'edit' link at the top of this page to play around in here.

== Italic Text ==

Look at the ''italic text''.

== Bold Text ==

Look at the '''bold text'''.

== Lists ==

*Lists are easy.
**Really easy.

== Images ==

Some images....

[[Image:Chk.png]]
[[Image:Nop.png]]

== Links ==

Links to other pages, external sites. etc

Link to page in this wiki
[[Sandbox]]

Link with no title
[http://www.google.com]

Link with title
[http://www.google.com The Google Search engine]

Link to category
[[Category:Installation/Build_Instructions]] -- this doesn't work. How do you do this properly??

Talk:Installing Code::Blocks

2006-05-23T05:51:25Z

Peso: Suggestion for new structure

There are several pages that give instructions on how to build codeblocks. I think this page should really be just a collection of links to all the specialised pages. Any opinions?

The build instructions can be found at [[Special:Allpages]]
Here are a list of those that still live

Unix specific
* [[Compiling_Code::Blocks_in_Linux_(applies_to_all_distros)]]
* [[Compiling_Code::Blocks_in_RPM_based_distributions]]
* [[Compiling_Code::Blocks_in_Gentoo]]
* [[Compiling_Code::Blocks_in_FreeBSD]]
* [[Compiling_Code::Blocks_in_Mac_OS_X]]
Windows specific
* [[Compiling_wxWidgets_2.4.2_to_develop_Code::Blocks_(MSW)]]
* [[Compiling_wxWidgets_2.6.1_to_develop_Code::Blocks_(MSW)]]
* [[Compiling_wxWidgets_2.6.2_to_develop_Code::Blocks_(MSW)]]
* [[Setting_the_WX_VER_variable]]

Peer Sommerlund, 2006-may-23

Template:Community:ImprovableArticles

2006-04-18T06:41:04Z

Peso:

*[[Debugger scripts]] could use a brief step-by-step instruction so you don't have to read and understand the forum links.
<div align="right">
<small>[https://wiki.codeblocks.org/index.php?title=Template:Community:ImprovableArticles&action=edit Edit]</small>
</div>

Roadmap for version 1.0

2006-04-18T06:22:51Z

Peso:

[[Category:Code::Blocks Documentation]]
==Version 1.0 (Pheidippides)==
''12 August 2006''

==Version 1.0 RC final (Athenades)==
''1 July 2006''
*No feature additions.
*Regression and bug handling only.

==Version 1.0 RC 3 (Ephialtes)==
''30 April 2006''
*[[Image:Chk.png]]Unicode support
**[[Image:Chk.png]]User interface
**[[Image:Chk.png]]Configuration system
**[[Image:Chk.png]]Editor component
**[[Image:Nop.png]]No fully automatic detection of document encoding
*[[Image:Blk.png]]Scripting support (Angelscript)
**[[Image:Chk.png]]Watch scripts (see [[Debugger scripts]])
**[[Image:Chk.png]]Build target scripts
**[[Image:Blk.png]]64bit support
*[[Image:Blk.png]]Global user variables
**[[Image:Chk.png]]Profile-dependent GUVs
**[[Image:Blk.png]]Multiple variable sets
**[[Image:Blk.png]]Custom variable definition
*[[Image:Chk.png]]wxFlatNoteBook editors
*[[Image:Chk.png]]wxAUI docking library
*[[Image:Chk.png]]Context-sensitive layout switching
*[[Image:Chk.png]]XML-based configuration system
*[[Image:Blk.png]]XML-based compiler framework
*[[Image:Blk.png]]Property-based build system
*[[Image:Chk.png]]Improved configuration user interface
*[[Image:Blk.png]]Automatic updates
*[[Image:Blk.png]]Usability and stability fixes for code completion plugin
*[[Image:Blk.png]]Regression and bug handling.

==Version 1.0 RC 2 (Leonidas)==
''25 October 2005''
*Precompiled headers (PCH) support! (currently works only with GCC)
*The source is now fully UNICODE-compatible!
*The source is also fully 64-bit compatible!
*Autoconf/automake build system is now used for non-windows platforms
* New editor functionality
**Find declaration
**Open #include
*Project wizard plugins
*Support for SDCC
*Better handling of modified files outside the IDE
*Single file compilation
*Find-in-Files for arbitrary paths/filemasks
*All internal file formats are well-formed, valid XML
*New plugins:
**Code statistics: counts nr. of source lines, nr. of comment lines, etc.
**CBProfiler: parses and displays the output of GProf, the GNU Profiler
**SourceExporter: exports the active file to HTML/RTF/ODT
*New lexers:
**Fortran77
**NVidia CG
**X-Base languages (Clipper, Foxpro)
*New and improved project templates:
**SDCC program
**Irrlicht 3D Graphics Engine
**Ogre 3D Graphics Engine
**GLFW project (OpenGL FrameWork)
**wxWidgets: static/dynamic unicode/ansi versions.

==Version 1.0 RC 1-1 (Oedipus)==
''2 August 2005''
*Several critical bug fixes

==Version 1.0 RC 1 (Laius)==
''25 July 2005''
*Compiler support for OpenWatcom
*Per-target environment variables
*Convenient "Start here" page
*Improved gcc error parsing
*Find in files functionality
*Ability to add files to project recursively.
*External dependency handling
*Better import of foreign project files
*Many GDB debugger updates
*Numerous user interface improvements
*New project templates
**QT4.
**Ogre3D.
* Modular Syntax highlighting
* Syntax highlighting support for:
**C/C++
**Windows resources
**HTML/XML/XSL
**Lua scripts
**GameMonkey scripts
**Hitach H8 ASM

Using STLFilt with MinGW

2006-04-18T06:18:32Z

Peso: /* Images */

Help:Editing

2006-04-01T15:28:31Z

Peso: /* The wiki markup */

== General ==

To edit a MediaWiki page, click on the '''"Edit this page"''' (or just '''"edit"''') link at one of its edges. This will bring you to a page with a text box containing the wikitext: the editable source code from which the server produces the webpage. For the special codes, see below.

After adding to or changing the wikitext it is useful to press "Preview", which produces the corresponding webpage in your browser but does not make it publicly available yet (not until you press "Save"). Errors in formatting, links, tables, etc., are often much easier to discover from the rendered page than from the raw wikitext.

If you are not satisfied you can make more changes and preview the page as many times as necessary. Then write a short edit summary in the small text field below the edit-box and when finished press "Save". Depending on your system, pressing the "Enter" key while the edit box is not active (i.e., there is no typing cursor in it) may have the same effect as pressing "Save".

You may find it more convenient to copy and paste the text first into your favorite text editor, edit and spell check it there, and then paste it back into your web browser to preview. This way, you can also keep a local backup copy of the pages you have edited. It also allows you to make changes offline, but before you submit your changes, please make sure nobody else has edited the page since you saved your local copy (by checking the page history), otherwise you may accidently revert someone else's edits. If someone has edited it since you copied the page, you'll have to merge their edits into your new version (you can find their specific edits by using the "diff" feature of the page history). These issues are handled automatically by the Mediawiki software if you edit the page online, retrieving and submitting the wikicode in the same text box.

== Dummy edit ==

If the wikitext is not changed no edit will be recorded and the edit summary is discarded.

A dummy edit is a change in wikitext that has no effect on the rendered page, such as changing the number of newlines at some position from 0 to 1 or from 2 to 3 or conversely (changing from 1 to 2 makes a difference, see below). This allows an edit summary, and is useful for correcting a previous edit summary, or an accidental marking of a previous edit as "minor" (see below). Also it is sometimes needed to refresh the cache of some item in the database, see e.g. A category tag in a template; caching problem.

== Minor edits ==

== The wiki markup ==

* http://www.mediawiki.org/wiki/Sandbox
* http://commons.wikimedia.org/wiki/Image:Cheatsheet-en.png

== Page protection ==

In a few cases the link labeled "Edit this page" is replaced by the text "Protected page" (or equivalents in the language of the project). In that case the page can not be edited.

Help:Editing

2006-04-01T15:28:08Z

Peso: /* The wiki markup */

== General ==

To edit a MediaWiki page, click on the '''"Edit this page"''' (or just '''"edit"''') link at one of its edges. This will bring you to a page with a text box containing the wikitext: the editable source code from which the server produces the webpage. For the special codes, see below.

After adding to or changing the wikitext it is useful to press "Preview", which produces the corresponding webpage in your browser but does not make it publicly available yet (not until you press "Save"). Errors in formatting, links, tables, etc., are often much easier to discover from the rendered page than from the raw wikitext.

If you are not satisfied you can make more changes and preview the page as many times as necessary. Then write a short edit summary in the small text field below the edit-box and when finished press "Save". Depending on your system, pressing the "Enter" key while the edit box is not active (i.e., there is no typing cursor in it) may have the same effect as pressing "Save".

You may find it more convenient to copy and paste the text first into your favorite text editor, edit and spell check it there, and then paste it back into your web browser to preview. This way, you can also keep a local backup copy of the pages you have edited. It also allows you to make changes offline, but before you submit your changes, please make sure nobody else has edited the page since you saved your local copy (by checking the page history), otherwise you may accidently revert someone else's edits. If someone has edited it since you copied the page, you'll have to merge their edits into your new version (you can find their specific edits by using the "diff" feature of the page history). These issues are handled automatically by the Mediawiki software if you edit the page online, retrieving and submitting the wikicode in the same text box.

== Dummy edit ==

If the wikitext is not changed no edit will be recorded and the edit summary is discarded.

A dummy edit is a change in wikitext that has no effect on the rendered page, such as changing the number of newlines at some position from 0 to 1 or from 2 to 3 or conversely (changing from 1 to 2 makes a difference, see below). This allows an edit summary, and is useful for correcting a previous edit summary, or an accidental marking of a previous edit as "minor" (see below). Also it is sometimes needed to refresh the cache of some item in the database, see e.g. A category tag in a template; caching problem.

== Minor edits ==

== The wiki markup ==

http://www.mediawiki.org/wiki/Sandbox
http://commons.wikimedia.org/wiki/Image:Cheatsheet-en.png

== Page protection ==

In a few cases the link labeled "Edit this page" is replaced by the text "Protected page" (or equivalents in the language of the project). In that case the page can not be edited.

Debugger scripts

2006-04-01T15:22:40Z

Peso:

== Debugger scripts ==

Debugger scripts are similar to [http://www.codeproject.com/csharp/ImageVisualizer.asp Visual Studio Debugger Visualizer]. It allows you to write a small piece of code that gets executed by the debugger whenever you try to view a specific type of variables.

Quote from Game_Ender - March 23, 2006

''I don't think its possible to open up another window to visualize something but the can you make a debugger script. This script is called by Code::Blocks when ever GDB encounters your variable type and can be used to show custom text with the important information you need in it. Search for "debugger scripts" on the forum. I don't think this feature is documented.''

The forum has the following topics:
* [/index.php?topic=2097.0 Custom Watch Script Pluggins]
* [/index.php?topic=2636.0 Change the format in the debugger]
* [/index.php?topic=2150.0 Watches modification]

Debugger scripts

2006-04-01T15:16:33Z

Peso:

== Debugger scripts ==

Debugger scripts are similar to [http://www.codeproject.com/csharp/ImageVisualizer.asp Visual Studio Debugger Visualizer]. It allows you to write a small piece of code that gets executed by the debugger whenever you try to view a specific type of variables.

Quote from Game_Ender

''I don't think its possible to open up another window to visualize something but the can you make a debugger script. This script is called by Code::Blocks when ever GDB encounters your variable type and can be used to show custom text with the important information you need in it. Search for "debugger scripts" on the forum. I don't think this feature is documented.''

The forum has the following topics:
* [/index.php?topic=2097.0 Custom Watch Script Pluggins]
* [/index.php?topic=2636.0 Change the format in the debugger]
* [/index.php?topic=2150.0 Watches modification]

Talk:Coding style

2006-04-01T14:52:03Z

Peso: Request for coding standard for comments.

How about comments?