[rkward] [Bug 360350] enhanced context menu for objects
https://bugs.kde.org/show_bug.cgi?id=360350 --- Comment #4 from Jan--- (In reply to Thomas Friedrichsmeier from comment #3) Thank you for your reply. I'm delighted about your interest. > I am slightly surprised by your choice of example actions, though: E.g. > dimensions (rows / columns) is already visible from the tool-tip, when > hovering the mouse over an object. You're right. Sometimes "nrow" and "length" return different results so a quick check via context menu would be useful (for me). Same with "names" and "colnames". > Also, the existing "View" action is meant to serve a somewhat similar purpose "View" isn't a good choice for an overview of large objects. Clicking at the tab "print(x)" shows "Fetching information. Please wait." for up to a minute. The command "head" give results much faster. > I am wondering: Would it make more sense to allow (the same / different?) > custom areas in the "View" window, in addition to / instead of your > suggestion? This is another possibility. Sometimes the first tab of the "View" window "summary(x)" also needs some time to be ready (for large objects). So the first tab should have only a limited amount of information. Example: first tab: various ncol: ... nrow: ... length: ... (Please both nrow and length) names: ... colnames: ... (Please both names and colnames) second tab: head(x) third tab: tail(x) (or head(x) and tail(x) combined in one tab) fourth tab: summary(x) fifth tab: print(x) sixth tab: str(x) Regards Jan -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 360350] enhanced context menu for objects
https://bugs.kde.org/show_bug.cgi?id=360350 Thomas Friedrichsmeierchanged: What|Removed |Added CC||thomas.friedrichsmeier@ruhr ||-uni-bochum.de --- Comment #3 from Thomas Friedrichsmeier --- Thanks for your suggestion. Makes sense. I am slightly surprised by your choice of example actions, though: E.g. dimensions (rows / columns) is already visible from the tool-tip, when hovering the mouse over an object. Also, the existing "View" action is meant to serve a somewhat similar purpose (although, admittedly, it has not seen any love in a _long_ time). I am wondering: Would it make more sense to allow (the same / different?) custom areas in the "View" window, in addition to / instead of your suggestion? Brainstorming welcome! Regards Thomas -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 360350] enhanced context menu for objects
https://bugs.kde.org/show_bug.cgi?id=360350 --- Comment #2 from y...@gmx.de --- The entries in the context menu should be configured by the user because the much-needed differ for each one. -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 360350] enhanced context menu for objects
https://bugs.kde.org/show_bug.cgi?id=360350 --- Comment #1 from y...@gmx.de --- Sorry, I pressed accidentally RETURN at the wrong formular element. That submitted the formular without the description. Often I need to look at the first part of a R object. So I type into the console e.g. head(mydataframe). Or I want to know the number of rows and I have to type nrow(mydataframe). My idea/wish is that these commands are available in the context menu of the Workspace browser. Selecting and clicking the command copies the command to the R console and executes it. -- You are receiving this mail because: You are watching all bug changes.