> On Jul 30, 2018, at 11:09 AM, Eric Blake <[email protected]> wrote: > > On 07/28/2018 08:22 PM, Programmingkid wrote: >> I thought of a way to make qemu-img much more user-friendly. When the user >> opens qemu-img without any arguments, we could present a prompt that guides >> the user on making an image file. >> This illustrates what I think should happen. >> <after user double-clicks on qemu-img...> >> Please select a format (qcow, qcow2, raw, vdi, vhdx, vmdk, vpc, vvfat): >> qcow2 >> Please enter a size (e.g. 100M, 10G): >> 4G >> Please enter a name: >> WinXP.qcow2 >> Creating image file...done >> The interactive prompt would contain enough options to make a usable image >> file. If the user wants to use some of the more advanced features of >> qemu-img he or she would still need to use the command-line. >> Would such a patch be welcomed? > > qemu-img is a command line tool, not a gui. Bloating it with a gui dialog > box is probably not a wise idea. There would be no gui dialog box. Qemu-img would still be a command-line tool. The patch would be done in printf/scanf calls.
> Personally, I'm just fine with the current command line behavior: > > $ qemu-img > qemu-img: Not enough arguments > Try 'qemu-img --help' for more information > > as 'qemu-img --help' tells you how to properly use the command, without > having to hand-hold you through the process. Hand holding feels way better than the coldness of the --help option.
