Revision History 2.x
![]() ![]() |
This version introduces several new features and many changes to how the code is organized. Version 2.0
It should be noted that not everything may be working properly, I didn't see anything not working but it's easy to miss something. |
![]() ![]() |
Version 2.1This edit is mostly about bug fixes and upgrading the code. I'm reducing the custom logic to generic code, making it more readable and maintainable. There is more that can be done on this front and the implementation is less than perfect. One task is to move the parsing logic from Item::getAdditional() into the actual objects involved. I do not foresee any major new features at this time. Notes:
|
![]() ![]() |
Version 2.2I've been meaning to upload a version 2.2 but I never had the time, so I kept making small changes... many small changes later... Now there have been so many changes to that I honestly couldn't list them all. The big feature in this release is real-time Sorting. And it works with AutoPager (auto updates)! It's really cool. One of the sort modes is by Series (and then by volume and title). Many more pages now get linkification. Creator searching is now possible in most situations. I have discovered that some of the pages include commented out living html. I've added parsing for this in many situations, so this script may be aware of more than what is just displayed. More importantly in a few situations, the script uncomments code. Particularly on the WaitingListForm page. I have not tried the restored functionality but I suspect the library would get billed for me using it. That and best to let sleeping dragons lay. Adding support for new pages is getting easier. Just an hour of coding and debugging and poof, another page supported, standard features work out of the bag. |
![]() |
Version 2.3I released this version to improve compatibility with Firefox 4.0. In addition to that, a new feature creeped into this release, early stages of updating of the item counter in searches. It's only been implemented on overdrive classic searches. |
![]() |
Version 2.4This version is mostly about code cleanup and maintaining compatibility with Greasemonkey, AutoPager and Firefox; though a few new features creped in. Latest versions of all three are now supported. |
![]() |
Version 2.5Improved sorting on searches. When searching, items that share the same title and creator are assumed to describe the same title. Instead of sorting each item on its individual metadata, the metadata is combined and they are sorted as if they were a single item. The most popular (non empty) value is the one to be used for sorting. To speed up sorting these average values are cached (the cached values are updated when a new item is added to the group). To facilitate this and other changes more code reorganization was required. Unstyled track lists are now styled. Current script size is hovering around 220 KiB, I'm trying to get it down by reducing code duplication and modernizing the script. One of my goals is to have this version be able to run in "strict mode". Some changes will be needed to have this work transparently. I have released 2.5 a bit before I wanted to but they have updated wishlists and searches and not wanting to leave my loyal (non-existent) fanbase without a working script I have rushed this out. Other changes include tighter loading restrictions (keeping the script out of https pages it shouldn't be in). More metadata filtering options. |
![]() |
Version 2.6I've uploaded this version despite it not working everywhere because It fixes most places that were broken by overdrive website updates. Also AutoPager rules are working sporadically and need tweaking. Changes:
|
![]() |
Version 2.7This version is intended to improve speed. It does provide better support for some websites (as did the previous). I didn't know this until I stumbled upon it in the Mozilla documentation, you can compile XPath expressions! So I've augmented my XPath functions to take compiled expressions and added a caching expression compiler. I've added an extra layer to the compiled expressions so I can keep some tracking information (and so I can examine it and know what the source expression was). The compiled expressions seem to work the same as their uncompiled counterparts. Next project is to reduce the number of calls to the compiler (it will be faster if the code can cache the expressions locally instead of having to dig through the compilers cache. |

