![]() Option 2: use the editor but render a tree per complex object in a custom editor widget ![]() ![]() Note: editor could be enhanced to render custom images, but customly rendered output which the user can interact with is tricky. Pro: find, selection, word wrap, performanceĬon: have to simulate the tree by using editor decorations / indentation, not enough flexibility (for possibly future requests of rendering custom things in the debug console). #26641 Option 1: use the editor and simulate the tree using editor decorations The tree also allows us to lazily fetch the children of each element and is virtualised. The benefit of using the tree is that we can easily render complex elements - the ones that have children. This has worked well thus far but has certain limitations. Currently we use the tree to represent all elements in the debug console. ![]() This item is intended as a discussion for the future of the debug console. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |