Ordered by Topic about gammalauncher HOT 2 OPEN

Hey there, thanks for these and sorry for the late reply :-)

I'm trying to figure out how this could look like and came up with this dummy patch. It's just a rough sketch that gives an idea of how this would eventually look like (wordings and all tbd). The (long) text descriptions are also there to help me reason about this, in the end they should end up in a tooltip.

A few questions though :

• What would the "Package compiler" checkbox do in the Advanced section? How does it play with the Source package directories and Editable packages tabs?
• Could you give more details on the Package compiler may cache option?
• I wonder if we should not keep the editor extensions setting as a negative thing that you have to explicitly enable. This setting could be dangerous : if we use the positive checked by default as you suggested (just Editor Extensions), someone could disable it and forget it, and then wonder why no extensions are working. Whereas if you keep it negative, and need to user to actually click it, it makes it more intentional and "memorable".

Let me know what you think!

Cheers

PS : change the extension of this to .vl, github goes brrrr with those
LauncherProto.txt

from gammalauncher.

Hey! Thanks a lot!

• If you disable the package compiler all packages (even the CoreLib, even if not listed in source package repositories nor in editable packages..) will get compiled from source. This can make sense if you have a last minute issue in your project and just don't have the time and nerve to do it properly by checking the source repository of VLStandardLibs or any other repo. So this is only used for real dirty hacking the vvvv installation or Nuget package folder or for trying to help us track down a bug real quick. It's not something that you typically do. That's why it's advanced.

• Package compiler may cache is only for debugging caching issues of the package compiler itself. I don't know of any reason to turn that off currently.

• Regarding on/off: It's super tricky. I was just trying to get rid of all negations, but this way you end up with a lot of options ticked by default. Package Compiler (may cache) would both be on by default. The story would be: pretty much everthing is enabled by default. But for debugging purposes you want to simplify the system. Even "Debuggable target code" could get negated and be called "Dense target code" (with a tooltip saying that you typically want to disable it in order to be able to read the target code). This way everything under Advanced would be turned on.

• We could even discuss Mute as being a negation. That way you would end up with a ticked checkbox when adding an item saying: it's enabled. As a library dev with many libraries entered in the editable packages I often only want to enable the one that I am currently working on in order to have decent startup time. So I would need to mute everything else. Also we'd need to explain that muting in the editable packages means something different than muting in the package directories even though both is called mute.

• One thing that came to my mind: since editable packages allows you to use * like so VL.Stride* it could make sense that the main control still is a textinput, but with a button allowing to seclect a folder. This would then just copy the folder name into the textbox still allowing you to edit it.

Completely open in all directions. That was just my train of thought.
Thanks again!

PS: I think it would be cool to also have the Nuget Package folder somewhere and show buttons for all folder related inputs opening an explorer window. In case you forgot those.

from gammalauncher.