1,079
edits
Difference between revisions of "User:Seldon/GSoC2007-ProjectDiary"
User:Seldon/GSoC2007-ProjectDiary (view source)
Revision as of 20:54, 4 July 2007
, 20:54, 4 July 2007→2007-07-03 (Tuesday) - current backend arhitecture: typo in the headline (sorry for messing with your personal page, but it just hurt my eyes too much ;)
m (→2007-07-03 (Tuesday) - current backend arhitecture: typo in the headline (sorry for messing with your personal page, but it just hurt my eyes too much ;)) |
|||
| Line 14: | Line 14: | ||
* study the new idea of events to replace engine specific keymapping code in the backends ( [Scummvm-devel] RFC: Flexible keymapping via new EVENT_ (post 0.10) by Max) | * study the new idea of events to replace engine specific keymapping code in the backends ( [Scummvm-devel] RFC: Flexible keymapping via new EVENT_ (post 0.10) by Max) | ||
== 2007-07-03 (Tuesday) - current backend | == 2007-07-03 (Tuesday) - current backend architecture == | ||
Yesterday and today I went through all backend implementations (classes that extend OSystem). I gathered the information about all methods in OSystem class hierarchy and presented it the form of tables. There one can easily see all of the OSystem virtual functions, their overriding counterparts in backend implementations, as well backend specific functions. Based on this information it is easy to see what are the common methods for all backends, which of them are simply duplicated, etc. | Yesterday and today I went through all backend implementations (classes that extend OSystem). I gathered the information about all methods in OSystem class hierarchy and presented it the form of tables. There one can easily see all of the OSystem virtual functions, their overriding counterparts in backend implementations, as well backend specific functions. Based on this information it is easy to see what are the common methods for all backends, which of them are simply duplicated, etc. | ||