!rGlCMuXgAhgEpdvJUz:nixos.org

NixOS KDE

135 Members
44 Servers

Load older messages


SenderMessageTime
5 Sep 2024
@outfoxxed:outfoxxed.meoutfoxxedwhat if we cache bare store qml only if its part of the same package as the application08:01:46
@outfoxxed:outfoxxed.meoutfoxxedwhich should be true in most cases08:01:54
@k900:0upti.meK900It doesn't seem to be?08:02:03
@k900:0upti.meK900Like looking at the list08:02:07
@k900:0upti.meK900Most of those are libraires08:02:09
@outfoxxed:outfoxxed.meoutfoxxedit will be wrong for some08:02:09
@k900:0upti.meK900* Most of those are libraries08:02:11
@outfoxxed:outfoxxed.meoutfoxxedyeah08:02:13
@outfoxxed:outfoxxed.meoutfoxxedis plasma-workspace a library?08:02:24
@k900:0upti.meK900Yes08:02:30
@outfoxxed:outfoxxed.meoutfoxxedalso consider08:02:36
@outfoxxed:outfoxxed.meoutfoxxedwait08:02:42
@outfoxxed:outfoxxed.meoutfoxxedi think ive got it08:02:45
@outfoxxed:outfoxxed.meoutfoxxedjust the presence of bare qml doesn't necessarily signify that there isn't any aot08:03:08
@outfoxxed:outfoxxed.meoutfoxxedwhen exporting qml modules it includes the bare qml in addition08:03:18
@outfoxxed:outfoxxed.meoutfoxxedyou'll have to actually check the build scripts to see how its included08:03:31
@k900:0upti.meK900Hm08:03:40
@k900:0upti.meK900Yeah I think that might be it08:03:48
@k900:0upti.meK900But then I wonder when we'd end up using those08:03:56
@outfoxxed:outfoxxed.meoutfoxxedwhen everything else somehow fails i think08:04:07
@outfoxxed:outfoxxed.meoutfoxxedlemme find the docs08:04:11
@outfoxxed:outfoxxed.meoutfoxxedhttps://doc.qt.io/qt-6/qt-add-qml-module.html#caching-compiled-qml-sources08:05:32
@outfoxxed:outfoxxed.meoutfoxxed

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:outfoxxed.meoutfoxxed *

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:outfoxxed.meoutfoxxedthis might be whats happening08:06:05
@k900:0upti.meK900Certain situations my ass08:06:11
@k900:0upti.meK900Very helpful08:06:15
@outfoxxed:outfoxxed.meoutfoxxedit sounds like the resource path only, but when I compiled a module from my own application it copied the source as well08:06:35
@outfoxxed:outfoxxed.meoutfoxxed * it sounds like the resource path only, but when I compiled a module from my own application it copied the source to the module dir as well08:06:43
@k900:0upti.meK900Here's a crazy idea08:07:27

Show newer messages


Back to Room ListRoom Version: 9