CocoMUD Planio: Issueshttps://cocomud.plan.io/https://cocomud.plan.io/favicon.ico2022-04-23T09:59:44ZCocoMUD Planio
Planio CocoMUD client - Feature #163 (Open): Create a system of categories for aliases/macros/triggershttps://cocomud.plan.io/issues/1632022-04-23T09:59:44ZVincent Le Goff
<p>Some of the configuration would be specific to a category, or a set of categories. These aliases, macros and triggers will only be active if the current category is active. This way, one could have a different set of aliases, macros and triggers in different playing situation (while fighting, while exploring, and so on).</p> CocoMUD client - Feature #162 (Open): Allow to have disabled aliases/macros/triggershttps://cocomud.plan.io/issues/1622022-04-23T09:55:49ZVincent Le Goff
<p>When CocoMUD connects to a world, the world configuration is loaded. The aliases, macros and triggers are added. All of them are active.</p>
<p>It would be useful to disable some of them, at least in Python, to make sure they're not used but still saved. This will come to be extremely handy when the system of categories is adopted.</p> CocoMUD client - Bug #160 (Open): Error on importing worldshttps://cocomud.plan.io/issues/1602020-11-06T12:33:55ZVincent Le Goff
<p>When importing worlds from a file (and probably from online too), after having selected the archive file, an error occurs:</p>
<pre>
Traceback (most recent call last):
File "C:\Users\vince\src\cocomud\src\ui\window.py", line 360, in OnImportOndisk
infos = World.get_infos(options)
File "C:\Users\vince\src\cocomud\src\world.py", line 347, in get_infos
config = ConfigObj(StringIO(configuration), encoding="utf-8")
TypeError: initial_value must be str or None, not bytes
</pre> CocoMUD client - Bug #155 (Open): Path evaluation in #play function fails if file is on different...https://cocomud.plan.io/issues/1552019-12-04T18:05:56ZVincent Le Goff
<p>The culprit is this line:</p>
<pre>
return os.path.relpath(filename, location)
</pre>
<p>If <code>filename</code> is on a device (say E:) and <code>location</code> is on a different one (say C:), then a <code>ValueError</code> exception is raised. Instead, encapsulate this call and go back to the absolute path if the relative path can't be found.</p> CocoMUD client - Bug #148 (Open): The audio library doesn't shift audio controllershttps://cocomud.plan.io/issues/1482018-12-23T09:36:28ZVincent Le Goff
<p>The audio system works great (and I was even told the sounds were better in this version). However, when we force the system to change the current audio device (if we plug in an external headphone by USB, for instance), the <code>audiolib</code> will keep playing on the main audio device, now muted. Check if there's a better way to find the default device and keep playing through it.</p> CocoMUD client - Feature #143 (Open): Translate CocoMUD in Spanishhttps://cocomud.plan.io/issues/1432018-12-06T09:07:15ZVincent Le Goff
<p>There was a great job done in CocoMUD's code to port the translation to Spanish. There remains a couple of entries that are still in English, due to the fact that no Spanish project existed on CocoMUD. This is now fixed, so I suggest a task with no time constraint.</p>
<p>We now have a Spanish project in CocoMUD, <a class="project" href="https://cocomud.plan.io/projects/es">es</a> . For the CocoMUD's projects, the English version is on the <a class="project" href="https://cocomud.plan.io/projects/cocomud-client">CocoMUD client</a> (the main project), sub-projects are for other languages (like <a class="project" href="https://cocomud.plan.io/projects/fr">fr</a>). It is not possible to alter the language of a project on Redmine while maintaining the language of separate projects, although users can select a default language to see Redmine in a more friendly way. With a full Spanish project, there are two things that could be done:</p>
<ol>
<li>Update the few entries that remain in English, in the <code>translations/es</code> catalog. See for instance "translations/es/ui/dialog/bug.yml" where the message and URL could be updated (for the URL you will need to specify the project ID of <a class="project" href="https://cocomud.plan.io/projects/es">es</a> , you might try various numbers and see if the project is selected when you open the URL).</li>
<li>The next task is more complicated: the wiki pages on <a class="project" href="https://cocomud.plan.io/projects/es">es</a> should be translated as well. Now, that's a lot of work, and I advise you to not do it at all, working extensively on translation isn't the most fun and the documentation isn't that light. The <a class="wiki-page" href="https://cocomud.plan.io/projects/es/wiki/Builds">Builds</a> page in particular is extremely long as it lists all builds of CocoMUD and new features. You do not need to translate it, we could leave the previous versions in English and only add Spanish for the new releases. To be discussed.</li>
</ol> CocoMUD client - Feature #137 (In Progress): additional map-creatorhttps://cocomud.plan.io/issues/1372018-10-10T05:37:41ZMoritz Wolfart
<p>This is only a little idea for an addon.<br />In many muds you can get in trouble by wildernes or very big maps.<br />The maps in muds are mostly based on asccii and reading them or interpretating them can be very tricky.<br />So, maybe some kind of map-recorder could be very very helpful.<br />For example you start the maprecorder and the programm start to recognice by collecting every place you visited by coordinates. You start at x0y0 and every room you travel after that x0y0 will be recorded in some kind of map-log you can access later or even use for a speedwalk.</p>
<p>Hope you understood my sometimes weird explanations.</p> CocoMUD client - Feature #115 (Open): General configuration (macros, aliases, triggers)https://cocomud.plan.io/issues/1152017-10-28T17:37:04ZMoritz Wolfart
<p>Some configuration is just repeated in all games. Some common aliases, macros, triggers and even channels. The idea would to be define "general-level" configuration. An easy solution is to create a <code>settings/config.set</code> file, as Moritz suggested, with the general configuration. The feature is almost supported as is, but some modifications to the user interface are needed:</p>
<ul>
<li>For aliases, channels, macros and triggers, an additional list should be added to change its scope. General, world, or category. Although category-level configuration may not be available, it's good to think about this feature already.</li>
<li>Remember than changing the scope will mean changing the file in which these are saved, and perhaps the order.</li>
<li>World configuration has precedence over general configuration. One should be able to define a macro that overrides the general macro, for instance.</li>
<li>Remember to keep channels stored in worlds, to avoid conflict. It might be a good idea to separate them on the client itself.</li>
</ul> CocoMUD client - Feature #113 (Open): Joypad for macroshttps://cocomud.plan.io/issues/1132017-10-25T07:12:38ZMoritz Wolfart
<p>Hey hey!<br />I realy would love the feature to use a joypad for macros.<br />Is this possible?</p> CocoMUD client - Feature #104 (Open): Have an auto-building strategy set for Linuxhttps://cocomud.plan.io/issues/1042017-08-01T08:43:27ZVincent Le Goff
<p>The updater currently supports only Windows. However, adding a Linux support shouldn't be too complicated. It would require building each version, just like under Windows, but it might provide the same level of accessibility. Furthermore, allowing CocoMUD to update on Linux shouldn't be a complicated task.</p> CocoMUD client - Feature #102 (Open): Offer console-like alternatives to configure and manipulate...https://cocomud.plan.io/issues/1022017-08-01T08:36:20ZVincent Le Goff
<p>Although wxPython is the most accessible window toolkit under Windows, its accessibility on other platforms, particularly Linux with Orca, tends to be a bit limited. Lists, in particular, do not render well, and manipulation through the arrow keys doesn't select anything, which generates errors.</p>
<p>Re-coding CocoMUD in GTK+, the accessible alternative on Linux, would be a major hardship, considering both versions would have to be maintained for accessibility. However, it turned out that the AccessPanel was completely accessible in Linux, particularly in the "screen reader support" mode. Therefore, a good compromise would be to allow users to access these areas secured by lists and other inaccessible elements through a console-like approach, with commands that should be quite close to MUD commands with a specific syntax. In fact, CocoMUD's sharp engine could easily be tied to such an interface.</p>
<p>The suggestion for a better accessibility goes as follow:</p>
<ul>
<li>If under Linux, open CocoMUD in its AccessPanel, with no current world selected, instead of opening the connection window.</li>
<li>The user would have to enter the <code>#connect</code> command, with either a world's name (if configured) or a full configuration instruction (host name, port, protocol).</li>
<li>Most settings will need to be changed to allow editing from this interface. Something like <code>#setting lang it</code>.</li>
</ul> CocoMUD client - Feature #101 (Open): Offer CocoMUD's accessibility on Linuxhttps://cocomud.plan.io/issues/1012017-08-01T08:27:30ZVincent Le Goff
<p>For the time being, CocoMUD has been successfully built on Windows, but not on other platforms. Most Python resources that are used are multi-platform libraries. However, respecting accessibility on another platform will prove much more difficult. This issue encompasses both aspects.</p> CocoMUD client - Feature #10 (Open): Support the NVDA screen readerhttps://cocomud.plan.io/issues/102016-09-19T22:06:31ZVincent Le Goff
<p><a class="project" href="https://cocomud.plan.io/projects/cocomud-client">CocoMUD client</a> has to work with the <a href="www.nvaccess.org/">NonVisual Desktop Access</a> screen reader, including its different navigation modes.</p> CocoMUD client - Feature #9 (Open): An easy yet powerful setting system for customizationhttps://cocomud.plan.io/issues/92016-09-18T21:53:00ZVincent Le Goff
<p>CocoMUD is intended for every user, with or without programming skills. The client should be easy to set up and allow to achieve already powerful task while only using the interface and a simple scripting system. For those willing to go beyond, however, CocoMUD will also provide an interface for developers who would be able to produce more complex scripts.</p>
<p>The setting model can be represented in three different layers:</p>
<ul>
<li>The upper layer contains every modification that could be done through the interface. These modifications should be simple, but allow interesting extensions nevertheless. Macros, aliases, triggers and more could be configured in the interface. More complex scripting could be achieved as well, but the aim is to allow every user with a setting they could modify without having to create and manage scripts.</li>
<li>The next layer contains a light-syntax scripting language that is used to perform more complex actions very easily. The syntax <code>#macro F1 north</code>, for instance, might associate the F1 shortcut with the <strong>north</strong> command. A list of possible actions will be presented with the users and clearly documented (if possible, in different languages).</li>
<li>The third layers contains bare scripting in Python language, that will allow features that are not supported through the basic scripting provided at the upper layer. Once more, clear documentation will be provided to users willing to extend their setting through Python code.</li>
</ul> CocoMUD client - Feature #6 (Open): An accessibility-oriented Graphical User Interfacehttps://cocomud.plan.io/issues/62016-09-18T21:38:26ZVincent Le Goff
<p>While a nice-looking interface is important, the major focus of this interface should be on accessibility. Accessing the history through diverse methods, depending on the screen reader being used, easily accessing the command prompt and command history, configuring the entire application, all are important facets of CocoMUD.</p>