Structure (C plus plus) - Revision history

Sprotiel: /* Simulation engine */ ->Numsgil

2006-01-07T22:31:40Z

‎Simulation engine: ->Numsgil

Sprotiel: refactoring

2006-01-07T22:18:40Z

refactoring

Numsgil at 22:06, 7 January 2006

2006-01-07T22:06:38Z

Sprotiel: a bit more

2006-01-07T21:46:07Z

a bit more

65.123.110.39 at 19:34, 7 January 2006

2006-01-07T19:34:22Z

65.123.110.39 at 19:33, 7 January 2006

2006-01-07T19:33:26Z

Sprotiel: First draft

2006-01-06T19:02:57Z

First draft

New page

<center>''This is only a proposal initiated by [[User:Sprotiel|Sprotiel]].''</center>

This page defines the algorithmic structure of the program in terms of objects, without going into too much coding details.

== User interface ==
If DarwinBots is to become a serious program, it should be able to run from batch files and/or (Python) scripts. Obviously though, a GUI is the prefered mode of interaction for most people and has to be the top priority. However, it should be thought of as a front-end and not be too tightly integrated into the core engine.

== Simulation engine ==
We should have a top-level object which has all the information needed to run a sim. Right now, it's the rather meager EngineClass. Most globals should be integrated into it.

@@ Line 12: / Line 12: @@
 == Simulation engine ==
-We should have a top-level object which has all the information needed to run a sim. Right now, it's the rather meager EngineClass. Most globals should be integrated into it. It might be useful to separate its purely physical part (that handles dynamics and collision and needn't know anything about the internals of the objects) from its biological part (metabolism, reproduction, etc.)
+=== Discussion ===
-<font color="Red">Do you mean how the source code files are organized, or the logical segregation of classes?  I am reluctant to segregate the physical files into folders more than they are already because it makes the include file paths unwieldly.  However, I've created logical files to group the source code into in MSVC, which is what I'd suggest doing.  I'm sure Dev-C allows you to do it too.</font>
+:<font color="Red">Do you mean how the source code files are organized, or the logical segregation of classes?  I am reluctant to segregate the physical files into folders more than they are already because it makes the include file paths unwieldly.  However, I've created logical files to group the source code into in MSVC, which is what I'd suggest doing.  I'm sure Dev-C allows you to do it too.</font> [[User:Numsgil|Numsgil]]
 == Robots ==

← Older revision		Revision as of 22:18, 7 January 2006
Line 33:		Line 33:

	The non-Core engine (things like mutations, DNA parsing, etc.) hasn't been worked over yet in thought or in code.		The non-Core engine (things like mutations, DNA parsing, etc.) hasn't been worked over yet in thought or in code.
−
−	~~=== Coding style ===~~
−
−	~~This is how I code:~~
−
−	~~void function(parameter 1, parameter 2)~~
−	{
−	~~for(some; things; inside)~~
−	{
−	~~blah;~~
−	}
−	}
−
−	~~Notice the 4 space indentation.~~
−
−	I don't care how you write code, so long as I can read it and understand it. When we edit each other's code, we should endeavor to maintain the same style as the rest of the function we're editing. That is, don't mix styles in the same function.
−
−	~~If you don't like the idea of mixing styles at all in the whole project, feel free to adopt my style. ;)~~
−
−	If you're adding a line that isn't very reader friendly, please comment in thoroughly. Write the code as if a bunch of non-savvy beginning programers are going to read and edit it. No fancy programming tricks please. Do in 8 lines what you can cram into 2 if 8 lines makes it more readable. Use lots of white space. This code needs to be maintainable by anyone and everyone.
−
−	My compiler is MSVC++ 6.0, and so that's the official compiler of the rest of the project. If you use a different compiler, I will endeavor to let it compile for you. But the privelege of compiling to the nice sight of 0 errors, 0 warnings is reserved for me and others using MSVC++ 6.0. I can supply versions of MSVC++ 6.0 to some who'd like it.

	At the moment, my goals are to get the C++ version equally working as the VB version. So things like batch runs etc. are simply a non-issue at the moment.		At the moment, my goals are to get the C++ version equally working as the VB version. So things like batch runs etc. are simply a non-issue at the moment.

@@ Line 13: / Line 13: @@
 == Simulation engine ==
 We should have a top-level object which has all the information needed to run a sim. Right now, it's the rather meager EngineClass. Most globals should be integrated into it. It might be useful to separate its purely physical part (that handles dynamics and collision and needn't know anything about the internals of the objects) from its biological part (metabolism, reproduction, etc.)
 == Robots ==

