- Monday, 01 August 2011
MSLICE Sequencing is a graphical tool for writing sequences and integrating them into RML files, as well as for producing SCMF files for uplink. When operated in a testbed environment, it also supports uplinking these SCMF files to the testbed via Chill.
This software features a freeform textural sequence editor featuring syntax coloring, automatic content assistance (including command and argument completion proposals), complete with types, value ranges, unites, and descriptions from the command dictionary that appear as they are typed. The sequence editor also has a “field mode” that allows tabbing between arguments and displays type/range/units/description for each argument as it is edited. Color-coded error and warning annotations on problematic tokens are included, as well as indications of problems that are not visible in the current scroll range. “Quick Fix” suggestions are made for resolving problems, and all the features afforded by modern source editors are also included such as copy/cut/paste, undo/redo, and a sophisticated find-and-replace system optionally using regular expressions.
The software offers a full XML editor for RML files, which features syntax coloring, content assistance and problem annotations as above. There is a form-based, “detail view” that allows structured editing of command arguments and sequence parameters when preferred. The “project view” shows the user’s “workspace” as a tree of “resources” (projects, folders, and files) that can subsequently be opened in editors by double-clicking. Files can be added, deleted, dragged-dropped/copied-pasted between folders or projects, and these operations are undoable and redoable.
A “problems view” contains a tabular list of all problems in the current workspace. Double-clicking on any row in the table opens an editor for the appropriate sequence, scrolling to the specific line with the problem, and highlighting the problematic characters. From there, one can invoke “quick fix” as described above to resolve the issue. Once resolved, saving the file causes the problem to be removed from the problem view.
. Refer to NPO-47292.