Summary: | Provide "Konsole" outputview with interaction | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | nagytam |
Component: | Output Views | Assignee: | KDevelop Developers <kdevelop-devel> |
Status: | RESOLVED DUPLICATE | ||
Severity: | wishlist | CC: | esigra, jens.dagerbo |
Priority: | NOR | ||
Version: | 4.0.0 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
nagytam
2003-06-30 15:37:19 UTC
WORKAROUND: Project Options | Debugger | Enable separate terminal for app I/O <- ON Anyway, would be nice to do it without a separate terminal... As a bug, this is a dupe of the closed http://bugs.kde.org/show_bug.cgi?id=55717. The question is: should the application view support input? I'm changing this to a wishlist item for now. Or the question is, how useable the application view if a separate terminal I/O is required for an interactive console app??? In current state KDevelop should warn the user that it is for output-only as long as input is not supported... Otherwise the console app is blocked! The debugger option mentioned above only works for debugging. I think that features supported for running and for debugging should not differ at all, though I'm not sure if that's reasonable to try embedding full-blown terminal emulator in the "application" window. As we can now (KDE4) open multiple konsole view's its not unreasonable to allow running/debugging apps just use a konsole as outputview. Of course the debugger would need some extra handling as the terminal interface is different from QProcess for sending/receiving data. closing as duplicate of 146194 as that has a lot more ideas how to interact. *** This bug has been marked as a duplicate of bug 146194 *** |