uChart - Enhanced Options Clarification Needed

226 views
Skip to first unread message

shanno...@gmail.com

unread,
Mar 12, 2009, 12:03:10 PM3/12/09
to XMPie Interest Group
I'm not sure if anyone has run into any of this, but I've been trying
to understand the ins and outs of uChart and the enhanced options that
it offers... in looking through the enhanced options, there are a few
parameters that I found need some clarification.

Example:
/AxisColor - the parameter says just color... what are the specifics
for "color" that can be used? I tried a hex code a few different ways
with no luck... I tried "grey" and that didn't work, but "gray" did. I
tried "maroon" and that didn't work, but "red" did (though I really
wanted more control over the color). Is there a list of available
color parameters that are usable?

Example:
/AxisStyle - the parameter just says lineStyle. I'm not entirely sure
if that means a point size for the line, or if you need to put
something in like "dashed", "dotted", though I tried "hairline" and
that didn't work. Is there a list of available lineStyle parameters
that are usable?

Example:
/LabelLocation - the parameter just says location. Are these X Y
coordinates? Is there a list of available location parameters that are
usable?

Example:
/LayerLabel - the parameter just says ( text ). I'm not really sure
about this one.

Example:
/LayerLabelFormat - the parameter just says ( stringFormat ). I'm not
really sure about this one either.

Example:
/LeftScaleFormat - the parameter just says ( numberFormat ). I'm not
really sure about this one either.

Example:
/MarkerShape - the parameter just says shape. Is there a list of
available shape parameters that are usable?

The uChart documentation that I am working off of is in Appendix C of
the uCreate User Guide.

If anyone has found the parameters needed for any of those mentioned
above, it would be much appreciated! Thanks!

galkahana

