Planning merging the single qqml engine

[David Edmundson]

On Mon, May 18, 2015 at 8:28 PM, Marco Martin <notmart at gmail.com> wrote:

> Hi all,
>
> I think the branches for the single shared qqmlengine are pretty much ready
> (few cleanups upcoming days), seems pretty stable here.. did someone ran
> the
> branch for a while as well?
>
> In the end i managed to get a single engine for the whole session, views
> included (had to duplicate the View class in plasmaquick and kept the old
> one
> as deprecated for retrocompatibility unfortunately)
>
> the memory save seems pretty good, i *hope* stability improved as well :p
>
> what still uses separed engines are the applet configuration dialogs: this
> is
> necessary because they are supposed to use a different style for the
> qquickcontrols, and being the settings object that decides the style a qml
> singleton (qml singletons are unique by engine), the engine has to be
> different from the desktop/panel. The good thing is that config dialogs are
> instantiated relatively rarely, in most sessions not at all, so shouldn't
> touch too much a "normal run"
>
> For retrocompatibility the applets unfortunately have to specify explicitly
> they can share the engine in their metadata file (or eventual
> plasmapackage:/
> urls break)
>
> at the moment it's using
> X-Plasma-RequiredExtensions=SharedEngine
>
> but I'm leaning more on the direction of something like
> X-Plasma-MinimumAPIVersion=5.11
>
> I would like to have all set before frameworks 5.11
>
> One thing you and I talked about once was having the shell have a hook in
p-f to call a static method setting what version of plasma-framework it was
expecting.
Would that be a suitable solution here?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20150519/415194e2/attachment-0001.html>