Planning merging the single qqml engine

[Mark Gaiser]

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

> On Monday 18 May 2015, Mark Gaiser wrote:
> > Anyway, with that attribute you let the applet developer OPT-IN in for
> > shared engine. Setting that attribute can be easily forgotten. If
> anything,
> > they should OPT-OUT thus by default use the shared engine.
> > Perhaps a attribute like this is more appropriate?:
> > X-Plasma-RequiresOwnQmlEngine=true
> >
> > or something alike.
> >
> > I'd definitely go for OPT-OUT (defaults = use shared engine).
>
> no, because the key here is retrocompatibility, old applets have to work as
> is.
> it's true that this makes it error prone, but that's the ugly need :/
> otherwise there wouldn't be any reason for supporting both modes


While that - on it's own - is a very nice goal, sometimes you just have new
developments that are clearly better and the way forward. This is one such
case. Sure, you want to keep compatibility, but you should also strongly
motivate those that develop applets to use the shared engine.

Ivan's idea of deprecating it and clearly letting the user know might be a
good compromise here. The ironic thing here is that something would have to
be introduced that will be deprecated from the beginning. Something sounds
wrong about that :)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20150518/78a8d663/attachment.html>