Projects/KGLEngine2D: Difference between revisions
< Projects
(Created a project page for KGLEngine2D) |
No edit summary |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
[[Image:Kglengine-logo.png]] | [[Image:Kglengine-logo.png]] | ||
== About KGLEngine2D == | == About KGLEngine2D == | ||
| Line 7: | Line 8: | ||
* Games being developed with KGLEngine2D: KTank, Katerpillar | * Games being developed with KGLEngine2D: KTank, Katerpillar | ||
* IRC Channel: #kglengine on Freenode | * IRC Channel: #kglengine on Freenode | ||
* Tutorial: http://techbase.kde.org/Development/Tutorials/Games/KGLEngine2d | |||
=== Ideas, Todos, etc === | === Ideas, Todos, etc === | ||
* Some stuff in the svn really | * Some stuff in the svn really doesn't belong in a lib and should be moved somewhere. This includes all the examples(some may become games of their own, but simple examples may still be needed, and all of them aren't games) and the KGLIntro class. | ||
* KGLEngine currently uses a lot of inlines functions, this makes keeping binary compatibility harder(see [[Policies/Library_Code_Policy#Inline_Code]]), we should run tests to see if having these functions not inlined really impact performances to know what we don't need to inline. | * KGLEngine currently uses a lot of inlines functions, this makes keeping binary compatibility harder(see [[Policies/Library_Code_Policy#Inline_Code]]), we should run tests to see if having these functions not inlined really impact performances to know what we don't need to inline. | ||
* KGLEngine should use d-pointers | * KGLEngine should use d-pointers | ||
| Line 15: | Line 17: | ||
* KGameKey should probably be moved in KDEGames lib | * KGameKey should probably be moved in KDEGames lib | ||
* Should GLPoint be renamed into KGLPoint? | * Should GLPoint be renamed into KGLPoint? | ||
* Should KGLItemBase be renamed into KGLBaseItem or KGLAbstractItem? Is this class relevent at all? | |||
* Engines subclasses should be notified when one of their items is removed (is overloading removeItem/eraseItem a good idea?) | * Engines subclasses should be notified when one of their items is removed (is overloading removeItem/eraseItem a good idea?) | ||
* QPixmap vs QImage | |||
Latest revision as of 18:35, 15 July 2012
About KGLEngine2D
KGLEngine2D is a 2D engine for KDE, especially designed for games creation (it should become a part of KDEGames in the future)
Development
General informations
- SVN: http://websvn.kde.org/trunk/playground/games/KGLEngineRefactoring/
- Games being developed with KGLEngine2D: KTank, Katerpillar
- IRC Channel: #kglengine on Freenode
- Tutorial: http://techbase.kde.org/Development/Tutorials/Games/KGLEngine2d
Ideas, Todos, etc
- Some stuff in the svn really doesn't belong in a lib and should be moved somewhere. This includes all the examples(some may become games of their own, but simple examples may still be needed, and all of them aren't games) and the KGLIntro class.
- KGLEngine currently uses a lot of inlines functions, this makes keeping binary compatibility harder(see Policies/Library_Code_Policy#Inline_Code), we should run tests to see if having these functions not inlined really impact performances to know what we don't need to inline.
- KGLEngine should use d-pointers
- Idea from it-s(Eugene Trounev): use KGLEngine to make KDE screensavers. Is this possible/relevant?
- KGLEngine Plasmoids --> possible/relevant?
- KGameKey should probably be moved in KDEGames lib
- Should GLPoint be renamed into KGLPoint?
- Should KGLItemBase be renamed into KGLBaseItem or KGLAbstractItem? Is this class relevent at all?
- Engines subclasses should be notified when one of their items is removed (is overloading removeItem/eraseItem a good idea?)
- QPixmap vs QImage