4 ms·

Good point, I haven't used emacs in 8 years, but I know a couple of developers who use it with a lot of passion, even though I imagine its hard for non develope

by arpit 16y ago

Good point, I haven't used emacs in 8 years, but I know a couple of developers who use it with a lot of passion, even though I imagine its hard for non developers to use it. But using the formal exported by that may not be a bad idea. I would love to flesh out the core elements (the model in the MVC sense) required that defines a task and its context. The format itself could be exportable as XML, JSON or Org-Mode consumable files. PS: Sorry about your issue with Disqus, I actually recently installed it because it allowed me to connect with the commentors even more since they signed in with Twitter etc. I should probably look into some graceful degradation back to core wordpress comments when needed.

rwl 16y ago
Good point, I haven't used emacs in 8 years, but I know a couple of developers who use it with a lot of passion, even though I imagine its hard for non developers to use it. Well, don't be afraid! I'm not a "developer," and I do 99% of my work in Emacs. (I am a philosophy student, though I do write programs from time to time.) It takes time to learn, but so do all worthwhile things. I would love to flesh out the core elements (the model in the MVC sense) required that defines a task and its context. The format itself could be exportable as XML, JSON or Org-Mode consumable files. Well, as far as Org is concerned, the core elements that define a task are: 1) Title 2) Todo state (user configurable: mine goes TODO -> INPROGRESS -> [possibly] WAITING -> DONE) With the following optionally present (I'm sure I'm missing some; this is off the top of my head): - Priority (also user configurable) - Description/free-form notes - Deadline timestamp (may be recurring) - Timestamp indicating when task is scheduled - Timestamp indicating when task was finished - running tally of time spent so far - a list of arbitrary tags - a list of arbitrary properties (key/value pairs) - a parent task - a list of sub-tasks - a property indicating whether sub-tasks must be completed in order This is all I need in a task model, and then some. You would probably also need a model to represent more global context (like the todo state-flow graph). Of course, Org also comes with a rich set of tools at the "view" layer, too, which I recommend looking into. Sorry about your issue with Disqus, I actually recently installed it because it allowed me to connect with the commentors even more since they signed in with Twitter etc. No worries; it comes with the territory when you're a paranoid NoScript user. (That said, I wasn't even able to post the comment after allowing all scripts on the page, so a fallback is probably in order.)

by arpit 16y ago

rwl 16y ago

Good point, I haven't used emacs in 8 years, but I know a couple of developers who use it with a lot of passion, even though I imagine its hard for non developers to use it. Well, don't be afraid! I'm not a "developer," and I do 99% of my work in Emacs. (I am a philosophy student, though I do write programs from time to time.) It takes time to learn, but so do all worthwhile things. I would love to flesh out the core elements (the model in the MVC sense) required that defines a task and its context. The format itself could be exportable as XML, JSON or Org-Mode consumable files. Well, as far as Org is concerned, the core elements that define a task are: 1) Title 2) Todo state (user configurable: mine goes TODO -> INPROGRESS -> [possibly] WAITING -> DONE) With the following optionally present (I'm sure I'm missing some; this is off the top of my head): - Priority (also user configurable) - Description/free-form notes - Deadline timestamp (may be recurring) - Timestamp indicating when task is scheduled - Timestamp indicating when task was finished - running tally of time spent so far - a list of arbitrary tags - a list of arbitrary properties (key/value pairs) - a parent task - a list of sub-tasks - a property indicating whether sub-tasks must be completed in order This is all I need in a task model, and then some. You would probably also need a model to represent more global context (like the todo state-flow graph). Of course, Org also comes with a rich set of tools at the "view" layer, too, which I recommend looking into. Sorry about your issue with Disqus, I actually recently installed it because it allowed me to connect with the commentors even more since they signed in with Twitter etc. No worries; it comes with the territory when you're a paranoid NoScript user. (That said, I wasn't even able to post the comment after allowing all scripts on the page, so a fallback is probably in order.)