| Summary: | JJ: code scratchpad command line test | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | jesse <sub448> |
| Component: | Language Support: CPP (old) | Assignee: | Amish Naidu <amhndu> |
| Status: | RESOLVED FIXED | ||
| Severity: | wishlist | CC: | akshay_ratan, amhndu, darvark, ganger695988290, shubham.chaudhary |
| Priority: | NOR | Keywords: | junior-jobs |
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Unspecified | ||
| Latest Commit: | https://commits.kde.org/kdevelop/37f68b8d4299a3a9a3ba7a6b1d7d102a9ccea5e1 | Version Fixed/Implemented In: | |
| Sentry Crash Report: | |||
|
Description
jesse
2008-11-29 00:02:10 UTC
This would be easy to implement as a plugin. If someone is interested, contact us. Is this bug still not solved ? There's no such plugin yet. Feel free to provide a patch! :) Is there anyone work for the plugin? If not , I want to have a try. Huang, just go ahead. You can ask for help in #kdevelop on Freenode. Post your patches to reviewboard, if any. See http://techbase.kde.org/Development/Review_Board HI, Does someone finished this plugin, or it's still open taks. No activity on that one, feel free to work on it. Again, you're welcome in #kdevelop. Personally, I'd love to have such a scratchpad. Current development progress with full kdevplatform source is available on https://github.com/darvark/scratchpad HI, Ok, lets assume that I have working plugin. Does after successful compilation, should I remove created files? Or leave them in case when someone want's to run it? And one more thing, I would be very thankful if someone could check it. Sometimes I have problems that after I use plugin, kdevelop process didn't end. There's some progress here: https://phabricator.kde.org/D16484 Git commit 37f68b8d4299a3a9a3ba7a6b1d7d102a9ccea5e1 by Amish Naidu. Committed on 11/12/2018 at 15:05. Pushed by anaidu into branch 'master'. Add scratchpad plugin Summary: Adds a scratchpad plugin, which allows you to keep "scratches" of code/text to experiment or quickly run something without the need for a project. The plugin adds a new tool-view, which will maintain a list of your scratches as well as allowing you to compile and run them. The scratches live in the directory `scratches` in the data directory and are regular documents so we get all the editing convenience of code-completion and diagnostics. Commands used to run them are saved per-scratches and new scratches use the last used command for that file type/suffix. Test Plan: Add the tool-view on the left tool bar and try creating and using the scratches. Currently no automated tests. Reviewers: #kdevelop, kfunk Reviewed By: #kdevelop, kfunk Subscribers: aaronpuchert, kfunk, gregormi, brauch, kdevelop-devel Tags: #kdevelop Differential Revision: https://phabricator.kde.org/D16484 M +1 -0 plugins/CMakeLists.txt A +25 -0 plugins/scratchpad/CMakeLists.txt A +38 -0 plugins/scratchpad/emptymessagelistview.h [License: GPL (v2+)] A +261 -0 plugins/scratchpad/scratchpad.cpp [License: GPL (v2+)] A +71 -0 plugins/scratchpad/scratchpad.h [License: GPL (v2+)] A +12 -0 plugins/scratchpad/scratchpad.json A +102 -0 plugins/scratchpad/scratchpadjob.cpp [License: GPL (v2+)] A +56 -0 plugins/scratchpad/scratchpadjob.h [License: GPL (v2+)] A +225 -0 plugins/scratchpad/scratchpadview.cpp [License: GPL (v2+)] A +62 -0 plugins/scratchpad/scratchpadview.h [License: GPL (v2+)] A +54 -0 plugins/scratchpad/scratchpadview.ui https://commits.kde.org/kdevelop/37f68b8d4299a3a9a3ba7a6b1d7d102a9ccea5e1 |