This page is used to keep a list of things that can be improved in the client-side javascript area. Feel free to add/comment/update.
there's now always a daisy object available with basic stuff like mountPoint and siteName (see layout.xsl). The document/naveditor specific things for these can be replaced by this.
we need a htmlarea Dialog equivalent for usage outside of the HTML editor context (e.g. for the cases where the document-browser dialog is reused). Dojo has a dialog class but this is for dialogs inside the browser window. Also, need to look into making the dialog sizing things work reliably.
having a global parameter somewhere to enable/disable dojo debug would
be helpful (right now need to change dojo-debug parameter to
daisy-forms-styling.xsl in the sitemap.xmap). Possibly even specified from the
client (e.g. some URL/request parameter to set a session attribute) so that it's
possible to enable dojo debugging just for yourself on a production
server.
improve caching of resources by browser (curently: cached for 5 hours)
replace the current field editor implementations with dojo-widget-based implementations. Consider using the LinkEditor widget from the workflow task screens also in the document editor.
look into enabling ajax for (some of) our cforms
...
long-term bigger things:
make use of dojo modules for all javascript stuff (except those on pages which don't load dojo of course)
rewrite tree editor widget as dojo widget, add collapse/expand and drag-and-drop
modernize our htmlarea codebase (possibly based on dojo editor?)
Things that could be improved by use of js:
dropdown-completion list for query language entry (i.e. auto-completion of schema type names etc.)
dialogs of the html editor:
use spinner widget for specifying table rows/cols when inserting new table
...
...
| Name | Value |
|---|---|
| Category | Design documents & proposals |