https://bugs.kde.org/show_bug.cgi?id=409137
--- Comment #5 from avlas <jsar...@gmail.com> --- (In reply to Nikita Sirgienko from comment #3) > (In reply to avlas from comment #2) > > (In reply to Nikita Sirgienko from comment #1) > > Would you consider adding this functionality to the backend languages for > > which this computation seems rather simple? Thinking about > > R/Octave/Scilab/Julia/Python, maybe others. > > I am thinking about it, and I'll see what i can do For those backends for which this may be possible, do you think it would be better/easier to show three columns (Name, Size and Values)? [Now that I think about it, should we add Type as well?] Ideally the columns for Size and Values (and Type if considered) could be enabled optionally. I would very much like to have sizes (and maybe types) at sight to better understand the data and code in mutual context, to ease debugging, etc. I don't feel that (an incomplet) list of values are that important, at least for my workflow. Also, having a bunch of Values is a bit distracting, for instance column arrays hide a lot of other variables in the workspace. [Side note: this behavior (how values are displayed) could also be changed. An example of this could be how latest stable versions of Octave display values in the workspace, and perhaps cantor could consider adding a specific variable display panel similar to Octave's variable editor (although this would be a more sophisticated/complicated add)] -- You are receiving this mail because: You are watching all bug changes.
