public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: "Stuart Stevens" <stuart_stevens@sierralogic.com>
To: "'Chad Walstrom'" <chewie@wookimus.net>, <help-gnats@gnu.org>
Subject: RE: Changes to gnatsweb.pl
Date: Tue, 28 Sep 2004 14:46:00 -0000	[thread overview]
Message-ID: <E1C9qTS-0006rD-Tu@lists.gnu.org> (raw)
In-Reply-To: <20040920163312.GI30447@wookimus.net>

Chad

Yes, the "sections" is hackish.  Better if attributes could be added to the
GNATs fields and then define well known attributes. I wanted to key off of
the database so the hack keys off of dummy fields that are enums with a
single value which is the title.  The gnatsweb.pl script catches field names
beginning with "Separator" and treats them specially.  Removes them from the
query forms and adds them to the view and edit pages.  For non gnatsweb
users these fields help break up the form still.

field "Separator1" {
    enum {
        values { "Problem Description" }
        default "Problem Description"
    }
}

Sections displays a single table row with the background color of the header
and text displayed as "H1".  The purpose is to break up the form into
sections that different people are responsible for.  There are some links at
the top of the page to take the user directly to the section they are
interested in.  Within the section there is a button which duplicates the
button at the top and bottom of the web page (edit or submit for view or
edit pages) (as you pointed out below).  We are using four sections that
break the edit and view pages into five sections

(initial section without a title) - 18 fields
Problem Description - Originator and problem fields (14)
Fix - Developer and fix info (17)
Verification - QA info (5 and expected to grow) 
Miscellaneous - Unformatted followed by audit-trail



-----Original Message-----
From: help-gnats-bounces+stuart_stevens=sierralogic.com@gnu.org
[mailto:help-gnats-bounces+stuart_stevens=sierralogic.com@gnu.org] On Behalf
Of Chad Walstrom
Sent: Monday, September 20, 2004 9:33 AM
To: help-gnats@gnu.org
Subject: Re: Changes to gnatsweb.pl

Stuart Stevens wrote:
> 2. Sections were added by creating dummy field entries in the GNATS
>    database.  Each field began with the word "Separator" and the
>    description field contained the text of the separation.

That sounds like a hack.  Effective, no doubt, but hackish.  What do you
mean by "sections"?

>    Quick links were added to the top of the web page.  "edit" or
>    "submit" buttons were added to the "view" and "edit" pages.

Useful.  However, isn't the "edit" and "submit" buttons already shown on the
view and edit pages, respectively?

-- 
Chad Walstrom <chewie@wookimus.net>           http://www.wookimus.net/
           assert(expired(knowledge)); /* core dump */



_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnats

  reply	other threads:[~2004-09-21 19:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-18 14:54 Stuart Stevens
2004-09-20 20:32 ` Chad Walstrom
2004-09-28 14:46   ` Stuart Stevens [this message]
2004-09-21 19:33 ` Yngve Svendsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1C9qTS-0006rD-Tu@lists.gnu.org \
    --to=stuart_stevens@sierralogic.com \
    --cc=chewie@wookimus.net \
    --cc=help-gnats@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).