Design document

[DanielPharos]

The QuArK 7 design document is located here: http://quark.sourceforge.net/quark7/design_doc/

[xmm0]

I'm excited to get started! 

[etlaayz]

I noticed that QObject is the same name as QT's foundation object. We might wan to change our name to avoid confusion.

[DanielPharos]

It's called QObject in Q6 as well. The only conflict could occur in the Qt library interfacing code, not in the main program. I'm reluctant to change the name just because of a collision there, but it's a good point. I guess we'll have to put all the QuArK classes in a separate namespace (which is actually a good idea anyway).

[etlaayz]

I am just curious, any particular reason you chose C++?

[DanielPharos]

I wanted a language that supported the datatypes of C natively, so interfacing with external libraries would not need any variable-conversions (speed! speed!). Obviously, C(++) is a natural choice then. I picked C++, because with a project this large, OOP is absolutely necessary to keep it maintainable. Also, there's lots of people that know C++.

But most of QuArK7 will reside in the Python-part of the code. The C++ code will only provide the underlying mechanisms.

[xmm0]

It's called QObject in Q6 as well. The only conflict could occur in the Qt library interfacing code, not in the main program. I'm reluctant to change the name just because of a collision there, but it's a good point. I guess we'll have to put all the QuArK classes in a separate namespace (which is actually a good idea anyway).

I'm all for the namespace idea. I'm crazy about naming conventions