remove these, they're repeats

KodiToAddonFuncTable_Peripheral Class KodiToAddonFuncTable_Peripheral Mouse, light gun, multitouch

game_stream_hw_framebuffer_properties Member game_stream_hw_framebuffer_properties::cache_context : Obsolete? Maybe frontend should just always assume this...

game_stream_hw_framebuffer_properties Member game_stream_hw_framebuffer_properties::bottom_left_origin : Move to GL specific interface

game_stream_hw_framebuffer_properties Member game_stream_hw_framebuffer_properties::stencil : Obsolete.

game_stream_hw_framebuffer_properties Member game_stream_hw_framebuffer_properties::depth : Obsolete

" cleanup this stupid big macro This macro includes now all for add-on's needed functions. This becomes a bigger rework after everything is done on Kodi itself, currently is this way needed to have compatibility with not reworked interfaces.

FIXME: This does not work for addons with multiple extension points! Are there any use for this? TODO: Fix hack in CScreenSaver::Destroy() and deprecate.

The parameter for these should really be on the first not the second property

these two don't allow duration(foo) and also don't allow more than this number of levels...

replace with a single system.platform

The parameter for these should really be on the first not the second property

this doesn't support foo.xml

Page Infolabels and Boolean conditions [docs] Improve the description and create links for functions

[docs] Separate boolean conditions from infolabels

[docs] Order items alphabetically within subsections for a better search experience

[docs] Order subsections alphabetically

[docs] Use links instead of bold values for infolabels/bools so we can use a link to point users when providing help

" remove these, they're repeats

change to IsScanning(Video)

Page Infolabels and Boolean conditions Make this annotate an array of infobools/labels to make it easier to track

move to a future window document.

" Find a better way of finding the art types instead of manually defining them here.

Page Infolabels and Boolean conditions missing reference in GuiInfoManager.cpp making it hard to track.

missing reference in GuiInfoManager.cpp making it hard to track.

description might be outdated

List of all art types

So maybe rather than a row each have one entry for Role.XXXXX with composer, arranger etc. as listed values

Not currently used

some values are hardcoded in the middle of the code - refactor to make it easier to track

get a way of centralize all random art strings used in core so we can point users to them while still making it clear they can have any value.