<PRE>
Ideas/Needs for future GRASSLinks releases:
email <a href="mailto:coopl@bcc.orst.edu">Len Coop</a> for adding ideas to the list.

Short-term/easy (version 3.3?)
- Get the system on SOURCEFORGE and recruit developers to help out
- Finish transition from GIF to PNG for output maps (a few cleanup fixes)
- Allow multiple query of rasters (currently base and overlay only)
- Make GL_matrix.html and associated utilities PROJECT dependent
- Add "skins" to allow easy edit of HTML appearance
- Continue efforts to extend query functions: add raster forms, ability
  to query and show forms for rasters other than the single displayed map
- Lots of work on improving legends (allow static and dynamic)

Longer-term (version 4.0?)
- Merge features of shellscript based GRASSLINKS v. 3.05,
  such as user input of site
  data, interpolate site data, compute contours, and more database support
- Add hierarchical display so vectors and sites are displayed only
  for designated zoom_factors abcde where each is defined as
  a North-South distance N-S in degrees (latlong) or meters (UTM
  and other meter based projections. If the calculated zoom_factor
  (NS distance) is greater than the abcde specified limits, then
  the "zoom" is too wide and the layer is not displayed. This should
  avoid the problem of overpopulating the map and make the system work
  more like modern desktop GIS programs.
- Show locations queried with a point or arrow, based on for example:
  echo "-121 43" | d.icons icon=vlg_point color=black size=2
  (note this would slow down queries since map would need redisplay)
</PRE>
