DJSTU said:
Normally I try my best to be complementary of your efforts to make improvements to RB (which are usually pretty good). But sometimes when people are putting forward suggestions/improvements, your response is instead making me irritated. And today is one of those days.
I think the problem here is that a short forum reply does not really show some important internal processes. Most suggestions, even if not immediately accepted (or implemented) still go to the internal bug tracker for later consideration; later they are being compared to other similar suggestions and our own view on how the product should develop. So nothing is dropped if I say "we won't implement this now".
DJSTU said:
Consumers are the ones that drive changes and should be listened to.
This is how it always was and will always be here. There are many new features added each version and most of them were asked before by csustomers. Like something is asked during RB 5.6 beta and the feature is added in 5.7 or 5.8. There are bad examples as well, when requested feature was added after 7 years. But this is an exception
and most of the time it is much faster.
DJSTU said:
a classic example of a bad software change was when Winamp tried to bring in their Ver 3
Yes, this is a good example of how changing the UI goes wrong, and that's why rearranging settings window in RadioBOSS could become such a bad example as well.
Yes, there are some settings that are accessed more frequently than others, but that also depends on the user's situation... RadioBOSS settings window is not really complicated, and it doesn't (yet) require complete overhaul (while some minor improvements could be made and anyone is welcome to suggest those). I suggest you to take a look at the options window from Visual Studio to compare (attached).
DJSTU said:
For me your Options layout is a nightmare to work through. Things are all over the show. Its like bits have been added in, and ohhh where will we put it, ohh lets just plonk it in here, because there is a gap.
This is not far from the truth, actually. The "Fading" section is the extreme case of this.
If you think that some changes should be made, now is a good time to state those - some of them might be implemented right in this beta, or be moved to the future releases.
DJSTU said:
You should instead of just saying to Basti that his graphics "look nice", instead you should be asking for others opinions on his layout, what do you lot think of his suggestions ?, and then considering those replies and making changes as a result.
This is implied, and anyone is free to comment on proposed changes, or offer something else.
DJSTU said:
Your HELP should be online and in one place only. Having help in the software these days is old hat and yesteryear. If you had it online, you would only need to make one change, in one place, and quickly, without it being such a laborious task under your present system.
I think I was misunderstood, the manual was mentioned to show that renaming some option is not as simple as might seem - and its should be done where it's justified.
The online help available as well: https://www.djsoft.net/enu/support.htm
And, of course, internally it has one base source from where all help formats are built.
DJSTU said:
There must be a much better system for translations. Surely ? Consumer driven. A place where nominated members can log on and can go and actually do the translations for you immediately, you then pick it up and make the change straight away in RB and in Help. You seem to have a laborious process for these language changes which could be improved, saving you a task which you don't seem to like doing ?
It's automated for the most part. Regardless of how the translation is made, if some option is renamed, it will require for the translation maintainer to update the translation - and this is one more reason to avoid renaming unless it really brings value.