Thankyou for your criticisms.zigbert wrote:mcewanw
You're doing great development here. Thanks a lot.
I have some suggestions:
1. I personally think that using <combobox> instead of <radiobuttons> for quality and bitrate would simplify the advanced gui.
2. Could you please include tooltips for every button. There is a lot of options I don't know which to pick. abr, cbr or vbr ???? card or device ??? ogg_mm or ogg_q ???? quality N1 ????? quality 00 ????
3. 'date stamped file' now includes a lot of gui. It could be that I'm not getting this right, but wouldn't it be easy to have an option/menu to choose the layout of output filename. User could add her/his default prefix.
4. The advanced gui contains 2 'Quit' buttons ????
5. The <entry> for seconds could be shrunk in width to keep gui clean.
. . .
6. If wanted, it is possible to skip button decoration for some buttons with <button relief="2">
. . .
7. I don't see the point of having 2 pause/stop buttons. I think it could be solved easily with combining some functions:
Code: Select all
. . . [snippits extracted from the structured precord GPLv3 code, as re-arranged and published by Signmund (mcewanw)]
Sigmund
Personally I prefer radio buttons to combobox for this application. It is a matter of taste in application design I suppose, so the idea of changing that... egentlig, önsker jeg ikke ä gjöre det... [I've no idea what a google translate will make of that and I couldn't find the symbol for stroke through the 'o', so used umlaut]
I purposively included separate pause and stop controls for Record and Play, after some earlier consideration, because these are two separate functions which I occasionally use separately. I can play a track (listening via headphones) whilst recording something different. I can also play, for example [EDIT] a music-only audio file, and record a voice track whilst it is playing (via mixer). I also use the separate functions when running or controlling precord from the commandline.
Actually, I wish everyone would endeavour to make their gtkdialog/bash apps also runnable from the commandline to at least some extent: that facility automatically provides accessibility (to a visually impaired user for example), and also fits in with UNIX philosophy in terms of allowing programs to be more easily chained together. Of course, you need to re-think your GUI designs to purposively incorporate commandline driving capability, when you want that; admittedly that is one of my interests (and when it comes to GUI's, I'm a one-click radiobox man, by preference, to some extent!)
But, I'm not asking others to write their apps differently; they put the effort into writing them afterall... (though occasionally I might request new features, if they have time and are willing to incorporate them...:-).
I had planned to reduce the duration seconds box, but forgot about it. Thanks for reminding me! :-)