Include Bare bones operator interface example

[NIExpert]

Even the "simple " operator interface is too complex for some applications.  It can also be somewhat intimidating to new developers,    

Many developers might benefit by having a "bare bones" (ie simplest possible) Operator Interface example to start with

[dug9000]

What would you propose go in such an interface? What about the simple UI is more complicated than you would like? It would be hard to make it much simpler without losing functionality.

[JÞB]

It would be hard to make it much simpler without losing functionality.

I think thats the point  too much functionality.  by "Bare Bones" I would assume "Run using Test UUTs", possibly "Select sequence" and maybe but not necessarilly, "View Report".  The barest necessary for a "Push the button, get a banana" style sequence since, that's really all we want to train a qualified operator to do anyhow.  We have widgets, we want them tested.  The operator doesn't need much training and anything else the operator touches breaks process flow.

[NIExpert]

I think many users would benefit from an OI that does not include any sequence or execution display and thaty only provides the following features:

Select Sequence File

Test UUT

Pass/Fail indicator

As Jeff mentions, the built in operator interface provides too much functionality for some applications.  Additionally, new developers may feel overwhelmed by the existing OI' and would greatly benefit from a stripped down example

[Elaine_R.]

as a side note, intermediate-level developers wishing to learn more about the API might benefit from a demo user interface that was both super simple and super oldschool. I.e. how to launch TS and run an execution on a file without using the cool 'easy' user interface controls/indicators (other than the managers)

i.e. a demonstration of Engine.GetSequenceFile, Engine.NewExecution, and Engine.ReleaseSequenceFile sort of demo since for very custom OI's it's often the case that the default widgets won't do as TS is to  be 'embedded'/hidden  inside of a very non-teststand front-end.

just my 2 cents.

it could be as easy as dredging up one of the old demo operator interfaces from TS 2.0.x

--Elaine R

[NIExpert]

I am suggesting a bare bones interface using the UI controls