Quote:
Originally Posted by EowynCarter
This WILL change the way calibre works for other users. Even something as simple as asking for a template at startup is a change.
Unlike some here, i realize that my needs aren't necessarily the same as other's need. So I cannot go "it fit me, so it will fit everyone else".
Or maybe i should go along, have the change made and committed, and let you whine afterwards ?
|
1st: change your attitude, or I stop answering. You're the first to act as if you have the answer to life, universe and all else, and that's annoying. I'm trying to provide you quick answers because today I can't spend more than 5 minutes at a time writing on a forum, but I'm not Kovid and I'm not paid to do this so I may as well leave you in your limbo.
Quote:
|
Unlike some here, i realize that my needs aren't necessarily the same as other's need. So I cannot go "it fit me, so it will fit everyone else".
|
Yet, you kept using
absolutes when talking about things that
you personally don't like. Saying that "it's useless", "is a mess", "doesn't work", "is stupid", "can't help", you imply that it's like this for every one. Only in very few instances I've seen you add the magic words "
for me".
2nd:
Unlike you, I have looked, even if briefly, at how is structured Calibre before making any complain to Kovid. Just so that I could see if what I thought was a good idea was feasible or not.
Unlike you, I've been writing code in a few open-source projects (not many, true, but a couple of lines of code here and there), and
unlike you I can easily imagine that adding, at installation, a radio-button list that says "[]choose the Folders' Structure Template or [X] Use Default Folders' Structure" is not a damn huge change, and surely is NOT a way to
break what already works".
3rd: you must only make sure that you
don't BREAK what already works, I don't give a damn about it if you "change" a button, or a list, or add a combo-box, or a whatever. Can you tell the difference between
breaking a feature and
changing a behaviour? You said you are a programer: if you really are, I bet that you keep adding buttons, changing behaviours, tweaking UI, and adding steps to the setup process every time a customer asks for a personalization or you make a new version of your software. When I worked as a programmer, I did it every day. At the same time I'm sure that you NEVER broke an EXISTING feature, because that's the meaning of adding features to a software, and that's how every single programmer works in this world.