drgullin
commented
10 years ago Hello @Ciel.
Actually, I've lowercased iCheck instance because it's a bit easier to type - you don't have to enter a cap in the middle of the word.
I agree that this may get confusing, especially, because some of the options and callbacks aren't lowercased.
I'll likely turn it back to iCheck in the next RC version, which should be the latest one before a final 2.x release.
I appreciate your thoughts on this, thanks.
This may be trivial; And the community may flame me. If I am out of line, I apologize. I have never cared enough about a project to comment on it, and so as such I am new to the entire etiquette about the entire ordeal.
The legacy 1.0 iCheck uses the function named 'iCheck' (case sensitive) - but the beta of 2.0 uses 'icheck', all in lowercase.
This is not really a problem, but it did take a while of going through code to make the corrections - or rather, to figure out the problem and make the corrections.
Is this by design or intention? Or is it merely an oversight? It is not really that troublesome to update my code, it just kind of blindsided me. I love the 2.0 upgrades so far.