Logic behind functionality implementation in Qt framework
I have a device that can't make use of Qt framework and I need to implement some stuff that Qt has already implemented.
I know that Qt is opensource and I can look into code and reverse engineer it into something that I want. But the problem is that Qt is big and covers a lot of concepts. For instance QScroller base implementation is quite simple: one calculates velocity of mouse and then calculates kinetic energy to get scroller stopping position but screen size, smoothing, easing, overshooting calculations and abstraction layers make it really difficult to understand that code :).
And here I am wondering is there some blog or documentation on how Qt implements stuff?
For the lower level details, you should rather ask on the interest mailing list or the #qt irc channel. You'll find there Qt's developers/maintainers. This forum is more user oriented.
Out of curiosity, why can't you make use of Qt on that device ?
In that case, shouldn't you rather use something like ugfx rather than re-write your own graphic stack ?
@SGaist Actually graphic stack is already written from scratch. I was just asked to investigate how Qt integrates stuff like multi touch gestures, kinetic scrolling some graphics processing so we could integrate it in our graphic stack.