Subject: Re: On Plasmate's recent project list

[Yuen Hoe Lim]

> IMO, the import/export tarball feature will be used only for backup and
> restore purposes. In that case, forcing an overwrite *will* make sense, and
> that is what I originally meant. We aren't aiming for a per-project export
> feature. Think of it as 'Backup All Projects' and 'Restore All Projects'. I
> hope I'm able to explain what I originally meant.
>
> I understood what you originally meant, but why restrict it so? I don't
personally think it's great to force overwrite and I don't think a conflict
scenario is all too unlikely - 'Backup All Projects' means I'm saving all
current my work and bringing it with me. There is no guarantee that I won't
create some projects and import a couple more in my new location before I
decide to bring in my old work. You can say that the 'correct' way to backup
all and restore all is to do the restore first thing, but users will do what
they want - and then complain when they have a problem. And no matter how
rare a conflict scenario is, forcing overwrite is serious business. We're
talking about forcing the user to choose between losing whole existing
projects, and not being able to import groups of projects. Either choice
could mean losing contact with a lot of the user's previous work. Also not
forgetting that folder names are not exposed to the user, so folder name
conflicts are not visible to the user, and he will probably be quite
bewildered if we suddenly pop up and say "hey you have a conflict!" when he
sees none.

IMO we should avoid force-overwrite if we can at all, and if Diego is right
(he probably is :P ) then it's pretty trivial to just get PlasMate to do
some under-the-hood renaming and circumvent all the possible problems.

----
Jason "moofang" Lim Yuen Hoe
http://yuenhoe.co.cc/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/plasma-devel/attachments/20100126/133fa589/attachment-0005.htm