Labs
  1. Labs
  2. LABS-361

[richtext] Make parsing of loaded strings optional and not always present

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: Current
    • Fix Version/s: Future
    • Component/s: Magma
    • Labels:
      None

      Activity

      Hide
      Simone Gianni added a comment -

      Due to how converters are implemented, when a meta-type (like richtext) is used, often double conversion occurrs. The first conversion is from the underlying type (like string) to the meta type, the second is from the metatype back to string to display it. When the content is modified by a form, it again happens twice.

      If conversion is rather simple, this poses no problem, but the whole idea behind underlying meta types is to offer better conversion and validations, so most probably converters will not be that simple.

      This can be desiderable in some context, for example if I'm migrating an already existing database that contains rich text fields, but previous contents were unfiltered, filtering them upon load can ensure proper formatting of the page, or while changing validation settings dureing developement.

      But it is overkill for most situations, and wastes a lot of cpu time parsing and reparsing HTML.

      Show
      Simone Gianni added a comment - Due to how converters are implemented, when a meta-type (like richtext) is used, often double conversion occurrs. The first conversion is from the underlying type (like string) to the meta type, the second is from the metatype back to string to display it. When the content is modified by a form, it again happens twice. If conversion is rather simple, this poses no problem, but the whole idea behind underlying meta types is to offer better conversion and validations, so most probably converters will not be that simple. This can be desiderable in some context, for example if I'm migrating an already existing database that contains rich text fields, but previous contents were unfiltered, filtering them upon load can ensure proper formatting of the page, or while changing validation settings dureing developement. But it is overkill for most situations, and wastes a lot of cpu time parsing and reparsing HTML.
      Hide
      jan iversen added a comment -

      outdated and closed, if not correct please reopen.

      Show
      jan iversen added a comment - outdated and closed, if not correct please reopen.

        People

        • Assignee:
          Unassigned
          Reporter:
          Simone Gianni
        • Votes:
          0 Vote for this issue
          Watchers:
          1 Start watching this issue

          Dates

          • Created:
            Updated:
            Resolved:

            Development