On Thursday, 7 December 2017 00:14:04 UTC+8, Tom Zander wrote: > On Wednesday, 6 December 2017 16:08:28 CET Unman wrote:
> > "useful, but wasnt any good" - do you mean buggy or poorly designed? > > What 2 features should be implemented/fixed? > > > > I confess I rarely use the Manager, so don't have a feel for what's wrong > > with it. > > To be clear, the main reason the old one is removed seems to be that it > would have had to be reimplemented due to the architecture changes in 4.0 I had a script that updated the templatevms and it was written in Python, taking advantage of the API. This script stopped working in 4.0. I rewrote it to use the commandline tools instead. Perhaps a new UI could also be based on those tools. Without a need to use Python, such UI could be implemented in any language. That would be an interesting project. > To support the point of view of "useful but wasn't any good", let me explain > what I think such a tool should behave like. I was the one who said that, and your statement is an almost spot-on summary of my opinion. > The first issue with the old tool, and also with some of the new tools, are > that you already have to know how things work in order to be able to use it. > For instance the terminology 'appvm', 'templatevm' etc are completely not > explained anywhere. You have to go to a website to learn what the mean. The 3.2 VM manager, with all is faults, did help newcomers a single place to see what was going on. It's not harder in 4.0, but I'd imagine that to a newcomer it would look a lot more opaque. This, I believe, is the most important feature of a new UI; the ability to guide a new user to the proper usage of the OS. > A clear success story of Qubes is its networking, abstracting the netVm is > done to add security without having any significant impact on usability. > Practically speaking, normal users can ignore the whole networking setup as > it "just works". For a new UI, I imagine a graphical representation of the networking setup. Think boxes with arrows, showing connections, ports, IP-addresses, etc. In fact, hardware assignments could be represented there as well. Do a Google image search for "flow control ui" to see what I'm thinking of. > * Which VMs are in which state. If you start something and the netvm/ > firewall VM are auto-started, this is not at all clear to the user. If > something fails, it gets even worse. Easy access to the logs from here would be a most welcome quality-of-life improvement. > * Graphical configuration of multiple qubes. Even in 3.2 not being able to > open more than one config dialog at a time was silly. Yes. The fact that the old VM manager was blocking, and you couldn't do anything with it while an operation was in progress was one of its biggest flaws. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/73f4d6f6-6595-4c31-af4c-a5d6b4631608%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
