TrackingDiagram - Revision history

Cg_pham at 09:22, 12 September 2013

2013-09-12T09:22:29Z

← Older revision		Revision as of 09:22, 12 September 2013
Line 1:		Line 1:
	~~<accesscontrol>Administrators,,Cem,,Maysunshine</accesscontrol>~~
	[[Category:Miscellaneous]]		[[Category:Miscellaneous]]

Cg_pham at 10:46, 24 October 2011

2011-10-24T10:46:31Z

← Older revision		Revision as of 10:46, 24 October 2011
Line 1:		Line 1:
	<accesscontrol>Administrators,,Cem,,Maysunshine</accesscontrol>		<accesscontrol>Administrators,,Cem,,Maysunshine</accesscontrol>
	[[Category:~~Guidelines~~]]		[[Category:Miscellaneous]]

	[[New Report Design - 2009]] => [[TrackingDiagram]]		[[New Report Design - 2009]] => [[TrackingDiagram]]

Cg_pham at 07:30, 5 October 2011

2011-10-05T07:30:04Z

← Older revision		Revision as of 07:30, 5 October 2011
Line 1:		Line 1:
			<accesscontrol>Administrators,,Cem,,Maysunshine</accesscontrol>
			[[Category:Guidelines]]

	[[New Report Design - 2009]] => [[TrackingDiagram]]		[[New Report Design - 2009]] => [[TrackingDiagram]]

Catglobe at 08:48, 21 April 2010

2010-04-21T08:48:33Z

