Difference between revisions of "WikiDB/Feature requests"

From TestWiki
Jump to: navigation, search
m
(Some feature suggestions)
Line 18: Line 18:
 
* some form of display size control - for large table it would be nice to add a syntax for specifying a display range, or using some default size, where it would display rows 1-20 and a link for "next 20" etc. even for the data records in the table definition itself it would be useful - one cannot view all records in large tables, due to the long processing time. I have a table with several thousands of entries and I get a PHP error indicating time limit exceeded after 30 seconds
 
* some form of display size control - for large table it would be nice to add a syntax for specifying a display range, or using some default size, where it would display rows 1-20 and a link for "next 20" etc. even for the data records in the table definition itself it would be useful - one cannot view all records in large tables, due to the long processing time. I have a table with several thousands of entries and I get a PHP error indicating time limit exceeded after 30 seconds
 
[[User:Osishkin|Osishkin]] 11:19, 22 July 2010 (BST)
 
[[User:Osishkin|Osishkin]] 11:19, 22 July 2010 (BST)
 +
 +
: That's definitely a good idea!  It should be relatively simple to add paging functionality to the data tab, though I think doing this in-page might be tricky.  Adding a 'limit' argument to the <repeat> tag should be simple enough, but allowing you to page through it in-page would involve designing and building the appropriate API handlers, which is not something I'm quite ready to embark upon yet.
 +
: However, thinking about the data tab, it occurs to me that there are other things that could be added here, e.g. the ability to sort or filter the data and to hide columns in the output.  The back-end code for this is already in place, so it shouldn't be too hard to add the UI for it.
 +
: If that functionality were added it would be relatively trivial (I think) to add a 'more...' link to the bottom of the output for repeat tags that are not showing all available rows, which would link through to the data tab, with the appropriate view.
 +
: I am currently trying to get a new release out, so I'm not considering new features at this point, but once it's out I'll try and put together some form of road-map for WikiDB, and this will be on it! --[[User:HappyDog|HappyDog]] 21:44, 7 August 2010 (BST)

Revision as of 20:44, 7 August 2010

Please add any feature requests which you may have for WikiDB to this page.

Before adding new suggestions, please check WikiDB/Features, WikiDB/ToDo and WikiDB/Bugs to ensure that it is not already covered by one of those.

Ignore link syntax in criteria when filtering on link fields

I'd like to submit one feature request, though I'm not sure how plausible it is. I came across this issue: I have a value I'd like to display elsewhere which is identified by one field's data being "ES012". However, for display purposes, the value as it is entered is "[[ES012]]", as I need it to display in a wikilink. Thus, I've defined the column as "wikistring", as this appears neccisary to make the link display correctly. Here is where my issue comes in: to repeat the data, I must put

criteria="Description=[[ES012]]"

rather than the more intuitive

criteria="Description=ES012"

So again, I'm not sure if it's possible or plausible to strip out the wikilink symbols when searching the table with the repeat tag, but it's something I'd very much like to see.

-- (sent by User:InShaneee, via e-mail)

Some feature suggestions

Afer some toying around with the extension I have several "Nice to have" features believe would be beneficial that I haven't seen mentioned

  • repeat tag syntax - besides being able to specify the table header, it would also be nice to have a possibility to add an index column, listing the number of the row in the resulting table
  • some form of display size control - for large table it would be nice to add a syntax for specifying a display range, or using some default size, where it would display rows 1-20 and a link for "next 20" etc. even for the data records in the table definition itself it would be useful - one cannot view all records in large tables, due to the long processing time. I have a table with several thousands of entries and I get a PHP error indicating time limit exceeded after 30 seconds

Osishkin 11:19, 22 July 2010 (BST)

That's definitely a good idea! It should be relatively simple to add paging functionality to the data tab, though I think doing this in-page might be tricky. Adding a 'limit' argument to the <repeat> tag should be simple enough, but allowing you to page through it in-page would involve designing and building the appropriate API handlers, which is not something I'm quite ready to embark upon yet.
However, thinking about the data tab, it occurs to me that there are other things that could be added here, e.g. the ability to sort or filter the data and to hide columns in the output. The back-end code for this is already in place, so it shouldn't be too hard to add the UI for it.
If that functionality were added it would be relatively trivial (I think) to add a 'more...' link to the bottom of the output for repeat tags that are not showing all available rows, which would link through to the data tab, with the appropriate view.
I am currently trying to get a new release out, so I'm not considering new features at this point, but once it's out I'll try and put together some form of road-map for WikiDB, and this will be on it! --HappyDog 21:44, 7 August 2010 (BST)