search

linkeddata / dokieli

:bulb: dokieli is a clientside editor for decentralised article publishing, annotations and social interactions
https://dokie.li/
Other
788 stars 81 forks source link

Export/save as selection #145

Open rhiaro opened 8 years ago

rhiaro commented 8 years ago
  1. Select some part(s) of a document.
  2. Save As -> generates new document with only that selection as the content.

Use case: I'm writing a diary-style braindump post and there are some paragraphs that I can use to seed something else, like a paper or proposal or blog post. Right now I have to create a new document and copypaste that section. If I could instead save directly to a new document, it can also keep derivation triples etc.

Would see this on the same interactions menu as making a selection to reply-to, annotate, like, bookmark, share, etc.

Related: https://github.com/linkeddata/dokieli/issues/116

csarven commented 8 years ago

interactions menu? I would prefer not to have a new button for this but reuse 'save as'. If there is a selection, 'save as' will take what's selected and put that somewhere, otherwise it does the default (the whole document).

The only thing that may be nice to have is preserving some sort of provenance... it somewhat overlaps with how annotation works (selection, prefix, suffix, target..). The initial pass can be simple: use the closest parent @id (as part of the URI) of the selection, else the document URI.

rhiaro commented 8 years ago

Reusing save as is fine. I suggested interactions menu because we have these two menus: 1. right-side DO menu, and 2. floating ME menu. In my head, the former being for document-level interactions and the latter being for selection-level or sub-document-level interactions. Saving a selection rather than saving a whole document falls under 2 in my opinion.

So far I assumed we were going to have duplicate buttons (reply, share, like, bookmark) on both menus, so this would just be another of those. I think we should either duplicate all or none, so in this case the floating interactions menu would only include annotate and highlight (as these can't occur on a document level) and for all the rest they'd be on the DO menu and just check for an existing selection.

I prefer the UX of the ME-style floating menus for all selection-based interactions though (one less click to go from selection to interaction).

Maybe we should mock up both and do some user testing :p

csarven commented 8 years ago

Okay, this goes along with issue #116 where we separate the annotation action from the ME ie., if the user is in 'read' mode, they get the social interactions menu on selection: annotation/like/reply/share/saveas.

csarven commented 8 years ago

Lets minimise code shuffling by doing #116 first.