You know what ? When I read and answered your first post about memory requirements, I didn't realize that it was you
If I had, I'd have started a conversation about the project !
Quote:
Originally Posted by itimpi
With the RAM set to 256MB the tool completed without an issue (it looked a though peak RAm was about 110MB). However it took a LONG time, and generated 15314 files totalling 260MB in size!
|
Well, in a previous version I generated one file per book, and then linked to this file in the books lists (recent, authors, series, and all books).
I found out that Stanza did not support this feature of the OPDS standard, and then I rewrote everything to include the full book entry in the books lists.
This, of courses, makes for a much bigger output than the first solution...
And then, the thumbnail generated are, of course, a huge part in this big space...
Quote:
Originally Posted by itimpi
The sorting seems a bit eratic:
Authors seemed to be unsorted
Series was fine (alphabetical ascending)
All Books and then a ltter was in reverse alphabetical
|
This is corrected in the next release.
Quote:
Originally Posted by itimpi
There probably needs to be another level of indirection in Series and Authors for large libraries (I have about 1200 series and 1100 authors). That was why I added that extra level in Calibre2Web. In fact I had though of adding even another level for the letters with a very large number of entries.
|
You mean, an option to split these lists by letter, too ?
Quote:
Originally Posted by itimpi
In the HTML output, you say either "Download ePub file" , but for all other formats use the text "Download this ebook as XXX"
|
Also corrected in the next release.
Quote:
Originally Posted by itimpi
You mention books as being "Book # in the xxx serie" (i.e. a missing s)
|
I'm not sure I understand ? "Book 2 in the Giants serie" is meant as "the second book in the Giants serie" ; is this wrong ?
Quote:
Originally Posted by itimpi
Having said that - the output is still useful - especially the HTML file option.
|
This one was actually Ian's idea, and I like it very much...
Quote:
Originally Posted by itimpi
I have (finally) started getting seriously into the Python version that will be able to handle large libraries as the pages will be generated dynamically on demand directly from the metadata database. If you do not mind I will "borrow" some of the ideas from your implementation. One big advantage that dynamic pages give is the ability to support search functions as well as avoiding the time overhead of generating the static catalogs.
|
That's great (having news about the Python version at last), I can't hide that I began this project because I thought that your Python script development was cancelled !
And of course I don't mind you borrowing, I even would like to help if I can...
Maybe I can explain the pitfalls I managed to avoid, and if I can upgrade my Python-fu to second dan, I may even be able to help you code ?
To be honest, I coded this in Java to be quick, because I know this language very well. But I know a bit of Python, and I'd love to learn more, if you're patient enough
Quote:
Originally Posted by itimpi
I am trying to write the Python is such a way that it can either be integrated into Calibre, or alternatively run as a free-standing piece of code under a web server such as Apache (so that calibre itself does not need to be running). Whether I can actually achieve that I am not yet sure. It may as a by-product also be able to output the static catalog files - do you have any objection to it possibly superseding your tool?
|
Again, of course, please reuse whatever you feel useful ; in fact, it may be cool to merge both projects, don't you agree ?
Feel free to contact me (dpierron at gmail dot com) about this, whatever your opinion about merging is ; in any case, I'll be more than happy to help and to share !
Cheers,
David.