We have made a developer release of the Silverlight 2 RC0 version of the Visifire. Since this is not a public release the link in the Downloads page will not be updated until Silverlight 2 RC0 becomes public. Applications built using this release will only work with the Silverlight 2 RC0 Developer Runtime.

Download links for Silverlight 2 RC0 compatible version of Visifire:

Visifire:  visifire_v1.5.0.zip

With documentation:  visifire_v1.5.0_with_documentation.zip

Visifire for managed code users:  visifire_v1.5.0_for_managed_code.zip

Visifire source:  visifire_v1.5.0_source.zip

Thanks for your attention,

Team Visifire

Comments(0)

This release contains a bug fix.

Bug Fixed:

1. An exception is thrown for single DataPoint in Column/ Bar chart with Animation selected as Type4.

Thanks for your attention,

Team Visifire

Comments(0)

This version contains improved reporting for errors. Now the error log shows even the inner exceptions thrown by Silverlight along with the line no. & character position.

For eg. If unknown attribute name set in XML user is alerted in the following way.

Message: Unknown attribute Yvalue on element DataPoint. [Line: 2 Position: 330]

& if a wrong property value is set this message is shown.

Message: AG_E_PARSER_BAD_PROPERTY_VALUE [Line: 2 Position: 328]

By this, users will know the specific attribute name or value set in XML that doesn’t conform to Visifire’s XML standards.

Cheers,

Team Visifire

Comments(0)

We have made a minor change to the Visifire.js. Now you can set the background color of the silverlight plug-in while creating the visifire charts object. For example,

var chart = new Visifire( ‘Visifire.xap’, ’slPlugin1′, 500, 300, ‘transparent’);

Here ’slPlugin1′ is the ID of the silverlight control and it is optional. The last parameter in the constructor is the color which is again optional with default set to ‘white’.

Note: To make the plug-in background transparent, you’ll have to set the windowless state to ‘true’ using function:

chart.setWindowlessState(true);

Thanks for your attention.

Team Visifire

Comments(2)

This release contains a new function added in the Visifire.js.

The “windowless” state of the silverlight plugin can now be set by using the setWindowlessState(windowless_state) function which accepts either “true” or “false“.

Thanks for your attention

Team Visifire

Comments(0)

With all the efforts put in by the members of our forums and by Visifire team we are now confident enough to move Visifire from beta to final. After several rounds of bug fixes, Visifire is now stable. Visifire is widely being used in many industrial applications with no issues reported on stability. Hence users can start using Visifire extensively in real-world applications.

I would like to thank the members of the forums for keeping us busy all these days.

Thanks for your attention.

Team Visifire

Comments(4)

In this release we have added few enhancements.

Enhancements:

1. AxisLabels will not be skipped if they have been provided in the DataPoints. Previously the interval of the labels would be dependent on the interval of the axis. Now, in this release we have made changes such that if the Interval property of AxisX or AxisLabels is not set then the interval will be generated such that all the axis labels provided along with the DataPoint will be displayed in the chart.
2. Improved memory management to reduce the memory usage.

Thanks for your attention,

Team Visifire

Comments(0)

This release contains few bug fixes.

Bug Fixes:

1. YValues with more than 7 digits were automatically approximating.
2. Exception would be thrown whenever Charts were added to a tab control.

Thanks for your attention,

Team Visifire

Comments(5)

With this new release we have introduced few new features.

• Embedding fonts in Visifire - With this new feature you can embed fonts which can be applied to the FontFamily of any Text element. Let’s take a look at the example below

<vc:Title Text="Visifire Charts" FontFamily="Mtcorsva.ttf#Monotype Corsiva" />

Here FontFamily is set in the Title element, the font file that I have used is "Mtcorsva.ttf". This file is located  in ClientBin folder. It can be present anywhere in the same application domain. The font file can be a " *.ttf " or " *.zip " file.

The format followed to specify the font has two parts : font file name followed by a hash (#) and the comma separated list of fonts.

FontFamily="<font_file> # <font_name_1>,< font_name_2>"

Until the font file gets downloaded default font will be applied. You can also put an archived font file with the same syntax:

<vc:Title Text="Visifire Charts" FontFamily="Mtcorsva.zip#Monotype Corsiva" />

This format is applicable where ever FontFamily is used. Have a look at the Documentation for more details.

The following is the screenshot of "Embedded Font" example.

 

 

• Multi-Line Text - This feature will help you to display text in multiple lines. All you need to do is just put "\n" in the text property of any Text attribute of an element as shown below:

<vc:Title Text="Athens 2004 \n Olympics"/>

Multi-Line text is applicable to all text content in Visifire. Have a look at the Documentation for more details.

The following is the screenshot of "Multi-Line Text" example.

Comments(0)

In this version of Visifire we have included several minor features and enhancements.

Features / Enhancements:

• Download and embed fonts.
• Support for Multi-line text.
• Attribute to set the Line Style for Line Charts.
• Attribute to set the target window (like self, parent etc..).
• TrendLine for secondary Y Axis.
• Improved exception logger.
• Additional support functions in Visifire.js.

The next blog will show how to embed fonts and use multi-line text.

Thanks for your attention,

Team Visifire.

Comments(1)