KDE Games/Porting

From KDE Community Wiki
Revision as of 11:09, 12 August 2010 by Majewsky (talk | contribs) (Created page with '== Targets of porting == * '''Rendering stack:''' Current solutions commonly include usage of a QSvgRenderer, possibly combined either with QGraphicsSvgItems or with (Q/K)Pixmap...')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Targets of porting

  • Rendering stack: Current solutions commonly include usage of a QSvgRenderer, possibly combined either with QGraphicsSvgItems or with (Q/K)PixmapCache. It is suggested to migrate to KGameRenderer instead. Integration with QGraphicsView is available through the KGameRenderedItem and KGameRenderedObjectItem classes. Integration with KGameCanvas is available through the KGameCanvasRenderedPixmap.
  • (more to come)

Porting status

The second column shows which graphics stack (e. g. QGraphicsView, KGameCanvas) is used by the application. The third column shows the rendering stack.

TODO: complete and prettify table

Application Graphics stack Rendering stack Who does/did the port?
bomber KGameCanvas KGameRenderer Stefan Majewsky
bovo
granatier
kajongg
kapman
katomic QGraphicsView KGameRenderer Brian S. Croom
kbattleship
kblackbox
kblocks
kbounce
kbreakout
kdiamond QGraphicsView KGameRenderer Stefan Majewsky
kfourinline
kgoldrunner
kigo
killbots
kiriki
kjumpingcube
klines
kmahjongg
kmines
knetwalk
kolf
kollision
konquest
kpat
kreversi QGraphicsView KGameRenderer Brian S. Croom
ksame QGraphicsView KGameRenderer Stefan Majewsky
kshisen
ksirk
kspaceduel
ksquares
ksudoku
ktron
ktuberling
kubrick
lskat
palapeli QGraphicsView N/A N/A