ExpressionScript Engine roadmap - Revision history

C schmitz: Text replacement - "ExpressionManager" to "ExpressionScript Engine"

2020-02-11T13:50:05Z

Text replacement - "ExpressionManager" to "ExpressionScript Engine"

← Older revision		Revision as of 15:50, 11 February 2020
Line 1:		Line 1:

	This page is for tracking the development status and TODO lists for ~~ExpressionManager~~		This page is for tracking the development status and TODO lists for ExpressionScript Engine

	__TOC__		__TOC__
Line 19:		Line 19:


	~~ExpressionManager~~ can be called dozens to hundreds of times per page. Instead, it should be possible to concatenate together the roughly tailored parts of the survey page and call Expression Manager once per page (or at least fewer times).		ExpressionScript Engine can be called dozens to hundreds of times per page. Instead, it should be possible to concatenate together the roughly tailored parts of the survey page and call Expression Manager once per page (or at least fewer times).

	To accomplish this, two things are needed:		To accomplish this, two things are needed:
	#Ensure that all replacement values are correct when called. Some values like {QUESTION} change multiple times per page. Others are constant across all pages.		#Ensure that all replacement values are correct when called. Some values like {QUESTION} change multiple times per page. Others are constant across all pages.
	#Find a way to concatenate together all page components prior to calling ~~ExpressionManager~~.		#Find a way to concatenate together all page components prior to calling ExpressionScript Engine.

	For values that change multiple times per page (like {QUESTION}), I'd like to replace calls to templatereplace(), replaceTokens(), insertAnsReplace(), dTexts, and replaceFields() (several of which call ~~ExpressionManager~~) as follows:		For values that change multiple times per page (like {QUESTION}), I'd like to replace calls to templatereplace(), replaceTokens(), insertAnsReplace(), dTexts, and replaceFields() (several of which call ExpressionScript Engine) as follows:
	*Templates: (except for Group and Question) - return as they are so they get processed at the end;		*Templates: (except for Group and Question) - return as they are so they get processed at the end;
	*Group Template: Replace {GROUP} with something like {GROUP_N} which ~~ExpressionManager~~ would then substitute at the end;		*Group Template: Replace {GROUP} with something like {GROUP_N} which ExpressionScript Engine would then substitute at the end;
	*Question Template: Replace {QUESTION} and {ANSWER} with something like {QUESTION_N} and {ANSWER_N} which would also get replaced after the whole page was composed.		*Question Template: Replace {QUESTION} and {ANSWER} with something like {QUESTION_N} and {ANSWER_N} which would also get replaced after the whole page was composed.

C schmitz: C schmitz moved page Expression Manager roadmap to ExpressionScript Engine roadmap

2020-02-11T13:32:07Z

C schmitz moved page Expression Manager roadmap to ExpressionScript Engine roadmap

← Older revision	Revision as of 15:32, 11 February 2020
(No difference)

Cdorin: /* Where within LimeSurvey is each Keyword Used? */

2018-08-07T13:24:05Z

Where within LimeSurvey is each Keyword Used?

← Older revision		Revision as of 15:24, 7 August 2018
Line 205:		Line 205:

	A green 1 means that the keyword is used in that file at least once.		A green 1 means that the keyword is used in that file at least once.


	[[File:keywords-usage-1.jpg]]		[[File:keywords-usage-1.jpg]]


	[[File:keywords-usage-header.jpg]]		[[File:keywords-usage-header.jpg]]


	[[File:keywords-usage-2.jpg]]		[[File:keywords-usage-2.jpg]]

Cdorin at 13:23, 7 August 2018

2018-08-07T13:23:35Z

