There's two parts to this problem:-
a) using an index in the pluggable list means that you will inevitably get a
problem if the underlying collection changes size or ordering. It can simply be
fixed by allowing the use of names instead of the numeric index. At least that
way you avoid many of the immediately annoying trouble. Anyone who has an old
copy of a ObjectWorks or early VisualWorks will probably be able to find a
working implementation to work from. Of course, in some cases you don't want to
use the names because they're not unique - so you need to allow a choice for
the coder.

b) cross-browser updating would fix much of the rest of the problem EXCEPT you
have to consider what to do as part of the update. Simply making the browser
fetch a new SystemOrganization might inadvertently dump all your work in a not-
yet-accepted TextView for example! Take care....

tim
PS I'd dig out working code to suggest but I'm on a short timeline right now.
Sorry.

-- 
Last one out, turn off the computer!
Tim Rowledge:  rowledge at interval.com (w)  +1 (650) 842-6110 (w)
 tim at sumeru.stanford.edu (h)  <http://sumeru.stanford.edu/tim>