On Jul 9, 2008, at 2:05 PM, Jeffrey Harris wrote:
I'm sure we could find workable solutions for #s 2 and 3, but I'm
concerned about time at this point, so let's explore #1 as it appears
to be the least frightful option :)
I have logged a separate bug to keep track of #2 and 3 for future
reference - https://bugzilla.osafoundation.org/show_bug.cgi?id=12233
To answer Jeffrey's question - we already auto-export to a
backup.chex file when you quit. Could we simply auto-reload when you
restart with the caveat that we don't do this more than once a week?
Originally, I had thought we could pop-up something that asks the
user if they want to reload in the interest of speeding things up.
But I'm beginning to wonder what the point of that would be. It feels
like yet another confusing pop-up that you have to figure out.
We've done a lot of work (as in Grant has done a lot of work) to make
it so you are barely aware of export/reload when upgrading. It would
be a shame to re-introduce these concepts now along with more pop-ups.
We would also get rid of the auto-purge dialog. Users can still purge
by invoking the feature from the Tools menu.
https://bugzilla.osafoundation.org/show_bug.cgi?id=12234
Thoughts?
Mimi
Hi Mimi,
1. Replace weekly auto-purge with auto-export/reload. (Would this
actually help?)
I think this would work. Making it work smoothly and in a fault-
tolerant way would take some thought, though. Does it run at shut-
down? Start-up?
2. Auto-archive anything that was triaged to DONE more than 1
year?? ago
- The simplest way to do this might be to take a snapshot of your
data, export it to an Archive.chex file that is timestamped so
that if you ever need it, you can always reload it into Chandler
to take a look at it.
- We could eventually add a File menu item that allowed you to
switch easily between archived data sets and your current data
set. (Sort of like the way Andi's repo-switch feature worked.)
I don't really see this working very well with sharing and
recurrence, and I think it would take a lot of work to get it right.
3. Discard anything older than 1 year
Of course, all of these things would be optional (except for maybe
#1) accompanied by an explanation that if you feel like Chandler
is getting sluggish, you should do them.
This terrifies me. I can't quite say why, I guess there's no
reason users shouldn't be allowed to do this, but opportunities to
shoot yourself in the foot seem plentiful with a path like this.
Sincerely,
Jeffrey
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
