End Drag Refactoring

We continue to suffer under one poor choice I made early in the project: drag refactoring. This was a design goal. I had hoped that a carelessly organized set of pages could be drag and drop refactored into a better design.

See Footer Item Search for motivation.

I can't remember where I have done this in my own writing. (Except for just now.) I suspect it is too hard.

Copying a paragraph is made hard too since you have to remember to hold the shift key down while dragging and ignore the fact that it seems to have moved the item anyway (It hasn't, refresh to see that.)

Let's embrace footer item search as our best method of exploring provenance by getting rid of shift-drag and adopting this simple rule: drag within a page is move, between pages is copy.

Suggestion:

Can I suggest that dragging between pages that share the origin server defaults to a move as well? As an author of both pages I will rarely wish to copy the paragraph - rather to move it from one page to the other.

I suggest that this is intuitive enough, as dragging an item on the same page is a move - to extend this to the same site will not be too counterintuitive.

Should this be problematic then shift drag between pages could move as opposed to the new default of copy?

Of course how drag is interpreted is determined by the origin server. We don't have to worry about changing all servers at once. The copy interpretation will be obvious if other behavior were expected because less would happen on the screen. The copied element would remain in the source, not something that happened visually.

# See also - Citation Bar