Jobs done in week 5.

******The recording of meeting in week 5 will be uploaded to the project website.******

In previous weeks we've discussed about the concepts, ideas and functions to be covered in our project. So I think it's time to actually start coding jobs now.

The assignments for this week is simple. Jeff takes care of the DATABASE part, Henry takes the DOCUMENTATION part, Allen collects and organize MULTIPLE CHOICE QUESTIONS and I take the real coding part.

And now I'm going to talk about the problems & difficulties I met...

1. Different IDEs & Project building

Different IDEs are used in our group, thus a project file in one IDE isn't compatible with another.

That costs extra time and effort to rebuild projects.

And in terms of project building, it's absolutely not like writing a CPP file in assignments of other subjects. There are many, and going to be hundreds of (or even thousands of) resource files and source files. We need to get things organized, every function into its own source file and decide what files are to be shared by other files, otherwise we just get ourselves messed up. This job is not concerned about the skills of programming, but it's very tricky.

2. The use of IDEs & advanced C++ techniques

We four people don't have experiencing in programming in IDE before, so no matter it's Visual Studio or Netbeans and the later to be used QT, we don't know how to operate it efficiently and it takes time for us to familarize ourselves with these tools. So it might be useful to slow down the progress on coding and to take more time in reading and searching references.

It's the same situation with C++. We need to take time to learn how to use new header files.