Announcing gnatsweb 2.9.0

Announcing gnatsweb 2.9.0

[Yngve Svendsen]

A new release of Gnatsweb is available for download.

The version number is 2.9.0. A couple of features were backported from the 
imminent Gnatsweb 4.0, a couple of bugs were squashed and some small 
submitted patches were incorporated.

Gnatsweb 2.x won't work with the upcoming Gnats 4. Versions working with 
Gnats 4 will have version numbers starting with a '4'. Patches and 
contributions for version 2.x are still welcome, even though no further 
releases are currently planned. The Gnatsweb 2.9.0 distribution (60 kB) is 
available at ftp://ftp.gnu.org/pub/gnu/gnatsweb/ immediately.

This is the entry for 2.9.0 in the NEWS file of the distribution:

Changes from 2.8.2 to 2.9.0
* Usability enhancement. There is now a navigation bar on top of all
   pages with links to all major Gnatsweb functions.
* Bug fix. Properly handle a locked GNATS database. This used to make
   Gnatsweb bomb out when submitting edits and leave the PR locked.
* Minor bug fixes related to attachments.
* Add X-Mailer header to outgoing mail.
* Bug fix. Text attachments are no longer truncated at the first blank
   line.

Yngve Svendsen
Gnatsweb maintainer

patch to gnatsweb 2.9.0

[Robert Lupton the Good]

[-- Attachment #1: Type: text/plain, Size: 1711 bytes --]

I've finally got around to forward-porting some of my 2.7 changes.

Here's a patch that:

	1/ Adds a button to load stored queries; they can then
	be modified and submitted.  This provides a way to edit
	stored queries.

(Note: this uses a hidden atribute 'full_cmd' to avoid making the
submit/delete/load stored query too wide with long labels)

	2/ Supports a callback
		cb('init_prefs', '');
	to set values in %global_prefs after init_prefs has run.


	3/ Include the date that a query was submitted in the result
	page.  This is very useful when the query is printed and filed
	away.

	This is only done if $global_prefs{'show date'} is true
	(default: 1).  I'm not quite sure that I did this in the
	approved manor.


I did not update the docs; your discussion of stored queries is pretty
short, and I didn't know how you want to do this.  Here's some sample HTML:

<dl>
<dt><b>submit stored query</b> (button and combobox)
<dd>If there are stored queries (done on the <a href="#qmatches">Query Results Page</a>),
    this selects one of them.  If no queries are stored, then
    this field is not displayed.
<dt><b>delete stored query</b> (button and combobox)
<dd>If there are stored queries (done on the <a href="#qmatches">Query Results Page</a>),
    this deletes one of them.  If no queries are stored, then
    this field is not displayed.
<dt><b>load stored query</b> (button and combobox)
<dd>If there are stored queries (done on the <a href="#qmatches">Query Results Page</a>),
    this loads one of them into the various fields on this page as if you'd
    just typed them in; this allows you to edit a stored query.
    If no queries are stored, then this field is not displayed.
</dl>

			R



[-- Attachment #2: patch1 --]
[-- Type: text/html, Size: 9012 bytes --]

Announcing gnatsweb 2.9.0

[Robert Lupton the Good]

A minor bug in gnatsweb 2.9.0:

In submitedit, the scope of $mail_sent is the LOCKED block, but it's
referred to at main scope at the bottom of the routine:
    page_heading($page, ($mail_sent ? 'Edit successful; mail sent'
                         : 'Edit successful'));

(Fix: move "my $main_sent = 0;" up the routine)



					R

Re: Announcing gnatsweb 2.9.0

[Yngve Svendsen]

At 11:20 13.09.2001 -0400, Robert Lupton the Good wrote:

>A minor bug in gnatsweb 2.9.0:
>
>In submitedit, the scope of $mail_sent is the LOCKED block, but it's
>referred to at main scope at the bottom of the routine:
>     page_heading($page, ($mail_sent ? 'Edit successful; mail sent'
>                          : 'Edit successful'));
>
>(Fix: move "my $main_sent = 0;" up the routine)

Thanks. This bug shouldn't have any effect whatsoever on the way Gnatsweb 
works, except for the words "mail sent" never being printed, but if there 
ever is a 2.9.1, I will certainly apply this fix.

Yngve Svendsen
Gnatsweb maintainer