| Summary: | rcmdr through rkward | ||
|---|---|---|---|
| Product: | [Applications] rkward | Reporter: | RKWard Team <rkward-devel> |
| Component: | general | Assignee: | RKWard Team <rkward-devel> |
| Status: | REPORTED --- | ||
| Severity: | wishlist | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | All | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
RKWard Team
2009-07-13 23:19:32 UTC
I'll provide a short initial feedback: \- In the long run, all Rcmdr functionality should be reimplemented in RKWard. \- In the short term, a solution along your lines sounds like a good idea. However, I am not currently sure, whether and how this could be done. I will need to investigate this, but some other issues are higher up in priority ATM. This is not quite what you're asking for, but may be of interest: In RKWard 0.5.1, you can now \(again, after a long time\) invoke the Rcmdr interface from within RKWard in the usual way \(by typing "library\(Rcmdr\)" in the console\). Most features work as expected, this way. |