Mailing list
A mailman mailing list is setup to discuss problems and follow updates for the Computer Game Development course at cgd@lists.openengine.dk.
All participants have automatically been added with the email information supplied at the aula course website. If you for some reason have not been added (you should have received an initial email on subscription) please subscribe at http://lists.openengine.dk/mailman/listinfo/cgd, and make sure that you are signed up for the course at the aula course website.
To change your personal preferences visit http://lists.openengine.dk/mailman/options/cgd. Here you can change options such as receiving batches once a day and the email you have subscribed with.
Why
The change from a forum to a mailing list as our means of discussion was proposed to increase the discussion between groups.
A mailing list has the property that the information is sent to you instead of the forum where you yourself must seek it out.
How
To post on the list simply send an email to cgd@lists.openengine.dk. If replying to a previous post please always reply to that email so the thread does not break.
For those that have not used a mailing list before a couple of guidelines are in place.
Send plain text (read: not html)
This is a mailing list used mostly by developers. Some use outlook, others thunderbird and - god forbid - some use emacs or vi as their email client. Plain text works with all and is a good default.
Always use reply all
Note: The cgd@lists.openengine.dk list has been modified to automatically set the reply-to header to the list itself. You may therefor disregard the following.
Most email client have two means of replying. One that just sends an email to the sender. And one that sends to the sender and all other recipients. We wish to always (with very few exceptions) use reply all in order for other participants to gain knowledge about the discussion.
Top posting vs. bottom posting
This is a topic of much discussion that we do not care for. Here is our standpoint.
When using a list with others it is important to be able to follow the current discussion. Top-posting makes this hard and it muddles the discussion because you loose context and have to repeat things. We therefor prefer bottom-posting.
I hope the following examples illustrate the pros and cons.
Example (top):
That is a wired error. The EXCLUDE_FROM_ALL option is used so the tests are not compiled by the default all target. A quick fix to get on with building is to apply this patch to tests/CMakeLists.txt --- head/openengine/tests/CMakeLists.txt 2007-09-05 21:01:04.000000000 +0200 +++ work/openengine/tests/CMakeLists.txt 2007-09-05 12:24:34.000000000 +0200 @@ -20,6 +20,7 @@ ADD_EXECUTABLE(testsuite - EXCLUDE_FROM_ALL ${test_SOURCES}) If others are having this problem please report to this thread. > `cmake --version' gives me `cmake version 2.4-patch 6' and I > am running Ubuntu (Edgy). >> Could you please supply the version of cmake and what >> platform you are running. >>> I get a build error when using the command ./make.sh rebuild >>> The error i get is about not being able to find the file >>> EXCLUDE_FROM_ALL and then it stops.
Example (bottom):
>>> I get a build error when using the command ./make.sh rebuild >>> The error i get is about not being able to find the file >>> EXCLUDE_FROM_ALL and then it stops. >> Could you please supply the version of cmake and what >> platform you are running. > `cmake --version' gives me `cmake version 2.4-patch 6' and I > am running Ubuntu (Edgy). That is a wired error. The EXCLUDE_FROM_ALL option is used so the tests are not compiled by the default all target. It seems that your cmake thinks that it is a source file for the target :/ A quick fix to get on with building is to apply this patch to tests/CMakeLists.txt --- head/openengine/tests/CMakeLists.txt 2007-09-05 21:01:04.000000000 +0200 +++ work/openengine/tests/CMakeLists.txt 2007-09-05 12:24:34.000000000 +0200 @@ -20,6 +20,7 @@ ADD_EXECUTABLE(testsuite - EXCLUDE_FROM_ALL ${test_SOURCES}) If others are having this problem please report to this thread.
An example of good usage of context
Post:
If i change the structure of the SDLInput module i break the test for that module. Must i stick to the structure? and do the tests need to pass? Also what is the meaning of this top vs. bottom posting conversation?
Reply:
> If i change the structure of the SDLInput module i break the test for > that module. Must i stick to the structure? You must adhere to the IMouse and IKeyboard interfaces to maintain compatibility with future code. But you may extend it and restructure as you see fit. > and do the tests need to pass? No. They are there to help you, not hinder. > Also what is the meaning of this top vs. bottom posting conversation? I hope that is apparent to you now.