← Older revision		Revision as of 15:23, 7 August 2018
Line 3:		Line 3:

	__TOC__		__TOC__


	=Status=		=Status=


	EM was introduced in version 1.92+ (released in March 2012). Since then it is a part of every LimeSurvey distribution.		EM was introduced in version 1.92+ (released in March 2012). Since then it is a part of every LimeSurvey distribution.

	~~=Upgrade Notes=~~

	~~There are a few backwards incompatibilities between 1.92 and 1.91. Please [[Upgrade hints for version 1.92\|read them]] carefully.~~

	=Wish List for EM-Related Enhancements=		=Wish List for EM-Related Enhancements=
	*[[Project Ideas for GSoC 2012#Enhance Expression Manager\|Enhance Expression Manager]]		*[[Project Ideas for GSoC 2012#Enhance Expression Manager\|Enhance Expression Manager]]
	*[[Project Ideas for GSoC 2012#Optimize LimeSurvey for Long Surveys\|Optimize LimeSurvey for Long Surveys and better performance and maintenance in general]]		*[[Project Ideas for GSoC 2012#Optimize LimeSurvey for Long Surveys\|Optimize LimeSurvey for Long Surveys and better performance and maintenance in general]]


	=Performance Tuning Notes=		=Performance Tuning Notes=

	ExpressionManager can be called dozens to hundreds of times per page. ~~Instead~~, it should be possible to concatenate together the roughly tailored parts of the survey page and call Expression Manager once per page (or at least fewer times).
			ExpressionManager can be called dozens to hundreds of times per page. Instead, it should be possible to concatenate together the roughly tailored parts of the survey page and call Expression Manager once per page (or at least fewer times).

	To accomplish this, two things are needed:		To accomplish this, two things are needed:
	#Ensure that all replacement values are correct when ~~called~~. ~~Some~~ values like {QUESTION} change multiple times per page. ~~Others~~ are constant across all pages.		#Ensure that all replacement values are correct when called. Some values like {QUESTION} change multiple times per page. Others are constant across all pages.
	#Find way to concatenate together all page components ~~priort~~ to calling ExpressionManager.		#Find a way to concatenate together all page components prior to calling ExpressionManager.

	For values that change multiple times per page (like {QUESTION}), I'd like to replace calls to templatereplace(), replaceTokens(), insertAnsReplace(), dTexts, and replaceFields() (several of which call ExpressionManager) as follows:		For values that change multiple times per page (like {QUESTION}), I'd like to replace calls to templatereplace(), replaceTokens(), insertAnsReplace(), dTexts, and replaceFields() (several of which call ExpressionManager) as follows:
	*Templates: (except for Group and Question) - return as is so they get processed at the end		*Templates: (except for Group and Question) - return as they are so they get processed at the end;
	*Group Template: ~~Replace~~ {GROUP} with something like {GROUP_N} which ExpressionManager would then substitute at the end		*Group Template: Replace {GROUP} with something like {GROUP_N} which ExpressionManager would then substitute at the end;
	*Question Template: ~~Replace~~ {QUESTION} ~~and~~ {ANSWER} with something like {QUESTION_N} and {ANSWER_N} which would also get replaced after the whole page was composed.		*Question Template: Replace {QUESTION} and {ANSWER} with something like {QUESTION_N} and {ANSWER_N} which would also get replaced after the whole page was composed.


	==When are each of the following attributes changed?==		==When are each of the following attributes changed?==


	Here are the possibilities:		Here are the possibilities:
	*global - means that the value is global for the LimeSurvey instance (across all surveys and sessions		*global - means that the value is global for the LimeSurvey instance (across all surveys and sessions);
	*survey - means each survey might have a different value		*survey - means each survey might have a different value;
	*session - means the value should be static across a given session		*session - means the value should be static across a given session
	*page - means that the value on each page might differ		*page - means that the value on each page might differ
Line 196:		Line 199:
	\|		\|
	\|}		\|}


	==Where within LimeSurvey is each Keyword Used?==		==Where within LimeSurvey is each Keyword Used?==


	A green 1 means that the keyword is used in that file at least once.		A green 1 means that the keyword is used in that file at least once.


	[[File:keywords-usage-1.jpg]]		[[File:keywords-usage-1.jpg]]


	[[File:keywords-usage-header.jpg]]		[[File:keywords-usage-header.jpg]]


	[[File:keywords-usage-2.jpg]]		[[File:keywords-usage-2.jpg]]

Cdorin: Cdorin moved page Expression Manager Roadmap to Expression Manager roadmap

2017-08-02T12:41:08Z

Cdorin moved page Expression Manager Roadmap to Expression Manager roadmap

← Older revision		Revision as of 14:41, 2 August 2017
(No difference)

Tammo: /* Status */

2016-11-22T17:10:23Z

Status

← Older revision		Revision as of 19:10, 22 November 2016
Line 6:		Line 6:
	=Status=		=Status=

	1.92+ ~~stable was~~ released in March, 2012.		EM was introduced in version 1.92+ (released in March 2012). Since then it is a part of every LimeSurvey distribution.

	=Upgrade Notes=		=Upgrade Notes=

Han: /* Wish List for EM-Related Enhancements */

2013-06-17T13:47:35Z

Wish List for EM-Related Enhancements

← Older revision		Revision as of 15:47, 17 June 2013
Line 14:		Line 14:
	=Wish List for EM-Related Enhancements=		=Wish List for EM-Related Enhancements=
	*[[Project Ideas for GSoC 2012#Enhance Expression Manager\|Enhance Expression Manager]]		*[[Project Ideas for GSoC 2012#Enhance Expression Manager\|Enhance Expression Manager]]
	*[[Project Ideas for GSoC 2012#Optimize LimeSurvey\|Optimize LimeSurvey for Long Surveys and better performance and maintenance in general]]		*[[Project Ideas for GSoC 2012#Optimize LimeSurvey for Long Surveys\|Optimize LimeSurvey for Long Surveys and better performance and maintenance in general]]

	=Performance Tuning Notes=		=Performance Tuning Notes=

Han: /* Wish List for EM-Related Enhancements */

2013-06-17T13:46:39Z

Wish List for EM-Related Enhancements

← Older revision		Revision as of 15:46, 17 June 2013
Line 14:		Line 14:
	=Wish List for EM-Related Enhancements=		=Wish List for EM-Related Enhancements=
	*[[Project Ideas for GSoC 2012#Enhance Expression Manager\|Enhance Expression Manager]]		*[[Project Ideas for GSoC 2012#Enhance Expression Manager\|Enhance Expression Manager]]
	*[[Project Ideas for GSoC 2012#Optimize LimeSurvey ~~for Long Surveys and better performance and maintenance in general~~\|Optimize LimeSurvey for Long Surveys and better performance and maintenance in general]]		*[[Project Ideas for GSoC 2012#Optimize LimeSurvey\|Optimize LimeSurvey for Long Surveys and better performance and maintenance in general]]

	=Performance Tuning Notes=		=Performance Tuning Notes=

Han: /* Wish List for EM-Related Enhancements */

2013-06-17T13:43:32Z

Wish List for EM-Related Enhancements

← Older revision		Revision as of 15:43, 17 June 2013
Line 13:		Line 13:

	=Wish List for EM-Related Enhancements=		=Wish List for EM-Related Enhancements=
	*[[Project Ideas for GSoC 2012\|#Enhance Expression Manager\|Enhance Expression Manager]]		*[[Project Ideas for GSoC 2012#Enhance Expression Manager\|Enhance Expression Manager]]
	*[[Project Ideas for GSoC 2012\|#Optimize LimeSurvey for Long Surveys and better performance and maintenance in general\|Optimize LimeSurvey for Long Surveys and better performance and maintenance in general]]		*[[Project Ideas for GSoC 2012#Optimize LimeSurvey for Long Surveys and better performance and maintenance in general\|Optimize LimeSurvey for Long Surveys and better performance and maintenance in general]]

	=Performance Tuning Notes=		=Performance Tuning Notes=

TMSWhite at 06:10, 30 June 2012

2012-06-30T06:10:58Z

@@ Line 13: / Line 13: @@
 =Wish List for EM-Related Enhancements=
 *[[Project Ideas for GSoC 2012|#Enhance Expression Manager|Enhance Expression Manager]]
 *[[Project Ideas for GSoC 2012|#Optimize LimeSurvey for Long Surveys and better performance and maintenance in general|Optimize LimeSurvey for Long Surveys and better performance and maintenance in general]]