Dimitar (Mitko) Asenov
Dimitar (Mitko) Asenov
Not much else to add
Currently, all children of an item are always rendered and they are visible in their entirety. In some cases (e.g. the output console in `ConsoleOverlay`) we need a way to...
There should be a generic mechanism that allows plug-ins to register custom callbacks to the handlers of particular object types, without having to reimplement the handler. An ad hoc solution...
This is an interesting construct from a visualization perspective. It is also used in many projects, including jEdit, which we want to experiment with.
The different elements in `DynamicGridFormElement` are all rendered on the same background and without any separators. We could make the elements more distinguishable by some combination of: - including separator...
When using `auto` either `->` or `.` should be used in subsequent code visualizations based on what the `auto` types evaluates to. After `this` either `->` or `.` should be...
See the attached whiteboard photo for some details on the issue + pointers to a solution. 
When growing a child object positioned using `GridLayouter`, the grid will be enlarged with every edit, which causes all other items in the grid to be potentially updated and redrawn....
At the moment, when an expression is edited, its nodes are recreated after every parse. In most cases the new expressions is only minimally different than the old one, and...
At the moment, each command that is added to the undo stack, stands on its own, even if it can be easily merged with the previous one (e.g. typing each...