Integrate text processing API

[juliusknorr]

Based on nextcloud/server#38854 we will add options to process selected text.

This is the summary of what I discussed with @julien-nc during our meeting:

• Assistant app will provide a generic way across nextcloud in the menubar
  • Will trigger a dialog
• For text we will have some sort of action to trigger this dialog which gets prefilled with the selected text, processing task, app, identifier)
• As text processing is an async operation, we will need
  • a list of pending/finished tasks per document which could be rendered inline
  • the list provides a action to insert at cursor position
  • the list provides an option to dismiss the result
  • the list needs regular refreshing, could also get triggered by the notification from the assistant app

Depends on

• Server: Provide an OCS endpoint to list tasks for app+identifier
• Assistant app: Provide a JS API to launch a modal, pseudo code API:

openTextProcessingModal(appId, identifier,  task, inputText) 
    => new Promise((resolve, reject) => { resolve(ScheduledTask) })

• Assistant app: PHP event dispatched to trigger enhancing the notification with the link to the file to open in text

  • Task is finished -> assistant app prepares a notification -> emits an event -> text adds the file link (based on app+identifier) -> assistant app emits the notification

• UI questions to discuss

  • Where to put the processing options (menubar button, popover menu on select, menu next to the paragraph)?
  • How does the list look like (positioning, overflow, buttons, mobile)

[julien-nc]

LGTM!
Depends on

• AI admin settings server#39567

which contains a fix.
The text processing assistant app will be there https://github.com/julien-nc/textprocessing_assistant

[juliusknorr]

@nimishavijay This is the tracking issue for bringing support of nextcloud/server#39478 to text. When discussing this with @julien-nc We were basically considering the following UI wise:

• Text offers a button to start the modal outlined in ✨ Nextcloud-wide mechanism to translate, lengthen text, make more serious, etc. server#39478 prefilled with the currently selected text
  • Question: Where should we put that button? It could be next to the already existing translate button in the menubar for example or would this be not visible enough?
    
• When the task is scheduled we will list all pending and succeeded tasks in the bottom of a text document
  • This can be used to get back to scheduled tasks once they are finished to insert the result into the document
  • Quick-and-dirty mockup:
    

[nimishavijay]

Question: Where should we put that button? It could be next to the already existing translate button in the menubar for example or would this be not visible enough?

So the original idea was that for Text it would be a floating button next to the line which has the cursor. That way the text fed into the TP widget would be the text in that line, or the text that has been selected. Would that be possible? It would look something like this:

If not I would agree that it could go into the formatting bar. Since this is a feature we would like to market, I'd also agree that placing it near Translate is not visible enough. How about we place it as the last action before the remaining actions, and it is styled as a secondary icon-only button similar to the screenshot above. It would be great if the action menu with the subactions is there, but that is also something to be discussed with Julien :) What do you think?

When the task is scheduled we will list all pending and succeeded tasks in the bottom of a text document

That's a great idea! Indicating the progress would be different for each app, but this is a great solution for Text. The quick screenshot you pasted already is pretty close to how it would look ideally. I would only suggest that it be moved to the top right as in the bottom left there is a chance for it to overlap with the outline.

It would also be nice to be able to collapse it in case it gets in the way :)

[mejo-]

So the original idea was that for Text it would be a floating button next to the line which has the cursor.

I just wanted to mention that we just got rid of the floating menu for links with Nextcloud 26 and that people were constantly annoyed by the floating menu. A button right to cursor position of the editor is less annoying, but still might be a bit too intrusive, given that it travels with your cursor all the time when typing/navigating in the document.

[juliusknorr]

Yes, definitely something to consider. @nimishavijay What do you think? Wouldn't the button changing position all the time be a bit too much when just working with the document?