Symphony 2.3 User Interface

sym_userinterfaceupdates.markdown

Symphony 2.3 User Interface

JavaScript

Expected

• Implement unified concept for Javascript plugins using .each() and .delegate()
• Make all Javascript plugins chainable
• Update jQuery to latest version
• Update jQuery colour plugin to latest version (http://blog.jquery.com/2011/05/31/jquery-color-v2-beta-1-released/)
• Make sure fields settings don't attach events directly but make use of event delegation
• Make Pickable use data attributes to prevent name clashes (#623)
• Remove deprecated Symphony object variables (e. g. Symphony.WEBSITE)
• Rewrite data source editor using updated Pickable (#623), fix issues with hidden included elements (#641)
• Implement Modenizer like checks into Symphony object

Possible

• [UI Framework] Create a new Notify plugin to be used instead of Symphony.Message (currently Members and other extensions have to replicate core code to initialize systen messages)
• [UI Framework] Create a new Drawer plugin offering a unified interface that can be used by Dashboard, Publish Filtering, EDUI
• [UI Framework] Create a new Tabs plugin offering styles and behaviour for tabbed components (see Publish Tabs, Multilingual Support, Subsection Tabs)
• Allow system messages to be minimised/hidden (using localStorage)

Backend UI

Expected

• General interface refresh
• Unify layout of the core field's preferences in the section editor (field positions, fieldsets)
• Rethink the way Symphony visually notifies the user about extension updates, rethink the install vs. update vs. enable problem
• Introduce a new column "Type" in the list of extensions
• [eKoeS] Distinct indexes for Datasources, Events and Utilities (comes from EDUI)

Possible

• Introduce a collapsible tree view for pages and nested children, make this concept abstract so that it can be used by extensions (e. g. http://symphony-cms.com/discuss/thread/70113/#position-2)

Features

Expected

• Add parameter negation to data source editor directly (#623)
• Add additional tag list options that are already implemented in the Javascript (like singular)

Possible

• Add new data source option to output a distinct list of all available tags in a specified tag list field
• Extended syntax for data source params like {$test?foo:bar} (if $test is set, use foo, bar otherwise) or {$test!foo:bar} (if $testis not set, use foo, bar otherwise)
• Review the "with selected" option and see if helpful options can be added easily to the different areas of the system (e. g. adding data sources to pages, setting or removing page types)
• Replace "Are you sure" dialogs with a Gmail like undo functionality or think about modal boxes offering that don't block the browser
• [eKoeS] Implement filtering for entries, datasources, events & co. ?
• [eKoeS] We need to look at some popular UI extensions to see if there are features that deserve to be promoted to the core