Setup modes about taskmaster

[ctengel]

This is essential to make this work and be worthwhile

[ctengel]

If we are committed to this mode - should we simplify tm.py, then add DB storage layer, then build API around tm.api?

The "timelines" concept is much less complex here, and indeed in "simplified mode" already existing.

Basically:

• List => the DB table itself (perhaps with a list column/filter)
• Item => the Todo Item with ways to go into DB format or JSON/API format
  • Don't fear marshmellow
• Timeline => simplify to DateTime (and have some way to import complex datetime if needed)
  • Backwards-compatibility doesn't have to be part of the MVP. Since today we are just using text files for the most part

[ctengel]

Interactive CLI may serve as good MVP for some of these, especially Triage.
See:

• https://github.com/python-cmd2/cmd2
• https://github.com/CITGuru/PyInquirer

[ctengel]

ncurses Urgent Important ABC Frog - just push a key 0/1/2... Timing
Shift key for filter/sort
Enter to confirm, escape to cancel

[ctengel]

Now focused on server side. APIs to add from #4

• GET /tasks/ - Filters - closed, triage, scheduleable, followupable
• GET /tasks/?search=
• GET /tasks/id/similar
• POST /tasks/id/action - Duplicate

[ctengel]

As needed to accomplish this goal...

• More fields in the DB and API model
• replicate any legacy taskmaster code

[ctengel]

Hide closed by default, but allow including or only

[ctengel]

Next steps:

1. Review notes and above to document lifecycle in README
2. Establish M.V.P.
3. Create issues for all beyond M.V.P. (see also #10 )
4. Document any APIs needed to make MVP happen
5. Enable or uncomment any DB fields needed to make MVP happen
6. Write server code to make MVP happen
7. Write client library code to effectively communicate in a mode-native way with server for MVP
8. Establish whether MVP mode is quickest via User Interface:
   • #9 Interactive CLI
     • or just Basic CLI
   • #12 and/or #11
     • static HTML with JS that calls API?
     • Flask WebGUI front end that leverages client library API
     • separate Flask GUI code from API, abstracting out key operations from both (not preffered)
9. Note that existing or new issue here
10. Close this issue

[ctengel]

MVP:

• collect => triage => schedule => warm => close
• no multiple users
• no dependencies
• triage and schedule together?
• no upsert

APIs

• triage mode, stage mode, warm mode

DB

• wakeup
• staged/warm
• due???
• poms/urgent/important/pri??

[ctengel]

Also

• frog
• GET /tasks/?mode=triage/schedule/stage/execute

[ctengel]

• better serialization of dates
• document on params https://flask-restx.readthedocs.io/en/latest/swagger.html
• https://flask-restx.readthedocs.io/en/latest/parsing.html

[ctengel]

Lots of issues with dates - flask-restx should be handling - but is it?

Also timezone...

[ctengel]

https://www.fullstackpython.com/flask-views-methodview-examples.html

[ctengel]

• GET /tasks?mode=frog ?
• the test is essentially run a task through all the steps, using the client lib, and check each "mode" to ensure it is where it's expected but not where it isn't
• which all begs the question - should the task listing item simply just TELL us which mode(s) it is in... i.e. have simple python logic that does same thing as SQL logic and some assertion to ensure that it always matches

[ctengel]

https://flask.palletsprojects.com/en/2.0.x/testing/

[ctengel]

Modes:

• all (N/A)
• closed (closed != NULL)
• open (closed == NULL)
• execute (warm == True; closed ==NULL)
• stage (closed == NULL; wakeup <= NOW)
• schedule (closed == NULL; warm == False; wakeup == NULL)
• triage (closed == NULL; no poms, no urgent, no importan)

Assign a primary "state" to each:

• if closed, closed
• if warm, warm
• if wakeup <= NOW, awake
• if wakeup > NOW, sleep
• if pomodoros != null, urgent !=null, important != null, triage
• else, schedule

[ctengel]

Next steps:

1. Finish basic manual testing, using #28
2. Close this issue
3. Build some import #13
4. Mode CLI #9
5. Rest of milestone including #12 and #32
6. Close milestone
7. Do rest including #11