If I have the bric menu open and select a bric, my mouse pointer shows the bric I have chosen. As my mouse moves, the blue line appears showing where that will be dropped.
If I select something in blocsapp it tells me what I have selected, so it should be possible to copy everything, to do with that component (including anything nested inside) just like blocaspp does when duplicating.
If I then initated a paste operation then blocsapp could then behave as though I was inserting that component, so the cursor would change and the blue line would appear, as though an insertion was being made. If you were super-clever the cursor would be the similar to an insertion being made.
This is fine for brics.
Blocs might be a bit more challenging because the placement works slightly differently on creation, but the great thing about a blocs is that they are easy to move, so putting one in the wrong place isn’t a massive issue, but you could even implement the blue line cursor for bloc pastes.
If you can crack this then the re-use possibilities for blocs goes up massively. Instead of re-creating that design wheel all the time I could re-use designs I have made. Copy and paste elements between files? yes please!
There’s a bit of a caveat when copying and pasting between files - custom classes. You’d need to bring in custom classes too and that might cause name clashes. There are ways around this, the simplest being to abandon the import of a specific custom class if it already existed in the file being pasted into. It would be nice to be told that had happened. It would also be great not to worry about class name clashes if the custom classes in both files were equivalent (but retain the custom class attribute on the imported item).
If you can crack this Norm, then we have the ability to use templates and create design libraries to accelerate site builds.
Of course, my button problem would be solved with an asset paste, which would be a step in the right direction, though I hadn’t envisaged that as a specific operation (I mentioned copying assets as a way of implementing the pasting of brics).