On Sep 17, 11:27 am, David Duymelinck <[EMAIL PROTECTED]> wrote:
> I understand people want to use the latest version of jQuery and
> plugins for all of their projects but i don't think it's possible.
agreed 100%.
> As far as jQuery is concerned i would rather see a table of methods and
> selectors that are available for each version so it can be used as a
> cheatsheet for projects that use another version than the latest.
The main problem with that approach is that with every new release
you've got to update the cheat sheet and compare compatibility
backwards against an arbitrary (and growing) number of previous
releases. e.g. if we start today with a chart for 1.1.4 and 1.2.0,
1.2.1, we could compare 3 versions. Next time it's 4. Then 5... ad
nauseum.
> For the plugins i guess most developers already announce which jQuery
> version they used and which browsers they tested it on. I would suggest
> to do this for all the versions of their plugin(s). That way you know if
> a browser isn't mentioned or the jQuery version you use is newer or
> older you are a tester.
The past week i've had to go through my plugins (7 of them) and try
them out with 1.2.0 and then 1.2.1. i can assure you that it gets
amazingly dull to have to go through 7 plugin demos on each new jQuery
release and check every feature of each of them. That is simply to say
that we cannot expect all plugin authors to post up-to-the-minute
version compatibility info. My tendency is normally "don't post a
compatible-with-version-number until someone complains that it doesn't
work their version."
> people who use plugins are so tough on the developers. All developers
> doing their best to release the best plugin using their workflow and
> skills.
Amen. Along those lines, i agree 100% with John Resig's response to
the above post, where he says: "Why not help to add that to the main
jQuery plugin repository? We already have all the plugins and the full
application..."
i think that most plugin authors are using (or starting to use) the
nice plugin repo facility at the jQ site, and adding this as a feature
would certainly "coerce" me to update the version compatibility info
as i go through the normal update routine for my plugins.
> Back on topic. Not all developers put their plugins in the repository,
> sometimes they only announce it here.
The plugin repo is fairly new, though (well, the new one is, of
course... i never got around to using the old one). i think there is a
movement (if we can call it that) to try to encourage plugin authors
to post their plugin(s) there. It's easy to do and provides features
like bug tracking, so there's little reason not to use it. (It's
probably also good for one's google rankings, with jquery.com pointing
back to your home page ;).)
