[limesurvey-developers] ls 2.05 to 2.06 to 3.00

[Denis Chenu]

Hi,

Actually we have 3 LimeSurvey version for devloppment.
- 2.05 : stable version, fixing bug only
- 2.06 alpha2 version : can put new feature, fix bug, new plugin event,
rework core code
- 3.00 develop version : reworking all code, and some great new feature,
in Sammousa github only.

Sam can not do 3.00 alone. I think it's hard for us to work on the 2
(2.06 and 3.00) directly, because a lot of thing change. But we need to
work on 2.06 (maybe call it 2.1 version ...) and we have some "dev
feature" to do , that can be done in 2.06 (2.1) , maybe some can be done
and can be directely inckuded in 3.00.

Let speak from some point

* HTML admin part : using layout, and new admin menu widget :
o 2.06 : see
https://manual.limesurvey.org/Project_ideas_for_GSoC_2015#Make_use_of_the_SettingsWidget_for_core_functions
. I think doing it for 2.06 help us to move to 3.00 : rigth ? or
not ?
o 2.06
https://manual.limesurvey.org/Project_ideas_for_GSoC_2015#Replace_current_CKEditor_usage_with_TinyMCE
: same think
o https://manual.limesurvey.org/Project_ideas_for_GSoC_2015#Remove_jQuery_UI_and_replace_it_with_Bootstrap.2C_harmonize_GUI_of_different_admin_screens
Moving to layout step by step (using same layout than "plugin")
starting by "User management" for example. Can be started in
2.06 (2.1) rigth ?
* Expression Manager : see develop here :
https://github.com/SamMousa/LimeSurvey/commits/develop/application/helpers/expressions/em_manager_helper.php
and some GSOC 2015 project :
o how move some part to 2.06/2.1 to be more simple to move to 3.0
new system after ? Is it possible ?
o Did move "public function
_CreateSubQLevelRelevanceAndValidationEqns" to differenet
function (call a function for each question attribute ? exemple
: if (isset($qattr['commented_checkbox']) &&
trim($qattr['commented_checkbox']) != '') : move to own Class ?
Hard to start but i think can really help.
o Removing inline javascript (or really use Yii regsiterScript ..)
https://manual.limesurvey.org/Project_ideas_for_GSoC_2015#Expression_Manager_JavaScript_optimizations
: think it can help too
o $_SESSION :
https://github.com/SamMousa/LimeSurvey/commit/9dbf6b6ccdb40f31fa9f22c35e5ba41a3169c0e7#diff-c60bef10a130572a2bf26fd0a9db519bR615
and https://bugs.limesurvey.org/view.php?id=9522 (same idea ...)
o function _UpdateValuesInDatabase : move to Yii updateAll ...
(really think it can be done in 2.06).
* TWIG for template : i really don't look at this part for develop ls3
version, then don't know actually
* Surely other ...

I just want to have 3.0 at a time, but make evolution of LS core before
3 comes to public.

Denis

[Sam Mousa]

As far as I know, 2.06 has been feature locked for a while now; and it only
needs some bug fixes before it can be released.

I am strongly opposed to adding new features to 2.06.
If anyone wants to aid in development, we can use help in bugfixes in 2.06
or (bug)fixes / feature implementation in LS3. Note that LS3 is currently
not in a state where adding new features will be easy; however there is a
lot of skeleton code that needs to be fleshed out (
http://www.thefreedictionary.com/fleshed+out).

Post by Denis Chenu
Hi,
Actually we have 3 LimeSurvey version for devloppment.
- 2.05 : stable version, fixing bug only
- 2.06 alpha2 version : can put new feature, fix bug, new plugin event,
rework core code
- 3.00 develop version : reworking all code, and some great new feature,
in Sammousa github only.
Sam can not do 3.00 alone. I think it's hard for us to work on the 2
(2.06 and 3.00) directly, because a lot of thing change. But we need to
work on 2.06 (maybe call it 2.1 version ...) and we have some "dev
feature" to do , that can be done in 2.06 (2.1) , maybe some can be done
and can be directely inckuded in 3.00.
Let speak from some point
o 2.06 : see
https://manual.limesurvey.org/Project_ideas_for_GSoC_2015#Make_use_of_the_SettingsWidget_for_core_functions
. I think doing it for 2.06 help us to move to 3.00 : rigth ? or
not ?
o 2.06
https://manual.limesurvey.org/Project_ideas_for_GSoC_2015#Replace_current_CKEditor_usage_with_TinyMCE
: same think
o
https://manual.limesurvey.org/Project_ideas_for_GSoC_2015#Remove_jQuery_UI_and_replace_it_with_Bootstrap.2C_harmonize_GUI_of_different_admin_screens
Moving to layout step by step (using same layout than "plugin")
starting by "User management" for example. Can be started in
2.06 (2.1) rigth ?
https://github.com/SamMousa/LimeSurvey/commits/develop/application/helpers/expressions/em_manager_helper.php
o how move some part to 2.06/2.1 to be more simple to move to 3.0
new system after ? Is it possible ?
o Did move "public function
_CreateSubQLevelRelevanceAndValidationEqns" to differenet
function (call a function for each question attribute ? exemple
: if (isset($qattr['commented_checkbox']) &&
trim($qattr['commented_checkbox']) != '') : move to own Class ?
Hard to start but i think can really help.
o Removing inline javascript (or really use Yii regsiterScript ..)
https://manual.limesurvey.org/Project_ideas_for_GSoC_2015#Expression_Manager_JavaScript_optimizations
: think it can help too
https://github.com/SamMousa/LimeSurvey/commit/9dbf6b6ccdb40f31fa9f22c35e5ba41a3169c0e7#diff-c60bef10a130572a2bf26fd0a9db519bR615
and https://bugs.limesurvey.org/view.php?id=9522 (same idea ...)
o function _UpdateValuesInDatabase : move to Yii updateAll ...
(really think it can be done in 2.06).
* TWIG for template : i really don't look at this part for develop ls3
version, then don't know actually
* Surely other ...
I just want to have 3.0 at a time, but make evolution of LS core before
3 comes to public.
Denis
------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live
exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
limesurvey-developers mailing list
https://lists.sourceforge.net/lists/listinfo/limesurvey-developers

[Denis Chenu]

Hi,

A example,
Did this :
https://github.com/LimeSurvey/LimeSurvey/commit/fda369ebaa63de221585db75e211bb8982a89715#diff-47997bba4383b1b4959a1dc61b9fe73aR8
help us for ls3.
Doing same for
https://github.com/LimeSurvey/LimeSurvey/blob/2.06/application/views/admin/user/personalsettings.php
help us for ls3 ?
Adding a datetime settings to widget help us or not, an real HTML widget
(with EM replacement and upload) etc .

I really think we can not develop LimeSurvey with old development
method, and we need to adapat.
We don't have time or money for some "waterfall model" etc. ... We need
to adapt more Agile development method.

Actually start working on ls3 seems very difficult without looking at
all update made, and understand why you made it, and your final objective.
I already done 2 fork of LimeSurvey with specific event, but this event
need to be reworked. I can do more and more fork, but time consumed to
work on fork are time not consumed to work on LS core.
Before 1.92, doing fork is the only way to have some functionnality, i
think 2.05, 2.06 ... remove this. But not really ...

Denis

Post by Sam Mousa
As far as I know, 2.06 has been feature locked for a while now; and it
only needs some bug fixes before it can be released.
I am strongly opposed to adding new features to 2.06.
If anyone wants to aid in development, we can use help in bugfixes in
2.06 or (bug)fixes / feature implementation in LS3. Note that LS3 is
currently not in a state where adding new features will be easy;
however there is a lot of skeleton code that needs to be fleshed out
(http://www.thefreedictionary.com/fleshed+out).

[Denis Chenu]

Hi,

After a look at 2.06 and 3.00 code, i think :
- I search to fix 2.06 broking beta version bug quicky, then assign it
to me.
- Don't put any new feature/system/improvment to 2.06
- Go to fix and improve 3.00 when 2.06 is out.

Denis