This is a reponse to the problem of having really long lines in
Markdown cells, which makes the content difficult to read. Users
want wide code cells, so we don't want to narrow everything. The
solution here is to give a prompt area to the heading/md cells
to narrow their content area slightly. The only problem is that
this makes it more difficult to distinguish between output
and md content that follows that output. The solve this, we are
adding a narrow line between output and following md.
Don't check for wx in the test suite.
An interaction between wx and threads was blocking certain Unix signals,
causing an unrelated test to fail for me.
We were only checking for wx to exclude the inputhookwx module from the
test run. It contains no tests anyway, so we may as well just exclude it
in all cases.
An interaction between wx and threads was blocking certain Unix signals,
causing an unrelated test to fail for me.
We were only checking for wx to exclude the inputhookwx module from the
test run. It contains no tests anyway, so we may as well just exclude it
in all cases.
Spring Cleaning, and Load speedup
0) prompt '*' strore fix + tab remove tooltip
tab was not cancelling tooltip bringing to cases where you could have
tooltip andcompleter open.
Do not store '*' when serializing cells.
get rid of most slowdown at notebook loading.
1) Do not setOption('mode',new_mode) on CM if new and old mode are the
same. It triggert a lot of calculation of bounding box in the
end.
2) Do not select cell when loading the notebook it triggers
a lot of CM even that check visible things and so on and so
forth. So add a option to add_cell_at_index not to select it
3) jQuery $.attr has some magics, but has a slight overhead on
real native ELEM.setAttribute DOM method. Seem slight improvement
when loads of PNGs on one page
1) Do not setOption('mode',new_mode) on CM if new and old mode are the
same. It triggert **a lot** of calculation of bounding box in the
end.
2) Do **not** select cell when loading the notebook it triggers
**a lot** of CM even that check visible things and so on and so
forth. So add a option to add_cell_at_index not to select it
3) jQuery $.attr has some magics, but has a slight overhead on
real native ELEM.setAttribute DOM method. Seem slight improvement
when loads of PNGs on one page
Configuration docs refresh
- Moved the technical details of the config system into the development directory.
- Added a new 'intro' document describing how to use the config system, without the technical info.
- Autogenerate lists of config options for the main components (this doesn't yet include the parallel machinery).
- Condense and tidy up other config docs, removing outdated information.
Daemon StreamCapturer
The StreamCapturer should die if the main thread crashes. On Shiningpanda, a failure in another nose plugin has been causing the tests to hang, because the main thread exits, but the StreamCapturer thread is still alive.
Under normal conditions, the thread will still be shut down cleanly - it will only die a messy death if the main thread does.