[ Return to Bugs & Features | Post Text | Post File | Prev | Next ]

STR #1940

Application:	FLTK Web Site
Status:	5 - New
Priority:	1 - Request for Enhancement, e.g. asking for a feature
Scope:	3 - Applies to all machines and operating systems
Subsystem:	Unassigned
Summary:	STR search wish list
Version:	Web Site
Created By:	AlbrechtS
Assigned To:	Unassigned
Fix Version:	Unassigned
Update Notification:	Receive EMails Don't Receive EMails

Trouble Report Files:

No files

Trouble Report Dialog:

	Name/Time/Date	Text
	AlbrechtS 04:07 Apr 24, 2008	I would like to see some more options for searching STRs on the FLTK STR search page. All the following should not change existing behavior, but be additional options. It would be sufficient to add (some of) them to the documentation as options like "version:..." (1) sort STRs by number (for better overview) (2) sort STRs by modification date     (opt. (1) would obviously sort by creation date, so this would      not be needed as a sort option) (3) select STRs by creation and/or modification date (3a) either by a date range (3b) or like "changed during the last <n> days" (3c) or both (only one at a time) Option 1 would enable something like a historical overview, options 2 and 3 would let you see what has changed since your last visit to the STR page.
	AlbrechtS 08:19 Apr 24, 2008	And one more: When looking at one STR, e.g. this one http://www.fltk.org/str.php?L1940 there should be a "previous" and a "next" button/link to walk through the STRs sequentially.
	AlbrechtS 01:20 Apr 25, 2008	And still one more: The title of the HTML page should reflect the "Summary:" item (title) of the STR. Right now it is (for this STR) "STR #1940 - Fast Light Toolkit (FLTK)" A better title would be "STR #1940 - STR search wish list". This is because you would (a) see the subject in the browser window title, and (b) bookmarks (at least in firefox) get the window title in their description by default. Thus I am used to change the bookmark properties after adding a bookmark for an interesting STR - this would not be necessary any more after this change.
	AlbrechtS 01:28 Apr 25, 2008	I would also like to see that STR changes would be mirrored to fltk.bugs, even after the STR has been assigned to a developer (which is not the case now, IIRC - I don't know the rules exactly, but I know that I don't see STR changes in fltk.bugs for some STRs). I'm using fltk.bugs to see all changes, and maybe I would want to reply to a change in an STR, but I don't see it, if the STR has been assigned already. That's annoying, because you never know, when an STR would be assigned to a developer. The only way is to register for mail notification, but that's a different source of information that needs to be checked (and you would see the same STR change twice, before it is assigned...).
	AlbrechtS 03:13 Apr 25, 2008	This one has nothing to do with "search", but I think that it could be useful to add a new STR state "close pending", if a developer wants to close the STR after a fix. This would achieve the following: (1) Other users would still see the STR, if they search _open_ STRs. (2) Users could still reply to an STR after a fix to confirm that it works, or to suggest to reopen the STR. STRs in the state "close pending" would be closed automatically or by the assigned developer after one or two weeks - maybe the developer would get a notification ... But maybe I'm only dreaming ;-) Why would I want this? Sometimes I don't check STRs dayly, and I saw some STRs closed after a few hours with or without solution.
	matt 13:21 Apr 25, 2008	Added summary (SVN 493) Added prev and next (SVN 494)