Let's assume you are going to do 'something' that makes jQuery better but changes the API.
What is the suggested way to bind a click function or a toggle function NOW so we don't have to change later?
I'd rather change now before things go live. :)
Glen
On 10/15/06, Jörn Zaefferer <[EMAIL PROTECTED]> wrote:
Ⓙⓐⓚⓔ schrieb:
> I feel there are too many names for the ajax functions.... they can
> all be coded ajax.. and some share names with non ajax function (as
> John mentioned)... perhaps new names for these weirdly overloaded
> functions?
>
Good point. Having a common prefix for all ajax related methods could be
a big help.
> Which brings up the matter of deprecating... it would be helpful if
> you use a function in an old manner, you could get a deprecated
> message in the log
>
I don't think we should use deprecation in a library that depends
heavily on file size. You never know when the time has come to actually
remove that crap, therefore it sticks there for all time. Great ugly
example: The Java runtime enviroment (JRE). It gets bigger with every
release, but never smaller (though this may actually change).
I think branching may hurt more at first, but help a lot to evolve the
API while maintaining stable releases.
-- Jörn
_______________________________________________
jQuery mailing list
[email protected]
http://jquery.com/discuss/
_______________________________________________ jQuery mailing list [email protected] http://jquery.com/discuss/
