RadioButton - addButton vs setGroup

I was looking at using RadioButton objects, and had a few quick thoughts regarding how they're implemented. I had a few thoughts:

Right now, the RadioButton seems to have to call setGroup(ButtonGroup bg); before it'll work properly. I was wondering though if this is really all that smart idea - to have a component know about it's container? I was looking at the code, and i'd almost think it would be smarter to have the ButtonGroup do the manipulations for the RadioButton? This way, the RadioButton really only sees itself - it doesn't see anything else.

I'm assuming that the reasons for having the RadioButton to see what group its part of is to set the name in HTML (thus, making it a radio button and not just a button). However, I'd think that a property of group_name or something like that would be a better solution.

Am I off the mark on this? Is there something I'm missing here?
Jason

From API point of view (if

From API point of view (if echo wants to be similar to swing), there should be no RadioButton.setGroup() method. The difference between echo and swing makes confusion, because using only ButtonGroup.addButton() doesn't work.