Provide field widgets

Created on 9 June 2024, 5 months ago
Updated 13 June 2024, 5 months ago

Problem/Motivation

Since I see intention to move interpolator to "ai" module (aligining with starshot) or even maybe changing the name, could we go a step further, and align it to usual editor workflow? Could interpolations run when user interact with widgets?

For example, I edit an article and click "generate image" next to the image field (instead of uploading an image), next I go to audio field and click "generate audio" (instead of uploading it), next I go to a text field and select one of configured interpolator options and click "Generate". If I do not like the text, I click "Re-generate" or choose another interpolator. All inline the moment user is writing the article, part of editor workflow, the same way people are used to using Drupal.

There could be multiple interpolations setup for the same field, so user could, for example, choose what kind of image to generate, or what kind of audio, interpolating from what fields. There could multiple alternative interpolators setup for each node, optional and initiated on user request.
Its quite a task, so maybe augmentor team could help out with widgets if it becomes official Drupal solution? We could merge it all.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Feature request
Status

Active

Version

1.0

Component

Code

Created by

🇱🇹Lithuania mindaugasd

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @mindaugasd
  • 🇩🇪Germany marcus_johansson

    I have already started experimenting with this one, including to incorporate it into CKEditor with disposable entities. It will be possible, however this ticket is kind of a blocker: https://www.drupal.org/project/ai/issues/3453581 📌 AI Interpolator v2: Allow multiple rules on one field Active

    So, it would be worked on for the AI Interpolator v2, which will 99.99% be part of the AI module. Can we move the ticket there somehow? Also its marked as bug, I guess that is wrong? :)

  • 🇨🇦Canada mandclu

    +1 for considering this a feature request instead of a bug. Moving this to the AI issue queue is also worth consideration.

    I will add that the ability to manually trigger processing directly within the UI is what really got me excited about Augmentor. The approach taken there is to have the site builder define new fields for the buttons that trigger the processing. I'm not sure if that's the best approach, but there is a successful implementation there to consider. Alternatively it might be possible to look at something that could leverage third party settings, and hook_field_widget_complete_form_alter() or something similar to add controls to existing widgets.

  • 🇨🇦Canada mandclu

    +1 for considering this a feature request instead of a bug. Moving this to the AI issue queue is also worth consideration.

    I will add that the ability to manually trigger processing directly within the UI is what really got me excited about Augmentor. The approach taken there is to have the site builder define new fields for the buttons that trigger the processing. I'm not sure if that's the best approach, but there is a successful implementation there to consider. Alternatively it might be possible to look at something that could leverage third party settings, and hook_field_widget_complete_form_alter() or something similar to add controls to existing widgets.

  • 🇱🇹Lithuania mindaugasd

    Indeed not a bug :-)

    I am moving issue to https://www.drupal.org/project/ai

    Issue description will need an update after further discussion.

    We just had discussion about widgets in this issue 📌 Create simple way to iterate for rule Active , which produced some very interesting ideas. Summary:

    • expose backend configuration to the frontend (as widgets and popup modals)
    • anyone could be able to create any user interface of AI tool they need.
    • user interfaces could probably be shared and installed between developers using Drupal recipes.
Production build 0.71.5 2024