... ...however the gui is full of buttons that don't have any text labels,
So??? you may say, just add the text labels. Well every additional text label and it's translation into every language qbittorrent supports have to be embedded into the application and the relevant language string has to be in memory when the application is running, eating resources and adding to the 'footprint', and the 'small footprint' is the one thing that qbittorrent is 'sold' to users with.
I am attempting to highlight the 'knock on' effects of adding extra 'features' that may appear at first to be insignificant but do have detrimental effects when deployed fully. The aim of qbittorrent is a small running footprint of minimal resources being used that means that some unnecessary 'features' are going to be left out.
[quote="ciaobaby"]
I am attempting to highlight the 'knock on' effects of adding extra 'features' that may appear at first to be insignificant but do have detrimental effects when deployed fully. The aim of qbittorrent is a small running footprint of minimal resources being used that means that some unnecessary 'features' are going to be left out.
[/quote]
I have seen minimal resources programs have a pretty cool looking theme... I don't get it, I am fine with the one we have now, doesn't bother me but.. I still don't get the point.
nobody is asking to remove text and just put icons, they are asking for renewed icons from what I seen, don't know how that blind guy would have programs with that.
Okay, you are looking at it from the point of view of an average user who is in possession of all the usual faculties associated with human beings generally.
Now, if you are a 'developer' of applications or software tools that are intended for use by the 'general public' who may have various 'issues' as the Americans like to call it, there is a legal obligation in most if not all, parts of the world to ensure that your user interface is usable and accessible by people with 'disabilities'. most people "assume" that these standards apply to "website access only" but it does cover all manner of computer software, and even "Open Source" developers have to comply with these regulations. So in order to comply, every 'visual' item requires an alternative method for 'visually impaired' users in the form of a textual prompt which can be read aloud by 'helper' applications, such as 'screen readers' or operating system accessibility functions, there should also be a keyboard alternative for every operation for people who may be unable to use a mouse.
So each time someone asks for some additional GUI element, button, column etc. there should be at least two more elements added, and one object has suddenly become three that have to be loaded and events to be monitored whenever the interface is active.
It soon mounts up.