Hi all -
I have been trying to understnad the logic behind why changing menus is so involved, where as there is an actual editor for this provided by Mystic and other BBS software. I can see the power of making menus run off JavaScript, but for those of us who know next to nothing about the language, have low vision and/or prefer the WYSIWYG of a dynamic menu system makes changing your > BBS into something more unique a snap. I've been running Synchronet on my
lab VM and Mystic on my production host. The only reason I went with Mystic is for the menu "overcomplexity".
Did I basically just say "Synchronet is not for me", or is this something that could be incorporated as perhaps a secondary option for menu creation/editing?
I have been trying to understnad the logic behind why changing menus is so involved, where as there is an actual editor for this provided by Mystic and other BBS software. I can see the power of making menus run off JavaScript, but for those of us who know next to nothing about the language, have low vision and/or prefer the WYSIWYG of a dynamic menu system makes changing your BBS into something more unique a snap. I've
Did I basically just say "Synchronet is not for me", or is this something that could be incorporated as perhaps a secondary option for menu creation/editing?
There is a menu editor for Synchronet though - I haven't used it myself, but I think it's supposed to work - Take a look at menuedit.js.
People have created menu editors for Synchronet in the past, including me, and it turns out nobody uses them because they're too limiting. If you look at a modern command shell (e.g. exec/default.js), it's pretty obvious how to change it and there are no limitations on where you can go from there. By contrast, any menu editor will have to have a limited number of actions or verbs and supported syntax.
Re: Synchronet menu system
By: Digital Man to Winzlo on Mon Jul 20 2026 11:24 am
People have created menu editors for Synchronet in the past, including me, and it turns out nobody uses them because they're too limiting. If you look at a modern command shell (e.g. exec/default.js), it's pretty obvious how to change it and there are no limitations on where you can go from there. By contrast, any menu editor will have to have a limited number of actions or verbs and supported syntax.
Totaly agree - canned menus can be nice, but they need to be customizable afterwards to fit the "personality" of the BBS. meunedit.js should put me closer to having a workable replacement menu than if I were to try and alter an existing shell's command handler, screens, etc.
As said, coming from the
world of systems where there is 0 actual development work to set up a menu system, this is a fairly moderate learning curve for something that is critical to the operational flow of tthe BBS.
People have created menu editors for Synchronet in the past, including me, and it turns out nobody uses them because they're too limiting. If you look at a modern command shell (e.g. exec/default.js), it's pretty obvious how to change it and there are no limitations on where you can go from there. By contrast, any menu editor will have to have a limited number of actions or verbs and supported syntax.
| Sysop: | CyberNix |
|---|---|
| Location: | London, UK |
| Users: | 23 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 191:11:54 |
| Calls: | 920 |
| Files: | 5,854 |
| D/L today: |
38 files (9,919K bytes) |
| Messages: | 861,000 |