Your LimeSurvey version: 3.x
==================
Is it possible by plugin to implement a custom question type or expanding a rendering (question theme?) for an existing question type?
I'd like to create a "push button" question, saving an integer.
The question should save as answer how many times you clicked its button.
The button actually, it's a link, with bootstrap button's class.

I'm digging into it, by reading documentation.

Maybe I can implement a beforeQuestionRender event who is going to render the question type numeric, if some conditions are supported. For example if I have a string inside the question text.. <!-- #MYPLUGINNAME -->

Or maybe I can install a Question theme, during plugin activation ... But in this case I should write SQL queries to get things done . But this part is undocumented, and differs from 5.x and 3.x

With plugin :

1. You can add question advanced settings
2. You can update answers
3. You can add JS

A lot of sample : gitlab.com/SondagesPro/QuestionSettingsType

You need (in init)

Thanks for your reply! I managed to add a switch option to numeric question. Something as "MyPluginBtn" true-false flag.
Now I can't realize how to substitute numeric input widget with a push button thing. The idea is to have an hidden field pretending to be the numeric and the button doing the numeric increment by jquery.
I bet I should hook to beforeQuestionRender hook and filtering two parameters, the numeric field type "N" having MyPluginBtn attribute = 1 
 

I wrote this as filter for the event. But where's stored question output?

Maybe inside the event? $this->getEvent()->get('question') ?

Did you look at www.limesurvey.org/manual/BeforeQuestionRender ?
text : the question text
answers : the complete HTML answers part

And don't use $this->getEvent() , because event can update during your plugin.
$renderEvennt = $this->getEvent();
$renderEvennt->get('qid')
…

Oh thanks, I forgot about reading event's wiki page
I've read all others events pages

Thank you as usual! So you mean I should "snapshot" the event attribute inside a scoped variable as soon the event gets fired.
I need some refactorings

tassoman wrote:

Thank you as usual! So you mean I should "snapshot" the event attribute inside a scoped variable as soon the event gets fired.

 

Not necessary, but it's better.
If (for example) you save a model : $this->getEvent is afterSave event. If you create a twig : it's another event.

And maybe : if you call a function without event today, maybe there are a new event in some month …
And remind other plugin can create (then update) event too …

Now : i always put my needed event in a var. Because i have the issue … and don't understand what happen after some hours (says ?) of research …