Hang on, does this mean anyone who wants to run from git will need extra
set up steps? I agree about separating external dependencies, but it's a
useful feature that people can very easily test development versions.

Does this handle version dependencies? Will it install exactly the right version of codemirror for the currently-checked-out git tree? Can I update the codemirror installation if I check out a different version?

Hang on, does this mean anyone who wants to run from git will need extra
set up steps? I agree about separating external dependencies, but it's a
useful feature that people can very easily test development versions.

No, this is just a test to see how things are going with CM3. Of course we will keep dev usable as-is.
Probably with a build step that bundle the right files in the right place.

Does this handle version dependencies? Will it install exactly the right version of codemirror for the currently-checked out git tree? Can I update the codemirror installation if I check out a different version?

Yes, bower does deal with dependencies, right now it target "latest" but one can say in the right file to target a particular range of version number or even a specific sha.

Right now this is mostly to see how easily we can use a "stock" version of codemirror that does not have extra patches, and test bower.

I would say that you can checkout any version of CM3 as long as it is under /component/codemirror directory it should work, so you can also use submodules or stuff like that.

Python mode for codemirror is now configurable, we can use the singleOperator config option to match ? instead of maintaining a patched version.

We could also maybe probably config for % and %% magics.

This is a great start.

• You have another PR that moves the ipython CM css theme (Move CM IPython theme out of codemirror folder #2942). Should that one be closed?
• At the dev meeting, we talked about having our bower components at the top level of static, so it would be static/codemirror, etc. This will mean adding a .browerrc file one level up that sets the directory option to static.
• Code mirror doesn't use proper git tags that bower can recognize, so it will be difficult for us to depend on a particular version of codemirror. We need to think about how we want to handle this.
• Obviously, we do want to ship a stable CM in static/codemirror.
• I am about to start the "great JavaScript code reorganization" so we need to finish this PR up soon.
• Can you update your list of things that need to get done for this to be finished? (matching ?)

You have another PR that moves the ipython CM css theme (#2942). Should that one be closed?

I would prefere #2942 to be merged,
this one is mainly an experiment to test the transition (not too hard)

Code mirror doesn't use proper git tags that bower can recognize

Doesn't bower understand commit hash ?

There are some bugs in our version of CM that I think CM 3 might fix. I would like to move to CM 3, but maybe this is not the PR for that? Should we close this? Originally, you said that #2942 should be merged instead? What do you think? I would love to get our CM stuff cleaned up as it is blocking some other work.

There are some bugs in our version of CM that I think CM 3 might fix. I would like to move to CM 3, but maybe this is not the PR for that?

Need to be rebased cleaned up and tested. Their are probably bugs in usage.
Question is, if we do it this week, I won't be there to fix things the 2 weeks after.

Should we close this?

I'll rebase soon.

Originally, you said that #2942 should be merged instead?
Merged before. it was to ease this one.

I would love to get our CM stuff cleaned up as it is blocking some other work.
Should I commit all CM fils or leave it as a component ?
In a component folder or elsewhere ?

I rebase and updated a little.

Could someone install codemirror through bower, it is not going through the F-@$%&-G proxy anymore, so I had to test by git cloning manually.

Then, could the same person issue a PR agains my branch and/or open a new one ?

Also this need to commit files in the component directory (once codemirror installed), wherease not all of files in component directory are required (bootstrap...). So this will conflict with one of min's recent PR.

One of the things that we could do is .gitignore specific subpath of components.

@williamstein mentioned to me that CM3 has some performance issues with resizing many instances that CM2 (possibly) didn't have. Maybe it would be good to test a page with many CM3 instances with content, and resize the page (i.e., resize the instances). I haven't done the test myself, but it would be good to check.

I was using cm 3.1 on OS X...
On Apr 9, 2013 8:59 AM, "Jason Grout" [email protected] wrote:

@williamstein https://github.com/williamstein mentioned to me that CM3
has some performance issues with resizing many instances that CM2 didn't
have. Maybe it would be good to test a page with many CM3 instances with
content, and resize the page (i.e., resize the instances). I haven't done
the test myself, but it would be good to check.

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/2944#issuecomment-16121921
.

And chrome.
On Apr 9, 2013 9:23 AM, [email protected] wrote:

I was using cm 3.1 on
On Apr 9, 2013 8:59 AM, "Jason Grout" [email protected] wrote:

@williamstein https://github.com/williamstein mentioned to me that CM3
has some performance issues with resizing many instances that CM2 didn't
have. Maybe it would be good to test a page with many CM3 instances with
content, and resize the page (i.e., resize the instances). I haven't done
the test myself, but it would be good to check.

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/2944#issuecomment-16121921
.

Closing, this PR has been replaced by #3232