Views
From INDI Library
The next major release of libindi (v0.7) is currently under heavy development. The target release date is now set at Nov. 1st, 2010 given that all goes well.
- Features:
- Dynamic renaming of drivers upon run time: indiserver currently sends clients a static name of the driver, which is usually hard-coded in the driver source code. This presents a dilemma for identical drivers that need to run simultaneously. Suppose we have an encoder driver and two encoder devices (e.g. Alt & Az encoders). As it stands now, the driver cannot change its name (e.g. "ENCODER") to (e.g. "AZ_ENCODER") on run time. In libindi v0.7, indiserver supports dynamic renaming of drivers.
- Standard helper API to create and utilize INDI clients: Sometimes it is necessary for a meta driver to act as client to other drivers (i.e. ability to send commands). Prior to v0.7, this mundane task was done manually. Now with the aid of helper classes, it is a trivial task.
- Ability to load driver properties from an external XML file. No need to hard code properties any more!
- Ability to write/read XML configuration files for driver values to be loaded at run time: Long requested feature is now at works! In libindi v0.7, all drivers under the new framework can automatically read and save XML configuration files for startup values or last-setup values.
- Facilitating debugging and simulation of drivers.
- New C++ framework to facilitate the development of new INDI drivers.
- Multitude of new 3rd party drivers!
- Several bug fixes for current drivers and framework.