Two suggestions to improve Cantor's worksheet.

Alexander Rieder alexanderrieder at
Mon Oct 26 10:27:01 UTC 2015

On Sun, Oct 25, 2015 at 9:10 AM, Alexander Semke <Alexander.Semke at> wrote:
> *Adding new expressions:*
> Currently it's impossible to add new expressions between two already existing
> expressions by clicking with the mouse in the area between those two
> expressions. It's not possible to add a new expression at the very top or at
> the very bottom of the worksheet, neither. Mathemica and wxMaxima can do this.
> In Cantor there is only the short-cut "ctrt+return" to add a new item after
> the currently selected one. But this is not flexible enough. It would be great
> to have a "tolerance area" of couple of pixels aroung each item. By hiting
> this are with the mouse a new item should be produced.

I'm not sure what you mean by this. You can already insert new
expressions by using the context menu. (there are items for insert
before this expression and insert after).
Is this not sufficient for your use, or just not intuitive?

> *Highlighting:*
> Sometimes you want to highlight a certain expression by changing its font
> (size and color) or to change the background color. Or you want to add an
> empty line and to change its color to indicate a certain logical separation in
> your calculations. If I see it correctly, Cantor currently lacks any kind of
> formatting like this. Mathematica can do this.

Cantor currently offers the possibility of inserting items with rich
text formatting. We do not offer any formatting
options in the command entries itself, mostly in order to not
interfere with the automatic syntax highlighting there.
Do people really need formatting in the commands/results they produce,
or is it sufficient if they can write annotated text in between
different commands?

> Sidenote: when starting Cantor in the terminal, the terminal is full of debug-
> messages like QRectF(80,156 1x47) QRectF(0,0 677x584). Are they really
> needed/helpful?

yes, we really have accumulated a lot of noise in the debug output. We
should clean that up a bit.

best regards,

> --
> Alexander
> _______________________________________________
> kde-edu mailing list
> kde-edu at

More information about the kde-edu mailing list