I have decided that it is time to move the 3.5 release into a ‘final’ state. Giving it a ‘final’ label may encourage those who do not like to run software labelled as ‘beta’ the confidence to move to this release. The 3.5 release has had lots of bug fixes since the 3.4 release as well as ton of new features. There are also some under-the-covers performance related changes that should significantly reduce the time taken to generate a large catalog if you are generating both the XML and the HTML versions of the catalog.
The Calibre2opds source code has been migrated to gitHub as the Google Code site which has served us well for some time is going to be closed down later this year. As we are just about to start development for the 3.5 release now seems an appropriate time to do this migration rather then perhaps being forced to do it in the middle of the development for the 35 release.
This means that the 3.4 release is the last one hosted on Google Code. It will be available in read-mode for some time, but if you want to get the latest code you will have to go to the new gitHub repository.
There will be a short period where the online documentation has not been updated to reflect this change. It will be updated appropriately as experience is gained in working with gitHub.
EDIT: The changes to use gitHub seem to be less than anticipated, so the changes to the online documentation were minimal and should now be complete.
It is possible that it might also be appropriate to migrate the handling of issues and feature requests to gitHub to keep things in one place and to provide integration between versioning and issue resolution. However no decision has yet been made on this area.
The development cycle for Calibre2opds 3.5 is starting up.
Initial ideas for inclusion are:
- Enhance the generation process to make it more intelligent so that it only attempts to generate catalog pages that have actually changed since the last run. This would provide significant run time performance gains of the current approach of generating all possible pages to a temporary area and then after the generation only copying changed files to the final catalog location.
- Allow for the use of Calibre Custom Column field types to be used in search and filter expressions.
If you have some other feature that you would like to be considered for inclusion then please raise it as a feature request on the Calibre2opds Issue register.
One other change that will also be happening as part of the development of this release is moving the source and version control to an alternative service (probably gitHub). Google have announced that the GoogleCode service we currently use will be closing down later this year and so projects need to migrate off it.
It has been decided that it is time to move the 3.4 release into a ‘final’ state. There have been no significant bug reports for a while now, so giving it a ‘final’ label may encourage those who do not like to run software labelled as ‘beta’ the confidence to move to this release. The 3.4 release has had lots of bug fixes since the 3.3 release as well as ton of new features.
For some time Calibre2opds has had a browser based search feature that has been labelled as experimental. It has been decided to change the status of this feature to ‘deprecated’ (although we have not yet removed it from the Calibre2opds program).
The reason for this is that the Calibre2opds search feature was based on the draft HTML 5 database feature (commonly known as WebSQL) that was going through the standardisation process. However this specification has since been withdrawn and is deprecated by the W3C standardisation process. A consequence is that major browser such as Internet Explorer and Firefox have decided not to support this feature. Browsers that DO appear to support it are Safari, Chrome and Opera but since this feature is no longer up to be standardised support could well be removed in future versions.
If you decide that you DO want to generate a Calibre2opds catalog to support this feature, then if you use a browser that is not compatible with the current implementation then you will now get an error message stating this when you try and use search.
If anyone can point out any open-source libraries that implement browser side databases in a manner compatible with all major browsers then we would be happy to look at changing the Calibre2opds search feature to utilise such a library.
We have made the Calibre2opds 3.3 (rev 274) into final release as there have not been nay bug reports for a little while now.
The 3.4 release beta program will therefore be starting for any bug reports received against the 3.3 final release, and also for development of new features.
It has been decided that we have finished adding features to the Calibre2opds 3.3 release, so the latest build (currently rev 269) has been designated as a Release Candidate. If no issues are reported in the next week or so that require fixing then this will become the final 3.3 release and we will start working on the 3.4 release for any new features. There are lots of new features present in the 3.3 release based on feedback from users. Many users do not like using releases designate as beta so getting the 3.3 release into ‘final’ state will help encourage users to move on from the 3.2 release (this is important as many bugs reported against the 3.2 release are fixed in the 3.3 release)..
There was one significant feature that we had originally envisaged might make the 3.3 release that proved hard to implement and therefore are now going to be delayed until at least the 3.4 release. This was the ability to specify Calibre custom columns that could be used to generate a new Catalog sub-section that would behave rather like the current Tags section. Associated with this was the enhancement to the calibre2opds search syntax to support custom columns.
A point to note is the move to using GoogleDrive to host downloads. This is not nearly as friendly as the previous downloads based on GoogleCode, but has been forced on us as Google discontinued the ability (from mid-January) to add new downloads to GoogleCode. If any users have suggestions on improving the GoogleDrive experience for downloads then we would welcome them.