Statements
The reason why we employ QT in our project is more than GUI design itself.
We were introduced to Threads implementation and Network stuff in CSCI212, and all that we learned and built was under POSIX standard, on Linux platform. However, these technologies don’t seem to be supported on Windows, and that’s why QT is useful in this situation. We can benefit from the powerful support from QT, and it also makes it possible for us to release Linux version of our project in the future (if we want to…).
Report for Week 2
We spent quite many efforts implementing QT with VS, but some problem exists. For example, VS don’t recognize the QT libraries so everytime you include a QHeader you always see a read line indicating “error”. As it doesn’t affect compiling, it’s becoming difficult to tell the real errors and fake “errors”.
Activities
In this week’s meeting we basically talked about some technical problems regarding the QT environment and IDE in details, and tried to solve those problems. Also I got feedbacks from Allen and Henry that QT is easy to start, but not so easy to really write a real GUI. Considering all the problems with QT and VS, as well as the facts that they’re still waiting a configured IDE with QT, we decided to move from VS to Netbeans for all our members. This will certainly make us slow in the progress, but it’s the best choice so far.
Tasks
Coding!
All members should start coding from this week, based on the ideas we sketched in the preliminary technical documentation.
Jeff and Drake (me) will continue to seek a way to implement QT with Netbeans.
No comments:
Post a Comment