Thinking about new theme for mobile only

Plus d'informations
il y a 7 mois 6 jours #184020 par holch

Take my word for it, I will never force you to use this template... ;-)


Probably not you personally, but the survey developers that use your template to develop their surveys. ;-)

I'm not a LimeSurvey GmbH member. I answer at the LimeSurvey forum in my spare time. No support via private message.
Some helpful links: Manual (EN) | Question Types | Workarounds

Connexion ou Créer un compte pour participer à la conversation.

Plus d'informations
il y a 7 mois 1 jour #184137 par tammo
Here is a quick sketch about what we are thinking of for single choice (all answers in one block) or multiple choice (all answers separate).

Feel free to comment, but no death threats please.




Tammo ter Hark at Tools for Research
Proud developers of the TFR Responsive Limesurvey theme
toolsforresearch.com/limesurvey-responsive-template
Pièces jointes :

Connexion ou Créer un compte pour participer à la conversation.

Plus d'informations
il y a 7 mois 23 heures #184144 par DenisChenu
Personnaly , i‘m more to move out all question from core to be in external modules, activated or not and loaded or not (or downloaded or not).

Then you can have a complete LimeSurvey with only some simple question, but if yu need more : you download it at «Question type store system»

Assistance on LimeSurvey forum and LimeSurvey core development are on my free time.
I'm not a LimeSurvey GmbH member, professional service on demand , plugin development .
An error happen ? Before make a new topic : remind the Debug mode .

Connexion ou Créer un compte pour participer à la conversation.

Plus d'informations
il y a 7 mois 16 heures #184147 par tammo
I am not sure about the words "external modules", but I do see a good business case for "profiles" that can be defined at some level (user? theme?) where question types can be switched on and off.

And yes, let all question types be separate modules, that can be extended by other modules.


Tammo ter Hark at Tools for Research
Proud developers of the TFR Responsive Limesurvey theme
toolsforresearch.com/limesurvey-responsive-template

Connexion ou Créer un compte pour participer à la conversation.

Plus d'informations
il y a 7 mois 15 heures #184148 par DenisChenu

tammo écrit: I am not sure about the words "external modules", …

Nopt sure for myself of the exact way to do :)
But a directory inside LimeSurey where we can found manual.limesurvey.org/Question_object_types

In my opinion : this Question object must have
1. Extend another Question object allowed
2. Completly new Question object
3. Column type+number must be part of the question object (then when someone found times, we don't need all Array different questions workaround and plugin)
Etc …

See

A question type manager, like plugin manager, where it's possible to install, deactivate and manager which questions are available on the system

on wiki for base system.

Assistance on LimeSurvey forum and LimeSurvey core development are on my free time.
I'm not a LimeSurvey GmbH member, professional service on demand , plugin development .
An error happen ? Before make a new topic : remind the Debug mode .

Connexion ou Créer un compte pour participer à la conversation.

Plus d'informations
il y a 7 mois 9 heures - il y a 7 mois 9 heures #184166 par holch
I think the modular approach proposed is a good idea.

But my fear with this, as with the plugins as well, is that suddenly vital elements of Limesurvey suddenly won't work for a couple of months, when a new version comes out, etc.

So I think the question type modules should come with the core and should be tested before stable release. My fear is, that suddenly we will have a pure barebone system after each new release and I guess this will lead to even less bug testing by users than today, because the platform might not be "usable" for them until a certain time after, when all the modules are up to date.

On the other hand the modular approach, would give us the chance to finally implement many "question types" that currently can only be done via work arounds (nothing against work arounds, but in my opinion they should be kept at a minimum and only for special occasions) as a "real" question type. With the risk that they might not be always up to date, but this can also happen with the work arounds.

I'm not a LimeSurvey GmbH member. I answer at the LimeSurvey forum in my spare time. No support via private message.
Some helpful links: Manual (EN) | Question Types | Workarounds
Dernière édition: il y a 7 mois 9 heures par holch.

Connexion ou Créer un compte pour participer à la conversation.

Plus d'informations
il y a 7 mois 8 heures #184167 par tammo
I fully agree that all questions that are in LS as it is now, are core modules.

After this, succesful additional modules could be taken up into the core set, but this will mean that the original developer of the custom modules looses "ownership" and the new core module will have to fit in the work flow of the core developers. Wouldn't it?

The same happended to various custom modules of Drupal, that now make part of the core package.

Tammo

Tammo


Tammo ter Hark at Tools for Research
Proud developers of the TFR Responsive Limesurvey theme
toolsforresearch.com/limesurvey-responsive-template

Connexion ou Créer un compte pour participer à la conversation.

Plus d'informations
il y a 7 mois 6 heures - il y a 7 mois 6 heures #184170 par DenisChenu
My exact position about this is
1. LimeSurvey default come with all current question in «question object» and «attributes plugin» (except, maybe some specific part (5 point emoji, timer script (because this one broke a lot and must be improved) etc … Hude text since it's exactly long text with different default attribute).
2. LimeSurvey light can be ditributed alone
3. LimeSurvey «another light»

:)

I already create plugins for core, this plugins still active since creation (remind all exports are plugin currently).

the original developer of the custom modules looses "ownership" and the new core module will have to fit in the work flow of the core developers.

It's FLOSS, original author still their, but other dev can upgragde/improve.

Assistance on LimeSurvey forum and LimeSurvey core development are on my free time.
I'm not a LimeSurvey GmbH member, professional service on demand , plugin development .
An error happen ? Before make a new topic : remind the Debug mode .
Dernière édition: il y a 7 mois 6 heures par DenisChenu.

Connexion ou Créer un compte pour participer à la conversation.

Plus d'informations
il y a 7 mois 6 heures #184174 par holch

I already create plugins for core, this plugins still active since creation (remind all exports are plugin currently).


Yeah, but you are one of the good ones... ;-)

I'm not a LimeSurvey GmbH member. I answer at the LimeSurvey forum in my spare time. No support via private message.
Some helpful links: Manual (EN) | Question Types | Workarounds

Connexion ou Créer un compte pour participer à la conversation.

Plus d'informations
il y a 7 mois 6 heures #184175 par DenisChenu

holch écrit: Yeah, but you are one of the good ones... ;-)

What i mean : it's already the case for some «core» plugins : AuthDB it's the principal example …
But exportR or AuthLDAP too for example.

Assistance on LimeSurvey forum and LimeSurvey core development are on my free time.
I'm not a LimeSurvey GmbH member, professional service on demand , plugin development .
An error happen ? Before make a new topic : remind the Debug mode .

Connexion ou Créer un compte pour participer à la conversation.

Commencez dès maintenant !

Créez simplement un compte et commencez à utiliser LimeSurvey dès aujourd'hui.

Inscrivez-vous maintenant

Inscrivez-vous à notre Newsletter!