Commit Graph

8 Commits

Author SHA1 Message Date
Nicolas Fella
4169a9f50a Don't pass unused window ids around
The wid is only relevant for the xcb framebuffer

We can just query it there, no need to pass it around everywhere
2022-08-03 22:00:16 +02:00
Alexander Lohnau
fbf4fcbce0 Derive plugin id from filename, clean up json files
We ignore the name/description and only display the id in the ui.
To make sure the is are the same, the OUTPUT_NAME cmake target property is set.
Otherwise, we would need a json file with the KPlugin object and then the id in it, which is
unnecessary work for sth. that can be done in a single line.

Having the file base name and id differ is also discouraged, see https://phabricator.kde.org/T14499
2022-04-23 19:18:18 +00:00
Alexander Lohnau
c7ee6f1e0e Drop empty deconstructors of plugins
We have one defined in the base class, consequently we do not violate the rule of life when removing the empty ones
2022-04-23 19:18:18 +00:00
Alexander Lohnau
0d8cc44ec2 Simplify plugin declaration using K_PLUGIN_CLASS_WITH_JSON
This way we do not need to take care of setting the factory name and typing out the registration manually
2022-04-23 19:18:18 +00:00
Aleix Pol
608762c7ac Allow passing plugin backends some arguments
WId is irrelevant on Wayland and it doesn't fully describe everything we
might be doing, we can pass a variant map to make sure all necessary
information is provided.
2021-10-29 14:05:34 +00:00
Jeremy Whiting
10176b9e01 Port from KServiceTypeTrader, etc. to new json style plugins.
Finish porting away from KDELibs4Support.
Changed preferred framebuffer config to use plugin ids defaulting to x11.
2015-09-16 20:55:30 -06:00
George Goldberg
c74886dfe7 Apply KDELibs code style with astyle to clear up the mess that was there before.
svn path=/trunk/KDE/kdenetwork/krfb/; revision=1189254
2010-10-24 11:21:53 +00:00
George Goldberg
0b04afe5c1 Framebuffers are now plugins. This means we can switch between the Qt and X11 framebuffers at runtime.
- Currently there is no configuration UI, so you have to edit the krfbrc by hand to select the framebuffer plugin to use. This will be fixed later.
- Framebuffers are shared, so that when krfb supports having mutliple servers running, the framebuffer can be shared between them (when appropriate) for better performance.
- Currently defaults to the X11 framebuffer, since this is what was hardcoded before.

svn path=/trunk/KDE/kdenetwork/krfb/; revision=1027330
2009-09-23 20:57:47 +00:00