Definitely good addition. I need this too often not to appreciate such a method.

+1

Yeap, I agree too

+1

I would use this a lot.

Would these two then be equivalent?

#!js
$(foo).radioClass('on');
$(foo).addClass('on').siblings().removeClass('on');

Even though Ext may go with radioClass, it doesn't specifically target radio's which can appear misleading; siblingClass() would be more logical to me.

But on the whole, it doesn't seem to be enough of an improvement to deserve it's own syntactic sugar. This would also be the only attribute manipulation method that assumes a specific DOM relationship. A bit odd to me.

-1

not so sure this needs to be in core (though it seem some people like it). the name is certainly misleading, and i think that if something like this is going to go in, it way as well work natively to apply this behaviour on checkboxes, which at present wouldn't really be manipulated by this enhancement.

I'm in agreement with paul.irish in both the naming and usefulness. The method would only be useful when dealing with exclusive classes in sibling relationships.

If you wanted to add something like this, I'd would say it is more valuable to have some flexibility.

Assuming you had

#!js
<div id="parent">
  <h3>heading</h3>
  <ul>
    <li class="active">1</li>
    <li>2</li>
  </ul>
  <h3>heading</h3>
  <ul>
    <li>1</li>
    <li>2</li>
  </ul>
  <h3>heading</h3>
  <ul>
    <li>1</li>
    <li>2</li>
  </ul>
</div>

Something like...

#!js
$("#parent ul:last li:first").exclusiveClass('active', $("#parent"));

Where the second argument would be the scope that you should maintain exclusiveness within (perhaps making it so that the default scope is within the direct parent).

-1

I agree with paul_irish completely.

I agree with my chums from #jquery.

I'd rather see these type of extension functions go into an 'optional' lib which would be available to download alongside the core. Lets keep the core lean and mean.

It's definitely useful.

+1

Needs review/attention

To have the same behavior as the Ext method, radioClass must also take an array of classes, as in my little plugin here:

http://code.doublerebel.com/jQuery/jquery.radioclass.js

Interestingly, this ticket was filed (and various radioclass blog posts were written) about the same time I created that. I think radioClass would definitely see use.

Without a public repo, unit tests or docs, it's hard to support something that already seems easily accomplished with existing core methods - as noted by paul.irish

-1