← Older revision		Revision as of 08:48, 21 April 2010
Line 349:		Line 349:
	*SelfDefinedLayoutType.Tracking_TrendApplied would be inserted info dictionary ChartLayoutInfo.SelfDefinedLayouts<SelfDefinedLayouts, object> by AJAX serializing on client side, which means SelfDefinedLayoutType (also SelfDefinedCriteriaType) converted is in DiagramInfoScriptConverter, through converting class named EnumerableKeyedDictionaryConverter<T> with T is an enum parameter.<br>		*SelfDefinedLayoutType.Tracking_TrendApplied would be inserted info dictionary ChartLayoutInfo.SelfDefinedLayouts<SelfDefinedLayouts, object> by AJAX serializing on client side, which means SelfDefinedLayoutType (also SelfDefinedCriteriaType) converted is in DiagramInfoScriptConverter, through converting class named EnumerableKeyedDictionaryConverter<T> with T is an enum parameter.<br>
	*In TrendHandler, data of trend is solved by TrendDataApplier, style of trend is solved by TrendStyleApplier		*In TrendHandler, data of trend is solved by TrendDataApplier, style of trend is solved by TrendStyleApplier
			*Further feature request can be found [http://forum.catglobe.com/viewtopic.php?f=17&t=101&p=376&sid=4c260ea436b322cefcfb043ed8347940 here]

	[[Image:Trend.png]]<br>		[[Image:Trend.png]]<br>

	=== Unit Test ===		=== Unit Test ===

Catglobe at 07:56, 21 April 2010

2010-04-21T07:56:14Z

← Older revision		Revision as of 07:56, 21 April 2010
Line 352:		Line 352:
	[[Image:Trend.png]]<br>		[[Image:Trend.png]]<br>

	=== Unit Test ===		=== Unit Test ===

			[[Image:TrackingDiagram_FullImplementation_UnitTest.png]]

	== Document revisions ==		== Document revisions ==

Catglobe at 07:47, 21 April 2010

2010-04-21T07:47:18Z

← Older revision		Revision as of 07:47, 21 April 2010
Line 335:		Line 335:
	*TrendHandler and TrackingDiagramTrendHandler (for specific trends of Tracking, inehrits from TrendHandler) :		*TrendHandler and TrackingDiagramTrendHandler (for specific trends of Tracking, inehrits from TrendHandler) :

	#TrendHandler object is one property of DiagramInfo.		#TrendHandler object is one property of DiagramInfo.
	#TrendHanlder would be initialized inside method Freeze of DiagramInfo, if Trend feature has been marked as activated, right after original Expressions (having role to create the original expressions, trace up Specification section, expressions in column B and C).		#TrendHanlder would be initialized inside method Freeze of DiagramInfo, if Trend feature has been marked as activated, right after original Expressions (having role to create the original expressions, trace up Specification section, expressions in column B and C).
	#TrendHanlder would wait untill being called when a framework Diagram builds its data series array : Firstly its method Freeze is called to retrieve its TrendExpressionResolver, known as Trends. Secondly each trend data series and trend data item (trace up Specification section, expressions in column D and E) will be created based on Trends.Thirdly normal data series and trend series become an union.<br>		#TrendHanlder would wait untill being called when a framework Diagram builds its data series array : Firstly its method Freeze is called to retrieve its TrendExpressionResolver, known as Trends. Secondly each trend data series and trend data item (trace up Specification section, expressions in column D and E) will be created based on Trends.Thirdly normal data series and trend series become an union.<br>
Line 341:		Line 341:
	==== Flow of Trend style: ====		==== Flow of Trend style: ====

	*SetPredefinedLayout, SetPredefinedCriteria, SetStyleSheet methods won't be inside Freeze method of DiagramInfo anymore.<br>		*SetPredefinedLayout, SetPredefinedCriteria, SetStyleSheet methods won't be inside Freeze method of DiagramInfo anymore.<br>
	*Styles of trend lines are series styles next to the series styles of normal series, customized (having the same color to corresponding series such as column B and D in Specification section example, line width = 2, etc.) by modifying the style sheet of input diagram, through calling TrendStyleApplier of TrendHandler of DiagramInfo, inside method CopyStaticDataFrom(diagram) then SetStyleSheet(diagram).<br>		*Styles of trend lines are series styles next to the series styles of normal series, customized (having the same color to corresponding series such as column B and D in Specification section example, line width = 2, etc.) by modifying the style sheet of input diagram, through calling TrendStyleApplier of TrendHandler of DiagramInfo, inside method CopyStaticDataFrom(diagram) then SetStyleSheet(diagram).<br>
	*SetPredefinedCriteria(diagram) and SetPredifinedLayout(diagram) methods are also move into CopyStaticDataFrom<br>		*SetPredefinedCriteria(diagram) and SetPredifinedLayout(diagram) methods are also move into CopyStaticDataFrom<br>
Line 347:		Line 347:
	==== Note:<br> ====		==== Note:<br> ====

	*SelfDefinedLayoutType.Tracking_TrendApplied would be inserted info dictionary ChartLayoutInfo.SelfDefinedLayouts<SelfDefinedLayouts, object> by AJAX serializing on client side, which means SelfDefinedLayoutType (also SelfDefinedCriteriaType) converted is in DiagramInfoScriptConverter, through converting class named EnumerableKeyedDictionaryConverter<T> with T is an enum parameter.<br>		*SelfDefinedLayoutType.Tracking_TrendApplied would be inserted info dictionary ChartLayoutInfo.SelfDefinedLayouts<SelfDefinedLayouts, object> by AJAX serializing on client side, which means SelfDefinedLayoutType (also SelfDefinedCriteriaType) converted is in DiagramInfoScriptConverter, through converting class named EnumerableKeyedDictionaryConverter<T> with T is an enum parameter.<br>
	*In TrendHandler, data of trend is solved by TrendDataApplier, style of trend is solved by TrendStyleApplier		*In TrendHandler, data of trend is solved by TrendDataApplier, style of trend is solved by TrendStyleApplier

	[[Image:Trend.png]]<br>		[[Image:Trend.png]]<br>

			=== Unit Test ===

	== Document revisions ==		== Document revisions ==

Catglobe at 07:20, 21 April 2010

2010-04-21T07:20:38Z

← Older revision		Revision as of 07:20, 21 April 2010
Line 142:		Line 142:
	<br>		<br>

	== Full further implementations<br> ==		== Full further implementations<br> ==

	=== Free labels<br> ===		=== Free labels<br> ===
Line 179:		Line 179:
	#Average respondents		#Average respondents
	#Warning low base		#Warning low base
	#Target group: Target group~~ : ~~<br>		#Target group: Target group<br>
	#Subtitle		#Subtitle
	#Calculation methods: Calculation methods : <Rolling average> Week(s)		#Calculation methods: Calculation methods : <Rolling average> Week(s)
Line 207:		Line 207:
	==== Initials:<br> ====		==== Initials:<br> ====

	Inside DynamicExpressionResolver, filters are splitted into concrete types: Time period filter, common filters and target group filters.<br>		*Inside DynamicExpressionResolver, filters are splitted into concrete types: Time period filter, common filters and target group filters.<br>

	==== Flows:<br> ====		==== Flows:<br> ====

	TrackingDiagramInfo (Filters from DiagramInfo) => DynamicExpressionResolver [][] (CommonFilters appended directly into Calculator of DynamicExpressionResolvers, only TimePeriodFilter is appended as conditions into ouput value as expression).		*TrackingDiagramInfo (Filters from DiagramInfo) => DynamicExpressionResolver [][] (CommonFilters appended directly into Calculator of DynamicExpressionResolvers, only TimePeriodFilter is appended as conditions into ouput value as expression).
			*Such as DynamicExpressionResolvers has Value is "=count() where Q1==[1]", TimePeriodFilters is "StartDate >= #2008-1-1# && EndDate <= #2008-2-2#", Filters are "Q2==[2]" and "Q3==[3]", Target groups is "Q4==[4]", then output Value is "=count() where Q1==[1] && StartDate >= #2008-1-1# && EndDate <= #2008-2-2#", its Calculator has Filters including: "Q2==[2]" and "Q3==[3]" and "Q4==[4]".<br>
	Such as DynamicExpressionResolvers has Value is "=count() where Q1==[1]", TimePeriodFilters is "StartDate >= #2008-1-1# && EndDate <= #2008-2-2#", Filters are "Q2==[2]" and "Q3==[3]", Target groups is "Q4==[4]", then output Value is "=count() where Q1==[1] && StartDate >= #2008-1-1# && EndDate <= #2008-2-2#", its Calculator has Filters including: "Q2==[2]" and "Q3==[3]" and "Q4==[4]".<br>		*This leads expession result (for table results) will just show Value with TimePeriodFilter. All filters (including Target groups) shown in Filter section only. This will make the long expression table seems easier to review.<br>

	This leads expession result (for table results) will just show Value with TimePeriodFilter. All filters (including Target groups) shown in Filter section only. This will make the long expression table seems easier to review.<br>

	==== Notes:<br> ====		==== Notes:<br> ====

	Both Target groups and Filters are recognized as CommonFilters.<br>		*Both Target groups and Filters are recognized as CommonFilters.<br>
			*Target groups and Filters can be distinguished by type of FilterInfo (must be initialized whenever input Target groups/Filters). Filters should have FilterInfoType as Normal, Target groups should have FilterInfoType as Specific (just for further case when it's necessary to pick up particular Filters or Target groups).<br>
	Target groups and Filters can be distinguished by type of FilterInfo (must be initialized whenever input Target groups/Filters). Filters should have FilterInfoType as Normal, Target groups should have FilterInfoType as Specific (just for further case when it's necessary to pick up particular Filters or Target groups).<br>		*To apply general filters into filters of each DynamicExpressionResolver:<br>
			*Property Filters of DiagramInfo becomes virtual.<br>
	To apply general filters into filters of each DynamicExpressionResolver:<br>		*Property Filters of TrackingDiagramInfo overrides DiagramInfo's, also immediately update CommonFilters of its Expressions which are set.<br>
			*Property Filters of ICalculator has purpose to handle FilterExpressions of its Interpreter (known as CGScriptEngine)
	Property Filters of DiagramInfo becomes virtual.<br>

	Property Filters of TrackingDiagramInfo overrides DiagramInfo's, also immediately update CommonFilters of its Expressions which are set.<br>

	Such as:<br> <source lang="csharp">public override FilterInfo[] Filters		Such as:<br> <source lang="csharp">public override FilterInfo[] Filters
Line 246:		Line 241:
	[[Image:Target Filters.png]]<br>		[[Image:Target Filters.png]]<br>

	<br>		<br>

	=== Trendline ===		=== Trendline ===
Line 302:		Line 297:

	\|-		\|-
	\| Separation between Trend line and normal data<br>		\| '''''Separation between Trend line and normal data'''''<br>
	\| Trend series are separated from normal series by number of series<br>		\| Trend series are separated from normal series by number of series<br>
	\|		\|
Line 311:		Line 306:
	\| <br>		\| <br>
	\|-		\|-
	\| Style of Trend lines<br>		\| '''''Style of Trend lines'''''<br>
	\|		\|
	Stylesheet stays directly on viewer page, initialized & interfered when it's called on the first time by object StyleSheetFactory, by so that the line styles of Trends can be modified with the same of corresponding main series<br>		Stylesheet stays directly on viewer page, initialized & interfered when it's called on the first time by object StyleSheetFactory, by so that the line styles of Trends can be modified with the same of corresponding main series<br>
Line 336:		Line 331:
	#Trimming unneeded properties (such as Condition, ValueFiltered etc.) because Trend function has the only one formula and structure		#Trimming unneeded properties (such as Condition, ValueFiltered etc.) because Trend function has the only one formula and structure
	#Override to get resulted value through property ValueResulted. ValueResulted of DynamicExpressionResolver is only calculated by its inner Calculator and its ValueFiltered. ValueFiltered of TrendExpressionResolver is calculated by an outer DataTable joining the Value of itself (trace the Specification section).		#Override to get resulted value through property ValueResulted. ValueResulted of DynamicExpressionResolver is only calculated by its inner Calculator and its ValueFiltered. ValueFiltered of TrendExpressionResolver is calculated by an outer DataTable joining the Value of itself (trace the Specification section).
	#ICalculator, PseudoCalculator, CGScriptCalculator also get one new method named Execute(DataTable) to evaluate the whole input data table with formulas related to other result inside data table (trace the Specification section)		#ICalculator, PseudoCalculator, CGScriptCalculator also get one new method named Execute(DataTable) and Execute(DataTable, Converter<object, object>) to evaluate the whole input data table with formulas related to other result inside data table (trace the Specification section)

	*TrendHandler and TrackingDiagramTrendHandler (for specific trends of Tracking, inehrits from TrendHandler) :		*TrendHandler and TrackingDiagramTrendHandler (for specific trends of Tracking, inehrits from TrendHandler) :

	#TrendHandler object is one property of DiagramInfo.		#TrendHandler object is one property of DiagramInfo.
	#TrendHanlder would be initialized inside method Freeze of DiagramInfo, if Trend feature has been marked as activated, right after original Expressions (having role to create the original expressions, trace up Specification section, expressions in column B and C).		#TrendHanlder would be initialized inside method Freeze of DiagramInfo, if Trend feature has been marked as activated, right after original Expressions (having role to create the original expressions, trace up Specification section, expressions in column B and C).
	#TrendHanlder would wait untill being called when a framework Diagram builds its data series array : Firstly its method Freeze is called to retrieve its TrendExpressionResolver, known as Trends. Secondly each trend data series and trend data item (trace up Specification section, expressions in column D and E) will be created based on Trends.Thirdly normal data series and trend series become an union.<br>		#TrendHanlder would wait untill being called when a framework Diagram builds its data series array : Firstly its method Freeze is called to retrieve its TrendExpressionResolver, known as Trends. Secondly each trend data series and trend data item (trace up Specification section, expressions in column D and E) will be created based on Trends.Thirdly normal data series and trend series become an union.<br>
Line 346:		Line 341:
	==== Flow of Trend style: ====		==== Flow of Trend style: ====

			*SetPredefinedLayout, SetPredefinedCriteria, SetStyleSheet methods won't be inside Freeze method of DiagramInfo anymore.<br>
	*Styles of trend lines are series styles next to the series styles of normal series, customized (having the same color to corresponding series such as column B and D in Specification section example, line width = 2, etc.) by modifying the style sheet of input diagram, through calling TrendStyleApplier of TrendHandler of DiagramInfo, inside method CopyStaticDataFrom(diagram) then SetStyleSheet(diagram).<br>		*Styles of trend lines are series styles next to the series styles of normal series, customized (having the same color to corresponding series such as column B and D in Specification section example, line width = 2, etc.) by modifying the style sheet of input diagram, through calling TrendStyleApplier of TrendHandler of DiagramInfo, inside method CopyStaticDataFrom(diagram) then SetStyleSheet(diagram).<br>
	*SetPredefinedCriteria(diagram) and SetPredifinedLayout(diagram) methods are also move into CopyStaticDataFrom<br>		*SetPredefinedCriteria(diagram) and SetPredifinedLayout(diagram) methods are also move into CopyStaticDataFrom<br>
Line 351:		Line 347:
	==== Note:<br> ====		==== Note:<br> ====

	*SelfDefinedLayoutType.Tracking_TrendApplied would be inserted info dictionary ChartLayoutInfo.SelfDefinedLayouts by ~~javascript~~ serializing on client side, which means SelfDefinedLayoutType converted is ~~appended into~~ DiagramInfoScriptConverter, named ~~SelfDefinedLayoutTypeConverter~~.<br>		*SelfDefinedLayoutType.Tracking_TrendApplied would be inserted info dictionary ChartLayoutInfo.SelfDefinedLayouts<SelfDefinedLayouts, object> by AJAX serializing on client side, which means SelfDefinedLayoutType (also SelfDefinedCriteriaType) converted is in DiagramInfoScriptConverter, through converting class named EnumerableKeyedDictionaryConverter<T> with T is an enum parameter.<br>
	*In TrendHandler, data of trend is solved by TrendDataApplier, style of trend is solved by TrendStyleApplier		*In TrendHandler, data of trend is solved by TrendDataApplier, style of trend is solved by TrendStyleApplier

Catglobe at 04:49, 19 April 2010

2010-04-19T04:49:29Z

← Older revision		Revision as of 04:49, 19 April 2010
Line 229:		Line 229:
	Property Filters of TrackingDiagramInfo overrides DiagramInfo's, also immediately update CommonFilters of its Expressions which are set.<br>		Property Filters of TrackingDiagramInfo overrides DiagramInfo's, also immediately update CommonFilters of its Expressions which are set.<br>

	Such as:<br> public override FilterInfo[] Filters~~<br>~~ {~~<br>~~ get { return _filters; }~~<br>~~ set~~<br>~~ {~~<br>~~ _filters = value;~~<br>~~ if (Expressions~~ ~~!= null)~~<br>~~ {~~<br>~~ for (var r = 0; r ~~<~~ Expressions.Length; r++)~~<br>~~ for (var c = 0; c ~~<~~ Expressions[r].Length; c++)~~<br>~~ Expressions[r][c].CommonFilters = _filters;~~<br>~~ }~~<br>~~ }<br> }<br>		Such as:<br> <source lang="csharp">public override FilterInfo[] Filters
			{
			get { return _filters; }
			set
			{
			_filters = value;
			if (Expressions != null)
			{
			for (var r = 0; r < Expressions.Length; r++)
			for (var c = 0; c < Expressions[r].Length; c++)
			Expressions[r][c].CommonFilters = _filters;
			}
			}
			}</source><br>

	[[Image:~~Target_Filters~~.png]]<br>		[[Image:Target Filters.png]]<br>

	<br>		<br>

Catglobe at 07:32, 16 April 2010

2010-04-16T07:32:05Z

← Older revision		Revision as of 07:32, 16 April 2010
Line 323:		Line 323:
	#Trimming unneeded properties (such as Condition, ValueFiltered etc.) because Trend function has the only one formula and structure		#Trimming unneeded properties (such as Condition, ValueFiltered etc.) because Trend function has the only one formula and structure
	#Override to get resulted value through property ValueResulted. ValueResulted of DynamicExpressionResolver is only calculated by its inner Calculator and its ValueFiltered. ValueFiltered of TrendExpressionResolver is calculated by an outer DataTable joining the Value of itself (trace the Specification section).		#Override to get resulted value through property ValueResulted. ValueResulted of DynamicExpressionResolver is only calculated by its inner Calculator and its ValueFiltered. ValueFiltered of TrendExpressionResolver is calculated by an outer DataTable joining the Value of itself (trace the Specification section).
	#ICalculator, PseudoCalculator, CGScriptCalculator also get one new method named Execute(DataTable~~, Func<object, string>~~) to evaluate the whole input data table with formulas related to other result inside data table (trace the Specification section)		#ICalculator, PseudoCalculator, CGScriptCalculator also get one new method named Execute(DataTable) to evaluate the whole input data table with formulas related to other result inside data table (trace the Specification section)

	*TrendHandler and TrackingDiagramTrendHandler (for specific trends of Tracking, inehrits from TrendHandler) :		*TrendHandler and TrackingDiagramTrendHandler (for specific trends of Tracking, inehrits from TrendHandler) :

Catglobe at 03:06, 16 April 2010

2010-04-16T03:06:55Z

← Older revision		Revision as of 03:06, 16 April 2010
Line 360:		Line 360:
	\|-		\|-
	\| 0.1.1		\| 0.1.1
	\| 15.01.~~2009~~		\| 15.01.2010
	\| Nguyễn Điển Nghĩa		\| Nguyễn Điển Nghĩa
	\| Initialize basic class		\| Initialize basic class
Line 366:		Line 366:
	\|-		\|-
	\| 0.1.2		\| 0.1.2
	\| 01.02.~~2009~~		\| 01.02.2010
	\| Nguyễn Điển Nghĩa		\| Nguyễn Điển Nghĩa
	\| Finished TD, coding and wiki report		\| Simplest case : Finished TD, coding and wiki report
	\| 59899		\| 59899
			\|-
			\| 0.1.3
			\| 16.04.2010
			\| Nguyễn Điển Nghĩa
			\| Full implementation : TD for Trendline, Target groups/Filters,...
			\|
	\|}		\|}