On Friday 08 May 2015 20:16:49 Hausmann Simon wrote: > Nice - as a plasma user I'm looking forward to the lower memory usage :) > > Regarding the url interceptor: > > Could you make the feature optional? An applet that needs absolute > package:// urls would have to continue to create it's own engine. But using > a new constructor perhaps you could introduce new behavior that requires > the use of relative urls simply, so that you have to resolve the root item > url only once manually in the framework?
that may be done, and would make most of the stuff work. however it would still lose some features, besides the package:/ url scheme. one thing is that it forbids loading qml files that are within other applets paths, to be sure applets authors don't get ideas :p an important thing is some fallbacks of files that package class does: for the use in devices, the applets can have device specific qml files, so, trying to open stuff.qml, contents/ui/stuff.qml if the system is configured to be a tablet, would chose instead platformcontents/tablet/ui/stuff.qml and fallback to contents/ui/stuff.qml if not existent we are probably need this a bit more in the future, so I would really love to find a way to not lose it but i can't think about other ways to tap into it since only ways i can think of is to ave more context in the interceptor which i don't have or be able to intercept somehow QQmlContextData::resolvedUrl() (eh, too bad isn't a virtual :p) -- Marco Martin _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
