This release contains few bug fixes.
- YValues with more than 7 digits were automatically approximating.
- Exception would be thrown whenever Charts were added to a tab control.
Thanks for your attention,
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.
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,
In this blog I’ll show how to create Sparkline Charts using Line charts from Visifire.
The following XML is a bare bone XML required to create sparkline charts:
<vc:Chart xmlns:vc="clr-namespace:Visifire.Charts;assembly=Visifire.Charts" AnimationEnabled="False" Padding="1" BorderThickness="0" Watermark="False"> <vc:AxisX Enabled="False"/> <vc:AxisY Enabled="False" StartFromZero="False"/> <vc:DataSeries RenderAs="Line" LabelEnabled="False" MarkerEnabled="False" > . . . </vc:DataSeries> </vc:Chart>
Highlighting of the various points has to be done by selecting the color for the marker.
To highlight any point you have to enable the marker for the point and set the color. If color is not selected then default color will be applied. Also set the marker size as per requirement. Have a look at the example below, it shows how to highlight the start and end points.
<vc:Chart xmlns:vc="clr-namespace:Visifire.Charts;assembly=Visifire.Charts" Theme="Theme1" AnimationEnabled="False" Padding="1" BorderThickness="0" Watermark="False"> <vc:AxisX Enabled="False"/> <vc:AxisY Enabled="False" StartFromZero="False"/> <vc:DataSeries RenderAs="Line" LabelEnabled="False" MarkerEnabled="False" MarkerSize="5" LineThickness="0.5" Color="Black"> <vc:DataPoint YValue="44.01" MarkerEnabled="True" Color="Blue" /> . . . <vc:DataPoint YValue="44.5" MarkerEnabled="True" Color="Blue" /> </vc:DataSeries> </vc:Chart>
Any point can be highlighted to show its importance
The screen shot below shows a HTML table containing Visifire sparkline charts, click on the image below to see silverlight example:
The code for this example can be downloaded from the here.
Visifire sparkline charts support all events that are supported by line charts and hence can be easily used for creating drill down charts.
- Create a chart.
- Call a function to get updated XML.
- Call render function to display the chart.
- Repeat from step 2.
The following image is the screen shot of real-time chart example. Click on the image see it in action:
You can download the source for this example here.
The re-rendering process can also be used if the updated XML is stored in files, by using the chart.setDataUri function.
With this new release we have introduced a feature that allows you to easily re-render charts to give real time effect. It’s amazingly easy to create real-time charts with this new feature. See this blog for more details.
- Render function in visifire.js is updated, such that it can re-render charts.
- LabelAngle property in AxisX was not functional.
- Cursor property in DataSeries was not being applied to 3D charts.
Thanks for you attention,
Visifire has been successfully ported to Silverlight 2 Beta 2.
Below are the few changes done to achieve compatibility :
- Explicit typecasting of constants while setting dependency properties like TopProperty, LeftProperty etc.
- Resources are now added with a key element and resource object reference , instead of passing just the reference.
- The Target property for animations has been changed from String to PropertyPath object.
Hey, there is more to add, Visifire now supports the most coveted feature : Secondary Y – Axis. Check this post for more info.
Thanks for listening,
Visifire v1.0.11 Beta is released with the most coveted feature: Secondary Y Axis. Visifire is now compatible with Silverlight 2 Beta 2. You can download the latest release from the download page.
- Secondary Y Axis – In the DataSeries use AxisYType="Secondary" to specify the reference axis for the DataSeries and Visifire automatically creates the secondary axis. To change the settings of the Secondary Y Axis just create a regular AxisY and set the attribute as AxisType="Secondary". If this attribute is not set then the default axis type will be "Primary". Have a look at the Visifire Gallery for charts having Secondary Y Axis.
Bug Fixes / Enhancements:
- ToolTipEnabled property for trend line was redundant, as providing ToolTipText enables it automatically. Hence it was removed.
- ScalingEnabled property for AxisX/AxisY was redundant, as providing ScalingSets enables it automatically. Hence it was removed.
- Exception was being thrown in Area Charts if there was only one DataPoint in a DataSeries.
Thanks for your attention,