Hi Sean,

It looks like you're doing pretty well, considering the documentation is not yet as detailed as you'd like.

1. Although I can't speak to when the docs will be updated it may also be worth noting that there is another place you can get support - the gitter rooms - which use a chat, rather than forum based format. Lots of friendly, super helpful people on there :)

https://gitter.im/adaptlearning/adapt_framework

2. You can set any property you want on the model using this.model.set("someProperty", "someValue"). This is a Backbone Model feature. I've found the Backbone docs really helpful at times

http://http://backbonejs.org/#Model-set

The reason the property is not in the component defaults is because it wouldn't necessarily be relevant to every component type e.g. textInput. It's set on the matching component so that it can be used to determine the value that .isPartlyCorrect returns. Like I say, you can store any properties you like to help determine isCorrect and isPartlyCorrect. I hope that helps.

3. With regard to your code, I'd remove this.model.set('_isCorrect', true) from your .isCorrect method. You should simply return either true or false and the questionModel will take care of this for you. You also won't need this.model.set('_isAtLeastOneCorrectSelection', true) the second time.

If you are not getting _isCorrect in your setScore function it's because your isCorrect method has returned false. Ollie's right - you'll need to do some debugging here, like logging numberOfCorrectAnswers to the console to see what's going on. You are also using a correctOrder array in there but I can't see where that's defined.

One more thing which might help at this stage while the docs are not yet there, is looking at questionModel.js

https://github.com/adaptlearning/adapt_framework/blob/master/src/core/js/models/questionModel.js

You'll see a number of noop methods e.g. restoreUserAnswers which are designed to be overridden in each component and make fit for your own purpose.

Good luck!

Just about to send and spotted this. Instead of 

$(".sortable-item-inner").each(function(index) {
      if ($.trim($(this).text()) == correctOrder[index]) numCorrect++;
   });

You may need

$(".sortable-item-inner").each(function(index, element) {
      if ($.trim($(element).text()) == correctOrder[index]) numCorrect++;
   });

As "this" refers to the $(".sortable-item-inner") collection rather than the iterated item. Does that work?

Cheers,

Dan

3. A brief example:

QuetionView + ButtonsView work together:
https://github.com/adaptlearning/adapt_framework/blob/master/src/core/js/views/questionView.js#L112-L145

ButtonsView goes through these states to control the flow of questionView:
https://github.com/adaptlearning/adapt_framework/blob/master/src/core/js/enums/buttonStateEnum.js#L4-L10

The state is always at "SUBMIT" on first visit. When the submit button is clicked this function executes:
https://github.com/adaptlearning/adapt_framework/blob/master/src/core/js/views/questionView.js#L155-L211

(You can almost ignore the _runModelCompatibleFunction wrapper, this just says to either run the function from the model if available, or run the function on the view if no model is supplied - legacy style, we're trying to shift to have models for each component).

From the view function onSubmitClicked you should be able to see the order in which the model functions are executed. (Anything not wrapped in _runModelCompatibleFunction is a view only function, such as: showInstructionError, onCannotSubmit, removeInstructionError, showMarking, recordInteraction, showFeedback, onSubmitted).
The order of the model and view function executions when onSubmitClick is executed are:

  model.canSubmit (your code),

view.showInstructionError (core),

  view.onCannotSubmit (your code),

model.updateAttempts (core),

model.setQuestionAsSubmitted (core),

view.removeInstructionError (core),

  model.storeUserAnswer (your code), // specifically for restoring the state

model.markQuestion (core),

  model.isCorrect (your code),

  model.isPartlyCorrect (your code),

  model.setScore (your code),

  view.showMarking (your code),

model.checkQuestionCompletion (core),

  view.recordInteraction (your code), // specifically for scorm cmi.interactions

model.setupFeedback (core),

model.setupCorrectFeedback (core), 

model.setupPartlyCorrectFeedback (core), 

model.setupIncorrectCorrectFeedback (core),

model.updateButtons (code),

view.showFeedback (core),

  view.onSubmitted (your code) // mostly unneeded

Any of these functions can be overwritten on your model or view if you need bespoke behaviour, the ones with (core) next to them have default behaviour, the ones with (your code) need you to write something. There are only 6 functions that are really mandatory (if you exclude onSubmitted, storeUserAnswer and recordInteraction).

The attributes used and changed on the model with the core code include these:
_attemptsLeft,

_isEnabled,

_isSubmitted,

_isCorrect,

_isInteractionComplete,

_buttonState,

_canShowModelAnswer,

feedbackTitle,

feedbackMessage

Any other attributes are not part of this feedback process. They may be used but the core framework (see the inheritance chains of each core type, AdaptView>ComponentView>QuestionView, and AdaptModel>ComponentModel>QuestionModel) or by the component itself.

MCQ is a really good example of a question. 

Sorry that you're frustrated by the lack of docs. We're getting there slowly.

Ollie