Orxonox

ok, the last part is crap for my work in the last few hours... But no problem to fix: find and replace through files... But I agree: even though Ogre and OIS are upper case, lowercase makes more sense: namespaces -> Classes -> variables and functions Ha, already done ;) edit: added the '_s' postfix ...

I have a suggestion for the namespace part in the style guide: Don't write "using namespace ..;" in header files because otherwise if someone included that header file, the "using namespace .." would automatically be included as well. That may lead to unwanted errors. I'm not sure whether I'm tellin...

I have had a look at CMake. But I don't think hacking something together in order to make my project work under Windows is a good idea. It probably wouldn't even be such a big deal since the cmake structure from the trunk should work under Windows, too. But without really understanding what cmake do...

I feared so. For the rest, I'll keep it short since I have already written it all once (just clicked wrongly on a button on the page, schwups, everything was gone): - deleted "main_reto", added a real branch "main_reto" and "main_reto_vs05", in which I keep my up-to-date files for now - make... that...

About the style guide and the '{': I don't think that this is important enough to define a clear rule. I wouldn't mind, if we did that mixed ways. However, the '{' in a function is quite important, since it structures the code. And by the way: I really don't think if everyone changes the style guide...

I'm seriously asking myself how you got my post... I've edited the message minutes afterwards.
I'm guessing you are administrator..

Sometimes it actually happens (wouldn't believe it myself) that you forget to set a comment for the SVN commit. I thought that the omni potent svn should allow one to rewrite comments (implemented nicely in the TortoiseSVN GUI), but I wasn't successful in doing so. Is this my problem or does the rep...

Never mind...

x3n wrote:

1337 wrote:But this is definitly not the document we've seen. ("{" in while or if, the last part of the document..)

personally i prefer to put the "{" on a new line, but thats one of the less important points in the styleguide

Agreed. I'm so used to putting '{' on a new line...

I've just come across a 'problem' with Doxygen: It is possible to write a comment for a function in the header file and in the code file. Now, on the doxygen homepage there is a description of what will be taken in this case (Brief descrition from header, detailed one from the source). Since I haven...

Sorry, didn't realise that we are ALL allowed to make ANY changes in the wiki.

Link has been changed...

Oh, and what is about doxygen?

And I suggest that every function has a comment header with tags like author, what it does, bugs, etc. But this header should be consistent.

I just wanted to have a look at the coding rules from yesterday: http://www.orxonox.net/wiki/CodingRules But this is definitly not the document we've seen. ("{" in while or if, the last part of the document..) So: where is the actual one? Edit: Found it: http://www.orxonox.net/wiki/c%2B%2B_styleguid...

I'm going to sign in as soon as I'm t home (I don't have my schedule at hand).
Just got the mail about the this event yesterday...

Yeah, right now it is a little bit of a patch work. Wherever new code is be inserted (like ships, enemies, etc. in RunManager) there is a mess. Simply something that shows anything but a black screen. Right now we're having physics lecture and I'm working on how to implement a simple ship (I'm gonna...