5 Sep 2024 |
K900 | Some are pure JS kwin plugins, so no qrc | 08:01:11 |
outfoxxed | ok heres an idea | 08:01:24 |
outfoxxed | what if we cache bare store qml only if its part of the same package as the application | 08:01:46 |
outfoxxed | which should be true in most cases | 08:01:54 |
K900 | It doesn't seem to be? | 08:02:03 |
K900 | Like looking at the list | 08:02:07 |
K900 | Most of those are libraires | 08:02:09 |
outfoxxed | it will be wrong for some | 08:02:09 |
K900 | * Most of those are libraries | 08:02:11 |
outfoxxed | yeah | 08:02:13 |
outfoxxed | is plasma-workspace a library? | 08:02:24 |
K900 | Yes | 08:02:30 |
outfoxxed | also consider | 08:02:36 |
outfoxxed | wait | 08:02:42 |
outfoxxed | i think ive got it | 08:02:45 |
outfoxxed | just the presence of bare qml doesn't necessarily signify that there isn't any aot | 08:03:08 |
outfoxxed | when exporting qml modules it includes the bare qml in addition | 08:03:18 |
outfoxxed | you'll have to actually check the build scripts to see how its included | 08:03:31 |
K900 | Hm | 08:03:40 |
K900 | Yeah I think that might be it | 08:03:48 |
K900 | But then I wonder when we'd end up using those | 08:03:56 |
outfoxxed | when everything else somehow fails i think | 08:04:07 |
outfoxxed | lemme find the docs | 08:04:11 |
outfoxxed | https://doc.qt.io/qt-6/qt-add-qml-module.html#caching-compiled-qml-sources | 08:05:32 |
outfoxxed |
All .qml, .js, and .mjs files added to the module via the QML_FILES argument will be compiled to bytecode and cached directly in the backing target. This improves load-time performance of the module. The original uncompiled files are also stored in the backing target's resources, as these may still be needed in certain situations by the QML engine.
| 08:05:42 |
outfoxxed | *
All .qml, .js, and .mjs files added to the module via the QML_FILES argument will be compiled to bytecode and cached directly in the backing target. This improves load-time performance of the module. The original uncompiled files are also stored in the backing target's resources, as these may still be needed in certain situations by the QML engine.
| 08:05:48 |
outfoxxed | this might be whats happening | 08:06:05 |
K900 | Certain situations my ass | 08:06:11 |
K900 | Very helpful | 08:06:15 |
outfoxxed | it sounds like the resource path only, but when I compiled a module from my own application it copied the source as well | 08:06:35 |