So, a ToDo item has a Period in which you want to work on it; and a
period would be data from an Agenda aspect, really.
Actually, let me stop right here and say that Tycho is not intended
for to-do or appointment types of things.
I do have a different app I've been playing with for that (a web-based
one) and might look at synergy between them later. But right now they
are both too immature. In fact, Kronos has been rebugged so much that
even I can't use it at the moment.
I find agenda a must for my pim software.
I have an agenda, but the code is oooold (from my earlier ruby days) and
unreliable, so I'll have to rewrite some parts of it.
Since ToDo can have relations with software, bugs, fixes and more, I will
leave that out (or very simple) for now.
I fear I will have to move forward without Tycho.
Discussion in this thread has been very useful, thanks.
Utterly primitive view (who cares) on *some* of the data.
Note that you can not access :8881 which runs a local view on *all* the
data
I've looked at this, but I'm not entirely sure of the
significance of what I see. Is it that you've put
together a directory-oriented form of storage? In very
little code, I would guess?
FYI, I'm also working on a private project which would
be a to-do list tailored for my own use. I do plan,
however, to make it customizable so that people could
turn off the freaky features that only I would want.
Currently it's a web app, but if I rewrite it carefully,
even more of the "guts" can be re-used, e.g., in a
desktop GUI app.
If you're interested in that, we can talk offlist. We
might be able to share some code. I've made significant
progress toward handling repeating events and such.
otoh, trying to get a generic storage is fun,
and ruby allows you to actually use it with so few code.
I've looked at this, but I'm not entirely sure of the
significance of what I see. Is it that you've put
together a directory-oriented form of storage? In very
little code, I would guess?
The app does what it does, based on the .aspects file.
the example web-app picks out what is marked as Public.
(and I wanted a second server to be able to look at everything).
An agenda app could pick things out based on
Anniversary[born, died]
Anniversary[married, divorced]
and who-knows-what.
Some things are harder. The .behaviour files to get
- dependencies for exceptions in repeating appointments
- aggregations in tree structured todos
is... merely an idea in my head.
FYI, I'm also working on a private project which would
be a to-do list tailored for my own use. I do plan,
however, to make it customizable so that people could
turn off the freaky features that only I would want.
Currently it's a web app, but if I rewrite it carefully,
even more of the "guts" can be re-used, e.g., in a
desktop GUI app.
If you're interested in that, we can talk offlist. We
might be able to share some code. I've made significant
progress toward handling repeating events and such.
Is it that you've put