text
stringlengths 0
99.6k
|
|---|
of values receives it's own shading pattern.
|
: Line - Each value is represented by a large shaded point. Lines
|
connect each set of values. Points are shaded to show
|
group.
|
: Pie - One set of values is represented as a circle, with each
|
individual value presented as a shaded wedge.
|
: Point - Each value is represented as a large point. Each set of
|
values receives it's own shading pattern.
|
: Scatter Point - Each value is represented as a large point. Each set of
|
values receives it's own shading pattern. Labels are
|
removed to permit precise determination of X and Y
|
coordinates.
|
: Scatter Line - Similar to Scatter Point, but with lines connecting the
|
points of each set of values.
|
: Unibar - One set of values is represented as a large bar, with
|
each individual value presented as a shaded rectangle.
|
A sort of rectangular pie chart.
|
Text may be edited from within geoChart. Patterns may be assigned to
|
different values. The background grid may be varied. A wide variety of chart
|
display options are provided. A variety of number formats are supported,
|
including dollar amounts and leading-zero suppression.
|
The charts may be printed to any supported GEOS printer, or may copied to a
|
photo scrap for import into other GEOS applications. Printed geoCharts take up
|
about 1/8th page. Photo scraps may be copied in three different sizes, due to
|
limitations in the size that certain applications will accept. Supported sizes
|
are for geoWrite, geoPaint, and a full-screen size, which is acceptable to
|
geoPublish. The geoWrite and geoPaint sizes are achieved by reducing the size
|
of all elements, rather than by reproducing only a portion of the chart. The
|
geoPaint and geoWrite scraps are displayed when created.
|
Problems:
|
No problems were encountered during my "first look". It would be
|
surprising if the first release of any program of this complexity were truly
|
bug-free, and I have no doubt that some problems will surface, but this seems
|
to be quite a solid program.
|
Quibbles:
|
It seems cruel to criticize this package for this when it supports so many
|
different kinds of charts, but an `exploded' option for the pie charts would
|
have been a nice touch.
|
While not as complex as geoPublish, a geoChart file can have an awful lot
|
of graphic elements. These are redrawn during many operations, resulting in
|
the program being slower than it needs to be. Some attention to avoiding
|
redrawing that which has not changed would be a good thing in a future release.
|
An option for manual data entry, and editing, would be appreciated.
|
In conclusion:
|
geoChart is a powerful tool for creating charts. While it is probably of
|
greatest use to geoCalc users, it is appropriate for anyone who wishes to chart
|
data from GEOS. It is capable of producing very professional results. This
|
product was rumored, and later announced, some time ago. It's good to see that
|
the wait has, by and large, been worth it.
|
Ed Flinn, CBMART Sysop, 76703,4032
|
ARC VERSION 2.20 PAGE - 14
|
move <[s:]pattern> [[[s:]pattern]...] <d:>
|
Copies files between drives. As many as eight patterns
|
may be given as parameters. If either the source or the
|
destination drive is omitted, it is assumed to be the
|
default drive. Some examples are:
|
move a:arc c: - move file "arc" on drive 8,0
|
to drive 9,0
|
move a:* b:* c: - move all files from drives a:
|
and b: to drive c:
|
move b:test - moves file "test" on drive b:
|
to the default drive
|
move test b: - moves file "test" on the
|
default drive to drive b:
|
NOTE: MOVE won't handle relative files properly.....yet
|
ren [d:]oldname newname
|
renames a file named 'oldname' to 'newname' on drive d:
|
type [s:]<pattern>
|
Simply copies the contents of the file named to the
|
screen. Only the first file found will be displayed if
|
wildcards are used.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.