Hi Jorn, > ...As long as this is > introduced with a major release with proper release notes, it shouldn't > be a big problem to upgrade.
I disagree with this statement. If my codebase is dependent on a specific type of return value from a method and I've used that method in numerous places in my code, upgrading will not be a trivial task depending on how I've used the return value. I refer back to EasyDOM that, at the moment, will only work on v1.0a. The upgrade to v1.0.1 broke the functionality. Further, I recall an email that I sent out early this month that referred to the set() method, which is used in EasyDOM, to which John replied letting me know that it had been superseded by attr(). This affected EasyDOM and I'm sure others that took advantage of the original method. I understand the need to enhance the library but there has to be a better way of moving forward without simply (or arbitrarily) deprecating methods. I would really like some thought given to how this would be done. I'm using serialize() extensively now in my current project and would hate to have to modify code when alternatives to implementing the form plugin exist. Rey.... _______________________________________________ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
