Future version food for thought ... implement system API(s)

[grumpyinca]

Investigate the issues of implementing system-level program APIs. Note that there are actually two APIs to be considered: the user facing functions currently exposed by commands like start, change, list, fix, free, search, save, etc. plus, the internal API by which problems like PCyl and spring design connect in to the rest of the system. The latter currently consists of more code-centric functions like eqnset and contnt plus more data-centric files and tables used in startup, standard size selections and catalog selections. The spring design problem also incorporates material property tables and yet another level of complexity in the implementation of end types, heat treatment, shot-peening and alternate methods for calculating material properties.

Currently, the only way to access the user facing system-level functions is through the command line interface. Providing a program API which is then used to implement the command line interface, a web interface and potentially other interfaces may be worthwhile. Factors like cost and benefit need to be considered. A code development plan should be developed.

Note the example of the GitHub command line interface as compared to the GitHub web interface.

As of this writing there is no schedule expectations for such a project.