|
|
| (One intermediate revision by one other user not shown) |
| Line 1: |
Line 1: |
| Plugins can be implemented around marble.
| | {{ Moved To Community }} |
| | |
| The interface for plugins relies on the {{class|PluginInterface|kdeedu|4.x}} base class.
| |
| All plugins will have their lifecycle managed by the {{class|PluginManager|kdeedu|4.x}}.
| |
| | |
| They will thereafter be managed by another class handling them.
| |
| | |
| There are different categories such as:
| |
| | |
| == Network Plugins ==
| |
| They inherit from {{class|NetworkPluginInterface|kdeedu|4.x}}
| |
| They are manipulated by an {{class|HttpDownloadManager|kdeedu|4.x}}
| |
| | |
| == Position Provider Plugins ==
| |
| They inherit from {{class|PositionProviderPluginInterface|kdeedu|4.x}}
| |
| They are manipulated by the {{class|PositionTracking|kdeedu|4.x}} for now, and a new manager that tracks the history of positions should be implemented to replace the old gps layer.
| |
| | |
| == Render Plugins ==
| |
| They inherit from {{class|RenderPluginInterface|kdeedu|4.x}}
| |
Latest revision as of 04:47, 26 October 2016
