 News |
FAQ
|
| Search
|
Home
|
| Getting Started | Documentation | Glish | Learn More | Programming | Contact Us |
|
| Version 1.9 Build 1367 |
|
Our approach has been to build on existing freeware and shareware rather than just sitting down and coding everything from scratch.
Consequently, the bulk of our time to date has been spent in prowling around anonymous ftp servers for source code, porting potentially useful candidates to Charlottesville, and examining them in some detail. Packages considered for adoption have also been compiled and tested (though not extensively exercised).
In this manner, we've discarded most candidates, for a variety of reasons: requires use of a commercial package such as Motif; doesn't compile by following the instructions, or with a managable amount of hacking; doesn't look useful; looks like it will create as many problems as it solves; etc.
We've also used this opportunity to compare the available compilers and environments, and to obtain needed technical information (e.g.: assessing the feasibility of compilers; determining the required setup and mechanics of integrating FORTRAN subroutines into C++ classes; comparing the implementation of various packages to determine good and bad ways of doing things; accumulating classes which can profitably be used in implementing AIPS++ classes, so as to avoid re-inventing wheels; the considerations and proper implementation of shared libraries; incorporating documentation in the code for use on-line).
This having been completed, we're up to speed and ready to proceed to the next phase of the project: implementing the classes within the responsibility of Basic Libraries.
The remainder of this report (1) makes specific recommendations regarding the import of pre-existing graphics into AIPS++, (2) briefly discusses what classes will implemented by us in general terms, and (3) discusses problems that may or will give us trouble. War stories, regurgitations of experiences, and techno-minutiae are intentionally omitted.