Been out with knee surgery among other things, but better late than never, eh?
> Let me explain - for many years I have been thinking about how to organize > information. Yes, fascinating how it starts out seeming so simple, but grows exponentially. > I like the idea of small fragments of information that mutate and change. Yes, I do too. I also like the option of a variety of fixed-format data types. For example, I'm adding a birthday record that not only tells you the day of the event, but if you know the birth year of the victim, it will calculate their age for each event. And before anyone asks, no, I personally don't want it connected to Facebook. :P Along similar lines, I want recurring maintenance items that would be based upon, say, car mileage instead of just absolute dates. So, for example, on the first Monday of the month, you get a tickler to update your mileage and Chandler would tell you how soon you need to get an oil change or rotate your tires. I also would like some kind of contact info record that can be associated with other items. Where did I get that last set of tires? What is the contact info for the radiologist? What is the web link to pay my water bill? What Amazon orders have I not received yet? How many more days do I have to give Amazon or Ebay feedback on that item I bought? Have I bought from this vendor before? Was I happy? Ideally, I include all this stuff on the Android client, and it pops up a tickler that says, "Did you bid on that item?" or "Are you in the car? What's the mileage?" or "Time to make your next appointment, should I dial the number?" I'm also interested in esoteric things like sunrise and sunset times, and how I might use them to schedule my bicycle training routine. While I'm dreaming, it would be nice to have build-in periodization calculations for training too. Another area of interest is financial items. I haven't found a financial management program I like, so I use a spreadsheet and project a year or so ahead, taking into account all recurring payments and savings goals. I would very much like that to be completely contained within Chandler, so that I can keep my checking account balance and have recurring reminders to pay bills, etc. If I pay a bill early, that item gets flagged "Done" and goes away. (Right now, if you flag an item as done before its due date, Chandler displays the item again on its due date. I think that's a bug, but there's nobody to report it to.) Having TVM functions would be fun too - what if I pay an extra $200 a month on my mortgage, when would it be paid off? If I throw an extra $50/month in my savings account, when will I reach $1000? FWIW, I'm calling this fork of the code "Chandler Money". >From a big picture perspective, I really would like to switch to a development model that would provide a cleaner installation package. I think that means either statically linking everything, or providing dynamically loadable libraries. I love Python, but using a compiler would get rid of an entire class of runtime errors. To be continued? Doug _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
