[Hamlib-cvs-digest] CVS: hamlib PLAN,1.2,1.3

[Stephane F. <f4...@us...>]

Update of /cvsroot/hamlib/hamlib
In directory slayer.i.sourceforge.net:/tmp/cvs-serv10009

Modified Files:
	PLAN 
Log Message:
* cosmetic changes

Index: PLAN
===================================================================
RCS file: /cvsroot/hamlib/hamlib/PLAN,v
retrieving revision 1.2
retrieving revision 1.3
diff -C2 -r1.2 -r1.3
*** PLAN	2000/09/16 01:08:32	1.2
--- PLAN	2000/11/01 23:18:11	1.3
***************
*** 1,27 ****
  
  
! Here is a non-exhaustive list of things IMO to keep in mind when
! developping the hamlib library.
  
  
  Plan:
  ----
! o Hamlib is intended to provide the means to control any rig
  o develop the library as a shared/static library
! o portable (not only Linux, but UN*X, Win32 using cygwin,etc.  -> autoconf?)
! o generic (any rig made, any model)
! o wrappable (Java, perl module, Python module, etc.)
  o support serial ports, IrDA ports, USB ports, network ports (w/ a daemon)
  o thread safe (reentrant) would be a must
  o support preference file (eg. /etc/hamlibrc, ~/.hamlibrc )
! o written in C (C++ would have been more appropriate, but C is okay)
  o support more than one rig per application (ie. generic code)
  o support more than one rig per serial port (ie. Icoms)
! o handle serial retransmission and timeouts would be nice
  o i18n support if applicable
  o software compensation for the actual radio oscillator frequency errors(mode?)
  o if avail., support events sent by the rig (eg. main freq has been changed,..)
  o maybe add some misc functions like PTT signaling (through serial/parallel..)
! o Well documented API, and Howto write a new backend
  o ...
  
--- 1,28 ----
  
  
! Here is a non-exhaustive list of things IMO to keep in mind while
! developping the Hamlib library.
  
  
  Plan:
  ----
! o Hamlib is intended to provide the means to control any capable rig
  o develop the library as a shared/static library
! o portable (not only Linux, but UN*X, Win32 using cygwin, etc. -> autoconf?)
! o be good, be generic (any rig made, any model)
! o uniform data types/units (eg. for power, use Watts, not rig specific val)
! o wrappable (Java, C++, perl module, Python module, etc.)
  o support serial ports, IrDA ports, USB ports, network ports (w/ a daemon)
  o thread safe (reentrant) would be a must
  o support preference file (eg. /etc/hamlibrc, ~/.hamlibrc )
! o written in C (C++ would have been much more appropriate, but C is okay)
  o support more than one rig per application (ie. generic code)
  o support more than one rig per serial port (ie. Icoms)
! o handle nicely serial retransmission and timeouts
  o i18n support if applicable
  o software compensation for the actual radio oscillator frequency errors(mode?)
  o if avail., support events sent by the rig (eg. main freq has been changed,..)
  o maybe add some misc functions like PTT signaling (through serial/parallel..)
! o Well documented API, and Howto write a new rig backend
  o ...
  
***************
*** 30,34 ****
  ----------------
  o SANE, with frontend/backend scheme, dynamic loading, autoconf, etc.
! o struct net_device (Linux kernel) for the void *priv idea
  o any rigctrl sources out there ?
  
--- 31,35 ----
  ----------------
  o SANE, with frontend/backend scheme, dynamic loading, autoconf, etc.
! o struct net_device (Linux kernel) for the "void *priv" idea
  o any rigctrl sources out there ?
  
***************
*** 44,48 ****
  	working code for this) it does 40 frames / sec and no load, 
  	really cool to see time and spectral info !!
! 	I have based it on generic data engine and plugins !! output also to
  	small gtk window.
  o doppler compensation in tracking mode (using mtrack satellite tracker?)
--- 45,49 ----
  	working code for this) it does 40 frames / sec and no load, 
  	really cool to see time and spectral info !!
! 	He has based it on generic data engine and plugins !! output also to
  	small gtk window.
  o doppler compensation in tracking mode (using mtrack satellite tracker?)
***************
*** 52,55 ****
--- 53,57 ----
  o software controlled hopping (poor mans GSM frequency hopping)
     also, must output hopping sequence to other rig to be useful
+ o computer assisted scanner
  o <add here the application you thought it'd be impossible>
  
***************
*** 69,73 ****
  o freq ranges supported: rx/mode, tx/modes/power
  o number of VFO, operations (set VFO separately, VFO A=B, switch, ..)
! o freq granularity (resolution), tuning steps (-> array)
  o SCAN functions (start, stop, ..)
  o Split (cross band, duplex, ...)
--- 71,75 ----
  o freq ranges supported: rx/mode, tx/modes/power
  o number of VFO, operations (set VFO separately, VFO A=B, switch, ..)
! o freq granularity, tuning steps (-> array)
  o SCAN functions (start, stop, ..)
  o Split (cross band, duplex, ...)