ngchart - Project Hosting on Google Code

Earlier this year May 29, 2009 issue 7 (Referenced assembly 'NGChart' does not have a strong name.) commented on by DanLatuk - I realized this after I posted my comment. Thanks. I realized this after I posted my comment. Thanks. May 28, 2009 issue 7 (Referenced assembly 'NGChart' does not have a strong name.) changed by erymski - Actually, you can checkout the source code as described at http://code.google.com/p/ngchart/source/checkout. Let me know if there is a problem with it. Status: WontFix Owner: erymski Actually, you can checkout the source code as described at http://code.google.com/p/ngchart/source/checkout. Let me know if there is a problem with it. Status: WontFix Owner: erymski May 28, 2009 issue 7 (Referenced assembly 'NGChart' does not have a strong name.) reported by DanLatuk - I get the following error when compiling my project: "Assembly generation failed -- Referenced assembly 'NGChart' does not have a strong name" Can you please share the source code so I can generate a strong name for this assembly? I get the following error when compiling my project: "Assembly generation failed -- Referenced assembly 'NGChart' does not have a strong name" Can you please share the source code so I can generate a strong name for this assembly? Apr 02, 2009 issue 6 (Data Scaling Range Collapse) reported by lifeoflust - What steps will reproduce the problem? 1. Use a datapoint which exceeds 61 (i.e. barchart) What is the expected output? What do you see instead? The range is a lovely chart and then collapses because of the Google API encoding algorithm used which must use values within the range of the ~61 characters used for text based data encoding. It appears that when values exceed this, the encoding bumps up to the 4096 range using double char pairs. However, this compresses chart data to an unusable visual range. Please implement scaling based on pixel granularity. The If the data is first converted to 0-100, and range scaling is applied as shown in the API (ie. "&chxr=0,{xmin},{xmax}\|1,{ymin},{ymax}") then you don't need to switch the encoding method based on datarange but on pixel range. For instance below chart has 300 pixels, so the max visual step is .33 (%). Set a threshold of this fraction and toggle between the 62 and 4096 range based on it. Love the rest of the API! What version of the product are you using? On what operating system? FF3, XP SP3. Please provide any additional information below. Nice chart --> // Test out some charting classes BarChart chart = new BarChart(BarsType.Stacked, BarsDirection.Vertical, new ChartSize(300, 200), new ChartData(new int[] { 20, 1, 25, 61 }) ); // set colors Color[] colors = new Color[] { Color.DodgerBlue, Color.Orchid, Color.DarkSalmon }; chart.Colors = new ChartColors(colors); Bad Chart --> // Test out some charting classes BarChart chart = new BarChart(BarsType.Stacked, BarsDirection.Vertical, new ChartSize(300, 200), new ChartData(new int[] { 20, 1, 25, 62 }) ); // set colors Color[] colors = new Color[] { Color.DodgerBlue, Color.Orchid, Color.DarkSalmon }; chart.Colors = new ChartColors(colors); What steps will reproduce the problem? 1. Use a datapoint which exceeds 61 (i.e. barchart) What is the expected output? What do you see instead? The range is a lovely chart and then collapses because of the Google API encoding algorithm used which must use values within the range of the ~61 characters used for text based data encoding. It appears that when values exceed this, the encoding bumps up to the 4096 range using double char pairs. However, this compresses chart data to an unusable visual range. Please implement scaling based on pixel granularity. The If the data is first converted to 0-100, and range scaling is applied as shown in the API (ie. "&chxr=0,{xmin},{xmax}\|1,{ymin},{ymax}") then you don't need to switch the encoding method based on datarange but on pixel range. For instance below chart has 300 pixels, so the max visual step is .33 (%). Set a threshold of this fraction and toggle between the 62 and 4096 range based on it. Love the rest of the API! What version of the product are you using? On what operating system? FF3, XP SP3. Please provide any additional information below. Nice chart --> // Test out some charting classes BarChart chart = new BarChart(BarsType.Stacked, BarsDirection.Vertical, new ChartSize(300, 200), new ChartData(new int[] { 20, 1, 25, 61 }) ); // set colors Color[] colors = new Color[] { Color.DodgerBlue, Color.Orchid, Color.DarkSalmon }; chart.Colors = new ChartColors(colors); Bad Chart --> // Test out some charting classes BarChart chart = new BarChart(BarsType.Stacked, BarsDirection.Vertical, new ChartSize(300, 200), new ChartData(new int[] { 20, 1, 25, 62 }) ); // set colors Color[] colors = new Color[] { Color.DodgerBlue, Color.Orchid, Color.DarkSalmon }; chart.Colors = new ChartColors(colors); Older Nov 18, 2008 issue 5 (Unable to specify missing value) reported by Maxim.Koval.Navrotsky - For example I need to render a chart for this data: 0.2,0.1,0.3,-1,0.3,0.2,0,5 minus one means missing value. Current implementations assumes that I have to create an array like this: float? foo = new float?[] {0.2,0.1,0.3,null,0.3,0.2,0,5}; But ChartData class does not support nullable types for datasets. For example I need to render a chart for this data: 0.2,0.1,0.3,-1,0.3,0.2,0,5 minus one means missing value. Current implementations assumes that I have to create an array like this: float? foo = new float?[] {0.2,0.1,0.3,null,0.3,0.2,0,5}; But ChartData class does not support nullable types for datasets. Sep 04, 2008 issue 4 (Line grids of line chart?) commented on by zjtopspeed - Sorry, it is grid lines Sorry, it is grid lines Sep 04, 2008 issue 4 (Line grids of line chart?) reported by zjtopspeed - It seems that there is no line grid for line chart now, or I missing something? currently, i append "&chg=100,10" to my generated url. It seems that there is no line grid for line chart now, or I missing something? currently, i append "&chg=100,10" to my generated url.

