| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 11.1 | Draft ready for review | SUPER::ROUNDS | Kristin Rounds, DTN 381-1066 | Fri Dec 07 1990 12:02 | 3 | 
|  | A draft of this module is available for review in:
	SUPER::ES$REVIEW:[RA0293]RA0293_CHAP_3_PROFILE.PS
 | 
| 11.2 | Reading, UK - first pass | UKEDU::SHONE | Keith Shone @RKA 830-4074 | Thu Dec 13 1990 10:22 | 35 | 
|  |     I found the flow of this chapter OK.
    My nits, typos and other observations are below.
    NOTE: These are my feelings etc. not of the UK as a whole.
    I comment on typos etc on instructor pages as well as customer pages.
    Instructors deserve to have unambiguous, correctly spelled and
    technically accurate information too! :-)
    
    I feel the DCL command CREATE should get a mention somewhere  along the
    way. It's probably of greater utility in the  construction of command
    procedures within command procedures, if you follow :-)
Page	Observation
----    -----------
1-6	Next last bullet: VAX workstations - not strictly true!
	I don't believe EVE works under ULTRIX but the latter
	certainly runs on VAX workstations.
	How about "...and on workstations running VMS."?
1-8	The explanatory text suddenly switches from talking
	about files to talking about buffers.
	Are buffers left to be explained by instructors? If so
	that's fine. Might be worth a note on the facing
	instructor page.
1-20	Last line: ...the other buffers to a file.
                                      -
1-28	Last line: Should add a note here (or on the instructor 
		   page) highlighting the danger of using
		   quit in EDT - it doesn't give one a second
		   chance to save many hours of work, it just
		   QUITs without question!
 | 
| 11.3 | Keep the course VAX-independent | HARDY::MATTHEWS |  | Wed Feb 20 1991 17:22 | 20 | 
|  |     A comment, not too late I hope.
    
>1-6	Next last bullet: VAX workstations - not strictly true!
>	I don't believe EVE works under ULTRIX but the latter
>	certainly runs on VAX workstations.
>	How about "...and on workstations running VMS."?
    Keith is right for the wrong reason... A TPU/EVE for RISC/ULTRIX is
    in internal field test!
    
    A more compelling reason is that if we make our courses accurate for
    both VAX VMS and RISC VMS, we won't have to change them when RISC VMS
    becomes a product. Someone should do a global search for "VAX" in the
    source, and reword the material to eliminate "VAX" if possible.
    
    (What the V in EVE will then stand for is still under discussion! I
    think I'd relegate "Extensible VAX Editor" to the instructor page as
    trivia.)
    
    					Val
 | 
| 11.4 | New version available | SUPER::ROUNDS | Kristin Rounds, DTN 381-1066 | Tue Apr 30 1991 06:46 | 6 | 
|  | This has become chapter 4 of the course.  It is available in:
	SUPER::ES$REVIEW:[RA0293]RA0293_CHAP_4_EDIT.PS
We removed some of the advanced EVE features because the course was
too long.
 | 
| 11.5 | Error in EVE figure + minor queries | DUCK::SHONEK | Keith Shone UK Edu 830-4074 | Wed May 01 1991 13:01 | 39 | 
|  |     These comments are on the module:
    
    		Creating Memos, Reports, and Data Files
    
    Page 1-3:
    Following the statement "To create a file, you can use:" might include
    the /OUTPUT qualifier to a DCL command
    
    Page 1-5:
    Bullet 3: I know that a system interruption is the reason for
    journaling but could we be more diplomatic? How about "unexpected
    interruption of the editing session"? (Since CTRL-Y is cited later
    and power failures are another asynchronous, unexpected source of
    interruption).
    
    Bullet 8: the word Functions at the start of this sentence started me
    reading with the wrong sense. I was looking for something that VT100,
    VT200 and VT300s could do for me rather than the editor running from
    one of these terminals! How about something like "This editor can be
    used from VT....."
    
    Page 1-7:
    The figure has a serious omission: the status line does not include
    the READ/WRITE status to the left of "Insert". This is a default
    status.
    
    Page 1-23:
    REPLACE: in addition to deleting text it also sets the mode to INSERT
    
    Page 1-26:
    Should point out that EDT won't question a QUIT command - all the work
    done is lost, immediately!
    
    Page 1-27:
    In place of system crash could we have something euphemistic like
    power failure or other unexpected interruption (CTRL-Y). :-)
    
    That's all for today folks.
    
 | 
| 11.6 | Response to 11.5 | HARDY::ROUNDS | Kristin Rounds, DTN 381-1066 | Thu May 02 1991 14:51 | 6 | 
|  | Thanks for your comments, Keith.  I incorporated them into the chapter.
Regarding the problem with figure 1, I caught that during the pilot and
requested that the art be corrected.
	Kristin
 |