|
: 26 : 26 : 0 |
I've been hacking the summary views of calendars, using embedded views to categorize single time entries, writing time-based agents, and ditzing with workarounds for @Today in views for quite awhile, more than a decade. I think it would be a real plus if I could provide more time-selectivity in views, without touching the document.
The simple & obvious point would be to not constantly rebuild a view through the day, when "@Today" is used. It could be discarded at 12 midnight.
However, a lot of the uses of "@Today" could be even less onerous -- maybe calculating the "@Today" column specifically for entries being displayed, something like that. Or special options on a column that would deliver something like this.
It would be great-great-great if something more sophisticated could be implemented, maybe integrating some calendar capabilities. Somtimes I use the calendar's "show one day" feature and then rewrite the date so it's in the "right" days. Often things don't change for a week, either. Or a month. Or they change a particular day of the month or week.
Just truncating a view for "[field] in future" or "[field] in past" entries only, would be a really useful feature for me.
|