Tell me what to do with the template tree

Salutation nation

So, first, there was a post: Qube Manager redesign (visual connections between qubes, drag & drop, zooming) (status: mockup)

And then, I have decided that I want something like this, but tty instead of GUI, and templates instead of network.

And now, I have it. For a while, actually.

The problem is that I’m barely a developer, even if you squint hard. Qubes developers are probably busy working on actually useful things, so they aren’t going to react to it in any way any time soon. I want you to tell me what you think before (and if) they get there, so I (or someone else) could improve it.

In addition to everything said on github, now, when I use it, I’ve decided that I also want it (and network tree as well) to show the subtree if VMNAME is provided. Is it a good idea?

1 Like

It is your code, so feel free to do whatever you want with it.

1 Like

Yeah, and I already kind of did, and am looking for advice and / or good ideas. Maybe an inspiration even.

In part, because I don’t like my haphazard UX decision. But also because my integration and code aren’t elegant, and I feel slippery uncertainty about it.

Of course, sooner or later I may come up with something better myself, but even given that I still want to know what people think.

1 Like

The only advice I have is to address any points of frustration, no matter how small, so that by the time you eventually finish development, you have a solution you are willing to consistently use over any other method.