Programmatically add menu items/ script 'plugins' directory

MUSHclient's existing menus house quite a large array of functionality. But I do thing it would be very convenient if it were possible to programmatically add new items to the menu.

This would allow script authors to create 'plugins'. For example, Magnus recently requested a feature which would allow exporting triggers and aliases to a file. It would not be very difficult to create some script code which would generate such a thing.

All that's missing is a way to add it to the menus. The command would need parameters to indicate what parent item the new item is attached to, and what the 'shortcut key' would be, and what script subroutine would be called.

While we're at it, it would be nice if there was a way to keep script plugins separate from each other, but still available to MUSHclient. What about a Plugins directory, whose contents are executed at MUSHclient startup? Then users would simply need to download a file, drop it in the Plugins Directory, and refresh/restart MUSHclient to benefit from code others create. No more tedious editing of each world's script file.

Additionally, if the script files in the Plugins directory all shared the same scope when executed, they could easily serve as 'include files', defining common code and variables which are used across all your world script files.

Good idea, I have added that as suggestion #437.

I like the idea of plugins, because they allow extensibility over what the original designer might allow for.

Your suggestion is a good working idea of how it could be done.

It could be a problem if some plugins don't work, so we would need a method of reporting errors (eg. plugin 3, 6 and 8 have syntax errors). However that should be achievable.

Extensible menus probably go hand-in-hand with keystroke customisation.

I suppose I should ask, would this apply to MUSHclient as a whole or be specific to particular worlds? What would happen if certain menus only applied to certain worlds?

Would you expect all plugins to be in the same language?

The easiest way I can think of to be completely customisable, but to allow for ease of configuration woud be to have a main Plugins directory under the Mushclient directory, then have PLugins directories under each world.

By doing this, you could just relocate the plugin and make it available across all worlds or confined to a specific one without much of anything in the way of configuration. The user, no matter their experience level, would simply download a script file and drop it where it would do the most good.

In my opinion, all the script files should be executed using the same scope, so they could share each others' subroutines, functions, classes, etc. Even if MUSHclient has to simply load them, concatenate them internally, and then execute the resulting script file.

Ideally, it should support multiple languages (active server pages manages this) because there may be many script authors in many languages. I have no idea of this would be compatible with the above idea of sharing scope (though active server pages does again manage this: Perl and java and vbscripts can make use of each others' subroutines)

Hey, I may not get my whole wish, but if I put all my ideas out front, I'll get more of it than I otherwise would :)