Manual talk:Technical Manual

From Mudlet
Revision as of 19:15, 7 October 2014 by Vadi (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Suggestion for topic "Multi Session Gaming"

I did not find it intuitive that clicking "Connect" and then selecting another profile would start a new connection in a tab, leaving my already connected MUD session active in another tab. This is also related to the MultiView button, which does not react how you would expect - i.e. The button is always active (non-grey) while connected to a single MUD, but clicking the button does nothing (until you start at least one more session). There are currently no help topics associated with MultiView, tabbed sessions, etc. that I could find.

I did not want to edit the help wiki without some guidance from others on the procedure, I have not participated in a wiki previously.

This topic may be more appropriate in Manual:Introduction, or split between both with varying degrees of detail. --Kd8cgo 02:14, 5 November 2012 (EST)

Hi - Did you mean that you want to adjust the Mudlet Manual, or adjust how Mudlet works about this? --Vadi 03:44, 5 November 2012 (EST)
I don't think the way it works is -bad- or needs changed, but adding some description to the manual so that a newbie like me can :: make sense of it without much guesswork. (multi session tabs, MultiView). :) --kd8cgo 11:35, 5 November 2012 (EST)
Ah. I think it would go well into the technical manual then, expand on the info in there. --Vadi 14:29, 5 November 2012 (EST)
Added short info to chapter "Multi Session Gaming". Feel free to expand more. :) --Kebap 09:03, 7 October 2014 (EDT)


Remove Lua API from Manual?

As it stands, the chapter "Lua API" takes 2/3 of the place of the manual. Even more in the content overview. The overview is so long, it may be discouraging people to look at other chapters. The style of writing is very different between most of the manual (casual, explaining, combining style) and the API info (to the point, structured info, for each command separately). Why not just put a short few sentences to describe the API, then only link to the details page for interested users. --Kebap 08:58, 7 October 2014 (EDT)

Is this an actual problem observed in the wild? Because a lot of guesses can be made using logical reasoning but without any proof... --Vadi 15:15, 7 October 2014 (EDT)