Any way I could get calibre usable ?

[Lo Zeno]

Originally Posted by EowynCarter

Work out a solution with them ? Hey, what about the rest of calibre users ?
Kind of stupid to go code stuff, then have your code rejected because it breaks stuff other actually cares about.

You don't need the other users to know what the existing features are: there's a nice and handy list in Calibre's website. Just make sure you don't break anything already written in that list, and you're sure to be approved.

[EowynCarter]

Originally Posted by Lo Zeno

You don't need the other users to know what the existing features are: there's a nice and handy list in Calibre's website. Just make sure you don't break anything already written in that list, and you're sure to be approved.

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 ?

[Manichean]

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 ?

If you want to use the "a new UI element means change, which you clearly don't want"- excuse, well, you won't be able to implement the changes you want without new UI elements. In case you hadn't noticed: Most of us just don't care either way what system Calibre uses to save the files. As long as interoperability between multiple installs of Calibre gets preserved (think multiboot), I don't think anybody is going to mind.
Edit: It's not that the regular users on this forum, if I may be so bold to speak for most of them, mind changes. It's just that we don't care about the changes you want.

[EowynCarter]

If you want to use the "a new UI element means change, which you clearly don't want"- excuse, well, you won't be able to implement the changes you want without new UI elements.

Yep.
I never looked at any of calibre's code line. I have zero knowledge with python. Makes it hard to tell how profound the changes would have to be, and the impact.
And the fist two facts makes me reluctant to get into any coding, that other could do faster and better than me.

[DoctorOhh]

Originally Posted by EowynCarter

I never looked at any of calibre's code line. I have zero knowledge with python. Makes it hard to tell how profound the changes would have to be, and the impact.
And the fist two facts makes me reluctant to get into any coding, that other could do faster and better than me.

It's not hard to discuss this with Kovid through private messages. Outline your basic idea, tell him if it is doable you want to take a crack at coding it and you need some insight on where to start.

[Lo Zeno]

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.

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.

[EowynCarter]

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.

At works, the user asks the changes. Thus, I know they agree with it. (And yes, they do complain about slight change in the UI made without their approval..)

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".

I can't believe it would be that easy, and no one actually bothered doing it.

[DoctorOhh]

Originally Posted by EowynCarter

I can't believe it would be that easy, and no one actually bothered doing it.

No one said it is easy, but how does changing the file names help you with version control which was one of the main items you were concerned with? That would still need to be implemented at the metadata level, wouldn't it?

[EowynCarter]

Originally Posted by dwanthny

No one said it is easy, but how does changing the file names help you with version control which was one of the main items you were concerned with?

using custom tag in the library path.

[DoctorOhh]

Originally Posted by EowynCarter

using custom tag in the library path.

Does this mean a separate entry in the library view for each version?

[Manichean]

Originally Posted by EowynCarter

I can't believe it would be that easy, and no one actually bothered doing it.

It may be easy, but, as I've said before, nobody bothered doing it because nobody cared. And those who do care seem curiously unwilling to change anything.

[EowynCarter]

Originally Posted by dwanthny

Does this mean a separate entry in the library view for each version?

yes.

It may be easy, but, as I've said before, nobody bothered doing it because nobody cared. And those who do care seem curiously unwilling to change anything.

If you react that way with everyone who dare mentioning changing stuff, not a surprise. Guess they just went using something else.

Your attitude really fell like : please please , don't change my software. I like it that way in changing it will make me unhappy. Maybe that's not what you're thinking, but you're making a good impression of it.
Maybe if your stoped discouraging people from doing some work, work would get done ?

[DoctorOhh]

Originally Posted by EowynCarter

yes.

In that case you can do that now with custom columns as has already been suggested. I'm not saying it can't be better but adjusting the file name in the path isn't going to go far to helping with your version control issues.

Some other things to also consider (among thousands).

1. The potential of running into the filename/path character limit in the database. Currently some file names end up truncated in the database because of this limit.

2. Currently the files in the database are not automatically updated with current metadata or covers until exported from the database via Save to disk, Send to device or Connect to folders features. I believe this is limited to increase application responsiveness during normal operations.

Good Luck

[EowynCarter]

In that case you can do that now with custom columns as has already been suggested. I'm not saying it can't be better but adjusting the file name in the path isn't going to go far to helping with your version control issues.

Right now, when browsing the folders i have no indication who's who.

1. The potential of running into the filename/path character limit in the database. Currently some file names end up truncated in the database because of this limit.

Didn't even knew there where such a limit

2. Currently the files in the database are not automatically updated with current metadata or covers until exported from the database via Save to disk, Send to device or Connect to folders features. I believe this is limited to increase application responsiveness during normal operations.

Responsiveness is the obvious problem with synchronizing.

[DoctorOhh]

Originally Posted by EowynCarter

Right now, when browsing the folders i have no indication who's who.

My point goes back to the beginning. If you are going to go to multiple entries per book for version control and use custom tags to differentiate the versions (that can be done now) then there isn't any reason to cruise through the database/file structure to muck around with books.

But, again, if you have such a need use the save to disk feature to keep a clean hierarchy file structure separate from calibre's database. This file structure as currently implemented would have the metadata all updated and be ready to tweak to your hearts desire outside of calibre.

I look forward to seeing the end product your proposing. Personally I don't see the gains outweighing the time put into coding such a system, but its not my time.

I wish you well.