XWiki Platform
  1. XWiki Platform
  2. XWIKI-7820

When using the 'Long Text' field, preview/load the WYSIWYG/Text/PureText editor in the 'Structure' step of the Wizard when the user hits 'Apply changes'

    Details

    • Type: Improvement Improvement
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 4.0
    • Fix Version/s: None
    • Component/s: App Within Minutes
    • Labels:
      None
    • Difficulty:
      Unknown
    • Similar issues:
      XWIKI-6634Attempt to go through all the remaining steps when finish is triggered in a wizard
      XWIKI-2705WYSIWYG Editor is not refreshing when you modify font-size or font-family of some text, letting think user that it is not working
      XWIKI-6635Add support for non-interactive wizard steps
      XWIKI-7795The browser back button doesn't restore unsaved changes in step 2 of App Within Minutes wizard
      XWIKI-7532UI Issue on WYSIWYG Editor when editing Application Class
      XWIKI-8619Use livetable's column 'list' type instead of 'text' when displaying list fields in AppWithinMinutes's homepage livetable
      XWIKI-5602text inside Macro's is changed
      XWIKI-11033Rename the "Default editor to use" Text entry from user's profile
      XWIKI-2859Text is moved on the next line when hitting enter after a link
      XWIKI-8649Error when changing the number type of a field from an application

      Description

      When the user is using 'Static List', 'User', 'Group', 'Database List' fields and he configures them, any change is applied in the preview after hitting the 'Apply changes'.

      Same should be for the 'Long Text' field when the user is changing the Editor type. For this field type, changing the number of rows works in the preview.

      Reasons:

      • consistency in behavior with the other field types and with other properties for the same field type;
      • previewing the change will clarify the user about what 'Text', 'PureText', 'WYSIWYG' means, since these options are not descriptive at all (what's the difference between text and pure text, etc.);
      • preserves the WYSIWYG feel for the wizard, imitating the look in the View mode;
      • the user doesn't need to go to the View mode to see what those options are about.

      Possible problems:

      • maybe some performance issues?

        Activity

        Hide
        Marius Dumitru Florea added a comment -

        Last time I talked with Ludovic about this he was somehow against it. He preferred to "simulate" the WYSIWYG editor, i.e. display a fake tool bar.

        Loading the WYSIWYG editor with minimum options shouldn't generate performance issues (as long as you don't increase the number of Long Text fields too much).

        Show
        Marius Dumitru Florea added a comment - Last time I talked with Ludovic about this he was somehow against it. He preferred to "simulate" the WYSIWYG editor, i.e. display a fake tool bar. Loading the WYSIWYG editor with minimum options shouldn't generate performance issues (as long as you don't increase the number of Long Text fields too much).

          People

          • Assignee:
            Unassigned
            Reporter:
            Ecaterina Moraru (Valica)
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Date of First Response: