| Date Of Receipt: 16-OCT-1996 12:33:57.87
From: SEAN::davidson "D. Sean Davidson 16-Oct-1996 1231"
To: sean::smart
CC: sean::odehelp, sean::harty, sean::davidson
Subj: re: srequest stuff
------- Forwarded Message
Date: Wed, 16 Oct 96 11:24:53 -0400
From: James Smart USG <smart@witsend.zk3.dec.com>
To:
cc: harty
Subject: srequest stuff
Geez - this ptc srequest stuff is nutso.
Being unable to enter file lists and/or diffs (including just a pointer to
diffs) via the gui interface, I now tried to use
"srequest -term -update <sreq>". Do I really have to pop into the editor
over 10 times to enter the responses for each subsection ? Boy, the earlier
srequest process whereby I jumped into the editor once and just filled things
out is much easier.
And I still was not given an opportunity to update the file list (bstat -all)
and diffs (bdiff...) sections on the form. After asking for the file list,
it jumped right to asking me whether it should submit the modified form (or
quit, or restart the whole process over again).
>
> The new srequest automatically updates the bstat and bdiff information when
> and update is performed. No more do you have to edit those sections to
> contain your current set of files for a sandbox. The list of files is
> presented at the beginning of the srequest session unless you specify -all
> on the command line. You can also have it point to a user specified bdiff
> output log that was done prior to the srequest session by answering the
> question 'How do you want the bdiff's represented [i|l|p] ?' by responding
> with a 'i' to include the bdiff's, 'l' to specify the location of the bdiff's
> to be included or 'p' to just place the path to the bdiff logs that were
> previously generated.
>
> Including files in the gui version is just a matter of using mouse button 3
> while positioned over any multiple line text area. Normal window cut and
> paste works also for multi and single line text areas.
>
> The terminal interface is just a fall back for when an X display device is
> not available (e.i. working from home on a vt220 terminal.).
>
Also, I want to add the abstract lines (which include severity) into the
QAR field that the submit is in response to... I can't. Not only is there
not enough room for all the QAR numbers the submit corresponds to, but
multi-line input like this can't be done (this is true for both the GUI and
the terminal versions).
>
> The QAR/CLD/SPR field has been expaned to accept multiple lines.
>
My recommendation is to trash both of these new processes and revert to
what we have been doing in the past.
-- James
------- End of Forwarded Message
|
| Date Of Receipt: 16-OCT-1996 13:01:42.66
From: SEAN::"smart@witsend.zk3.dec.com"
To: davidson@sean.zk3.dec.com, smart@sean.zk3.dec.com
CC: harty@sean.zk3.dec.com, odehelp@sean.zk3.dec.com
Subj: re: srequest stuff
My comments prefixed by "J>"
When is the odeman page for "srequest" going to be updated ?
There is no mention of "-term" or of any of this other behavior as well
(or hopefully I wouldn't be bugging you so much).
-- James
------- Forwarded Message
Date: Wed, 16 Oct 96 11:24:53 -0400
From: James Smart USG <smart@witsend.zk3.dec.com>
To:
cc: harty
Subject: srequest stuff
Geez - this ptc srequest stuff is nutso.
Being unable to enter file lists and/or diffs (including just a pointer to
diffs) via the gui interface, I now tried to use
"srequest -term -update <sreq>". Do I really have to pop into the editor
over 10 times to enter the responses for each subsection ? Boy, the earlier
srequest process whereby I jumped into the editor once and just filled things
out is much easier.
J> Any easier way to not have to enter the editor 10 times ?
And I still was not given an opportunity to update the file list (bstat -all)
and diffs (bdiff...) sections on the form. After asking for the file list,
it jumped right to asking me whether it should submit the modified form (or
quit, or restart the whole process over again).
>
> The new srequest automatically updates the bstat and bdiff information when
> and update is performed. No more do you have to edit those sections to
> contain your current set of files for a sandbox. The list of files is
> presented at the beginning of the srequest session unless you specify -all
> on the command line. You can also have it point to a user specified bdiff
J> I never specified "-all" for the gui, so I assume this is for the -term
J> option only ? (then again, on the update via -term, I didn't specify -all
J> and I was never prompted for a file list as well). Since I didn't get a
J> file list in via the gui, how (or what) would the "update" have used for
J> a file list ?
J>
J> Given that the update via -term didn't prompt for file list, and assuming
J> that an update uses the existing file list (hopefully obtained properly
J> in the creation), how would I go about updating the srequest with
J> additional files.
> output log that was done prior to the srequest session by answering the
> question 'How do you want the bdiff's represented [i|l|p] ?' by responding
> with a 'i' to include the bdiff's, 'l' to specify the location of the bdiff's
> to be included or 'p' to just place the path to the bdiff logs that were
> previously generated.
J> I assume this is if created via -term. In no case, creation via gui or
J> update via -term was I asked this question.
> Including files in the gui version is just a matter of using mouse button 3
> while positioned over any multiple line text area. Normal window cut and
> paste works also for multi and single line text areas.
J> Ok. Now that I know about this, I'll have to try it.
J> Note: When I created (and updated) the srequest via the gui, I was cut
J> and pasting into the file list and diffs areas, but this information
J> never came out in the subsequent srequest.
> The terminal interface is just a fall back for when an X display device is
> not available (e.i. working from home on a vt220 terminal.).
Also, I want to add the abstract lines (which include severity) into the
QAR field that the submit is in response to... I can't. Not only is there
not enough room for all the QAR numbers the submit corresponds to, but
multi-line input like this can't be done (this is true for both the GUI and
the terminal versions).
>
> The QAR/CLD/SPR field has been expaned to accept multiple lines.
>
J> Thanks....
My recommendation is to trash both of these new processes and revert to
what we have been doing in the past.
-- James
------- End of Forwarded Message
|