MVP WebGUI

[ctengel]

Split from #4 (fully API based)

Just basic CRUD so this becomes usable for daily tasks...enhance with #11 later

[ctengel]

Note we basically have to make the same design decision as in ctengel/LPM-index#3

[ctengel]

• https://github.com/dsternlicht/RESTool
• https://netdevops.me/2019/creating-a-bootstrap-based-front-end-for-your-simple-rest-service/
• https://www.reddit.com/r/flask/comments/aic4vj/how_do_i_make_a_gui_for_my_rest_api/
• https://testdriven.io/blog/developing-a-single-page-app-with-flask-and-vuejs/

[ctengel]

• See notepad
• See wanderer idea
• see insomnia/postman

[ctengel]

https://github.com/hoppscotch/hoppscotch

[ctengel]

The MVP should actually just be the daily mode

• context display and switch
• flash area to communicate changes
• today's date
  • optional close day (bulk unstage) option
• table
  • pri
  • task
  • due
  • buttons: up-pri, down-pri, complete, unstage
• ... (display ALL tasks until xyz date)
  • same but add "stage" and next calendar button
  • at bottom note "next session to
  • focus button to collapse

Most of these other ideas file somewhere as API browser

[ctengel]

we need two addition paths

• add a new task to today view (default unstaged)
• add unsorted task (maybe to any view???)

[ctengel]

• Also a way to view done tasks? - like #20 and/or #71 ?
• Way to complete a task AND schedule recurrence of it?
  • do a POST /tasks/<id>/action close&duplicate
  • distinct from #64 ? (or is this webgui implementation of that CLI version?)
• Note that delete #46 is not in scope

[ctengel]

Seem to have figured out context issue for now ( see #86 )

However, new problem. WebGUI design envisions multiple execute contexts... i.e. one can stage tasks in one context, swap to another, and then swap back contexts.

API and CLI was not built with this in mind, they were built with single "stage" of all contexts.

So if we are in GUI "execute mode" we cannot pull just one context - GET /tasks/?mode=execute&context=xyz fails.

Maybe this IS an issue for #86 - decide how this should work.

[ctengel]

Per #86 discussion - conform to API for now - single stage.

[ctengel]

still todo

• [x] initial context picker
• [ ] bulk unstage (see #11 )
• [x] any concept of priority (see #45 )
• [x] implement task actions
• [x] stage mode (see #87 )
• [x] add tasks

[ctengel]

1. Actions
2. Manually add timelines and adjust contexts via CLI
3. Start eating the dog food
4. Test and fix stage mode
5. Prioritize
6. Other

[ctengel]

Quality of life:

• context picker
• if task is different context, link to switch
• after doing an action maintain stage/exec mode

[ctengel]

• table mode
• change context?
• change due date

[ctengel]

make available on mobile

[ctengel]

https://stackoverflow.com/questions/9117209/no-line-break-between-button-and-form

[ctengel]

essentially done, see "Restful wander ideas" in keep