DM,
before I put in a git, I thought I'd run this by you. Does it make sense so split out the transfer menu section and make it it's own xfer_sec or something like that? It would make sense sice we now have chat_sec, xtrn_sec, email_sec, and text_sec.
Might be good to do this before people start dipping into their own customizations.
DM,
before I put in a git, I thought I'd run this by you. Does it make sense so split out the transfer menu section and make it it's own xfer_sec or something like that? It would make sense sice we now have chat_sec, xtrn_sec, email_sec, and text_sec.
Might be good to do this before people start dipping into their own customizations.
Different command shells have traditionally very different file transfer sections/menus (from the other command shells), so I don't really see the value in that.
Re: Splitting out transfer from main shell
By: Digital Man to Nelgin on Wed Mar 15 2023 22:06:45
Different command shells have traditionally very different file transfer sections/menus (from the other command shells), so I don't really see the value in that.
It just seems like a logical step. You've got the 5 major functions, email/netmail, file transfers, external programs, text area, and chat.
It just seems cleaner and logical to have a "main" menu and then control everything else from their own .js file. Otherwise, why separate all the other parts out. I think making the transfer section its own sec.js would
It just seems like a logical step. You've got the 5 major functions, email/netmail, file transfers, external programs, text area, and chat.
It just seems cleaner and logical to have a "main" menu and then control everything else from their own .js file.
Sysop: | Coz |
---|---|
Location: | Anoka, MN |
Users: | 2 |
Nodes: | 4 (0 / 4) |
Uptime: | 189:05:57 |
Calls: | 183 |
Files: | 5,413 |
Messages: | 222,737 |