[cap-talk] Drag & "Attenuated" Drop?

[Rob Meijer]

In explaining how in theory MinorFs could work with a MinorFs aware GUI,
I've been saying that drag and drop could implicitly use MinorFs
decomposition.
That is, if some file or directory /mnt/minorfs/cap/$BASECAP_A/foo/bar
whould get drag dropped, the GUI could implicitly request the "cap"
extended attribute, that would point to /mnt/minorfs/cap/$BASECAP_B .

With an additional file system I am adding to MinorFs that next to
decomposition of the directory treegraph can do attenuation, the drag
and drop concept however seems to get a bit more complex, and extended
user interaction appears to be needed.

There seem to be 3 alternatives possible, all seem sub optimal:

1) Show an attenuation dialog box on each drop.
2) By default let drag+drop be a deep read only attenuation, use something
   like CTRL drag-drop to show an attenuation dialog box on drop.
3) By default let drag and drop be unatenuated, use something like CTRL
   drag+drop to show an attenuation dialog box.

Am I missing a better alternative, and if not, what of these 3 would be
the preferable one.


Rob