issue 6 (Data Scaling Range Collapse) reported by lifeoflust - What steps will reproduce the problem? 1. Use a datapoint which exceeds 61 (i.e. barchart) What is the expected output? What do you see instead? The range is a lovely chart and then collapses because of the Google API encoding algorithm used which must use values within the range of the ~61 characters used for text based data encoding. It appears that when values exceed this, the encoding bumps up to the 4096 range using double char pairs. However, this compresses chart data to an unusable visual range. Please implement scaling based on pixel granularity. The If the data is first converted to 0-100, and range scaling is applied as shown in the API (ie. "&chxr=0,{xmin},{xmax}|1,{ymin},{ymax}") then you don't need to switch the encoding method based on datarange but on pixel range. For instance below chart has 300 pixels, so the max visual step is .33 (%). Set a threshold of this fraction and toggle between the 62 and 4096 range based on it. Love the rest of the API! What version of the product are you using? On what operating system? FF3, XP SP3. Please provide any additional information below. Nice chart --> // Test out some charting classes BarChart chart = new BarChart(BarsType.Stacked, BarsDirection.Vertical, new ChartSize(300, 200), new ChartData(new int[] { 20, 1, 25, 61 }) ); // set colors Color[] colors = new Color[] { Color.DodgerBlue, Color.Orchid, Color.DarkSalmon }; chart.Colors = new ChartColors(colors); Bad Chart --> // Test out some charting classes BarChart chart = new BarChart(BarsType.Stacked, BarsDirection.Vertical, new ChartSize(300, 200), new ChartData(new int[] { 20, 1, 25, 62 }) ); // set colors Color[] colors = new Color[] { Color.DodgerBlue, Color.Orchid, Color.DarkSalmon }; chart.Colors = new ChartColors(colors);

What steps will reproduce the problem? 1. Use a datapoint which exceeds 61 (i.e. barchart) What is the expected output? What do you see instead? The range is a lovely chart and then collapses because of the Google API encoding algorithm used which must use values within the range of the ~61 characters used for text based data encoding. It appears that when values exceed this, the encoding bumps up to the 4096 range using double char pairs. However, this compresses chart data to an unusable visual range. Please implement scaling based on pixel granularity. The If the data is first converted to 0-100, and range scaling is applied as shown in the API (ie. "&chxr=0,{xmin},{xmax}|1,{ymin},{ymax}") then you don't need to switch the encoding method based on datarange but on pixel range. For instance below chart has 300 pixels, so the max visual step is .33 (%). Set a threshold of this fraction and toggle between the 62 and 4096 range based on it. Love the rest of the API! What version of the product are you using? On what operating system? FF3, XP SP3. Please provide any additional information below. Nice chart --> // Test out some charting classes BarChart chart = new BarChart(BarsType.Stacked, BarsDirection.Vertical, new ChartSize(300, 200), new ChartData(new int[] { 20, 1, 25, 61 }) ); // set colors Color[] colors = new Color[] { Color.DodgerBlue, Color.Orchid, Color.DarkSalmon }; chart.Colors = new ChartColors(colors); Bad Chart --> // Test out some charting classes BarChart chart = new BarChart(BarsType.Stacked, BarsDirection.Vertical, new ChartSize(300, 200), new ChartData(new int[] { 20, 1, 25, 62 }) ); // set colors Color[] colors = new Color[] { Color.DodgerBlue, Color.Orchid, Color.DarkSalmon }; chart.Colors = new ChartColors(colors);

Earlier this year

Older