PeerHood Qt

Qt

• Porting possibilities, especially Symbian S60
• Language mapping via Qt systems, C, Python, Java, ..
• More rich development base for PeerHood services by additional (to C++ standard library) C++ libraries, like Database (eg. sqlite), GUI (of course), XML libraries (for web usage), ..
• GUI for peerhood control and services.
• Common basic functionalities not in C++ standard library: file management, configuration, ..
• GUI Driven Service (middleware) Develoment ?

Goals

• Improve development of the PeerHood for Research (and Industrial) use.
• Give a development framework for PeerHood. C++ needs a framework for development and on Comlab we do not have resources neither motivation to make one. QT might be the best convention framework for C++ (compared to C++std boost extension, symbian, MS C++ foundation, ..).
• Apply Qt conventions: build system, singal-slot system, .. .
• Support UMSIC project, but not limited to it.

Challenges

• Reactor-ThreadPool work applied with Qt main loop and with DBUS main loop.
• Applying Qt for communications service middleware system. For example is Qt too GUI oriented ?

Research goals

• Comparison of Plain C++ PeerHood to Qt PeerHood
  • Easy to maintain
  • In feasibility to create services
  • Easy to learn to use (PeerHood Has been hard ?)
  • Performance
  • ..

UMSIC as main user of PeerHood at the moment

Notes

• As Plain PeerHood and Qt PeerHood are both C++ then maybe not complete rewrite is needed, but code can be move on some parts to new implementation.
• This created dependences to Qt libraries and as well coding usage to Qt. Exposes Qt to UMSIC as well.

• Very much needed

• Logging
• syslog, user log, development (debug) log management. Provided by Qt ?