The source code of a project appears to the original developer that the process is clearer, and if the original developer writes some documentation on how to read the source, it will inevitably be overlooked (because there are some things that seem natural to him that seem strange to the reader's first contact), Of course, want to least bit to express the whole project source code interpretation process, also inseparable from him. So this post I will be a first contact KBE Project Reader identity, will read the process and experience to share with you. If you find something wrong, please email[email protected]。 ;-)
* * Recently there are Jiang Yun children's shoes in KBE QQ group to share a server-side various architecture documents, against these architectures to read KBE will be more beneficial, this document I moved: Baidu Cloud Portal * *
kbengine activity Diagram (Visio UML activity diagram):
<ignore_js_op>
Changelog
v0.0.1: (Baidu Cloud Portal)
* Increase the backbone activity diagram of the service side
v0.0.2: (Baidu Cloud Portal)
* Add Ogre Demo's skeleton activity diagram (complete to Spaceavatarselect)
v0.0.3: (Baidu Cloud Portal)
* Add Loginapp activity diagram (Basic completion)
* Add Dbmgr activity diagram (complete to login interaction)
* Add Baseappmgr activity diagram (complete to login interaction)
kbengine Source code read (Word Code implementation parsing):
Changelog
v0.0.1: (Baidu Cloud Portal)
* Add the service side of the process interpretation
v0.0.2: (Baidu Cloud Portal)
* Fixed some typos
* Explanation of adding message processing mappings
* Added a title for word navigation
v0.0.3: (Baidu Cloud Portal)
* Added Ogre client's process interpretation (completed to Spaceavatarselect)
v0.0.4: (Baidu Cloud Portal)
* Add non-fixed messages (not in message_fixed.xml) and the establishment of processing mappings
* Add a single case interpretation
v0.0.5:
* Add Dbmgr Interpretation
Kbengine Source code Reading