[MudWalker] Several suggestions.

[Kevin Reid]

On Oct 16, 2005, at 7:58, Sune Foldager wrote:

> Greetings list.
>
> I just subscribed a few mins ago, because I have some feature 
> suggestions in particular wrt. the scripting system.

Thanks for the feedback. First, a general reminder to all list 
subscribers:

Unfortunately, my interest in working on MudWalker is rather low at the 
moment: it does what I need. If any of you are or know programmers, 
feel free to send patches to add the features you want! I'll gladly add 
them.


> 1. Firstly, the editing window for triggers and aliases is very small. 
> This is probably fine for simple things, but for more advanced 
> scripting, it gets rather annoying to have to scroll all the time. 
> Also, the width is far too small. A bigger window, a pop-up window for 
> editing or even an external editor command could be useful here :-).

Resizing of the settings window is now on the todo list.

> 2. I greatly miss the possibility of "reaching" Lua from the "command 
> line", i.e. from the normal mud input window. It would seem natural to 
> be able to type something like: @@foo = 12   to do the same as that 
> line would do if put in a trigger or alias. In particular, reading out 
> variables is a tedious process now, requirering one to make an alias.

This is on the todo list.

> 3. I would very much like to be able to reach aliases from inside 
> other aliases and triggers. Currently, I can use 'send' to send data 
> to the mud, but it would be nice if there was a way to inject data as 
> if it came through the input window.

I do not plan to add calling aliases; instead there will be a way to 
define Lua functions. For now, you can write these function definitions 
in the login script field, which is "wrong" but should work fine.

> 4. I would like commands to turn settings (aliases, triggers, 
> others..) on and off with commands, and in connection with this have a 
> "short name" assigned to each setting (that the user picks), used to 
> control it. So a command could look like   on("name_of_setting");    
> or similar.

This is on the todo list.

> 5. This is a bit more involved, but I propose a more elaborate 
> structure for settings such as aliases and triggers (this was inspired 
> by zMUD on Windows, although zMUD has many flaws in its implementation 
> IMO):
>
> There should then be a hierachy or "file structure" creatable and 
> maintainable by the user. The user can create 'folders' and 'sub 
> folders', and folders can contain settings such as trigger, aliases, 
> variables and maybe more. In a way acting like objects. Like triggers 
> and alises and other settings, folders can be turned off and on, and 
> this will have the obvious effect on its contents. ...

Interesting. Thanks for the idea. I've been planning to add 
categorization of triggers, but I hadn't thought of disabling them 
through folders.

-- 
Kevin Reid                            <http://homepage.mac.com/kpreid/>