Difference between revisions of "WikiDB/Roadmap"

From TestWiki
Jump to: navigation, search
(Syntax: Removed item that is fixed (will be in next release of WikiDB).)
(Added items moved from WikiDB/Features. Some were already present in a different formulation, in which case I have merged them.)
Line 5: Line 5:
 
The bug list has been moved to [[WikiDB/Bugs]].  Please report bugs there.
 
The bug list has been moved to [[WikiDB/Bugs]].  Please report bugs there.
  
== Back-end ==
+
== Planned features (in progress) ==
 +
 
 +
=== Back-end ===
 
* Add 'date' data-type.
 
* Add 'date' data-type.
 
* Joins in queries
 
* Joins in queries
 
* Foreign key definitions
 
* Foreign key definitions
  
== Syntax ==
+
=== Syntax ===
 
* Repeat tag syntax - some things to iron out (see [[WikiDB/Repeat tag syntax]] for the discussion)
 
* Repeat tag syntax - some things to iron out (see [[WikiDB/Repeat tag syntax]] for the discussion)
* Repeat tag - Allow LIMIT argument (or maybe 'range').
+
* Repeat tag - Add boolean NOT operator (AND, OR and XOR are implemented, but NOT is unary and therefore trickier).
 +
* Repeat tag - Add ability to compare fields with each other.
 +
* Repeat tag - Allow LIMIT argument (or maybe 'range'), possibly with pagination.
 
* Provide a mechanism for 'pass-through' parameters to the <data> tag (i.e. parameters that are supplied to the template, but which don't get added to the table).  Suggestion is to prefix the name with an exclamation mark.  Alternatively, an underscore could be used, as this is already reserved in table definitions, and therefore is not allowed in data tags (though this is not enforced) - may kill two birds with one stone...
 
* Provide a mechanism for 'pass-through' parameters to the <data> tag (i.e. parameters that are supplied to the template, but which don't get added to the table).  Suggestion is to prefix the name with an exclamation mark.  Alternatively, an underscore could be used, as this is already reserved in table definitions, and therefore is not allowed in data tags (though this is not enforced) - may kill two birds with one stone...
  
== Code Tidying ==
+
=== Interface ===
 +
* Highlight 'bad' data on the table's data page.
 +
* Add filtering/ordering functionality to the data tab.
 +
 
 +
=== Code Tidying ===
 
* Add profiling statements.
 
* Add profiling statements.
  
== Administration ==
+
=== Administration ===
 
* 'What links here' should show templates that are included via data tags.
 
* 'What links here' should show templates that are included via data tags.
  
== i18n / L10n ==
+
=== i18n / L10n ===
 
* Ensure all user-visible strings come from the message cache.
 
* Ensure all user-visible strings come from the message cache.
 
* The 'number' data type is not currently locale aware on input (renders correctly).
 
* The 'number' data type is not currently locale aware on input (renders correctly).
 +
 +
== Other possible features (speculative) ==
 +
These are some thoughts on later developments, for further down the line.
 +
 +
=== Interface ===
 +
* Form-based data entry.
 +
 +
=== Data linking ===
 +
* Ability to specify joins between tables.
 +
* Able to specify relationships between data, e.g. 'is a type of'

Revision as of 23:37, 30 May 2015

This is an (incomplete) list of features that I plan to add. There are also good ideas from other people scattered around the wiki, which I should really add to this page, but haven't yet.

Note that this page reflects my current development version - if an item is removed from this page due to being implemented, it may not turn up in a public release for a little while.

The bug list has been moved to WikiDB/Bugs. Please report bugs there.

Planned features (in progress)

Back-end

  • Add 'date' data-type.
  • Joins in queries
  • Foreign key definitions

Syntax

  • Repeat tag syntax - some things to iron out (see WikiDB/Repeat tag syntax for the discussion)
  • Repeat tag - Add boolean NOT operator (AND, OR and XOR are implemented, but NOT is unary and therefore trickier).
  • Repeat tag - Add ability to compare fields with each other.
  • Repeat tag - Allow LIMIT argument (or maybe 'range'), possibly with pagination.
  • Provide a mechanism for 'pass-through' parameters to the <data> tag (i.e. parameters that are supplied to the template, but which don't get added to the table). Suggestion is to prefix the name with an exclamation mark. Alternatively, an underscore could be used, as this is already reserved in table definitions, and therefore is not allowed in data tags (though this is not enforced) - may kill two birds with one stone...

Interface

  • Highlight 'bad' data on the table's data page.
  • Add filtering/ordering functionality to the data tab.

Code Tidying

  • Add profiling statements.

Administration

  • 'What links here' should show templates that are included via data tags.

i18n / L10n

  • Ensure all user-visible strings come from the message cache.
  • The 'number' data type is not currently locale aware on input (renders correctly).

Other possible features (speculative)

These are some thoughts on later developments, for further down the line.

Interface

  • Form-based data entry.

Data linking

  • Ability to specify joins between tables.
  • Able to specify relationships between data, e.g. 'is a type of'