-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Help system polish and trimming #13
Comments
The first pass of this should probably be done by @saraht45, with an emphasis of writing a doc in the master SkotOS-Docs explaining how instances of SkotOS should do this (for instance, all the tips are in Woe, and can leverage acmds for auto-typing commands into Orchil), and then the specifics for vRWOT edited by @wip-abramson. |
SkotOS:HelpNodes:* Remove Keep Keep and update for vRWOT Add help nodes for |
TextIF:Init needs to be rewritten for vRWOT |
SkotOS:Tip can be removed SkotOS:Tips:Intro Remove Keep Keep but update for vRWOT Add |
Would removing SkotOS:Tip turn off the tips on login? |
No, it appears the login tip calls upon SkotOS:Tips:Intro, which is the same database the @tip command uses. |
The help system, especially the tips system and initial online help, should be overridden by RWOT and replaced with something limited and appropriate. It should mention only verbs that RWOT actually supports well.
Where possible, other sources of online help should be updated (e.g. the tools popup hardcodes all kinds of outdated and weird help text.) But the priority should be on anything visible to end-users, with a secondary focus on anything visible to world-builders.
A lot of this is done in XML files (including the +tool popup, I think,) so I should see what parts can be repaired in the Tree of WOE. Those parts can potentially be handed off to Sarah, Will, etc.
Help appears to be in a lot of files under SkotOS:HelpNodes, which are WOE-editable.
Tips are in SkotOS:Tips:Intro, which is WOE-editable. There's a second list in SkotOS:Tip that I think is unused.
The text was updated successfully, but these errors were encountered: