syc-task 0.0.7 → 0.1.15
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- data/README.rdoc +159 -15
- data/bin/console_timer +75 -0
- data/bin/syctask +246 -68
- data/lib/syctask.rb +4 -1
- data/lib/syctask/environment.rb +427 -2
- data/lib/syctask/schedule.rb +84 -21
- data/lib/syctask/settings.rb +43 -0
- data/lib/syctask/statistics.rb +196 -0
- data/lib/syctask/task.rb +58 -2
- data/lib/syctask/task_planner.rb +94 -13
- data/lib/syctask/task_scheduler.rb +5 -1
- data/lib/syctask/task_service.rb +55 -15
- data/lib/syctask/task_tracker.rb +27 -17
- data/lib/syctask/times.rb +29 -0
- data/lib/syctask/version.rb +1 -1
- data/lib/syctime/time_util.rb +46 -7
- data/lib/sycutil/console_timer.rb +75 -0
- metadata +215 -136
metadata
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: syc-task
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.
|
|
4
|
+
version: 0.1.15
|
|
5
5
|
prerelease:
|
|
6
6
|
platform: ruby
|
|
7
7
|
authors:
|
|
@@ -9,7 +9,7 @@ authors:
|
|
|
9
9
|
autorequire:
|
|
10
10
|
bindir: bin
|
|
11
11
|
cert_chain: []
|
|
12
|
-
date: 2013-
|
|
12
|
+
date: 2013-04-26 00:00:00.000000000 Z
|
|
13
13
|
dependencies:
|
|
14
14
|
- !ruby/object:Gem::Dependency
|
|
15
15
|
name: rake
|
|
@@ -98,147 +98,222 @@ description: ! "= Simple task organizer\nsyctask can be used to create, plan, pr
|
|
|
98
98
|
you want to accomplish today. If you are not sure in which sequence to conduct the
|
|
99
99
|
task you can prioritize them with a pair wise comparisson. You can time tasks with
|
|
100
100
|
start and stop and you can finally extract tasks from a minutes of meetings file.
|
|
101
|
-
The schedule task will print a graphical timeline of the working day assigning
|
|
102
|
-
planned tasks to the timeline. Busy times are marked red. Meetings are listed
|
|
103
|
-
associated tasks that are assigned to the meetings
|
|
104
|
-
|
|
105
|
-
|
|
106
|
-
\"
|
|
107
|
-
\
|
|
108
|
-
|
|
109
|
-
task
|
|
110
|
-
|
|
111
|
-
|
|
112
|
-
|
|
113
|
-
|
|
114
|
-
|
|
115
|
-
|
|
116
|
-
|
|
117
|
-
|
|
118
|
-
|
|
119
|
-
|
|
120
|
-
|
|
121
|
-
|
|
122
|
-
|
|
123
|
-
|
|
124
|
-
|
|
125
|
-
|
|
126
|
-
|
|
127
|
-
|
|
128
|
-
|
|
129
|
-
\
|
|
130
|
-
\n ...\n
|
|
131
|
-
|
|
132
|
-
|
|
133
|
-
|
|
134
|
-
|
|
135
|
-
|
|
136
|
-
|
|
137
|
-
|
|
138
|
-
|
|
139
|
-
-
|
|
140
|
-
-
|
|
141
|
-
\
|
|
142
|
-
\
|
|
143
|
-
\
|
|
144
|
-
|
|
145
|
-
|
|
146
|
-
|
|
101
|
+
The schedule task \ncommand will print a graphical timeline of the working day assigning
|
|
102
|
+
the planned tasks to the timeline. Busy times are marked red. Meetings are listed
|
|
103
|
+
with associated tasks that are assigned to the meetings. With the statistics command
|
|
104
|
+
you can print statistical evaluation of tasks duration and count.\n\n===Create tasks
|
|
105
|
+
with new\nCreate a new task in the default task directory ~/.tasks\n $ syctask
|
|
106
|
+
new \"My first task\"\n\nProvide a description\n $ syctask new \"My first task\"
|
|
107
|
+
--description \"Explanation of my first task\"\n\nSchedule a task with a follow-up
|
|
108
|
+
and due date\n $ syctask new \"My first task\" --follow-up \"2013-02-25\" --due
|
|
109
|
+
\"2013-03-11\"\n\nSet a proirity for a task\n $ syctask new \"My first task\"
|
|
110
|
+
--prio 3\n\nPrompt for task input\n $ syctask new\nwill prompt for task titles.
|
|
111
|
+
Ctrl-D will end input.\n\nExcept for --description you can also provide short forms
|
|
112
|
+
for the options.\n\n===Plan tasks\nThe plan command will print tasks and prompts
|
|
113
|
+
whether to (a)dd or (s)kip the task. If (q)uit is selected the tasks already added
|
|
114
|
+
will be add to the today's task\nlist. If (c)omplete is selected the complete task
|
|
115
|
+
will be printed and the user\nwill be prompted again for adding the task.\n\nInvoke
|
|
116
|
+
plan without filter\n $ syctask plan\n 1 - My first task\n (a)dd, (c)omplete,
|
|
117
|
+
(s)kip, (q)uit? a\n Duration (1 = 15 minutes, return 30 minutes): 3\n -->
|
|
118
|
+
1 task(s) planned\n\nInvoke plan with a filter\n $ syctask plan --id \"1,3,5,8\"\n
|
|
119
|
+
\ 1 - My first task\n (a)dd, (c)omplete, (s)kip, (q)uit?\n\nMove tasks to another
|
|
120
|
+
days plan\n $ syctask plan today --move tomorrow --id 3,5\n\nThis will move the
|
|
121
|
+
tasks with ID 3 and 5 from the today's plan to the tomorrow's plan. The duration
|
|
122
|
+
will be set to the remaining processing time but at least to\n30 minutes.\n\n===Prioritize
|
|
123
|
+
tasks\nPlanned tasks can be prioritized in a pair wise comparisson. So each task
|
|
124
|
+
is\ncompared to all other tasks. The task with the highest priority will bubble
|
|
125
|
+
on\ntop followed by the task with the next highest priority and so on.\n\n $
|
|
126
|
+
syctask prio\n 1: My first task\n 2: My second task\n Task 1 has (h)igher
|
|
127
|
+
or (l)ower priority, or (q)uit: h\n 1: My first task\n 2: My third task\n
|
|
128
|
+
\ Task 1 has (h)igher or (l)ower priority, or (q)uit: l\n 1: My third task\n
|
|
129
|
+
\ 2: My fourth task\n Task 1 has (h)igher or (l)ower priority, or (q)uit:
|
|
130
|
+
h\n ...\n\nsyctask schedule will then print tasks as follows\n Tasks\n -----\n
|
|
131
|
+
\ 0: 10 - My fourth task\n 1: 7 - My third task\n 2: 3 - My first task\n
|
|
132
|
+
\ 3: 9 - My second task \n ...\n \nInstead of conducting pairwise comparisson
|
|
133
|
+
the order of the tasks in the plan\ncan be specified with the -o flag\n $ syctask
|
|
134
|
+
plan -o 7,3,10,9\n\nThe plan or schedule command will print the tasks in the specified
|
|
135
|
+
order\n Tasks\n -----\n 0: 7 - My third task\n 1: 3 - My first task\n
|
|
136
|
+
\ 2: 10 - My fourth task\n 3: 9 - My second task\n\nIf only a part of the
|
|
137
|
+
tasks is provided the rest of the tasks is appended to\nthe end of the task plan.
|
|
138
|
+
If you specify a position flag the prioritized tasks are added at the provided position.\n
|
|
139
|
+
\ $ syctask plan -o 7,9 -p 2\n Tasks\n -----\n 0: 3 - My first task\n
|
|
140
|
+
\ 1: 10 - My fourth task\n 2: 7 - My third task\n 3: 9 - My second task\n\n===Create
|
|
141
|
+
schedule\nThe schedule command will print a graphical schedule with assigning the
|
|
142
|
+
tasks\nselected with plan. When schedule command is invoked the planned tasks are
|
|
143
|
+
\nadded at or after the current time within the time schedule. Tasks that are done\nand
|
|
144
|
+
scheduled in the future are not shown. Tasks done and in the past are shown\nwith
|
|
145
|
+
the actual processing time.\n\nCreate a schedule with working time from 8a.m. to
|
|
146
|
+
6p.m. and meetings between\n9a.m. and 9.30a.m. and 1p.m. and 2.45p.m.\n $ syctask
|
|
147
|
+
schedule -w \"8:00-18:00\" -b \"9:00-9:30,13:00-14:45\"\n\nAdd titles to the meetings\n
|
|
148
|
+
\ $ syctask schedule -m \"Project status,Management meeting\"\n\nThe output will
|
|
149
|
+
be\n Meetings\n --------\n A - Project status\n B - Management meeting\n\n
|
|
150
|
+
\ A B\n xxx-///-|---|---|---///////-|---|---|---|\n 8
|
|
151
|
+
\ 9 10 11 12 13 14 15 16 17 18\n 1\n\n Tasks\n -----\n 0 -
|
|
152
|
+
1: My first task\n\nAdding a task to a meeting\n $ syctask schedule -a \"A:0\"\n\nwill
|
|
153
|
+
print\n Meetings\n --------\n A - Project status\n 1 - My first
|
|
154
|
+
task\n B - Management meeting\n\n A B\n ----///-|---|---|---///////-|---|---|---|\n
|
|
147
155
|
\ 8 9 10 11 12 13 14 15 16 17 18\n \n\n Tasks\n -----\n 0:
|
|
148
|
-
1 - My first task\n\
|
|
149
|
-
|
|
150
|
-
|
|
151
|
-
|
|
152
|
-
|
|
153
|
-
|
|
154
|
-
|
|
155
|
-
|
|
156
|
-
\
|
|
157
|
-
|
|
158
|
-
|
|
159
|
-
|
|
160
|
-
|
|
161
|
-
|
|
162
|
-
|
|
163
|
-
|
|
164
|
-
|
|
165
|
-
|
|
166
|
-
\
|
|
167
|
-
|
|
168
|
-
|
|
169
|
-
|
|
170
|
-
|
|
171
|
-
|
|
172
|
-
\
|
|
173
|
-
|
|
174
|
-
|
|
175
|
-
|
|
176
|
-
|
|
177
|
-
|
|
178
|
-
|
|
179
|
-
\
|
|
180
|
-
|
|
181
|
-
|
|
182
|
-
|
|
183
|
-
|
|
184
|
-
|
|
185
|
-
|
|
186
|
-
|
|
187
|
-
|
|
188
|
-
|
|
189
|
-
|
|
190
|
-
|
|
191
|
-
|
|
192
|
-
|
|
193
|
-
|
|
194
|
-
|
|
195
|
-
|
|
156
|
+
1 - My first task\n\nA task that is re-scheduled with\n $ syctask update 1 -f
|
|
157
|
+
tomorrow\n\nwill be shown as done (green) in the schedule and instead of separator
|
|
158
|
+
- it\nshows ~.\n \n Tasks\n ----\n 0: 1 ~ My first task\n\nA started
|
|
159
|
+
task will be indicated by *\n \n $ syctask start 1\n $ syctask sche\n Tasks\n
|
|
160
|
+
\ -----\n 0: 1 * My first task\n\n===List tasks\nList tasks that are not marked
|
|
161
|
+
as done in short form\n $ syctask list\n\nList all tasks in long form\n $
|
|
162
|
+
syctask list --all --complete\n\nSearch tasks that match a pattern\n $ syctask
|
|
163
|
+
list --id \"<10\" --follow_up \">2013-02-25\" --title \"My \\w task\"\n\n===Inspect
|
|
164
|
+
tasks\nLists each today's unplanned task and allows to edit, delete, mark as done
|
|
165
|
+
or\nplan\n $ syctask inspect\n 0016 Create command for inspection\n (e)dit,
|
|
166
|
+
(d)one, de(l)ete, (p)lan, (c)omplete, (s)kip, (q)uit: \n\n===Edit task\nEdit a task
|
|
167
|
+
with ID 10 in vi\n $ syctask edit 10\n\n===Update tasks\nExcept for title and
|
|
168
|
+
id all values can be updated. Note and tags are not\noverridden rather supplemented
|
|
169
|
+
with the update value.\n\nUpdate task with ID 1 and provide some informative note\n
|
|
170
|
+
\ $ syctask update 1 --note \"Some explanation about the progress on the task\"\n\n===Complete
|
|
171
|
+
tasks\nComplete the task with ID 1 and provide a final note\n $ syctask done
|
|
172
|
+
1 --note \"Finalize my first task\"\n\n===Delete tasks\nDelete tasks with ID 1,3
|
|
173
|
+
and 5 from the default task directory\n $ syctask delete --id 1,3,5\n\nDelete
|
|
174
|
+
tasks with ID 8 and 12 from the planned tasks of today. The tasks are\nonly removed
|
|
175
|
+
from the planned tasks and not physically deleted.\n $ syctask delete --plan
|
|
176
|
+
today --id 8,12\n\n===Settings\nThe settings command allows to define default values
|
|
177
|
+
for task directory and to create general purpose tasks that can be used for tracking
|
|
178
|
+
and later statistical evaluation.\n\nCreate general purpose tasks for phone and
|
|
179
|
+
talk\n $ syctask setting --general PHONE,TALK\n\nList all settings\n $ syctask
|
|
180
|
+
setting --list\n\n===Info\nInfo searches for the location of a task and lists all
|
|
181
|
+
task directories\n\nSearch for task with id 102\n $ syctask info --id 102\n\nList
|
|
182
|
+
all task directories\n $ syctask info --taskdir\n\n===Statistics\nShows statistics
|
|
183
|
+
for work and meeting times as well as for task processing\n\nEvaluate the complete
|
|
184
|
+
log file\n $ syctask statistics\n\nEvaluate work times, meetings and tasks between
|
|
185
|
+
2013-01-01 and 2013-04-14\n $ syctask statistics 2013-01-01 2013-04-14\n\nEvaluate
|
|
186
|
+
yesterday and today\n $ syctask statistics yesterday today\n\n===Task directory
|
|
187
|
+
and project directory\nThe global options --taskdir and --project determine where
|
|
188
|
+
the command finds\nor creates the tasks. The default task directory is ~/.tasks,
|
|
189
|
+
so if no task\ndirectory is specified all commands obtain tasks from or create tasks
|
|
190
|
+
in\n~/.tasks. If a project is specified the tasks will be saved to or obtained from
|
|
191
|
+
the task directories subdirectory specified with the --project flag.\n\n --taskdir
|
|
192
|
+
\ --project Tasks in\n - - default_task_dir\n x -
|
|
193
|
+
\ task_dir\n - x default_task_dir/project\n x x
|
|
194
|
+
\ task_dir/project\n\nIn the table the relation of commands to --taskdir and
|
|
195
|
+
--project are listed.\n\n Command --taskdir --project Comment\n delete
|
|
196
|
+
\ x x deletes the tasks in taskdir/project \n done x
|
|
197
|
+
\ x marks tasks in taskdir/project as done\n help - -
|
|
198
|
+
\ \n inspect x x lists task to edit, done, delete,
|
|
199
|
+
plan\n list x x lists tasks in taskdir/project\n new
|
|
200
|
+
\ x x creates tasks in taskdir/project\n plan x
|
|
201
|
+
\ x retrieves tasks to plan from taskdir/projekt\n prio -
|
|
202
|
+
\ - input to prio are planned tasks (see plan)\n scan x
|
|
203
|
+
\ x creates scanned tasks in taskdir/project\n schedule - -
|
|
204
|
+
\ schedules the planned tasks (see plan)\n start - - starts
|
|
205
|
+
task from planned tasks (see plan)\n statistics - - shows statistics
|
|
206
|
+
of time and count\n stop - - stops task from planned task\n
|
|
207
|
+
\ update x x updates task in taskdir/project \n\n===Files\n\n*
|
|
208
|
+
ID\nid file contains the last issued id.\n\n* IDS\nids file contains all issued
|
|
209
|
+
ids.\n\n* Task files\nThe tasks are named ID.task where ID is any Integer as 10.task.
|
|
210
|
+
The files are\nsaved as YAML files and can be edited directly.\n\n* Planned tasks
|
|
211
|
+
files\nThe planned tasks are save to YYYY-MM-DD_planned_tasks in syctask's system\ndirectory.
|
|
212
|
+
Each task is saved with the task's directory and the ID.\n\n* Schedule files\nThe
|
|
213
|
+
schedule is saved to YYYY-MM-DD_time_schedule in the default task directory.The
|
|
214
|
+
files are saved as YAML files and can be changed manually.\n\n* Log file\nCreating
|
|
215
|
+
schedule and task processings is logged to tasks.log. For example when a task is
|
|
216
|
+
started and stopped this is action is saved to tasks.log.\n\n* Tracked file\nA started
|
|
217
|
+
task is saved to tracked_tasks. A semaphore file is created with\nID.track when
|
|
218
|
+
the task ID is started. When the task is stopped the semaphore\nfile is deleted.\n\n*
|
|
219
|
+
General purpose tasks\nWith syctask setting -g PHONE so called general purpose tasks
|
|
220
|
+
can be created.\nThese tasks can be used for time tracking and later statistic evaluation
|
|
221
|
+
to\ndetermine the amount of disturbences e.g. by phone. These tasks are saved to\ndefault_tasks.
|
|
222
|
+
The general purpose tasks itself are also saved to the\n.syc/syctask directory as
|
|
223
|
+
regular task files.\n\n* Default task dir\nThe default task that is used e.g. with
|
|
224
|
+
list is saved to default_tasks_dir. This can be set with the setting command.\n\n==Working
|
|
225
|
+
with syctask\nTo work with syctask and get the most out of it there is to follow
|
|
226
|
+
a certain\nprocess.\n\n===Creating a schedule\n==== View tasks\nIn the morning before
|
|
227
|
+
I start to work I scan my tasks with syctask list or \nsyctask inspect to get an
|
|
228
|
+
overview of my open tasks.\n $ syctask list\n \n==== Plan tasks\nNext I start
|
|
229
|
+
the planning phase with syctask plan. If I have a specific schedule\nfor the day
|
|
230
|
+
I will filter for the respective tasks\n $ syctask plan\n\n==== Prioritize tasks
|
|
231
|
+
(optionally)\nIf I want to process the tasks in a specific sequence I prioritize
|
|
232
|
+
the tasks\nwith \n $ syctask prio\n\n==== Create schedule\nI create a schedule
|
|
233
|
+
with my working hours and meetings that have been scheduled with \n $ syctask
|
|
234
|
+
-w \"8:00-18:00\" -b \"9:00-10:00,14:30-16:00\" -m \"Team,Status\"\n\n==== Create
|
|
235
|
+
an agenda\nI assign the topics I want to discuss in the meetings to the meetings
|
|
196
236
|
with\n syctask schedule -a \"A:1,3,6;B:3,5\"\n \n==== Start a task\nTo begin
|
|
197
|
-
I start the first task in the schedule with syctask start
|
|
198
|
-
of the planned tasks
|
|
199
|
-
|
|
200
|
-
|
|
201
|
-
|
|
202
|
-
|
|
203
|
-
|
|
204
|
-
|
|
205
|
-
|
|
206
|
-
|
|
207
|
-
with
|
|
208
|
-
|
|
209
|
-
|
|
210
|
-
\
|
|
211
|
-
-
|
|
212
|
-
|
|
213
|
-
|
|
214
|
-
|
|
215
|
-
syctask
|
|
216
|
-
|
|
217
|
-
|
|
218
|
-
|
|
219
|
-
|
|
220
|
-
|
|
221
|
-
|
|
222
|
-
|
|
223
|
-
|
|
224
|
-
|
|
225
|
-
|
|
226
|
-
\
|
|
227
|
-
the
|
|
228
|
-
|
|
229
|
-
|
|
230
|
-
|
|
231
|
-
|
|
232
|
-
|
|
233
|
-
|
|
234
|
-
|
|
235
|
-
|
|
236
|
-
|
|
237
|
+
I start the first task in the schedule with syctask start -p ID (where ID is the
|
|
238
|
+
ID of the planned (-p) tasks)\n $ syctask start -p 10\n\n==== End a task\nTo
|
|
239
|
+
end the task I invoke \n $ syctask stop\nThis will stop the last started task\n\n====
|
|
240
|
+
Re-schedule a task\nIf I cannot finish a task than I update the task with a new
|
|
241
|
+
follow-up date\n $ syctask update 23 -f tomorrow\n\nThe task will be shown in
|
|
242
|
+
the today's schedule as done.\n\n==== Complete a task\nWhen the task is done I call
|
|
243
|
+
\n $ syctask done 23\n\n===Attachements\n* E-mails\nIf an e-mail creates a task
|
|
244
|
+
I create a new task with syctask new title_of_task.\nThe subject of the e-mail I
|
|
245
|
+
prepend with the ID and move the e-mail to a\n<b>open topics</b> directory.\n\n*
|
|
246
|
+
Files\nIf I create files in the course of a task I create a folder in the task\ndirectory
|
|
247
|
+
with the ID and save the files in this directory. If there is an\nexisting directory
|
|
248
|
+
I link to the file from the ID directory\n\n==Supported platform\nsyc-task has been
|
|
249
|
+
tested with 1.9.3. It also works in Windows using Cygwin.\n\n==Add TAB-completion
|
|
250
|
+
to syctask\nTo activate bash's TAB-completion following lines have to be added to
|
|
251
|
+
~/.bashrc\n\n complete -F get_syctask_commands syctask\n\n function get_syctask_commands\n
|
|
252
|
+
\ {\n if [ -z $2 ] ; then\n COMPREPLY=(`syctask help -c`)\n else\n
|
|
253
|
+
\ COMPREPLY=(`syctask help -c $2`)\n fi\n }\n\nAfter ~/.bashrc has
|
|
254
|
+
been updated the shell session has to be restarted with\n $ source ~/.bashrc\n\nNow
|
|
255
|
+
syctask followed by TAB TAB will print\n\n $ syctask <TAB><TAB>\n delete done
|
|
256
|
+
list plan scan stop _doc help new prio schedule start update\n \nTo complete a command
|
|
257
|
+
we can type\n\n $ syctask sch<TAB>\n\nwhich will complete to\n\n $ syctask
|
|
258
|
+
schedule\n\n==Output to Printer\nTo print syctask's output to a printer pipe the
|
|
259
|
+
command to lpr\n\n $ syctask schedule | lpr\n\nThis will print the schedule to
|
|
260
|
+
the default printer. \n\nTo determine all available printer lpstat can be used with
|
|
261
|
+
the lpstat -a command\n\n $ lpstat -a\n Canon-LBP6650-3470 accepting requests
|
|
262
|
+
since Sat 16 Mar 2013 04:26:15 PM CET\n Dell-B1160w-Mono accepting requests since
|
|
263
|
+
Sat 16 Mar 2013 04:27:45 PM CET\n \nTo print to Dell-B1160w-Mono the following
|
|
264
|
+
command can be used\n\n $ syctask schedule | lpr -P Dell-B1160w-Mono\n\n==Release
|
|
265
|
+
Notes\nVersion 0.0.1 \nImplementation of new, update, list and done commands.\n\nVersion
|
|
266
|
+
0.0.4\n* delete: deleting tasks or remove tasks from a task plan\n* plan: plan tasks
|
|
267
|
+
and add them to the task plan\n* schedule: create a schedule with work and busy
|
|
268
|
+
time and assign the tasks from\n the task plan to the free times\n\nVersion 0.0.6\n*
|
|
269
|
+
start: start a task and track the lead time\n* stop: stop the tracking and print
|
|
270
|
+
the lead time of the task\n* start, stop: the task is logged in the ~/.tasks/task.log
|
|
271
|
+
file when added and\n when stopped\n* prio: prioritize tasks in the task plan,
|
|
272
|
+
that is specifying the sequence in\n that the tasks should be conducted\n* plan:
|
|
273
|
+
--move flag added to move tasks from the specified plan to another days\n task
|
|
274
|
+
plan\n* update, new: when a follow-up or a due date is provided the task is added
|
|
275
|
+
to\n the provided dates task plan. If both dates are set the task is added to both\n
|
|
276
|
+
\ dates task plans\n\nVersion 0.0.7\n* updated rdoc\n\nVersion 0.1.15\n* IDs are
|
|
277
|
+
now unique independent of the task or project directory. After\n upgrading from
|
|
278
|
+
a version 0.0.7 or older the user asked whether to re-index\n the tasks. It is
|
|
279
|
+
adviced to tar the tasks before re-indexing with\n $ tar cvfz tasks.tar.gz
|
|
280
|
+
.tasks other_task_directories\n* start will now show a timer in the upper right
|
|
281
|
+
corner of the screen when\n started with the -t (--timer) flag.\n $ syctask
|
|
282
|
+
start 10 -t\n In order to use the task timer ncurses has to be installed as the
|
|
283
|
+
task timer\n uses tput from the ncurses library.\n* The schedule has a heading
|
|
284
|
+
with the schedule's date and the working time\n* Planned tasks are now added at
|
|
285
|
+
or after the current time if they are not done\n yet. Done tasks are shown in the
|
|
286
|
+
past with the actual processing time. Tasks \n done before the start of the schedule
|
|
287
|
+
are not shown in the schedule.\n* Meetings that are at the current time are indicated
|
|
288
|
+
with a *. Active tasks\n are indicated with a star, re-scheduled tasks are indicated
|
|
289
|
+
with a ~.\n* Assigning tasks to meetings in a schedule is now done with the task
|
|
290
|
+
ID\n* Statistics show statistics about work time, meeting times, general purpose\n
|
|
291
|
+
\ tasks and task processing. Total, min, max and average time and count is\n listed.
|
|
292
|
+
If you have used version 0.0.7 it is adviced to delete tasks.log that\n lives in
|
|
293
|
+
~/.tasks before upgrading or in ~/.syc/syctask after upgrading.\n Otherwise the
|
|
294
|
+
statistic results seem odd. \n* Meeting time in time line now shows correct duration\n*
|
|
295
|
+
Info command searches for the location of a task and lists all task\n task directories
|
|
296
|
+
with the tasks contained.\n* Plan move command sets the duration to the remaining
|
|
297
|
+
processing time but at\n least to 15 minutes\n* With the setting command the default
|
|
298
|
+
task directory can be set and general \n purpose tasks can be created. A general
|
|
299
|
+
purpose task can be used for tracking \n to analyse how much time for phone calls
|
|
300
|
+
is occupied.\n setting -l list all general purpose tasks and the default task directory\n*
|
|
301
|
+
Prio command now takes a position flag together with the order flag to \n determine
|
|
302
|
+
where to insert the newly ordered tasks\n* All commands that take an ID as argument
|
|
303
|
+
(done, edit, start, update) look up\n the task file associated to the id in the
|
|
304
|
+
ids file. If it is found the \n provided task directory is not considered for the
|
|
305
|
+
task file. If the id is not \n contained in the ids file the task is looked up
|
|
306
|
+
in the provided directory\n* Inspect command allows to list each today's unplanned
|
|
307
|
+
task to edit, delete,\n mark as done or plan\n* Update command now has a duration
|
|
308
|
+
flag to set the task's duration\n\n==Tests\nThe test files live in the folder test
|
|
309
|
+
and start with test_.\n\nThere is a rake file available to run all tests\n\n $
|
|
310
|
+
rake test\n \n==License\nsyc-task is released under the {MIT License}[http://opensource.org/licenses/MIT]\n\n==Links\n*
|
|
237
311
|
[http://www.github.com/sugaryourcoffee/syc-task] - Source code on GitHub\n* [http://syc.dyndns.org/drupal/wiki/syc-task]
|
|
238
312
|
- Development notebook\n* [https://rubygems.org/gems/syc-backup] - RubyGems\n"
|
|
239
313
|
email: pierre@sugaryourcoffee.de
|
|
240
314
|
executables:
|
|
241
315
|
- syctask
|
|
316
|
+
- console_timer
|
|
242
317
|
extensions: []
|
|
243
318
|
extra_rdoc_files:
|
|
244
319
|
- README.rdoc
|
|
@@ -256,12 +331,16 @@ files:
|
|
|
256
331
|
- lib/syctask/times.rb
|
|
257
332
|
- lib/syctask/schedule.rb
|
|
258
333
|
- lib/sycutil/console.rb
|
|
334
|
+
- lib/sycutil/console_timer.rb
|
|
259
335
|
- lib/syctask/environment.rb
|
|
260
336
|
- lib/syctask/task_tracker.rb
|
|
337
|
+
- lib/syctask/settings.rb
|
|
338
|
+
- lib/syctask/statistics.rb
|
|
261
339
|
- lib/syctime/time_util.rb
|
|
262
340
|
- lib/sycstring/string_util.rb
|
|
263
341
|
- README.rdoc
|
|
264
342
|
- syctask.rdoc
|
|
343
|
+
- bin/console_timer
|
|
265
344
|
homepage: http://syc.dyndns.org/drupal/syc-task
|
|
266
345
|
licenses: []
|
|
267
346
|
post_install_message:
|