I’ve just pushed version 0.3 of my related selects jQuery plugin to GitHub. Along with refactoring the code and some minor performance improvements, 0.3 allows you to return data in HTML format instead of JSON. This gives you direct control over the markup and individual option tags in case you want to use optgroups, assign classes to options, etc.
I’m still undecided whether or not I want to add caching. I thought about it when I first wrote it and a user suggested it, but I cannot picture a use case where caching would be necessary; people are likely to choose an option and either decide it was incorrect and change it, or stick with it. In either of these cases, caching doesn’t do anything other than add overhead. If a user selects an option and then continuously changes/reverts back to it, caching would be helpful, but how often is this likely to happen?
Anyways, here’s she is:
Related posts:
