Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

TODO list (2.0 branch)

should implement (in no particular order):

  • support new file format
  • integrate new charting API and convert old charting stuff to new charting API
  • use data factories implemented by the reporting engine
  • add generic inspections based on metadata, many existing inspections can be simplified or replaced by generic inspections
  • support changes made to the reporting model made in the preview pane
  • support showing preview data directly in the elements in the design view
  • support dynamic metadata supplied by data factories
  • rearrange or aggregate toolwindows or support a more flexible view manager (e.g FlexDock or preferably a simple one without too many dependencies)
  • add quality feedback to send bug reports (exceptions) with descriptions of the customer directly to JIRA, inbox or server log.
  • support columns, freeform subreports, OLAP stuff available in the new engine version
  • recent files in menu
  • add common actions to toolbar (change font, background, paint, border, align elements etc.)
  • support wizard element (in case it doesn't work like a regular element)
  • support context sensitive help
  • support to visually select and move edges of elements side by side. This makes changing table like layouts much easier.

would implement (in no particular order):

  • create better property editors
  • dropdown palette in color editor directly in property table
  • field chooser as editable combobox directly in property table
  • date chooser with dropdown calendar
  • time chooser with clock
  • formula/styleexpression editors with syntax/error highlighting, code completion
  • SQL query editor supporting syntax highlighting, error detection, code formating for commonly used databases (DB2, PostgreSQL, MySQL, HSQLDB). Implementation might be a challenge, simple keyword highlighting should be easy.
  • configurable menubar/toolbar layout
  • configurable shortcuts (by default use shortcuts also suitable on european keyboard layouts)
  • use ruler units for grid
  • support the zero-configuration dataset bundled in the report designer to minimize configuration frustration for new users
  • add editor dialogs for every element (like paragraph settings in open office). This can be implemented in a generic way using the metadata API of the engine.
  • support to add/edit named styles to elements
  • support styles storable in separate file
  • No labels