View Issue Details
Category | |||||
---|---|---|---|---|---|
SSPBT:本体(SSP) | |||||
Severity | feature | Reproducibility | N/A | ||
Status | closed | ||||
Fixed in Version | 2.5 (リリース) | ||||
Summary | 0000451: New development panel: request sending panel and the sakura script to open it | ||||
Description | This is what I found when I was thinking about tama's collaboration with ssp Consider a ghost shiori being loaded and run by ssp but debugged in tama: obviously it would be silly (and everything would get messy) if tama loaded another instance of shiori, but I want all the functionality of tama to still be available in this case The unloading/reloading of shiori can be done by sending a sakura script, so the problem is just the request sending panel I've thought about allowing other programs to send request execution requests to ssp via some sort of specification, but that's neither nice nor secure, so I think the safest thing to do is for ssp to also implement such an underlying debug panel and provide a sakura script to open it Considering that this feature is largely unused, I'm in no rush to implement it at all, enjoy your time � | ||||
Tags | No tags attached. | ||||
Attach Tags | |||||
Date Modified | Username | Field | Change |
---|---|---|---|
2022-03-04 18:56 | guest | New Issue | |
2022-03-04 18:56 | guest | Tag Attached: new specification | |
2022-03-06 20:13 | ponapalt | Assigned To | => ponapalt |
2022-03-06 20:13 | ponapalt | Status | new => assigned |
2022-03-06 20:14 | ponapalt | Status | assigned => confirmed |
2022-03-06 20:14 | ponapalt | Fixed in Version | => 2.5 (リリース) |
2022-03-06 20:14 | ponapalt | Note Added: 0001155 | |
2022-03-06 21:01 | ponapalt | Status | confirmed => closed |
2022-03-06 21:01 | ponapalt | Resolution | open => fixed |
2022-03-06 21:01 | ponapalt | Note Added: 0001159 | |
2023-02-02 04:44 | guest | Tag Detached: new specification |