| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 304.1 | use context sensitive help, no class wildcards | GOSTE::CALLANDER | | Tue Sep 04 1990 18:27 | 19 |
|
Though the SRM describes class wildcards, they are NOT supported
in MCC, especially NOT from the PM.
If your user wants to figure it out, suggest that they use the context
sensitive help of the FORMs mode in the FCL. By entering that part
of the entity that they know, they can place the cursor on the
"Entity" line and use the PF2 key. They will then receive a list
of all known child entities for the partial entity listed. Each
class that requires an instance will be followed by an "*" to signify
this.
Once they have figured out the entity then can enter the verb and
ask for help (using PF2) on the "Attr/Arg" field and get a list
of all attributes or arguments supported for the directive. Those
arguments that are required for the directive will be followed by
an "=" to signify this.
|
| 304.2 | Thanks, Jill | COOKIE::KITTELL | Richard - Architected Info Mgmt | Tue Sep 04 1990 18:34 | 0 |
| 304.3 | Hmmm, Context Sensitive Help Doesn't | COOKIE::KITTELL | Richard - Architected Info Mgmt | Wed Sep 05 1990 14:29 | 4 |
|
I tried using the forms interface as suggested in .1. I entered "MCC 0"
on the entity line and hit PF2. It displayed the list of global entities,
not the list of children of MCC.
|
| 304.4 | When? | MARVIN::COBB | Graham R. Cobb (Wide Area Comms.), REO2-G/H9, 830-3917 | Thu Sep 06 1990 10:02 | 7 |
| So, when will MCC (and FCL in particular) support wildcard classes, if ever?
This feature is in NCL and I use it today! It would be even more useful in
MCC where MCC could add the classic director added-value of implementing
SHOW <some-entity> *... ALL (i.e. all attributes of all descendents of
some entity).
Graham
|
| 304.5 | child help should work | GOSTE::CALLANDER | | Thu Sep 06 1990 13:23 | 46 |
|
RE .3
I don't know what version you are using Rich, but I know it works.
The following is a dump of the screen from the August MCS release
of the FCL.
Verb:
Entity: mcc 0
Attrib/Arg:
Qualifiers:
List Of Valid Child Entities
ALARMS
HISTORIAN_FM
DNA4_AM
BRIDGE_AM
ETHERNET_AM
SAMPLE_AM
DNA5_AM
CONFIG_FM
FCL
ICONICMAP
EXPORTER_FM
DOMAIN_FM
PA
CONTROL_FM
F17 F20 DO PREV/NEXT SCREEN HELP/PF2
Other Region Line Format Execute Scroll Help Field Help
**And yes, this is using the IFT version 1.1 dictionary with the 1.0
fcl.
GOSTE::GOSTE> instal list sys$share:Mcc_fcl_pm.exe
DISK$SYSDSK:<SYS13.SYSCOMMON.SYSLIB>.EXE
MCC_FCL_PM;4 Open Hdr Shar Lnkbl
GOSTE::GOSTE> dir/date sys$common:[syslib]mcc_Fcl_pm.exe
Directory SYS$COMMON:[SYSLIB]
MCC_FCL_PM.EXE;4 22-AUG-1990 12:29:06.65
Total of 1 file.
GOSTE::GOSTE>
|
| 304.6 | not yet scheduled, class wildcarding | GOSTE::CALLANDER | | Thu Sep 06 1990 13:25 | 7 |
| RE .4
Class wildcarding can be extremely useful. But at this point in
time, it has not been scheduled for the 1.0 or 1.1 releases.
jill
|
| 304.7 | sounds like fixed-in-MCS-release | COOKIE::KITTELL | Richard - Architected Info Mgmt | Thu Sep 06 1990 14:25 | 8 |
|
RE: .5
Jill, I'm running UT1.0.1 with the X1.1 update. I didn't go to the Aug MCS
kit because it was declared as not being compatible with the iconic stuff,
which I need for an upcoming demo.
So it sounds like you've got it working, 'nuff said.
|
| 304.8 | *... | TENERE::FLAUW | | Fri Sep 07 1990 03:34 | 19 |
| RE: .4, .6
Jill,
What Graham is talking about even goes further than just class
wildcarding. I also think that the ellipsis (*...) is an extremely
usefull feature, one I wish MCC had implemented already.
Class wildcarding might be a step in this direction, even if the
functionality is not equivalent. Also, as we both know, having the FCL
being able to give all the sub-class of an entity is a very nice
(and useful) feature, but not equivalent to true class wildcarding.
Best regards,
Marc.
|
| 304.9 | missed that in my reply | GOSTE::CALLANDER | | Fri Sep 07 1990 11:29 | 20 |
| Sorry, about that, I didn't miss it when reading it but forgot to
reply to it.
In my opinion, the ellipsis is critically important to MCC's success.
The discussions that are going on now, center around how this type
of information can be passed across the call interface. My feelings
on it's importance stem from the need to do things like request
all events on a specific entity and all of it's children, without
having to make a specific request to get the events for each and
every child. (**Don't worry about this, for the first release of
notification we are going to synthesize this effect; but solving
the problem is the better solution, just not always possible in
the short term.)
We hear you, and keep the suggestions coming. Among other things
suggestions help prioritize work and determine interest and market
requirements.
jill
|