I would prefer .maskInput as the method name, coz, it conveys both the intention and what it applies to. "mask" doesnt convey where it applies to and probably can be used for a more generic plugin.$('input.date').mask(...) should be good enough to imply what is meant I think. I used to be in favor of longer function names myself a while back, but recently found that shorter is better in most cases. A good example is jQuery itself: we have css() instead of setStyle(), load() instead of ajaxLoad() etc. The thing is as longer your name get's the less intuitive it is. When I started using jQuery I would discover functions by virtually guessing their names and only use the API if that resulted in an error. So I'm going to vote for mask() again ; ). -- Felix Ganeshji Marwaha wrote:
|
- [jQuery] Re: Naming Conventions Felix Geisendörfer
- [jQuery] Re: Naming Conventions Ganeshji Marwaha
- [jQuery] Re: Naming Conventions Josh Bush
- [jQuery] Re: Naming Conventions Jörn Zaefferer
- [jQuery] Re: Naming Conventions Sean Catchpole
- [jQuery] Re: Naming Conventions Jörn Zaefferer