Move web application into /web.
This commit is contained in:
4
web/doc/issues/0000tn4.rst
Normal file
4
web/doc/issues/0000tn4.rst
Normal file
@ -0,0 +1,4 @@
|
||||
Refactor models and views.
|
||||
==========================
|
||||
|
||||
Try to find the behavior that is common to mobile and desktop versions.
|
2
web/doc/issues/desktop/0000fs5.rst
Normal file
2
web/doc/issues/desktop/0000fs5.rst
Normal file
@ -0,0 +1,2 @@
|
||||
Add UI for note taking.
|
||||
=======================
|
9
web/doc/issues/desktop/0001fs5.rst
Normal file
9
web/doc/issues/desktop/0001fs5.rst
Normal file
@ -0,0 +1,9 @@
|
||||
Add Markdown converter for notes.
|
||||
=================================
|
||||
|
||||
Brief description.
|
||||
|
||||
========= ==========
|
||||
Created: 2011-05-15
|
||||
Resolved: 2011-05-15
|
||||
========= ==========
|
11
web/doc/issues/desktop/0002bs5.rst
Normal file
11
web/doc/issues/desktop/0002bs5.rst
Normal file
@ -0,0 +1,11 @@
|
||||
Duration mis-set on new entries.
|
||||
================================
|
||||
|
||||
Fix the duration bug when adding new events. Need to set the nextModel for
|
||||
the previously 'current' timestamp and set the nextModel of the new timestamp
|
||||
to 'null'
|
||||
|
||||
========= ==========
|
||||
Created: 2011-05-15
|
||||
Resolved: 2011-05-15
|
||||
========= ==========
|
15
web/doc/issues/desktop/0003ts3.rst
Normal file
15
web/doc/issues/desktop/0003ts3.rst
Normal file
@ -0,0 +1,15 @@
|
||||
Generate day seperators.
|
||||
========================
|
||||
|
||||
When generating EventViews in the EventListView, we need to automatically
|
||||
create and insert day seperators (see prototype).
|
||||
|
||||
Resolution
|
||||
----------
|
||||
|
||||
Day separators are added to the timeline by EntryListView.render.
|
||||
|
||||
========= ==========
|
||||
Created: 2011-05-15
|
||||
Resolved: 2011-05-17
|
||||
========= ==========
|
10
web/doc/issues/desktop/0004bn5.rst
Normal file
10
web/doc/issues/desktop/0004bn5.rst
Normal file
@ -0,0 +1,10 @@
|
||||
Fix UI for tasks with a duration a day or longer.
|
||||
=================================================
|
||||
|
||||
Tasks that are extremely long-running can overflow the space set aside for
|
||||
the *Duration* column.
|
||||
|
||||
========= ==========
|
||||
Created: 2011-05-15
|
||||
Resolved: YYYY-MM-DD
|
||||
========= ==========
|
14
web/doc/issues/desktop/0005bs2.rst
Normal file
14
web/doc/issues/desktop/0005bs2.rst
Normal file
@ -0,0 +1,14 @@
|
||||
Fix user menu UI.
|
||||
=================
|
||||
|
||||
UI for user menu does not work.
|
||||
|
||||
Resolution
|
||||
----------
|
||||
|
||||
UI menu changed to be displayed to the right of the username, in the empty black space vailable.
|
||||
|
||||
========= ==========
|
||||
Created: 2011-05-15
|
||||
Resolved: 2011-06-01
|
||||
========= ==========
|
9
web/doc/issues/desktop/0006bs2.rst
Normal file
9
web/doc/issues/desktop/0006bs2.rst
Normal file
@ -0,0 +1,9 @@
|
||||
Fix timeline menu UI.
|
||||
=====================
|
||||
|
||||
UI for timeline menu does not work.
|
||||
|
||||
========= ==========
|
||||
Created: 2011-05-15
|
||||
Resolved: 2011-06-07
|
||||
========= ==========
|
9
web/doc/issues/desktop/0007ts2.rst
Normal file
9
web/doc/issues/desktop/0007ts2.rst
Normal file
@ -0,0 +1,9 @@
|
||||
Implement timeline selection.
|
||||
=============================
|
||||
|
||||
Allow the user to change timelines.
|
||||
|
||||
========= ==========
|
||||
Created: 2011-05-15
|
||||
Resolved: 2011-06-08
|
||||
========= ==========
|
15
web/doc/issues/desktop/0008ts2.rst
Normal file
15
web/doc/issues/desktop/0008ts2.rst
Normal file
@ -0,0 +1,15 @@
|
||||
Create UI for timeline creation.
|
||||
================================
|
||||
|
||||
There should be a way through the interface for a user to create a new
|
||||
timeline.
|
||||
|
||||
Resolution
|
||||
----------
|
||||
|
||||
Abstracted the login dialog CSS to support other dialogs of the same look and feel. Used this to create a dialog for creating new timelines.
|
||||
|
||||
========= ==========
|
||||
Created: 2011-05-15
|
||||
Resolved: 2011-06-01
|
||||
========= ==========
|
12
web/doc/issues/desktop/0009tn3.rst
Normal file
12
web/doc/issues/desktop/0009tn3.rst
Normal file
@ -0,0 +1,12 @@
|
||||
Implement correct start time editor.
|
||||
====================================
|
||||
|
||||
The start time input field needs to look the same as the start time view.
|
||||
Alternatively, use a date picker.
|
||||
|
||||
----
|
||||
|
||||
========= ==========
|
||||
Created: 2011-05-15
|
||||
Resolved: YYYY-MM-DD
|
||||
========= ==========
|
18
web/doc/issues/desktop/0010tn4.rst
Normal file
18
web/doc/issues/desktop/0010tn4.rst
Normal file
@ -0,0 +1,18 @@
|
||||
Implement UI for entry re-order when chronological order changes.
|
||||
=================================================================
|
||||
|
||||
The UI should re-order the EntryList display when the chronological of the entries
|
||||
changes based on user input.
|
||||
|
||||
Two ways to do this spring to mind:
|
||||
|
||||
1. ``slideUp`` the EntryView at it's original position, find the new position,
|
||||
move it in the DOM and ``slideDown`` the element into view.
|
||||
2. Detach the element from the list, position it absolutely, animate it to it's new
|
||||
absolute position (based on the position of its new neighbors) and re-insert it
|
||||
into the list.
|
||||
|
||||
========= ==========
|
||||
Created: 2011-05-15
|
||||
Resolved: YYYY-MM-DD
|
||||
========= ==========
|
10
web/doc/issues/desktop/0011fn5.rst
Normal file
10
web/doc/issues/desktop/0011fn5.rst
Normal file
@ -0,0 +1,10 @@
|
||||
Create a subtle alternating background for EntryViews
|
||||
=====================================================
|
||||
|
||||
The goal is to visually tie together elements in the same row, and subtley
|
||||
distinquish each row from its neighbors.
|
||||
|
||||
========= ==========
|
||||
Created: 2011-05-15
|
||||
Resolved: YYYY-MM-DD
|
||||
========= ==========
|
9
web/doc/issues/desktop/0012fn6.rst
Normal file
9
web/doc/issues/desktop/0012fn6.rst
Normal file
@ -0,0 +1,9 @@
|
||||
Create tooltip/some help system.
|
||||
================================
|
||||
|
||||
Need some way to make actions discoverable and easy to understand.
|
||||
|
||||
========= ==========
|
||||
Created: 2011-05-15
|
||||
Resolved: YYYY-MM-DD
|
||||
========= ==========
|
10
web/doc/issues/desktop/0013fn5.rst
Normal file
10
web/doc/issues/desktop/0013fn5.rst
Normal file
@ -0,0 +1,10 @@
|
||||
Create a real-time tick-tock for the current entry duration.
|
||||
============================================================
|
||||
|
||||
Have some visible indication that the display is being updated as time passes.
|
||||
Blink the field, or just the units.
|
||||
|
||||
========= ==========
|
||||
Created: 2011-05-15
|
||||
Resolved: YYYY-MM-DD
|
||||
========= ==========
|
12
web/doc/issues/desktop/0014fn6.rst
Normal file
12
web/doc/issues/desktop/0014fn6.rst
Normal file
@ -0,0 +1,12 @@
|
||||
Automatic code highlighting.
|
||||
============================
|
||||
|
||||
Look at content in ``<pre>`` and ``<code>`` blocks and see if we can highlight it.
|
||||
Planning to use Highlight.js to do this.
|
||||
|
||||
----
|
||||
|
||||
========= ==========
|
||||
Created: 2011-05-15
|
||||
Resolved: YYYY-MM-DD
|
||||
========= ==========
|
9
web/doc/issues/desktop/0015ts2.rst
Normal file
9
web/doc/issues/desktop/0015ts2.rst
Normal file
@ -0,0 +1,9 @@
|
||||
Create new timeline button in timeline menu.
|
||||
============================================
|
||||
|
||||
Need a button to trigger the new timeline dialog.
|
||||
|
||||
========= ==========
|
||||
Created: 2011-06-01
|
||||
Resolved: 2011-06-07
|
||||
========= ==========
|
7
web/doc/issues/desktop/0016bn5.rst
Normal file
7
web/doc/issues/desktop/0016bn5.rst
Normal file
@ -0,0 +1,7 @@
|
||||
Duration of next previous entries are not updated when a timestamp is updated.
|
||||
==============================================================================
|
||||
|
||||
========= ==========
|
||||
Created: 2011-06-01
|
||||
Resolved: YYYY-MM-DD
|
||||
========= ==========
|
7
web/doc/issues/desktop/0017ts2.rst
Normal file
7
web/doc/issues/desktop/0017ts2.rst
Normal file
@ -0,0 +1,7 @@
|
||||
Implement timeline creation.
|
||||
============================
|
||||
|
||||
========= ==========
|
||||
Created: 2011-06-01
|
||||
Resolved: 2011-06-07
|
||||
========= ==========
|
15
web/doc/issues/desktop/0018bs2.rst
Normal file
15
web/doc/issues/desktop/0018bs2.rst
Normal file
@ -0,0 +1,15 @@
|
||||
Error in UI when creating or selecting a timeline.
|
||||
==================================================
|
||||
|
||||
A type error is occurring whenever a timeline link is clicked.
|
||||
|
||||
Resolution
|
||||
----------
|
||||
|
||||
The problem was an event registered on the AppView class, linked
|
||||
to 'selectTimeline' function, which was not defined.
|
||||
|
||||
========= ==========
|
||||
Created: 2011-06-07
|
||||
Resolved: 2011-06-08
|
||||
========= ==========
|
16
web/doc/issues/desktop/0019bn3.rst
Normal file
16
web/doc/issues/desktop/0019bn3.rst
Normal file
@ -0,0 +1,16 @@
|
||||
API calls fail silently after session timeout.
|
||||
==============================================
|
||||
|
||||
API starts failing with a 500 error after session time-out.
|
||||
|
||||
Steps to Reproduce
|
||||
------------------
|
||||
|
||||
1. Login
|
||||
2. Wait until session times out (5 min?)
|
||||
3. Try to create a new entry.
|
||||
|
||||
========= ==========
|
||||
Created: 2011-06-08
|
||||
Resolved: YYYY-MM-DD
|
||||
========= ==========
|
22
web/doc/issues/desktop/0020fs5.rst
Normal file
22
web/doc/issues/desktop/0020fs5.rst
Normal file
@ -0,0 +1,22 @@
|
||||
Add exclusion filter for entries.
|
||||
=================================
|
||||
|
||||
Add a way for users to add regexes for entries to be ignored in the
|
||||
display. Exclusions may be per-timeline or per-user.
|
||||
|
||||
Resolution
|
||||
----------
|
||||
|
||||
``ts_user`` and ``ts_timeline`` both support an exnteded data property called
|
||||
``entry_exclusions`` which accepts a list of regular expression strings. Any entries
|
||||
whose marks match any of the regular expressions should be excluded from view.
|
||||
|
||||
EntryListView.render filters out any matching entries from its display. It still
|
||||
takes them into account when calculating the duration of other entries.
|
||||
|
||||
----
|
||||
|
||||
========= ==========
|
||||
Created: 2011-06-10
|
||||
Resolved: 2011-06-15
|
||||
========= ==========
|
7
web/doc/issues/desktop/0021ts5.rst
Normal file
7
web/doc/issues/desktop/0021ts5.rst
Normal file
@ -0,0 +1,7 @@
|
||||
Constrain width of notes fields to width of mark.
|
||||
=================================================
|
||||
|
||||
========= ==========
|
||||
Created: 2011-06-10
|
||||
Resolved: 2011-06-17
|
||||
====================
|
12
web/doc/issues/desktop/0022bn5.rst
Normal file
12
web/doc/issues/desktop/0022bn5.rst
Normal file
@ -0,0 +1,12 @@
|
||||
Deleting an entry should cascade delete extended data.
|
||||
======================================================
|
||||
|
||||
Currently the data remains in the database. It should not cause any
|
||||
problems, but it is wasting space.
|
||||
|
||||
----
|
||||
|
||||
========= ==========
|
||||
Created: 2011-06-15
|
||||
Resolved: YYYY-MM-DD
|
||||
========= ==========
|
12
web/doc/issues/desktop/0023bn7.rst
Normal file
12
web/doc/issues/desktop/0023bn7.rst
Normal file
@ -0,0 +1,12 @@
|
||||
Check for exclusion after mark update.
|
||||
======================================
|
||||
|
||||
If a user rewrites the mark of an entry, we should check to see if it now
|
||||
matches one of the defined entry exclusions.
|
||||
|
||||
----
|
||||
|
||||
========= ==========
|
||||
Created: YYYY-MM-DD
|
||||
Resolved: YYYY-MM-DD
|
||||
========= ==========
|
11
web/doc/issues/desktop/0024tn5.rst
Normal file
11
web/doc/issues/desktop/0024tn5.rst
Normal file
@ -0,0 +1,11 @@
|
||||
Hide day separators when all entries that day are excluded.
|
||||
===========================================================
|
||||
|
||||
We should hide headings when there is no visible data.
|
||||
|
||||
----
|
||||
|
||||
========= ==========
|
||||
Created: 2011-06-17
|
||||
Resolved: YYYY-MM-DD
|
||||
========= ==========
|
21
web/doc/issues/desktop/0025tn5.rst
Normal file
21
web/doc/issues/desktop/0025tn5.rst
Normal file
@ -0,0 +1,21 @@
|
||||
Never animate excluded entries.
|
||||
===============================
|
||||
|
||||
We need to have some visible indication when a user enters an
|
||||
exlucded item that it was added, but it looks ugly and dirty when
|
||||
we first render the list.
|
||||
|
||||
Part of this is motivated by the fact that entering an excluded
|
||||
entry is the excpected way for a user to stop the timer on an item
|
||||
without having an explicit next item.
|
||||
|
||||
If we choose to implement *D0026* this would free up the UI a bit.
|
||||
In that case, we could gently flash the 'Show/Hide Excluded Items'
|
||||
button (*D0027*).
|
||||
|
||||
----
|
||||
|
||||
========= ==========
|
||||
Created: 2011-06-17
|
||||
Resolved: YYYY-MM-DD
|
||||
========= ==========
|
16
web/doc/issues/desktop/0026fn4.rst
Normal file
16
web/doc/issues/desktop/0026fn4.rst
Normal file
@ -0,0 +1,16 @@
|
||||
Add a default 'stop' behaviour.
|
||||
===============================
|
||||
|
||||
It might be more natural to allow the user to hit a button on
|
||||
the current entry to stop the timer on it than to explicitly
|
||||
create a new excluded entry.
|
||||
|
||||
Maybe have a default exclusion for all users, "ENTRY STOP" for example,
|
||||
and have the button automatically add this entry.
|
||||
|
||||
----
|
||||
|
||||
========= ==========
|
||||
Created: 2011-06-17
|
||||
Resolved: YYYY-MM-DD
|
||||
========= ==========
|
12
web/doc/issues/desktop/0027fn4.rst
Normal file
12
web/doc/issues/desktop/0027fn4.rst
Normal file
@ -0,0 +1,12 @@
|
||||
Create a way to unhide excluded entries.
|
||||
========================================
|
||||
|
||||
A button somewhere would be a good way to allow users to
|
||||
show/hide excluded entries.
|
||||
|
||||
----
|
||||
|
||||
========= ==========
|
||||
Created: 2011-06-17
|
||||
Resolved: YYYY-MM-DD
|
||||
========= ==========
|
11
web/doc/issues/desktop/0028tn5.rst
Normal file
11
web/doc/issues/desktop/0028tn5.rst
Normal file
@ -0,0 +1,11 @@
|
||||
Put more visual emphasis on the new entry text field.
|
||||
=====================================================
|
||||
|
||||
Add a shadow, or light highlight, something.
|
||||
|
||||
----
|
||||
|
||||
========= ==========
|
||||
Created: 2011-05-15
|
||||
Resolved: YYYY-MM-DD
|
||||
========= ==========
|
1
web/doc/issues/mobile/0000tn5.rst
Normal file
1
web/doc/issues/mobile/0000tn5.rst
Normal file
@ -0,0 +1 @@
|
||||
Prototype out mobile workflow.
|
Reference in New Issue
Block a user