Hey Marcel,

There are no stupid questions :) I'll give an honest try to answer your questions :)

1. Their type is actually same, the difference lies in the type of view their policy provide. For text type, the answer field represents a textarea, for which one can even set settings like the no. of rows and columns, whereas for string type the answer field is input type.

2. The matrix question type has model answers (labels) defined for both the rows and cols, but for choice_matrix type, model answer has just the col headers stored, the row headers are the description of the child question.

3. I'm unsure how question types have been implemented before, yet to go through it, but these types just fill in for them, as the mappings have also been listed in the previous mail. We believe, integration would be just a matter of replacing calls to the new built DBSE. Though some things need to be decided yet.

Regards
Pooja

On Mon, Jul 11, 2011 at 2:34 AM, Marcel Minke (Limesurvey) <marcel.minke@limesurvey.org> wrote:
Hi Pooja,

thanks for all your great work. Some - maybe stupid - questions:

1. What's the difference between string and text question type?

2. What's the difference between choice_matrix and matrix question type?

3. When you are done, will the Limesurvey survey engine use these new features for saving answer data? How do you plan the integration to be done? Won't there be a lot of code that has to be rewritten for saving and returning data?

Best regards,
Marcel

Am 10.07.2011 19:46, schrieb pooja narula:
Hey All,

Work Status:
This week following question types have been implemented (a week before the timeline :)) :
dbse_string_question_type
dbse_text_question_type
dbse_checkbox_question_type
dbse_choice_question_type
dbse_choice_matrix_question_type
dbse_matrix_question_type
with it's mappings to the front-end question types as given here: http://docs.limesurvey.org/Database+Storage+Engine+Project+M1+Database+Design#Question_Type_mappings With this the implementation phase is complete, now just integration and testing phase remaining.

Meeting Conclusions:
Decided to do testing before integration. Getting the know-how of the testing framework of CI: SimpleTester and get started with testing the full DBSE. Also, to work out on the integration details (when and where to start).

Any comments/suggestions are welcomed. The project action plan can be found here http://docs.limesurvey.org/Rebuild+the+database+frontend+using+CodeIgniter

Regards
Pooja
------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________ limesurvey-developers mailing list limesurvey-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/limesurvey-developers

------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
limesurvey-developers mailing list
limesurvey-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/limesurvey-developers