Uploaded image for project: 'Magnolia UI'
  1. Magnolia UI
  2. MGNLUI-4523

Integrate Extended Token Field

    XMLWordPrintable

Details

    • Story
    • Resolution: Fixed
    • Neutral
    • 6.0
    • None
    • None
    • None
    • Kromeriz 157, Kromeriz 158, Kromeriz 159, Kromeriz 160
    • 5

    Description

      We use Vaadin TokenField in content tagging today. There's another independent implementation called Extended Token Field. Compare the two fields. Are there benefits that would justify switching to the newer implementation?

      https://vaadin.com/directory#!addon/tokenfield
      https://vaadin.com/directory#!addon/extended-token-field

      The second implementation would solve the Remove issue reported in CONTTAGS-29:

      It's too easy to remove tags by mistake because clicking anywhere in the tag removes it. Remove a tag only when the x mark is clicked.

      Goals:

      • Validate Vaadin 8 usage with newer APIs (& V7 compatibility)
      • Consider also that we may want to make the token field a generic Magnolia field. Just like Multivalue and Twin-column, the token field can be used to link the current content item to almost any other items. It is not limited to tags. There's a really nice demo for adding multiple contacts from an address book. The user experience is superior to our current click-intensive link fields.

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                efochr Evzen Fochr
                ahietala Antti Hietala
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Task DoD