文件列表:

bismut_screenshot.png (137656, 2023-01-10)
site/ (0, 2023-01-10)
site/.prototypes/ (0, 2023-01-10)
site/.prototypes/action.erl (348, 2023-01-10)
site/.prototypes/element.erl (392, 2023-01-10)
site/.prototypes/page.erl (603, 2023-01-10)
site/ebin/ (0, 2023-01-10)
site/ebin/.empty (0, 2023-01-10)
site/ebin/diary.beam (15892, 2023-01-10)
site/ebin/index.beam (22548, 2023-01-10)
site/ebin/ling.beam (8164, 2023-01-10)
site/ebin/login.beam (18128, 2023-01-10)
site/ebin/mobile.beam (16616, 2023-01-10)
site/ebin/nitrogen.app (358, 2023-01-10)
site/ebin/nitrogen_app.beam (1076, 2023-01-10)
site/ebin/nitrogen_cowboy.beam (15536, 2023-01-10)
site/ebin/nitrogen_sup.beam (3804, 2023-01-10)
site/ebin/people.beam (22388, 2023-01-10)
site/ebin/salode.beam (3960, 2023-01-10)
site/ebin/settings.beam (32052, 2023-01-10)
site/ebin/tasks.beam (36108, 2023-01-10)
site/ebin/utils.beam (3464, 2023-01-10)
site/include/ (0, 2023-01-10)
site/include/records.hrl (0, 2023-01-10)
site/src/ (0, 2023-01-10)
site/src/actions/ (0, 2023-01-10)
site/src/actions/.ignore (0, 2023-01-10)
site/src/elements/ (0, 2023-01-10)
site/src/elements/.ignore (0, 2023-01-10)
site/src/index.erl (8025, 2023-01-10)
site/src/ling.erl (6664, 2023-01-10)
site/src/login.erl (3588, 2023-01-10)
site/src/nitrogen.app.src (188, 2023-01-10)
site/src/nitrogen_app.erl (334, 2023-01-10)
site/src/nitrogen_cowboy.erl (1247, 2023-01-10)
site/src/nitrogen_sup.erl (3214, 2023-01-10)
site/src/salode.erl (2315, 2023-01-10)
site/src/settings.erl (16987, 2023-01-10)
site/src/stat_utils.erl (1444, 2023-01-10)
... ...

Bismut ====== This is a hierarchical colored work tracker. Like a traditional bug/task tracker but with multicolored hierarchical items so your whole project looks a bit like a bismuth crystal, and you can see its status immediately just by looking at the tasks at hand.  *By David Abercrombie, [CC BY-SA 2.0](https://creativecommons.org/licenses/by-sa/2.0), via Wikimedia Commons* If you get the concept but want to suggest a feature or a bug fix, contact me at: akalenuk@gmail.ua. An example ---------- I'm currently writing a book called [Geometry for Programmers](https://www.manning.com/books/geometry-for-programmers). Tons of work, hundreds of tasks and bugs. However, even now, when the book is almost finished, my project board looks quite readable. In fact, this is the whole board:  Most of the chapters are finished so they are green and folded. There are multiple tasks in them but since neither of them bother me at the moment, they are hidden inside the folded large tasks. But one chapter remains unfolded, and one section in it too, since it contains an issue that needs my attention. As it turns out, while I was writing the book, the scientific community decided not to use [Lenna](https://en.wikipedia.org/wiki/Lenna) as a testing image anymore. I was not aware of that so I used Lenna in my book to demonstrate smooth image scaling and now I have to redo all the figures involved. In a normal bug tracker, this would have been a bug. In Bismut, bugs are not segregated from tasks. If you have something and you want something else, whatever you call it, a "bug" or a "user story", it needs work. So every bug-like task has a current or "before" state, and a desired or "after" state. The task for the work you want is then written with an arrow: Lenna as a test image → a picture of a cat as a test image This task is red since it is a blocker, I have to get it done before I can move to anything else. As soon as the problem is solved, and I get my picture of a cat instead of Lenna, I'll rerun the scripts that showcase the interpolation and generate the interpolation examples. I did that before with Lenna, so the generation task per se is green. However since a new issue occurred since then, and the task needs more work now, I added a new sub-task and painted only one new task yellow. The task doesn't need by immediate attention since I can't proceed with it before the blocker anyway. With hierarchical items, I don't have to repaint the whole tree, I just keep it open and paint the branches that need attention on the exact level they do. The white items at the bottom are the ones I haven't got to yet. Since they don't have a state "before" they all start with an arrow. They are not yet folded they just don't have a lot of items in them yet. I don't have to plan in detail before I start working. As soon as new issues occur, I'll simply add them as subtasks. Of course, this tool only fits a particular style of project management. But it serves me well, and I'm not pushing it on anyone else. How to run ---------- The source code is licensed under Apache 2.0. TL&DR: you do whatever you want, I don't take any responsibility. This is a Nitrogen site. To run your own instance, download Nitrogen, put the sources into the site/ folder, and run the Nitrogen node by running bin/nitrogen console The site will appear at http://127.0.0.1:8000 Disclaimer ---------- This is a prototype, a proof of concept. It uses the file system as a key/value storage and even keeps passwords there unhashed and unsalted. If you want to use it for anything other than toying with, at the very minimum, you have to patch these things up first.

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：