TouchUI Authoring Extensions

Form Components

• Prio 1 Checkbox form component that can remove "true" values and writes Data in JCR as Boolean

• Prio 1 Number textfield form component that validated for a valid number and writes Data in JCR as Integer or Double

• Prio 1 Path browser form component with separate touch-compatible browsing dialog using link wizward or miller clumns (hopefully Adobe will develop it), and with support for dynamically detecting the correct tree root (e.g. site root)

• Prio 2 Slideshow form multifield component

  • Should be possible to rearrange the slides

  • Flexible configuration of the slide panel items in the component definition. Each slide should be able to contain all basic input widgets (selection, text, richtext, image, link...). 

  • Ideally it should be possible to define multiple links per slide, but this would probably make the dialog unusable

• Prio 2 Rich Text: Custom Link Browse Dialog Extension

Paragraph systems

• Prio 1 Template def. Paragraph system

  • Define in page component which components are allowed in which parsys on a page

  • Allow inheritance via super resource type page components

  • Support regular expressions for path matching

  • Allow customizing of markup that is inserted before/after parsys, before/after each component

• Prio 1 Refresh Parent X Infrastructure

  • Allow flexible definition which parts of the parent DOM elements have to be refreshed on a dialog edit event (not only parent or whole page)

DAM-related extensions

• Prio 1 Media reference form component

  • Assigning DAM assets via drag&drop from sidepanel

  • Browsing DAM assets in the repository using path browser component (with browse dialog, see above)

  • Filtering assets by media format

  • Apply cropping based on media format ratios (or is this done directly in the asset?)

• Prio 2 Customized image map form component

  • Extension of the available forms, which can be applied to the image. Currently it is a square and a round regions, which dimensions can be changed. Most project require just a normal pin with predefined width and height (10x10 px)

  • Extension of the edit panel for each map region/pin. The panel should be possible to specify the items of the edit panel in the component definition. Possible configurations should include text, link, image

  • It should be possible to use the cropped image in the map definition

• Prio 2 Enhanced asset side panel

  • Supports filtering by path/subtree

  • Supports filtering by media format

• Prio 2 Automatic assignment of matching media formats and extraction of size-related metadata when binaries are added to DAM

• Later Support multi-language metadata (as already possible for tag manager)

Component Pool

• Later Component pool extension - copy components to pool, inherit from pool, break inheritance

Admin Console

• Later Monitor for Sling Jobs

  • Show running jobs with

  • Filter jobs by certain properties e.g. Site context

  • Show job progress (for jobs that support reporting back its progress)

  • Show job history (if supported by Job API)

  • Ability to cancel running jobs

  • Ability to reorder jobs in job queue or canceling them (if supported by Job API)