TODO - add comment for doing without transformers
This commit is contained in:
parent
17dbe4babc
commit
09936ba108
5
TODO.org
5
TODO.org
|
@ -197,12 +197,13 @@
|
|||
1. Some feature definitions already exist in features/, write step definitions for them.
|
||||
5. [ ] Remove duplication - the three =chronometrist-*-history-populate= functions seem to have a common pattern of iterating over each hash value (a list of plists) in =chronometrist-events=, and over each element of that list.
|
||||
6. [ ] Remove duplication - extracting user key-values from a plist seems to be a common operation.
|
||||
7. [ ] Extensions - redesign =chronometrist= such that it does not need to check for the availability of extensions (such as =chronometrist-goals=)
|
||||
7. [ ] Extensions - redesign =chronometrist= such that it does not need to check for the availability of extensions (such as =chronometrist-goal=)
|
||||
* Could make two "transformer lists" - =chronometrist-list-format-transformers= and =chronometrist-entry-transformers=.
|
||||
|
||||
The former would be called before =tabulated-list-format= is set. The latter would be called by =chronometrist-entries=, with each individual entry as an argument.
|
||||
|
||||
=chronometrist-goals= will simply added a function to each of those.
|
||||
=chronometrist-goal= will simply added a function to each of those.
|
||||
* Actually, are transformers really necessary? It could be done with a function inserted by =chronometrist-goal= into =chronometrist-mode-hook=. The function itself would become a little more complex, but it would remove the two transformer lists + the =call-transformers= dependency from the code. =chronometrist-mode-hook= is required either way, to set up =chronometrist-goal=.
|
||||
8. [ ] Ugly code - =chronometrist-print-non-tabular=; =insert-text-button= can be replaced with =make-text-button=
|
||||
|
||||
** Documentation [0%]
|
||||
|
|
Reference in New Issue