= Needed Command Functionality =
Chimera2 command functionality needed for early release(s) based on [wiki: Early Release Requirements].

This is somewhat high-level; more detailed guidelines and examples are in [http://www.cgl.ucsf.edu/home/meng/chi2/command-structure.html Chimera2 Command-Structure Thoughts].

== Late summer release ==

Initial versions (not necessarily final/full implementations) of:
* '''open''' (suggest same general syntax as Chimera1, possibly adjusting prefixes; covers both local files and web-fetch)
* '''display''', '''modeldisplay''' (suggest replacing with '''show/hide''')
* '''ribbon''' (suggest replacing with '''cartoon''' and including spline and any other whole-chain parameters)
* '''surface''' (see [https://www.rbvi.ucsf.edu/trac/chimera2/wiki/SurfaceCategories surface command and category thoughts]; should include calculation parameters, vertexDensity, visiblePatches)
* '''repr''', '''ribrepr''', '''ribscale''', '''surfrepr''' (suggest consolidating into a new '''style''' command, generalizing ribbon to cartoon as per [http://www.cgl.ucsf.edu/home/meng/chi2/ribbons.html ribbons writeup], and including pseudobonds)
* '''color''' (suggest consolidating with '''rainbow''' but leaving color-by-attr and color-by-scalar-field as separate commands)
* '''volume''' (redundancy with show/hide/color etc. OK with me, but should review structure and keywords vs. the negotiable [http://www.cgl.ucsf.edu/home/meng/chi2/command-structure.html command guidelines])
* some way to adjust subdivision/smoothness; any global setting could be covered by '''set''' (see below) and any attribute by '''setattr''', but there could also be options in '''surface''', '''volume''', '''cartoon''' and/or a top-level '''quality''' command

Extremely useful catchalls, I suggest retaining as permanent commands even though there will be some redundancy:
* '''set''' global settings: silhouettes, background color, depth-cuing parameters, shadows, lighting (if many sub-options, e.g. lighting, judiciously consider making a separate top-level command; also keeping a redundant but longer '''set''' command is OK with me) 
* '''setattr''' attribute values

GUI-only, or do we need commands?
* '''select''' (including up/down)
* save/restore session; maybe restore is covered by '''open'''
* save image with supersampling option

Command accoutrements:
* decide on keyword conventions
* decide on what kinds of colorspecs are allowed
* list of built-in color names

== December release ==

Initial versions (not necessarily final/full implementations) of:
* '''transparency''' analogous to '''color''' command
* '''set''' global settings: single-layer transparency
* '''findhbond'''
* '''distance'''

Command accoutrements:
* more built-in specs like protein, nucleic acid, element symbols, ''.etc.''