[Feature Request]: Unified Text Field Editor

[CyanVoxel]

Checklist

• I am using an up-to-date version.
• I have read the documentation.
• I have searched existing issues.

Description

As of #1354, TEXT_LINE and TEXT_BOX fields are now a single TextField type differentiated by an is_multiline boolean column in the database. As the difference is now superficial, I believe that this should be a toggleable option inside a unified text editor modal. As new options are added in the future (e.g. rich text options, hyperlink options, etc.) the single text editor interface can be added upon to handle all future TextField attributes.

Solution

Unified Text Field Mockup

Switching from "Single Line" mode to "Multiple Lines" mode

Alternatives

The mockups are one potential approach, which tries to also accommodate for the future ability to edit field titles as well as potential rich text editing options. Because there might be unconventional options in TagStudio such as treating an entire text field's contents as a hyperlink, or changing the the rendering mode from plain text to markdown to HTML, or enabling/disabling syntax highlighting, the UI will need to avoid becoming too cluttered as time goes on. Perhaps that's out of the scope of this feature request though, and a simple "Single Line/Multiple Lines" view toggle will suffice for now.

[TrigamDev]

• I believe it'd be better to have the single line/multiple lines control be a toggle, with two adjacent buttons with no gap between them, and have each button use an icon rather than text. The single button approach takes up a large amount of space, and the way it displays the currently selected state is a little unintuitive.
• It'd be better to have the rich text editor be separated into it's own component that can be used elsewhere if needed (based on the fact the buttons are on the same line as the "Field Text" label, I assume it isn't).

[CyanVoxel]

• I believe it'd be better to have the single line/multiple lines control be a toggle, with two adjacent buttons with no gap between them, and have each button use an icon rather than text. The single button approach takes up a large amount of space, and the way it displays the currently selected state is a little unintuitive.

  • It'd be better to have the rich text editor be separated into it's own component that can be used elsewhere if needed (based on the fact the buttons are on the same line as the "Field Text" label, I assume it isn't).

Agreed on both