| 5 Jan 2024 |
 champignoom | by filesystem I mean all the .norg files | 15:54:57 |
 max397#6761 | do whatever u want | 15:55:07 |
| max397#6761 | we could discuss about this all day long
you just want sth quick
and I think this makes no sense | 15:56:25 |
| champignoom | No I mean the future ideal UI can start already | 15:58:06 |
| champignoom | if the parts are reasonably decoupled | 15:58:25 |
| champignoom | with clear interfaces | 15:58:56 |
| champignoom | | 16:00:06 |
| max397#6761 | ik what u mean
and i disagree | 16:01:30 |
| champignoom | which part | 16:01:46 |
| champignoom | I think you're referring to the earlier topic | 16:02:00 |
| champignoom | not the one I'm quoting | 16:02:06 |
| max397#6761 | nope | 16:02:18 |
| max397#6761 | I'm referring to this | 16:02:22 |
| champignoom | then I'm confused | 16:02:30 |
| max397#6761 | I think you're underestimating how much there is to this | 16:02:50 |
| max397#6761 | how many different apis there have to be
how complicated the whole thing is and how much is has to be able to do | 16:03:08 |
| max397#6761 | it's just not just listing some tasks and being able to modify there state | 16:03:23 |
| champignoom | do you really mean "have to be", or "can be"? | 16:04:40 |
| champignoom | since at least for me, listing some tasks is already useful | 16:04:58 |
| champignoom | unless we're expecting some full-fledged query language | 16:08:03 |
| max397#6761 | have to be | 16:10:19 |
| max397#6761 | there isn't just a "get tasks" api which can be replaced when the "real" imlementation can be done | 16:10:39 |
| champignoom | any doc for the apis? | 16:12:16 |
| max397#6761 | iirc there is a document laying around | 16:12:38 |
| max397#6761 | no full specification though | 16:12:41 |
| champignoom | or any example of one api? | 16:14:31 |
| max397#6761 | nope | 16:14:46 |
| champignoom | | 16:15:11 |
| champignoom | anything from which I can get a different idea from "listing tasks" | 16:15:25 |
| max397#6761 | do you know how gtd works? | 16:16:31 |
