I’ve thought about this a bit, and I like where your head is at. I think everyone has wished they could just cut + paste all their hard work into different tabs on a page, or in different pop-ups. I know that the majority of time I run into this however, I’d like for there to be different models that drive the component (perhaps even the same underlying SFobject but different conditions etc. applied.)
Now the case of, as you put it “All the models would match up because the original components were built on the same page” doesn’t hold true. Skuid can be nasty when it comes to ripping + replacing models in existing components, and certain legacy attributes are left into the XML that can cause some weirdness.
If this is to be done well in my opinion, it’d have to have a really nice way of identifying all the models that are used in the desired XML tree and offering a chance for the user to change them.
