| > In 1.1 MONITOR interface screen,
> o An error message in message window not cleared when any key typed
> as part of next command line.
> Is this known?
I don't seem to notice this. What type are error is happening? Is it a
syntax error?
> o ctrl/z not take effect to exit from monitor.
Yes, it would be nice to have this. Phil, any chance we can squeeze
this one in?
> o "show time" command to display current time required.
You will have to wait until the next release for this to be added.
If you have any other additional functional requirements you'd like to
see entered, please send them to OPG::Philip.
>
> In 1.1 editor for character_cell terminal.
> o data entry style of add/modify command.
> It frustrated to entre/modify data. I wish PCM should use CLI
> such as vcs. If you need, build own command interpreter for
> any platform.
Our intention here was to use the same code for both Ultrix and OSF/1
platforms as well as VMS. In addition to saving developemnt time, we
also wanted both products to have the same look and feel so that users
going from one platform to another would not require any additional
training. Finally, the command line edit serves primarily as a backup
editor to the XWindows editor which will be used the majority of the
time.
Dave
|
| >> In 1.1 MONITOR interface screen,
>> o An error message in message window not cleared when any key typed
>> as part of next command line.
>> Is this known?
>
> I don't seem to notice this. What type are error is happening? Is it a
> syntax error?
I am with Dave on this one, exactly what is the problem here, can you
try this with the latest kit announced yesterday?
>> o ctrl/z not take effect to exit from monitor.
>
> Yes, it would be nice to have this. Phil, any chance we can squeeze
> this one in?
I thought we put this in, again, try the latest kit.
>> o "show time" command to display current time required.
>
> You will have to wait until the next release for this to be added.
> If you have any other additional functional requirements you'd like to
> see entered, please send them to OPG::Philip.
Its on the wish list, however, it will only get done if we get time, to
improve the chances of getting this implemented, please submit a phase 0
request when phase 0 is announced (Any day now).
>>
>> In 1.1 editor for character_cell terminal.
>> o data entry style of add/modify command.
>> It frustrated to entre/modify data. I wish PCM should use CLI
>> such as vcs. If you need, build own command interpreter for
>> any platform.
>
> Our intention here was to use the same code for both Ultrix and OSF/1
> platforms as well as VMS. In addition to saving developemnt time, we
> also wanted both products to have the same look and feel so that users
> going from one platform to another would not require any additional
> training. Finally, the command line edit serves primarily as a backup
> editor to the XWindows editor which will be used the majority of the
> time.
I am totally with Dave here, the DECwindows editor is our primary interface
we only supplied the character cell editor because we need it for the
install and it is sometimes nice to make changes whilst dialed in. In fact
you will find things that you can do in the X-windows editor that you cant
and never will be able to do in the character cell editor (such as
modifying a Dispatch).
Plus, we figured that as the editor will be used very little after the
initial setup of the product, our time was better spent on the other
parts of the product, such as ENS and the C3.
Anyway, thanks for the feedback, its always interesting to get other
peoples viewpoints, keep it coming.
Cheers,
Phil
|