@@ Line 40: / Line 40: @@
 I don't care how you write code, so long as I can read it and understand it.  When we edit each other's code, we should endeavor to maintain the same style as the rest of the function we're editing.  That is, don't mix styles in the same function.
-If you don't like the idea of mixing styles at all in the whole project, feel free to adapt my style. ;)
+If you don't like the idea of mixing styles at all in the whole project, feel free to adopt my style. ;)
 If you're adding a line that isn't very reader friendly, please comment in thoroughly.  Write the code as if a bunch of non-savvy beginning programers are going to read and edit it.  No fancy programming tricks please.  Do in 8 lines what you can cram into 2 if 8 lines makes it more readable.  Use lots of white space.  This code needs to be maintainable by anyone and everyone.

← Older revision		Revision as of 19:33, 7 January 2006
Line 8:		Line 8:
	== Simulation engine ==		== Simulation engine ==
	We should have a top-level object which has all the information needed to run a sim. Right now, it's the rather meager EngineClass. Most globals should be integrated into it.		We should have a top-level object which has all the information needed to run a sim. Right now, it's the rather meager EngineClass. Most globals should be integrated into it.
		+
		+
		+	== Comments by Numsgil ==
		+
		+	Basically, the code is divided into 3 primary areas:
		+
		+	GUI, GFX, and Engine, each doing their obvious respective function.
		+
		+	GUI is written in a library called "FOX GUI Toolkit", which was picked rather arbitrarily because it was one of the few GUIs I could figure out. Most of the code up till this point for the GUI has been written by Wolf. The GUI is also (at the moment) the frontend into the other three modules. So the GUI is also the central regulating machine.
		+
		+	GFX is written using openGL, with the consideration of allowing it to, in the future, be expanded to 3D. It's probably done really inefficiently, but I can't find anyone who knows more openGL to work on it with me.
		+
		+	The Core Engine (things that are called every cycle) is written with the consideration that Darwinbots has procedurally written in the past. And I have been a procedural programmer in the past. And Darwinbots needs to be fast and readable. All this results in a style more reminiscent of C (with some classes thrown in) than C++ (with it's crazy templating and polymorphism and fun things like that).
		+
		+	The non-Core engine (things like mutations, DNA parsing, etc.) hasn't been worked over yet in thought or in code.
		+
		+	=== Coding style ===
		+
		+	This is how I code:
		+
		+	void function(parameter 1, parameter 2)
		+	{
		+	for(some; things; inside)
		+	{
		+	blah;
		+	}
		+	}
		+
		+	Notice the 4 space indentation.
		+
		+	I don't care how you write code, so long as I can read it and understand it. When we edit each other's code, we should endeavor to maintain the same style as the rest of the function we're editing. That is, don't mix styles in the same function.
		+
		+	If you don't like the idea of mixing styles at all in the whole project, feel free to adapt my style. ;)
		+
		+	If you're adding a line that isn't very reader friendly, please comment in thoroughly. Write the code as if a bunch of non-savvy beginning programers are going to read and edit it. No fancy programming tricks please. Do in 8 lines what you can cram into 2 if 8 lines makes it more readable. Use lots of white space. This code needs to be maintainable by anyone and everyone.
		+
		+	My compiler is MSVC++ 6.0, and so that's the official compiler of the rest of the project. If you use a different compiler, I will endeavor to let it compile for you. But the privelege of compiling to the nice sight of 0 errors, 0 warnings is reserved for me and others using MSVC++ 6.0. I can supply versions of MSVC++ 6.0 to some who'd like it.
		+
		+	At the moment, my goals are to get the C++ version equally working as the VB version. So things like batch runs etc. are simply a non-issue at the moment.

@@ Line 1: / Line 1: @@
 <center>''This is only a proposal initiated by [[User:Sprotiel|Sprotiel]].''</center>
 This page defines the algorithmic structure of the program in terms of objects, without going into too much coding details.
 == User interface ==
@@ Line 7: / Line 12: @@
 == Simulation engine ==
-We should have a top-level object which has all the information needed to run a sim. Right now, it's the rather meager EngineClass. Most globals should be integrated into it.
+We should have a top-level object which has all the information needed to run a sim. Right now, it's the rather meager EngineClass. Most globals should be integrated into it. It might be useful to separate its purely physical part (that handles dynamics and collision and needn't know anything about the internals of the objects) from its biological part (metabolism, reproduction, etc.)
 == Comments by Numsgil ==