I am officially requesting that time-of-release the MacNewbPack includes documentation for the utilities it ships with, including a .txt or .html with links to the development site of these projects. I've just spent about an hour trying to find the documentation for Dwarf Family. Do you have any idea how many hits "Dwarf+Family+utility" gets on a website called Dwarf Fortress? Fer'serious!
Edit: About half the utilities are already shipping with readme.txts and .pdfs, so I guess what I'm asking for is a duplicate copy be set up in a Help folder, and that links to the project documentation be added for the missing ones. At which point, you may as well add in a button on the Utilities tab for that folder.
Obviously adding or creating README files is the responsibility of the utility developer, or falls to the pack maintainer.
Adding a button to each item on the utilities list, to open an autodetected README file with the default app for that file type, would help expose documentation to users. I've been planning to implement this eventually, but a user request means this deserves a spot on the issue tracker.
[Issue created by PeridexisErrant: 2015-12-26]
[Last updated on bitbucket: 2016-03-14]
[Comment created by Pidgeot: 2016-03-14]
Removing milestone: 0.11 (automated comment)
[Comment created by Pidgeot: 2016-03-14]
Add button to open readme for utilities (fixes #104)
Rename open_folder to open_file; use os.startfile to open things on Windows
→ <>
[Comment created by PeridexisErrant: 2016-01-19]
That implementation sounds good to me. I have a strong preference for local documentation, but it's not relevant now (and someone could have eg README.sh which opens online docs in a browser).
I don't think anyone is really delighted by the utilities list, so whatever works is fine.
[Comment created by Pidgeot: 2016-01-18]
Proposed implementation:
The first case-insensitive match for "README*" or "READ ME" in the utility folder will be used for auto-detecting a readme file.
When #103 is implemented, utility manifests should be able to override with a "readme" field specifying the path to open. This could potentially also be a URL if the documentation isn't included locally.
I'm not yet sure how we're going to actually put the controls to let the user launch them. Ideally, I'd like a right-click menu, but that's not really going to work in the current UI, so maybe we'll just add a "Open README" button to the window and have it launch the readme for all selected utilities...
http://www.bay12forums.com/smf/index.php?topic=128960.msg6691469#msg6691469
Obviously adding or creating README files is the responsibility of the utility developer, or falls to the pack maintainer.
Adding a button to each item on the utilities list, to open an autodetected README file with the default app for that file type, would help expose documentation to users. I've been planning to implement this eventually, but a user request means this deserves a spot on the issue tracker.
[Issue created by PeridexisErrant: 2015-12-26] [Last updated on bitbucket: 2016-03-14]
[Comment created by Pidgeot: 2016-03-14] Removing milestone: 0.11 (automated comment)
[Comment created by Pidgeot: 2016-03-14] Add button to open readme for utilities (fixes #104) Rename open_folder to open_file; use os.startfile to open things on Windows
→ <>
[Comment created by PeridexisErrant: 2016-01-19] That implementation sounds good to me. I have a strong preference for local documentation, but it's not relevant now (and someone could have eg
README.shwhich opens online docs in a browser).I don't think anyone is really delighted by the utilities list, so whatever works is fine.
[Comment created by Pidgeot: 2016-01-18] Proposed implementation:
The first case-insensitive match for "README*" or "READ ME" in the utility folder will be used for auto-detecting a readme file. When #103 is implemented, utility manifests should be able to override with a "readme" field specifying the path to open. This could potentially also be a URL if the documentation isn't included locally.
I'm not yet sure how we're going to actually put the controls to let the user launch them. Ideally, I'd like a right-click menu, but that's not really going to work in the current UI, so maybe we'll just add a "Open README" button to the window and have it launch the readme for all selected utilities...