Request:
I would like to request an enhancement to SyncTERM to support an integrated QWK offline mail workflow, allowing the user to stay inside SyncTERM for the full download/read-reply/upload process.
Current workflow:
1) Log onto a BBS with SyncTERM
2) Download a .QWK packet - Log off the BBS
3) Open a third-party offline mail reader
4) Read messages and reply, creating a .REP packet
5) Log back onto the BBS with SyncTERM
6) Upload the .REP packet
Desired workflow:
1) Log onto a BBS with SyncTERM
2) Download a .QWK packet - Log off the BBS
3) From within SyncTERM, launch a local offline reader/editor (Slyedit or FSeditor?) *
4) Read messages and reply, creating a .REP packet
5) Reconnect to the BBS with SyncTERM
6) Upload the .REP packet
Why this could be useful:
This would remove the current third-party middle step and keep the user from constantly going back and forth between applications. It would also preserve the same classic BBS look and feel in an 80x25 ANSI environment, making the whole QWK workflow feel more integrated and natural inside SyncTERM.
That said, a possible path forward may be JSDoor? My very limited understanding is that JSDoor provides a Synchronet JavaScript runtime that does not require a live Synchronet BBS session, which could make it a possible bridge for running JS-based tools locally from within SyncTERM.
I understand this is not a trivial request, especially for editors written against Synchronet-specific JS objects. Still, even partial support could be useful. And allow endusers to stay in one app and preserve the ANSI 80x25 look and feel of Syncterm and Syncronets full screen editors.
Anonymous