Question attributes redesign: Difference between revisions
From LimeSurvey Manual
DenisChenu (talk | contribs) |
|||
| Line 32: | Line 32: | ||
[[User:Olle|Olle]] ([[User talk:Olle|talk]]) 17:14, 3 February 2020 (CET) | [[User:Olle|Olle]] ([[User talk:Olle|talk]]) 17:14, 3 February 2020 (CET) | ||
Question attributes '''redesign''' : redesign is redesing. | |||
If you talk of re design : must be a real redesign . I move my previous comment to Notes :) in next edition | |||
[[User:DenisChenu|DenisChenu]] ([[User talk:DenisChenu|talk]]) 17:19, 3 February 2020 (CET) | |||
== Notes == | == Notes == | ||
TODO | TODO | ||
Revision as of 18:19, 3 February 2020
Question attribute code saw a rise in complexity between LS3 and LS4. This page will take a step back and analyze if it can be simplified.
Domain diagram
Class diagram
TODO
Database design
TODO.
Will not change.
Scenarios
All use-cases go here.
- Question class is clearly a Theme related attribute. Not linked to specific question
- Can we remove timer attribute from core please ! https://manual.limesurvey.org/Question_type_-_Short_free_text#Timer : remind : Not only for on,e question, didn't update any HTML/CSS part (only js)
- All expression part (min value , max number) are done in LimeExpressionManager : totally unrelated to QuestoinTheme
---
I was thinking basically all use-cases can be summarized to:
- Import question attribute from XML/question theme
- Save question attribute value
- Load question attributes for question type/question id
Olle (talk) 17:14, 3 February 2020 (CET)
Question attributes redesign : redesign is redesing.
If you talk of re design : must be a real redesign . I move my previous comment to Notes :) in next edition
DenisChenu (talk) 17:19, 3 February 2020 (CET)
Notes
TODO