View Model Code to Models - Create standard models

[oliverfoster]

We should create a series of core component models for standard model behaviour.

• This will reduce the footprint for bug fixing
• Facilitate reuse
• Standardise common behaviour

[oliverfoster]

we need a core model for each items, mcq and slider

the mcq one is done, but it still lives in the mcq

[oliverfoster]

graphic, text, blank and media still need doing.

[moloko]

graphic, text, blank and media still need doing.

what do you envisage going into the models for those?

[oliverfoster]

Nothing, just the bog standard model. They just need to conform to the model / view separation standard. I'd like to kill off "view only" components.

[moloko]

Oh right, I see - something a bit like this?

return Adapt.register('blank', {
        model: ComponentModel.extend({}), // Need to create a new class in the inheritance chain so that it can be extended per component type if necessary later
        view: BlankView
});

[oliverfoster]

Exactly. Then we can drop all that compatibility rubbish from QuestionView (not that it's needed for the presentation components, it will just feel a lot cleaner).

[moloko]

Excellent. Would you be happy to keep the view code in adapt-contrib-blank.js - or would you want it moved to a separate .js file?

[oliverfoster]

It's fine in the main file I think. I'd prefer a separate file as an example for everyone to follow but it's really only a stylistic wish. (I updated your code example btw ^ just so that you notice)

[moloko]

OK all done