On Apr 13, 2007, at 2:37 PM, Morgen Sagen wrote:
So instead what I would like to now propose for dump/reload of out-
of-the-box account items is... to not have any. The only reason
we create them in installParcel anyway is so that the Accounts
dialog will have something to show. What if the Accounts dialog
created them on the fly -- and only if needed? The Accounts dialog
could look to see if the currentSharingAccount reference points to
an item, and if it doesn't then create a default one. If a dump
file has been loaded in, the currentSharingAccount reference will
already be pointing to an account item, so there is no need to have
an out-of-the-box one defined in installParcel at all. Thus we can
remove the special casing in translator import which deletes an out-
of-the-box account if it's not being used. (Actually I already
removed that special case code when I assigned UUIDs to the sharing
accounts.)
So I went ahead and did this for sharing accounts. They are no
longer created in installParcel, but rather when the Accounts dialog
asks for them (which introduces a bug that Heikki pointed out in IRC,
and I will fix)
Brian K, does this work for email accounts?
Back to Heikki's earlier question:
On Apr 13, 2007, at 11:52 AM, Heikki Toivonen wrote:
It seems there is some confusion what reload really means. pje's
understanding was that it be used only as an upgrade path/data
migration
path, meaning the expectation on reload is for all userdata to go away
and be replaced with what is in the dump.
However, my understanding of some of the reload code seems to be
that it
is acting more like an import, i.e. adding that data in the dump to
the
current repository.
I was just thinking about this, and it could be quite useful to be
able to dump a given collection to a file and have another Chandler
be able to reload it (without blowing away their repo). So perhaps
the "reload" menu item could ask if you want to replace your data
with what is in the dump file, or add the data to your repo.
Also, I think we need a command line argument that will reload a dump
file, as in:
RunChandler --create --reload /path/to/file.dump
...and that would be used for the upgrade/migration route.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