unread,
Mar 15, 2009, 8:45:32 AM3/15/09
to XMPie Interest Group
Hi Shannon,
I am Gal Kahana, the product manager in charge of uChart. I agree that
we lack in giving information for the various options in uChart and
will try to improve. In the meantime i wrote down some info on the
features you asked, The format of a forum is slightly problematic for
rich text requirements...so i couldn't put illustrations, so you will
have to try by yourself to get the sense of some of the items. Let me
know if you need more info (if there is an email i can use i can write
them directly to you.

Answering each parameter separately:
1. /AxisColor [or all "color" types for that matter] use the
following possible built in colors:
Transparent, White, LightestGray, LighterGray,
LightGray, Gray, DarkGray, DarkerGray,
DarkestGray, Black, BlackOverprint,
BlueWash, LightestBlue, LighterBlue, LightBlue,
Blue, DarkBlue, DarkerBlue, DarkestBlue,
RedWash, LightestRed, LighterRed, LightRed,
Red, DarkRed, DarkerRed, DarkestRed,
GreenWash, LightestGreen, LighterGreen, LightGreen,
Green, DarkGreen, DarkerGreen, DarkestGreen

For example: /AxisColor RedWash
If you want to set specific values you can use one of 3 color spaces –
CMYK color (4 components), RGB color (3 components) or grayscale (1
component). RGB allow values from 0 to 255, CMYK and grayscale allow
values from 0 to 100.
Examples:
/AxisColor [100 0 0 0] (pure Cyan, CMYK)
/AxisColor [0 255 0] (pure Green, RGB)
/AxisColor 50 (gray, Grayscale)


2. /AxisStyle [or any lineStyle using features] can use one of the
built in styles:
Specify built-in lineStyles by name:
SolidLine, LongDashes, Dashes, ShortDashes, MiniDashes,
LongShortDashes,
Dots, LooseDots, TightDots, DotDashes, DotDashDashes, DotDotDashes

You can also define custom line styles using the following notation:
[N1 m1 n2 m2….] endcapStyle
Where N* is the width of a drawn dash and m* is the width of a
separating space. An optional endcapStyle keyword can be used for
defining an endcap form.
Examples:
/AxisStyle [3.5 3.5] FlatEnds
This will define dashed in 3.5 points width with 3.5 width of space.
The dashes will have FlatEnds style.

/AxisStyle [0.01 2] RoundEnds
This will create tiny 0.01 dashes (appearing as points) and 2 points
spaces. RouhndEnds style will cause them to appear as a long line of
dots.
Caps styles can be one of FlatEnds, RoundEnds, SquareEnds


3. /LabelLocation values depends on the chart type.

For pie charts the following are applicable:

Callout - default is to mimic /ValueLocation [next to the value]
Legend - in legend
CalloutLegend - both next to value and legend
Nowhere – no labels

For example:
/LabelLocation Callout
This will place labels next to the value text on each pie

For bar/line charts there are more possible values:
Header – at the head of the bar (if below axis, below, if above axis,
above)
Footer – at the footer of the bar (if below axis, above, if above
axis, below)
Head – in bar top
Foot – in bar bottom
Above - above the bar
Below – below the bar
AboveAxis - above the axis
BelowAxis – below the axis
Legend – in Legend
Nowhere - None
All of these are more options of placing labels below the graph
(“staggered” options allow for some labels to be higher than others,
interleaving. The rest keep the labels in the same height):
Floor
Staggered
Floor2Up
Staggered2Up

Group
GroupStaggered
Group2Up
GroupStaggered2Up

4. /LayerLabel means a label for a new column. You wouldn’t normally
use it as the columns are defined by the data that you pass. If you
wish to create an extra column, better define it in the table. In any
case the parameter for LayerLabel is a text string appearing like
this: “(myText)” , meaning the text inside parenthesis. It is using
postscript text notation, so that if you wish to use the parenthesis
themselves you can use a preceding backslash. Only one byte text is
allowed, and it is not guaranteed to function at all times. So
basically – better avoid it.


5. /LayerLabelFormat defines formatting for labels. It is used in
combination with LayerLabel, so I wouldn’t use it at all, preferring
to set the text correctly already using the column names.
In any case, LayerLabelFormat can be either a string enclosed in
parenthesis or an array of such strings, for example:
/LayerLabelFormat (___. 2001)

Or

/LayerLabelFormat [(___. 2001) (____)]

The first form is used to format all labels for the charts layers. The
2nd format is used when the user knows the exact number of layers. In
that case the number of strings is equal to the number of layers.

In the strings you can use any character, which will result in this
character appearing as is in the result label. This is true to all but
the following two characters which have the following meanings:
Underline ( _ ): prints as the next character from the data’s label
Vertical Bar ( | ): skips next data-label character; outputs nothing


Examples of usage can be like:
Use “September” as a label with the format on the left to get the
result on the right -
(___________) September
(___) Sep
(___. 2001) Sep. 2001

Use “1994” as a label with the format on the left to get the result on
the right -
(____) 1994
(||’__) ‘94


6. LeftScaleFormat is either a single number format, or array of
number formats (either setting for all columns, an alternating
sequence).

Like other number format parameters is a string surrounded by
parenthesis. LeftScaleFormat defines the format of numbers appearing
on the left of bar or line charts.
A numberformat string is simply one or more. Those characters are
printed
as-is, with the following exceptions which have special meaning:
Zero ( 0 ): prints a digit or leading zero
Nine ( 9 ): prints a digit, but not it it’s a leading zero
Dot ( . ): prints decimal point
Comma ( , ): thousands separator (nothing if no digits to the left)
Dash ( - ): minus sign if the number is negative, else nothing
Plus ( + ): minus sign if negative, plus if positive, nothing if zero

numberFormat works by lining up the decimal point in the number vs.
the
one in numberFormat (there’s an “implied” decimal at the right if none
was supplied). Working outward from the decimal point, 0 and 9 digits
in
the numberFormat match up with corresponding digits in the number.

Examples:
Number Format Output
1234.56 ($-000,000.00) $001,234.56
1234.56 ($-999,990.00) $1,234.56
.45 ($-999,990.00) $0.45
123.45 (-999,990.00) 123.45
45 (+990.0%) +45.0%
0.25 (9.00 Units) .25 Units


7. MarkerShape can be one of a predefined set:
BlankMarker, Hexagon, CrossRing, Square, Circle, HollowHexagon, Mark,
HollowSquare, HollowCircle, Star, Crosshair, SmallSquare, SmallCircle,
HollowStar, Dash, Triangle, Diamond, Asterisk, Stick, HollowTriangle,
HollowDiamond, Bullseye

It defines the markers shape on a line bar (you need to define
MarkerSize > 0 for this to function).

Like LeftScaleFormat and LayerLabelFormat you can either write one
string on array of strings:
/MarkerShape Dash
In this case all markers are dash
/MarkerShape [HollowSquare Triangle]
In this case there will be an alternating sequence of HollowSquare and
Triangle.


Cheers,
Gal.

shanno...@gmail.com

unread,
Mar 16, 2009, 10:06:02 AM3/16/09
to XMPie Interest Group
Thank you, Gal! This should help a ton! :)
Reply all
Reply to author
Forward
0 new messages