meta data for this page
Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
qt2010:grp1:start [2010/10/21 17:18] grp1 |
qt2010:grp1:start [2010/10/31 21:02] (current) grp1 |
||
---|---|---|---|
Line 7: | Line 7: | ||
===== Idea ===== | ===== Idea ===== | ||
- | Software will translate | + | QuTe Translation is targeted on people that are living abroad and on those who doesn' |
+ | QuTe Translation provide them an integrated tool for their mobile phones to translate | ||
+ | Also, QuTe Translation make it easier to response for those kind of messages, that are written | ||
+ | |||
+ | QuTe Translation | ||
==== Features ==== | ==== Features ==== | ||
- | - Translation | + | - Incoming translation |
- | - Text to Speech | + | - Outgoing translation |
- | - Word completion (optional) | + | - Daemon style |
===== Implementation Plan and Goals ===== | ===== Implementation Plan and Goals ===== | ||
Line 18: | Line 22: | ||
- Environment and language are QT creator and QT using C++. | - Environment and language are QT creator and QT using C++. | ||
- | - Translation is made using Google translate. | + | - Translation is made using Google translate, connection provided by network module and QHttp class. |
- | - To use Google translate a tcp/ip connection needs to be made, so Qhttp is used. | + | - User interface |
- | + | ||
- | - Text to Speech is done using eSpeak library. (http:// | + | |
^Feature ^ Priority ^ Status | | ^Feature ^ Priority ^ Status | | ||
- | |GUI|1|Do| | + | |GUI|1|Done| |
- | |Translation|1|Done | + | |Translation|1|Done| |
|Daemon implementation| 2 |Done | | |Daemon implementation| 2 |Done | | ||
- | |Text-to-Speech|2|Done| | + | |Language detection|3|Done| |
- | |Word completion|3|-| | + | |User data saving |
===== Design ===== | ===== Design ===== | ||
- | (structure of the software, class diagram) | ||
===== Screen shots ===== | ===== Screen shots ===== | ||
+ | {{: | ||
+ | * Screen-shot 1: New incoming message and it's translation is shown to user. | ||
+ | {{: | ||
+ | * Screen-shot 2: View for searching already received messages user want to translate. | ||
+ | {{: | ||
+ | * Screen-shot 3: User is sending reply in German, that will be delivered in English. | ||
===== Project Artefacts ===== | ===== Project Artefacts ===== | ||
- | Versio 1: | ||
- | fetching text from google, triggering by incoming sms {{: | ||
==== Presentation slides ==== | ==== Presentation slides ==== | ||
- | Short idea presentation: | + | * Short idea presentation: |
+ | * Final presentation: | ||
+ | * Final presentation: | ||
==== Report document ==== | ==== Report document ==== | ||
+ | * Brochure {{: | ||
+ | * Technical report {{: | ||
==== Source Package ==== | ==== Source Package ==== | ||
+ | {{: | ||
=== How to run software === | === How to run software === | ||
+ | |||
+ | - Open project in QtCreator | ||
+ | - Deploy it to the phone | ||
+ | - Wait for incoming message | ||
+ | **OR** | ||
+ | - Open project in QtCreator | ||
+ | - Build and run project in simulator | ||
+ | - Simulate incoming sms with simulator control panel | ||
===== Conclusion ===== | ===== Conclusion ===== | ||
+ | |||
+ | QT was not very clear to start with. Signal and slots took time to understand.But as it becomes clear, they are really handy to use and data can be delivered through classes that are no time synchronized. | ||
+ | But we are positively surprised with QT, with it we've managed to get all information we wanted from device, messages, contacts, etc. | ||
+ | |||
+ | During week of studying and coding, we've successfully done all our major tasks within project. | ||
----- | ----- | ||
Line 57: | Line 80: | ||
* NetworkAccessManager + QNetworkReply | * NetworkAccessManager + QNetworkReply | ||
- | http:// | + | * http:// |
- | http:// | + | |
* Receiving Sms | * Receiving Sms | ||
- | http:// | + | * http:// |
- | http:// | + | |