next »

[spraxyt]

I'm not convinced Accepted means a lot at present, though Vote Count would be useful. I suggest this could be headed VC, though with 'VC = Vote Count' added to the 'key' block to explain the acronym.

I notice a slight inconsistency has crept in alongside sorting - the key block is headed 'Pugit Items - ordered by Response Due date'; I suggest making this 'Current PUGIT Items'. However (see later), is this needed at all?

With regard to making this the default user interface - I suggest going for it once the VC column has been added. I think the "Comments welcome in 'The PUG place' forum." text is no longer needed since it says this in the Note, (with link); it could be changed to "Click here to display the extended User Interface".

However, yet more thoughts; does the 'Note' paragraph really merit being described as such? Could it be promoted ahead of the 'Hint' and given full paragraph status ("This list shows all current items …"). If this was done the Title line in the key block (currently 'Pugit Items - ordered by Response Due date') becomes redundant; it could be replaced by the ex-Note paragraph, but perhaps that paragraph is too long to fit comfortably there.

David

[MauriceB]

Now added 'Vote Count to the table to make it more effective. 

M

[spraxyt]

Excellent, I like it.

This may be a design feature of how IE7 works (on XP Home SP2), but if I sort the table on any column, then click the page-refresh button the display reverts to the default. Is there an HTML option to reinstate the sort?

David

[MauriceB]

Not sure what you would expect it to do?  Page refresh pulls a new page with the default data, whilst the table sort is done on the page using a bit of javascript?

No data passes back to the page generation code.

[spraxyt]

For the standard PUGIT interface, if I set Status = Pending Closure (for example) and press Submit Query 3 lines are displayed.

If I then press the Refresh button (or in fact return to the page later) the page comes up with Pending Closure selected and 3 lines displayed. So the Query must be stored somewhere.

It's probably wishful thinking on my part but I wondered if the same could be achieved with the sort status on the Stats page? It's not a major issue but if I don't ask …

But, of course, we've had discussions in the past on whether the query should reset before the table is fetched. 

[MauriceB]

For the standard PUGIT interface, if I set Status = Pending Closure (for example) and press Submit Query 3 lines are displayed.

If I then press the Refresh button (or in fact return to the page later) the page comes up with Pending Closure selected and 3 lines displayed. So the Query must be stored somewhere.

Yes.  But that is applying a filter to the data fetched from the database to only show the Pending Closure items and that is stored until you do a reset.  If you now Sort on any column and note the result, then refresh the page, you will note that the columns have reverted to their original status?

It's probably wishful thinking on my part but I wondered if the same could be achieved with the sort status on the Stats page? It's not a major issue but if I don't ask …

Well yes. But it's a lot more code and I'm not convinced of the need?

But, of course, we've had discussions in the past on whether the query should reset before the table is fetched. 

There is difference in the requirements for the PUGIT admin interface and the Stats pages.  I'm looking at 'fixing' the Stats bit real soon now

Maurice

[spraxyt]

Yes.  But that is applying a filter to the data fetched from the database to only show the Pending Closure items and that is stored until you do a reset.  If you now Sort on any column and note the result, then refresh the page, you will note that the columns have reverted to their original status?

Yes, it does as you say though I hadn't realised that.

Having raised the point and had this discussion, so I understand why, I'm happy with the behaviour as it is - quite chuffed to have this in the PUGIT Admin's armoury.
Thanks Maurice

David2