MobileRead Forums - View Single Post

davidfor · 12-29-2018, 08:30 PM

@FrustratedReader: DNSB answered most of my issues. But...

Personally, I don't think I was getting defensive. Or at least not very. But, you definitely were. You decided to install software without actually looking at what it did. You made assumptions about it that I cannot work out the basis for. And the fact that you have been a developer for over 30 years makes that almost a criminal act. Now, when I called you one this, you are attacking the developers of that software saying it is their fault. And, as I am one of those developers, I take that personally. Your lack of knowledge of MR is not a good excuse. As DNSB said, just about any search of these things will lead you hear. And the calibre help page explicitly points to MR as the place to "ask any question".

And just to be clear, the reason I rejected the change for the "Modify CSS" option is because it isn't better. The option as is, describes what is to be done (modify the CSS in a book when it is being uploaded). The tooltip gives some basic details of how this is done. If that is not enough, then you need to find help for this function. And searching the web would lead you here. Your suggestion doesn't give a clue as to what is being done. I will look revisit the options under my control. At the time that most of these were created, the configuration dialog was clumsy and hard to change. I rewrote that a while ago, but didn't change many of the option names or tooltips.

And also to be clear, as another developer with over 30 years experience, I am completely aware of developers blindness with respect to these things. I beg for people to tell me what is wrong with the documentation, the options, my posts or anything else. But, it is rare that someone says anything.

The other issue with all this is that you didn't do anything to help debug this problem. You reported a problem and gave some details of how you thought it it could be reproduced. But, that didn't work for anyone else. I remember trying and couldn't reproduce it. When you were asked a screenshot or a test file, you didn't produce anything. If you had posted a screenshot, about 30 seconds later, someone would have told you what the problem was. Or at least asked a question that would have lead to it. If you had posted a test file, or even code snippets, it would have taken 30 minutes for the same result.

12-29-2018, 08:30 PM	#42
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	@FrustratedReader: DNSB answered most of my issues. But... Personally, I don't think I was getting defensive. Or at least not very. But, you definitely were. You decided to install software without actually looking at what it did. You made assumptions about it that I cannot work out the basis for. And the fact that you have been a developer for over 30 years makes that almost a criminal act. Now, when I called you one this, you are attacking the developers of that software saying it is their fault. And, as I am one of those developers, I take that personally. Your lack of knowledge of MR is not a good excuse. As DNSB said, just about any search of these things will lead you hear. And the calibre help page explicitly points to MR as the place to "ask any question". And just to be clear, the reason I rejected the change for the "Modify CSS" option is because it isn't better. The option as is, describes what is to be done (modify the CSS in a book when it is being uploaded). The tooltip gives some basic details of how this is done. If that is not enough, then you need to find help for this function. And searching the web would lead you here. Your suggestion doesn't give a clue as to what is being done. I will look revisit the options under my control. At the time that most of these were created, the configuration dialog was clumsy and hard to change. I rewrote that a while ago, but didn't change many of the option names or tooltips. And also to be clear, as another developer with over 30 years experience, I am completely aware of developers blindness with respect to these things. I beg for people to tell me what is wrong with the documentation, the options, my posts or anything else. But, it is rare that someone says anything. The other issue with all this is that you didn't do anything to help debug this problem. You reported a problem and gave some details of how you thought it it could be reproduced. But, that didn't work for anyone else. I remember trying and couldn't reproduce it. When you were asked a screenshot or a test file, you didn't produce anything. If you had posted a screenshot, about 30 seconds later, someone would have told you what the problem was. Or at least asked a question that would have lead to it. If you had posted a test file, or even code snippets, it would have taken 30 minutes for the same result.