<br><br><div class="gmail_quote">On Tue, Jan 26, 2010 at 5:31 PM, Yuen Hoe Lim <span dir="ltr"><<a href="mailto:yuenhoe86@gmail.com">yuenhoe86@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="gmail_quote"><div class="im"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="gmail_quote"><div>What about performing a sort of sha1sum for each project file, and use it to perform a check when restoring a backup ?<br>
So, if we find two identical packages names with different hashes, we could prompt a dialog with the name of the package with an "overwrite" checkbox and a "details" button to give more infos about the projects. ( That's reptty rough I know, so what about your opinion?)<br>
</div></div></blockquote></div><div><br>Nonono I don't think we need anything half as complicated as that. Like I said, folder names are not visible to the user so we can rename it to anything we want. The following simple algorithm should work:<br>
<br>for each folder f in import archive {<br> while f also exists in the target location {<br> generate a new name for f and rename f in the archive;<br> }<br>}<br>extract archive to target location;<br></div>
</div></blockquote><div><br>What about giving the user a choice when a duplicate is found? As a user, I wouldn't like the software to create two copies of the same project (maybe different versions of it) and then me having to delete one of them. Lets just give a "Overwrite, Rename, Skip" option.<br>
What do you guys think ?<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="gmail_quote"><div><br>The user won't know (and doesn't need to know anyway) that any renaming has occurred, he will always end up with exactly all his current projects plus all the projects in the import archive at the end of the process. If this happens to create any duplicates (it shouldn't if he uses it right, but in case he doesn't), he could easily delete one of them off. Nice and clean.<br>
<br>I think this is easier and also more elegant and non-intrusive :) I did something similar for importing individual projects, so I can implement this if you guys don't have objections.<div class="im"><br><br clear="all">
----<br>Jason "moofang" Lim Yuen Hoe<br>
<a href="http://yuenhoe.co.cc/" target="_blank">http://yuenhoe.co.cc/</a><br><br>
<br></div></div></div>
<br>_______________________________________________<br>
Plasma-devel mailing list<br>
<a href="mailto:Plasma-devel@kde.org">Plasma-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/plasma-devel" target="_blank">https://mail.kde.org/mailman/listinfo/plasma-devel</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Shantanu Tushar (UTC +0530)<br><a href="http://www.shantanutushar.com">http://www.shantanutushar.com</a><br>