CM configurable Take 2

[Carreau]

Pinging @fperez,
This should fix your issues with markdown cell coloration.

It is a little more complicated than I expected if we want to avoid code duplication in a few places, so I'll work on that.

Change the way configurability works.
Config dict should be passed down to the parent class where it will be
merged with the default value and propagate to this only in the base
class.

This allow to both alter the configuration on a per instance basis, or
globaly by tempering with the class instance.

This also get rid of IPython global in some cases.

Still not perfect but I think this is the limit of my js knowledge, there is a minimal amount of code of 4 line to propagate the configuration :

var options = {foo:bar}; // default options can be class parameter
var overwrite_options ={boo:baz}; // came from args, or not
options = this.mergeopt(CodeCell, options, overwrite options);
IPython.Cell.apply(this,[options]);

I'm just not found of passing [option] instead of just options and the squash the options dict together in a 3 step way...

[minrk]

What is the relationship of this to #2973

[Carreau]

Hum... I'll close #2973, it will become part of this one once done.

#2973 was to close #2972, but there are deeper issues.

[minrk]

Okay, thanks for clarifying.

[Carreau]

No problem, thanks for filling the gap of my (too short) memory.

[ellisonbg]

Should we review and merge this one as is? Do you want to do the CM 3 stuff separately?

[Carreau]

Should we review and merge this one as is? Do you want to do the CM 3 stuff separately?

Haven't had time to look at it in a while. It shoudln't conflict with CM3 though. I'ts just a question of passing config around to be able to overwrite it. So Yes, this and CM3 are different things, I just have the same concern of me not beeing availlable 17-30.

[Carreau]

rebased, cleaned updated.
It shouldn't change the current behavior of the notebook at all.