Various development tips - Revision history

Artojon: contains outdated information and the article should be split

2006-09-01T09:33:45Z

contains outdated information and the article should be split

Artojon: edited categories

2006-07-08T14:12:50Z

edited categories

Thomas at 15:34, 6 February 2006

2006-02-06T15:34:16Z

Takeshi Miya: /* Using Code::Blocks' global configuration */

2005-12-13T22:35:35Z

Using Code::Blocks' global configuration

Grv: /* JIT debugging */

2005-08-24T10:15:34Z

JIT debugging

Grv: /* Using Code::Blocks' global configuration */

2005-08-23T13:04:07Z

Using Code::Blocks' global configuration

Mandrav: Using Code::Blocks' global configuration

2005-05-03T07:10:56Z

Using Code::Blocks' global configuration

New page

This page contains various tips for developing '''for''' Code::Blocks. It is meant for developers wanting to extend Code::Blocks.

====Using Code::Blocks' global configuration====

There are many cases where you may need to have persistent configuration values. For example, you may be writing a new plugin (or extend an existing).
The global configuration object is a singleton, meaning that only one exists for the program's lifetime. It can be accessed like this:

<pre>#include <configmanager.h>
...
ConfigManager::Get()->Read(...); // "read" example
ConfigManager::Get()->Write(...); // "write" example</pre>

As you can see, all that's needed is to include the relevant header file. To access the configuration then, you use the static member function ConfigManager::Get() which returns a ConfigManager object (the only). ConfigManager descends from wxConfigBase and so it inherits all its public methods for working with configuration files.

Let's see a real world example. Suppose you 're writing a new plugin and it needs to keep a directory path in a configuration value.
To write the configuration value, possibly prior to exiting (or after its imaginary configuration window is closed), do this:
<pre>// somehow set pluginDir to the value you want
wxString pluginDir;
// write it in the global configuration
ConfigManager::Get()->Write("/new_plugin/directory", pluginDir);
</pre>
And to read the saved value, do this:
<pre>// write it in the global configuration
// if we never written the value before, "default" will be returned
wxString pluginDir = ConfigManager::Get()->Read("/new_plugin/directory", "default");
</pre>
In the above examples, the "/new_plugin" part of the string should be replaced with something unique for the plugin you 're writing. For example, the compiler plugin uses "/compiler_gcc", the internal editor class uses "/editor" and so on.
That's how simple is to use Code::Blocks' global configuration :)

One more thing: if you want your plugin's configuration to be included in the import/export list in "Settings->Import/export configuration", just add in your plugin's constructor(s) the following:
<pre>ConfigManager::AddConfiguration(m_PluginInfo.title, "/new_plugin");</pre>
This line will add your plugin in the import/export list. Neat huh?

← Older revision		Revision as of 09:33, 1 September 2006
Line 1:		Line 1:
−	[[Category:~~Developer Documentation~~]]	+	[[Category:Outdated]]
		+	{{outdated}}
	This page contains various tips for developing '''for''' Code::Blocks. It is meant for developers wanting to extend Code::Blocks.		This page contains various tips for developing '''for''' Code::Blocks. It is meant for developers wanting to extend Code::Blocks.

← Older revision		Revision as of 14:12, 8 July 2006
Line 1:		Line 1:
−	[[Category:~~Code::Blocks Development~~]]	+	[[Category:Developer Documentation]]
	This page contains various tips for developing '''for''' Code::Blocks. It is meant for developers wanting to extend Code::Blocks.		This page contains various tips for developing '''for''' Code::Blocks. It is meant for developers wanting to extend Code::Blocks.

← Older revision		Revision as of 15:34, 6 February 2006
Line 1:		Line 1:
		+	[[Category:Code::Blocks Development]]
	This page contains various tips for developing '''for''' Code::Blocks. It is meant for developers wanting to extend Code::Blocks.		This page contains various tips for developing '''for''' Code::Blocks. It is meant for developers wanting to extend Code::Blocks.

← Older revision		Revision as of 22:35, 13 December 2005
Line 2:		Line 2:

	====Using Code::Blocks' global configuration====		====Using Code::Blocks' global configuration====
		+
		+	'''NOTE: All of this info is only valid up to 1.0RC2. New versions will have another way to access the configuration.'''
		+	'''''Please update this with the new info.'''''

	There are many cases where you may need to have persistent configuration values. For example, you may be writing a new plugin (or extend an existing).		There are many cases where you may need to have persistent configuration values. For example, you may be writing a new plugin (or extend an existing).

@@ Line 40: / Line 40: @@
 this will install drmingw as the jit debugger (drmingw -u to later uninstall)
 (windbg from the platform sdk can be installed as the jit debugger with windbg -I
-but it doesn't support gcc gcc debug symbols.  it does support vc5/6/7 .pdb files
+but it doesn't support gcc debug symbols.  it does support vc5/6/7 .pdb files
 generated by vc++ toolkit, providing true source level debugging)

← Older revision		Revision as of 13:04, 23 August 2005
Line 33:		Line 33:
	<pre>ConfigManager::AddConfiguration(m_PluginInfo.title, "/new_plugin");</pre>		<pre>ConfigManager::AddConfiguration(m_PluginInfo.title, "/new_plugin");</pre>
	This line will add your plugin in the import/export list. Neat huh?		This line will add your plugin in the import/export list. Neat huh?
		+
		+	====JIT debugging====
		+
		+	cd C:\mingw\bin
		+	drmingw -i -v
		+	this will install drmingw as the jit debugger (drmingw -u to later uninstall)
		+	(windbg from the platform sdk can be installed as the jit debugger with windbg -I
		+	but it doesn't support gcc gcc debug symbols. it does support vc5/6/7 .pdb files
		+	generated by vc++ toolkit, providing true source level debugging)
		+
		+	to test:
		+	- create a win32 project using the gcc compiler as default
		+	- place
		+	__asm("int3");
		+	somewhere in the code
		+	- compile & run
		+	gcc -g
		+
		+	- create a win32 project using vc++ toolkit compiler as default
		+	- place
		+	__asm{ int 3 };
		+	somewhere in the code
		+	- compile & run
		+	cl /Zi
		+	link /debug