CF8 and CFCHART problem

4 Message(s) by 2 Author(s) originally posted in flash and cfml

From: omega1234

Date: Friday, July 20, 2007

I could be wrong but it seems to me that Cold Fusion 8 never displays flash
charts when the name is specified, making it impossible to use charts within
cfforms.

ie - won't display:

<CFCHART format="flash" show3d="yes" pieslicestyle="sliced"
labelformat="currency" name="testChart" title="Summary of Revenue">
<CFCHARTSERIES type="pie">
<CFCHARTDATA item="a" value="50">
<CFCHARTDATA item="b" value="100">
<CFCHARTDATA item="c" value="100">
</CFCHARTSERIES>
</CFCHART>

but will:

<CFCHART format="flash" show3d="yes" pieslicestyle="sliced"
labelformat="currency" showmarkers="no" title="Summary of Revenue">
<CFCHARTSERIES type="pie">
<CFCHARTDATA item="a" value="50">
<CFCHARTDATA item="b" value="100">
<CFCHARTDATA item="c" value="100">
</CFCHARTSERIES>
</CFCHART>

From: BKBK

Date: Saturday, July 21, 2007

[i]it seems to me that Cold Fusion 8 never displays flash charts when the name
is specified[/i]

Neither did Cold Fusion MX7, perhaps not even earlier MX versions, either. It
is so by design. Paraphrasing the
http://livedocs.macromedia.com/Cold Fusion/7/htmldocs/00000226.htm,

[i]"[When you specify the name attribute, cfchart] generates the graph

1. <mathematics> A collection of {nodes} and {edges}.

	See also {connected graph}, {degree}, {directed graph}, {Moore
	bound}, {regular graph}, {tree}.

	2. <graphics> A visual representation of algebraic equations
	or data.

	(1996-09-22)

as
binary data

<data, data processing, jargon> /day't*/ (Or "raw data")
	Numbers, {characters}, {images}, or other method of recording,
	in a form which can be assessed by a human or (especially)
	input into a {computer}, stored and {processed} there, or
	transmitted on some {digital channel}.  Computers nearly
	always represent data in {binary}.

	Data on its own has no meaning, only when interpreted by some
	kind of {data processing system} does it take on meaning and
	become {information}.

	People or computers can find patterns in data to perceive
	information, and information can be used to enhance
	{knowledge}.  Since knowledge is prerequisite to wisdom, we
	always want more data and information.  But, as modern
	societies verge on {information overload}, we especially need
	better ways to find patterns.

	1234567.89 is data.

	"Your bank balance has jumped 8087% to $1234567.89" is
	information.

	"Nobody owes me that much money" is knowledge.

	"I'd better talk to the bank before I spend it, because of
	what has happened to other people" is wisdom.

	(1999-04-30)

and assigns it to the specified variable. [Specifying a name]
suppresses chart display. You can use the name value in the CFFILE tag

<language, text> An {SGML}, {HTML}, or {XML} {token}
	representing the beginning (start tag: "<p ...>") or end (end
	tag: "</p>") of an {element}.  In normal SGML {syntax} (and
	always in {XML}), a tag starts with a "<" and ends with an
	">".

	In {HTML} jargon, the term "tag" is often used for an
	"{element}".

	(2001-01-31)

to write

1. <chat> {Unix}'s simple {talk} command and {protocol}.
	write has been largely superseded by {talk} and then {irc}.

	An enhancement, {RWP}, has been proposed.

	2. <tool> A simple {text editor} for {Windows}.

	(1998-04-28)

the chart to a file

<file system> An element of data storage in a {file system}.

	The history of computing is rich in varied kinds of files and
	{file systems}, whether ornate (e.g., {Macintosh file system}
	for a well-known case) or deficient (e.g., many simple
	pre-1980s file systems don't allow {directories}).

	However, the prototypical file has these characteristics:

	* It is a single sequence of bytes (but consider {Macintosh}
	{resource forks}).

	* It has a finite length, unlike, e.g. a {Unix} {device}.

	* It is stored in a {non-volatile storage} medium (but see
	{ramdrive}).

	* It exists (nominally) in a {directory}.

	* It has a name that it can be referred to by in file
	operations, possibly in combination with its {path}.

	Additionally, a file system may associate other information
	with a file, such as {permission} bits or other {file
	attributes}; timestamps for file creation, last revision, and
	last access; revision numbers (a` la VMS), and other kinds of
	{magic}.

	Compare: {document}.

	(1997-04-08)

."[/i]

You could therefore simply extend

<programming> To add {features} to a program, especially
	through the use of {hooks}.

	"Extend" is very often used in the phrase "extend the
	{functionality} of a program."

	{Plug-ins} are one form of extension.

	(1997-06-21)

your code, thus <CFTRY>
<CFCHART format="flash" show3d="yes" pieslicestyle="sliced"
labelformat="currency" name="testChart" title="Summary of Revenue">
<CFCHARTSERIES type="pie">
<CFCHARTDATA item="a" value="50">
<CFCHARTDATA item="b" value="100">
<CFCHARTDATA item="c" value="100">
</CFCHARTSERIES>
</CFCHART>
<!--- create directory

<file system> A node in a hierarchical {file system} which
	contains zero or more other nodes - generally, {files} or
	other directories.

	Compare {folder}.

	(1997-04-10)

if necessary --->
<CFIF NOT directoryExists("c:\temp\test\")>
<CFDIRECTORY action="CREATE" directory="c:\temp\test\">
</CFIF>

<CFFILE action = "write" file = "c:\temp\test\test_chart.swf" output

<architecture> {Data} transferred from a computer system to
	the outside world via some kind of {output device}.

	Opposite: {input}.

	(1997-04-28)

=
"#testChart#">
Chart has been written to c:\temp\test\test_chart.swf
<CFCATCH type="Application">
error

1. A discrepancy between a computed, observed, or measured
	value or condition and the true, specified, or theoretically
	correct value or condition.

	2. <programming> A mental mistake made by a programmer that
	may result in a program {fault}.

	3. (verb) What a program does when it stops as result of a
	programming error.

	(2000-03-28)

occurred: <CFOUTPUT>#cfcatch.message#</CFOUTPUT>
</CFCATCH>
</CFTRY>

From: omega1234

Date: Saturday, July 21, 2007

Thanks, that's just what I needed. Should've read the docs more carefully.

From: BKBK

Date: Sunday, July 22, 2007

Next Message: Flash Form and Navigation Button Issue (DoFSCommand)