Updating the objects doesn't look like it would be too hard.
But updating all the scripts that use them might be.
To me, it looks like you have a lot of unnecessary layers in your alias objects? I use the Alias object to massively reduce the complexity of the object map. So if an intermediate layer changes, I can correct it and leave the lower level components alone in the Alias file. Correct the map file and the alias file sorts itself out.
Obviously, there are times where the Alias is also affected, but as long as your application is relatively stable, these should be minimal. They are for me.
I can't see what exactly your alias represents, but I would try and reduce the number of components it uses. Do you actually need all those intermediate components?
Jose - I know you and a few others on here use helper/search functions. If I'm working on something with a lot of dynamic components, I do the same. But in a non-dynamic site, are you not taking a big performance hit searching the whole DOM like that all the time?
Main point with name maps is not to bother with them until you are confident the site is relatively stable. Unfortunately, you do still have to take a hit occasionally. But with smart use of identification properties and aliases, you can really reduce the impact.
Updating all the alias references in the test scripts is far more of a problem. I've already seem someone ask for auto-updates to scripts when name map or alias changes happen. +1 to that from me! (QTPro does this from what I remember ...)
