- Updated ChangeLog

- Added original design decisions to README
This commit is contained in:
Paul Beckingham 2008-05-13 00:08:04 -04:00
parent b63cf606f0
commit 53747cc984
2 changed files with 147 additions and 13 deletions

120
ChangeLog
View file

@ -1,23 +1,117 @@
1.0.0 - First official release ()
- Bug: assertion fails for task info n, where n is out of range
- Bug: assertion fails on mobile for t v
0.10.0 - Productization ()
~ Documentation complete
~ Test suite
~ All known bugs fixed
------reality-----------------------------------
0.9.6
0.9.5
4/25/2007 Incorporated Grid code.
4/23/2008 Set up this ChangeLog file.
5/12/2008
+ Replaced Table storage with Grid.
5/10/2008
+ Added Grid.cpp to configure.ac
+ Added Makefile to src/.gitignore
+ Makefile should not be part of the repository.
+ Added Grid.cpp
+ Added Grid::Cell::operator==
4/27/2008
+ ChangeLog file begun.
+ Bumped version to 0.9.5 for next release.
0.9.4
4/26/2008
+ Integrated new Grid object into build - not yet integrated into Table.
4/19/2008
+ More .gitignore tweaks.
+ Added .gitignore
+ Added more missing files.
+ Added all source code.
+ Generic OSS files added.
+ Initial commit.
0.9.3
4/6/2008
---------8<----------- Suspicious content
0.9.2
4/3/2008 Configure now detects ncurses, flock.
4/3/2008
0.9.1
4/1/2008 First autoconf version released.
Bug: due dates not checked for correctness
Bug: attributes without values stored instead of removed
4/1/2008
0.9.0
---------8<-----------
3/23/2008
+ flat source directory
+ autoconf complete
+ "task next"
+ "task stats"
+ "task export"
+ Rule₋based colorization
4/19/2008 Created new repository at github.com. Lost history because І
cannot figure out how to manipulate git into exporting changes for
a subset.
0.8.16
3/13/208
0.8.14
2/20/2008
0.8.13
2/2/2008
0.8.1
1/28/2008
0.8.0 - Polish (1/25/2008)
+ Code cleanup, reorganization
+ "task overdue"
+ Add "age" column to list and long
+ Use 'conf' for build, version tracking
+ Add "/from/to/" description editing
0.7.0 - Multi-user, File handling, atomicity (1/8/2008)
+ Clean, publishable API reimplementation
+ File locking
+ retain deleted tasks
+ "task info ID" report showing all metadata
0.6.0 - Reports (12/27/2006)
+ "task history"
+ "task summary"
+ "task calendar"
+ due: support
+ Table sorting
0.5.0 - Multi-user support (12/10/2006)
+ Command logging
+ "task usage" report
0.4.0 - Destructive / modification commands (12/3/2006)
+ "task delete" complete
+ "task id ..." complete
+ "task list ..." synonym for "task find ..."
0.3.0 - Work in progress support (12/3/2006)
+ "task start" complete
+ "task done" complete
+ completed.data support
0.2.0 - Neutral commands (12/2/2006)
+ "task find" complete
+ "task projects" complete
+ "task tags" complete
0.1.0 - Constructive commands (12/1/2006)
+ "task add" complete
+ completed.data support
+ ~/.taskrc support
0.0.1 - Basic infrastructure (11/29/2006)
+ Command line parsing
+ API layer
+ Usage

40
README
View file

@ -5,3 +5,43 @@ Based on ideas in todo.sh
Movie at www.b.n/task.mov
Feedback, suggestions to task@beckingham.net
Task - a GTD utility featuring:
- Robust C++ implementation
- Tags
- Colorful, tabular output
- Reports
- Low-level API
- Auto-completion on all commands, options
- Multi-user file locking
- Clean architecture allowing quick addition of new features
- UUID for all tasks
Task is an implementation of GTD ideas, similar to todo.sh, but without many of
the limitations in todo.sh, namely:
- Bugs are not being fixed
- No response or web update from ________ on code submission
- todo.py is the todo.sh replacement, but requires a python installation - a
significant barrier to many users, and is currently merely a
reimplementation of todo.sh
- project.sh is the natural progression for todo.sh, but is intended to be a
project management solution, but is so far todo.sh with a "done" and
"overview" command
- There is no output formatting
- There is no way to enumerate projects, categories
- There is no file locking for multi-user access
- With no API, a graphical front end must reimplement the primitives
With a robust infrastructure in place for parsing commands, file I/O and
structured output, the development threshold for adding new features is kept
low.
It is intended that features, mainly in the form of reports will be added
frequently, with best practices and useful reports evolving.
Task is scope-limited to GTD functionality only.