Version 1.9 Build 1367

News	FAQ
Search	Home

Up: Note 186: The Tasking Environment of AIPS++ Previous: Standard Environment

Some Development Plan Items

This plan lists the high-level work items which need to be assigned to implement the design described here. Assignment of tasks and target dates will be recorded elsewhere. The items are listed in approximately the order I believe implementation should proceed.

1.: Control hub implementation in Glish.
2.: Implement C++ binding and C++ RTS along with some sample object servers.
3.: .aipsrc parsing in Glish/C++. [C++ is done]
4.: Package manipulation and registration (includes command line argument conventions to executables).
5.: Define Glish language binding (the Glish binding may drive enhancements in the Glish language). After, implement distributed object RTS for Glish
6.: Determine method of documenting both pure Glish functions, and especially inter-language classes (a FORTRAN programmer won't want to see a C++ class).
7.: Non-GUI aips browser implementation.
8.: Non-GUI task controller (including parameter/Record conventions).
9.: Logging, Help, Plot, Image display, Table editor interfaces and non-GUI implementations.
10.: Implement parameter database (requires tables to be able to store Record/keyword sets in a cell).
11.: Sample tasks.
12.: GUI interfaces for standard user services.
13.: C++, Glish, and FORTRAN ``compilers''. My feeling is that we can do two languages ``by hand'', but when we want to go to a third we will need automation.

Up: Note 186: The Tasking Environment of AIPS++ Previous: Standard Environment Contents