Plasma/libplasma2/modellikedataengines: Difference between revisions

From KDE Community Wiki
Line 20: Line 20:
{{FeatureProjectTodo|filebrowser||[email protected]}}
{{FeatureProjectTodo|filebrowser||[email protected]}}
{{FeatureProjectTodo|notifications||[email protected]}}
{{FeatureProjectTodo|notifications||[email protected]}}
{{FeatureProjectTodo|rss||[email protected]}}
{{FeatureProjectTodo|rss|Needs porting to KF5 first|[email protected]}}
{{FeatureProjectTodo|statusnotifieritem||[email protected]}}
{{FeatureProjectTodo|statusnotifieritem||[email protected]}}
{{FeatureProjectTodo|microblog||[email protected]}}
{{FeatureProjectTodo|microblog||[email protected]}}


|}
|}

Revision as of 16:45, 2 January 2014

Discussion

Many dataengines return data as series of items: like rss, microblog and tasks, and they do in different ways, rss has a list of Data in a single key, microblog has an item per key, tasks has an item per source.

Proposed Solution

In Plasma2 dataengine has a setModel method, that can associate a QAbstractItemModel instance to a Source.

Dataengines to port

Status Engine Comments Developer
DONE places <[email protected]>
TODO tasks use tasks model from libtaskmanager <[email protected]>
TODO activities either just use the import or the same model <[email protected]>
TODO applicationjobs <[email protected]>
TODO apps <[email protected]>
TODO filebrowser <[email protected]>
TODO notifications <[email protected]>
TODO rss Needs porting to KF5 first <[email protected]>
TODO statusnotifieritem <[email protected]>
TODO microblog <[email protected]>