Project ideas for GSoC 2015: Difference between revisions
From LimeSurvey Manual
Line 96: | Line 96: | ||
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 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. | ||
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. | |||
'''Skills''' | '''Skills''' |
Revision as of 18:53, 20 February 2015
Welcome
Project ideas
Update Limesurvey Template Engine to use Twig
Currently Limesurvey uses its own custom coded template engine. Since the framework used for Limesurvey ("Yii") supports the Twig template engine we plan to replace the custom coded template engine with Twig's template engine for better code maintenance and embedding with the Yii framework.
Steps
- Check how the current Limesurvey templates are structured
- Dig into the related code to find out how the underlying Limesurvey template engine works
- Get familiar with the structure of Twig templates
- Test-edit one of the shipped templates and make it twig-compatible
- Embed the Twig template engine into Limesurvey
- Test your test template and the Twig template engine carefully
- Adjust further shipped Limesurvey templates
Skills
You should know how a template engine and framework works. In addition to that HTML and CSS skills are required for adjusting the shipped Limesurvey templates. You should also know about PHP because switching the template engine will require adjustments of the Limesurvey source code as well.
Difficulty
Easy to medium
Mentor(s)
Marcel Minke (Mazi)
When creating a survey at the Limesurvey admin interface the current page structure is: survey list -> survey question groups -> questions (within the current group)
That structure forces users to often navigate using the drop down and back/next buttons when dealing with larger surveys. Having a new menu on the left presenting a structured overview of all question groups with all their questions would help a lot to easily jump from question X to question Y. That new overview should contain icons for:
- Deleting a question/question group
- Directly jumping to the survey question/question group edit mode
- Copying a survey question
- Adding a new question/question group at the appropriate survey section
Steps
- Check how the current Limesurvey survey designer is structured
- Have a look at the different features available on the different levels (survey/question group/question)
- Think which features could additionally be added to the icon list above
- Check the related code for creating a full overview of question groups + questions
- Adjust the admin GUI to embed the additional overview on the left
- Create the code for the new overview and the functions presented by the different icons (most of that code is already there)
- Testing, testing, testing...
Skills
You should be familiar with the "Yii" framework we are using for Limesurvey or at least other PHP frameworks. A good understanding of object-oriented PHP programmierung is required as well. For adjusting the GUI moderate HTML + CSS skills are needed.
Difficulty
Easy
Mentor(s)
Carsten Schmitz
SettingsWidget for core
Use and update (if needed) extension SettingsWidget for core Survey forms.
Some forms to be updated:
- Survey settings
- Personal settings
- Users settings
- Export settings
Skills
PHP, html, js and css
Difficulty
Easy to moderate : some settings can be more diffcult
Link on mantis
Mentor(s)
Expression Manager JavaScript optimization
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.
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.
Skills
Some PHP to update Expression Manager class, deep jQuery/JavaScript knowledge. A jQuery plugin might be a great idea.
Difficulty
Moderate
Mantis
Mentor(s)
Javascript optimisation on question
Due to old system, each input have onchange/onkeyup function. The idea is to remove this inline function and use only javascript existing event.
Skills
Some PHP to update qanda, jquery for new javascript function.
Difficulty
Low, but some test can be hardest.
Mentor(s)
Idea template
Describe the idea here in general terms
Skills
Explain what sort of coding skills would be needed for a student to implement this project
Difficulty
Explain the level of difficulty involved
Mentor(s)
Put your name (and tag) here if you are willing to mentor a student for this idea