Project ideas for GSoC 2015 - Revision history

C schmitz: Text replacement - "Expression Manager" to "ExpressionScript"

2020-02-11T13:45:12Z

Text replacement - "Expression Manager" to "ExpressionScript"

← Older revision		Revision as of 15:45, 11 February 2020
Line 20:		Line 20:
	==Visualize different paths through a survey based on conditions set at a survey==		==Visualize different paths through a survey based on conditions set at a survey==

	Limesurvey's ~~Expression Manager~~ (EM) allows [https://manual.limesurvey.org/Expression_Manager#Relevance_.28Controlling_Navigation.2FBranching.29 adding complex conditions] to survey questions so that certain questions are only shown if those conditions validate to "true". At lengthy surveys with lots of conditions this will create several different potentials paths through a survey depending on the answers given by a user.		Limesurvey's ExpressionScript (EM) allows [https://manual.limesurvey.org/Expression_Manager#Relevance_.28Controlling_Navigation.2FBranching.29 adding complex conditions] to survey questions so that certain questions are only shown if those conditions validate to "true". At lengthy surveys with lots of conditions this will create several different potentials paths through a survey depending on the answers given by a user.
	To help our growing user base to deal with this complex problem we plan to create a fully new tool for visualizing the different paths through a survey based on the existing conditions.		To help our growing user base to deal with this complex problem we plan to create a fully new tool for visualizing the different paths through a survey based on the existing conditions.


	'''Steps'''		'''Steps'''
	# Have a look at the [https://manual.limesurvey.org/Expression_Manager ~~Expression Manager~~ documentation] to get familiar with this powerful tool for creating complex conditions		# Have a look at the [https://manual.limesurvey.org/Expression_Manager ExpressionScript documentation] to get familiar with this powerful tool for creating complex conditions
	# Check how conditions are stored at the database		# Check how conditions are stored at the database
	# Analyse how EM internally handles conditions to determine whether a question should be displayed		# Analyse how EM internally handles conditions to determine whether a question should be displayed
Line 168:		Line 168:
	[[User:DenisChenu\|Denis Chenu]]		[[User:DenisChenu\|Denis Chenu]]

	==~~Expression Manager~~ JavaScript optimizations==		==ExpressionScript JavaScript optimizations==

	Actually the ~~Expression Manager~~ in LimeSurvey uses inline JavaScript for relevance, updating classes and updating HTML. In its current state an administrator or extension developer can not use their own functions. The task is to update Expression manager inline JavaScript to use an JavaScript-only event on update expression manager javascript to call an actual function on this events.		Actually the ExpressionScript in LimeSurvey uses inline JavaScript for relevance, updating classes and updating HTML. In its current state an administrator or extension developer can not use their own functions. The task is to update Expression manager inline JavaScript to use an JavaScript-only event on update expression manager javascript to call an actual function on this events.

	The second part of this task is to move inline Javascript to jQuery. In the old current system each input (when taking a survey) uses the onchange/onkeyup function to fire events. The idea is to remove these inline code and use only JavaScript/jQuery general code where possible.		The second part of this task is to move inline Javascript to jQuery. In the old current system each input (when taking a survey) uses the onchange/onkeyup function to fire events. The idea is to remove these inline code and use only JavaScript/jQuery general code where possible.
Line 176:		Line 176:
	'''Skills'''		'''Skills'''

	Some PHP to update ~~Expression Manager~~ class, deep jQuery/JavaScript knowledge. A jQuery plugin might be a great idea.		Some PHP to update ExpressionScript class, deep jQuery/JavaScript knowledge. A jQuery plugin might be a great idea.

	'''Difficulty'''		'''Difficulty'''

DenisChenu: /* Replace current CKEditor usage with TinyMCE */

2015-02-27T09:14:17Z

Replace current CKEditor usage with TinyMCE

← Older revision		Revision as of 11:14, 27 February 2015
Line 224:		Line 224:

	This task is linked with [[#Make_use_of_the_SettingsWidget_for_core_functions]]		This task is linked with [[#Make_use_of_the_SettingsWidget_for_core_functions]]

	'''Skills'''		'''Skills'''

DenisChenu: /* Make use of the SettingsWidget for core functions */

2015-02-27T09:13:49Z

Make use of the SettingsWidget for core functions

← Older revision		Revision as of 11:13, 27 February 2015
Line 162:		Line 162:
	* [http://bugs.limesurvey.org/view.php?id=9523 SettingsWidget :renderHTML]		* [http://bugs.limesurvey.org/view.php?id=9523 SettingsWidget :renderHTML]
	* [http://bugs.limesurvey.org/view.php?id=9501 SettingsWidget :renderDate / DateTime and Time]		* [http://bugs.limesurvey.org/view.php?id=9501 SettingsWidget :renderDate / DateTime and Time]
			* [http://bugs.limesurvey.org/view.php?id=9537 Plugin manager : legend without fieldset]

	'''Mentor(s)'''		'''Mentor(s)'''

Sammousa: /* Make use of the SettingsWidget for core functions */

2015-02-24T15:10:47Z

Make use of the SettingsWidget for core functions

← Older revision		Revision as of 17:10, 24 February 2015
Line 147:		Line 147:
	* Survey settings		* Survey settings
	* Personal settings		* Personal settings
	* Users settings		* Users settings (IN LS3 users' settings are managed by the authentication plugin and already use SettingsWidget)
	* Export settings		* Export settings

DenisChenu: /* Remove jQuery UI and replace it with Bootstrap, harmonize GUI of different admin screens */

2015-02-24T11:33:40Z

Remove jQuery UI and replace it with Bootstrap, harmonize GUI of different admin screens

← Older revision		Revision as of 13:33, 24 February 2015
Line 101:		Line 101:
	'''Mentor(s)'''		'''Mentor(s)'''

	Marcel Minke ([[User:Mazi\|Mazi]]), Carsten Schmitz		* Marcel Minke ([[User:Mazi\|Mazi]])
			* Carsten Schmitz
			* [[User:DenisChenu\|Denis Chenu]]

	==Re-organize the Limesurvey Admin Interface for better Navigation Usability==		==Re-organize the Limesurvey Admin Interface for better Navigation Usability==

DenisChenu: /* Replace current CKEditor usage with TinyMCE */

2015-02-24T11:32:50Z

Replace current CKEditor usage with TinyMCE

← Older revision		Revision as of 13:32, 24 February 2015
Line 220:		Line 220:
	As mentioned before the functionality of the existing CKEditor extensions need to be ported as TinyMCE plugins.		As mentioned before the functionality of the existing CKEditor extensions need to be ported as TinyMCE plugins.

			This task is linked with [[#Make_use_of_the_SettingsWidget_for_core_functions]]
	'''Skills'''		'''Skills'''

Line 236:		Line 236:
	*[[User:C_schmitz\|Carsten Schmitz]]		*[[User:C_schmitz\|Carsten Schmitz]]
	*Sam Mousa		*Sam Mousa
			*[[User:DenisChenu\|Denis Chenu]]

	==Idea template==		==Idea template==

C schmitz: /* Welcome, Google Summer of Code student aspirants! */

2015-02-23T15:32:16Z

Welcome, Google Summer of Code student aspirants!

← Older revision		Revision as of 17:32, 23 February 2015
Line 6:		Line 6:

	You can also find alot of ideas for new features in our [http://bugs.limesurvey.org/set_project.php?ref=view_all_set.php&project_id=12 feature tracker]		You can also find alot of ideas for new features in our [http://bugs.limesurvey.org/set_project.php?ref=view_all_set.php&project_id=12 feature tracker]

			Also have a look at our following documents:

			*[[GSoC FAQ]]
			*[[GSoC getting started]]
			*[[GSoC selection criteria]]
			*[[GSoC Student Application Template]]

	We are looking forward to your proposal. Good luck!		We are looking forward to your proposal. Good luck!

Mazi: /* Additional links */

2015-02-23T14:58:16Z

Additional links

← Older revision		Revision as of 16:58, 23 February 2015
Line 247:		Line 247:

	=Additional links=		=Additional links=
			==Official GSoC links==
	*[https://www.google-melange.com/gsoc/homepage/google/gsoc2015 GSoC 2015 website]		*[https://www.google-melange.com/gsoc/homepage/google/gsoc2015 GSoC 2015 website]
	*[https://www.google-melange.com/gsoc/events/google/gsoc2015 GSoC 2015 Timeline/Deadlines]		*[https://www.google-melange.com/gsoc/events/google/gsoc2015 GSoC 2015 Timeline/Deadlines]
			*[https://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2015/help_page GSoC 2015 FAQ page]

			==Limesurvey coding details==
	*[https://manual.limesurvey.org/Coding_guidelines Limesurvey coding guidelines]		*[https://manual.limesurvey.org/Coding_guidelines Limesurvey coding guidelines]
	*[https://manual.limesurvey.org/Accessing_the_source_code Accessing the Limesurvey source code]		*[https://manual.limesurvey.org/Accessing_the_source_code Accessing the Limesurvey source code]
			*[https://manual.limesurvey.org/Standard_for_Git_commit_messages Standard GIT commit messages]
	*[https://manual.limesurvey.org/Directory_structure Limesurvey code base and directory structure]		*[https://manual.limesurvey.org/Directory_structure Limesurvey code base and directory structure]
			*[https://manual.limesurvey.org/Yii Basic Yii framework information]

			==General information==
	*[https://manual.limesurvey.org/GSoC_getting_started GSoC - Getting started]		*[https://manual.limesurvey.org/GSoC_getting_started GSoC - Getting started]
	*[https://manual.limesurvey.org/GSoC_FAQ GSoC FAQ]
	*[https://manual.limesurvey.org/Writing_GSoC_application How to write your application]		*[https://manual.limesurvey.org/Writing_GSoC_application How to write your application]
	*[https://manual.limesurvey.org/GSoC_Student_Application_Template Application template]		*[https://manual.limesurvey.org/GSoC_Student_Application_Template Application template]
	*[https://manual.limesurvey.org/GSoC_selection_criteria Our selection criteria]		*[https://manual.limesurvey.org/GSoC_selection_criteria Our selection criteria]
	*[https://manual.limesurvey.org/~~Yii Basic Yii framework information~~]		*[https://manual.limesurvey.org/GSoC_FAQ GSoC FAQ]

	[[Category:GSOC_2015]]		[[Category:GSOC_2015]]

Mazi: /* Remove jQuery UI and replace it with Bootstrap, harmonize GUI of different admin screens */

2015-02-23T14:37:39Z

Remove jQuery UI and replace it with Bootstrap, harmonize GUI of different admin screens

← Older revision		Revision as of 16:37, 23 February 2015
Line 81:		Line 81:
	# Adjust the admin GUI code to make it fully Bootstrap compatible.		# Adjust the admin GUI code to make it fully Bootstrap compatible.
	# Check all Limesurvey admin screens, standardize the layout/design and polish them where needed.		# Check all Limesurvey admin screens, standardize the layout/design and polish them where needed.


	'''Skills'''		'''Skills'''

Mazi: /* Remove jQuery UI and replace it with Bootstrap, harmonize GUI of different admin screens */

2015-02-23T13:50:50Z

Remove jQuery UI and replace it with Bootstrap, harmonize GUI of different admin screens

← Older revision		Revision as of 15:50, 23 February 2015
Line 69:		Line 69:

	The Limesurvey admin GUI currently uses a mixture of jQuery UI and Bootstrap code. That does not only make the related code difficult to maintain, it also creates a lot of overhead.		The Limesurvey admin GUI currently uses a mixture of jQuery UI and Bootstrap code. That does not only make the related code difficult to maintain, it also creates a lot of overhead.
	In addition to that, the different admin screens are not overall standardized and lack harmonization		In addition to that, the different admin screens are not overall standardized and lack harmonization.

	This task aims at standardizing the ~20-25 different Limesurvey admin screens and cleaning up the underlying code for easier maintenance and faster loading times.		This task aims at standardizing the ~20-25 different Limesurvey admin screens and cleaning up the underlying code for easier maintenance and faster loading times.
Line 75:		Line 75:

	'''Steps'''		'''Steps'''
	# Click through the different screen at the Limesurvey admin interface. Note which screens already look nice and which ones or not following the overall design standards.		# Click through the different screen at the Limesurvey admin interface. Note which screens already look nice and which ones are not following the overall design standards.
	# Take a look at the related source code and views to see how the code for the ~~screens~~ is structured and which libraries are used.		# Take a look at the related source code and MVC views to see how the code for the views is structured and which libraries are used.
	# Note where at the code jQuery UI is used.		# Note where at the code jQuery UI is used.
	# Test how to best remove the jQuery UI elements and what is needed to replace that code with Bootstrap features.		# Test how to best remove the jQuery UI elements and what is needed to replace that code with Bootstrap features.
Line 94:		Line 94:

	Marcel Minke ([[User:Mazi\|Mazi]]), Carsten Schmitz		Marcel Minke ([[User:Mazi\|Mazi]]), Carsten Schmitz



	==Re-organize the Limesurvey Admin Interface for better Navigation Usability==		==Re-organize the Limesurvey Admin Interface for better Navigation Usability==