<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">---------- Messaggio inoltrato ----------<br>From: Yuen Hoe Lim <<a href="mailto:yuenhoe86@gmail.com">yuenhoe86@gmail.com</a>><br>
To: <a href="mailto:plasma-devel@kde.org">plasma-devel@kde.org</a><br>Date: Tue, 26 Jan 2010 13:16:50 +0800<br>Subject: Re: Subject: Re: On Plasmate's recent project list<br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">
By the way, we should also add a "Remove project" button or whatever
because, in order to test python/ruby/js plasmoid/dataengine/runner, I
created a lot of projects that are no longer needed; so we need a
button to do some "spring-cleaning" IMO :)<br></blockquote><br>Yeah I was planning to add that, that's why I was asking if all we needed to do to kill a project + git repo is to delete the whole folder :) You probably already know this, but in the meantime you could just kill all the stuff in ~/.kde4/share/apps/plasmate/ and kill the config files in ~/.kde4/share/config/plasmate* to start with a clean slate again :)<br>
<br></blockquote><div>Yep, that's why I need something more easy to accomplish that :)<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
----<br>Jason "moofang" Lim Yuen Hoe<br><a href="http://yuenhoe.co.cc/" target="_blank">http://yuenhoe.co.cc/</a><br>
<br>From: Shantanu Tushar Jha <<a href="mailto:jhahoneyk@gmail.com">jhahoneyk@gmail.com</a>><br></blockquote><div> </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"><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>And there is even more, in my opinion. When the number of projects becomes relevant, the user could forget how he/she properly named each of them, thus it's easy to create a new project with a name already assigned. So a conflict scenario is more plausible.<br>
( I'm wondering if could be cool to implement a bacukp support over gitorious, when my backend will be available :)<br></div></div></blockquote><div><br>Oh yes, then we have to have a conflict resolution method anyway. <br>
</div></div></blockquote><div><br>Of course we have :) The coolness I was talking is about having version controlled backup system over gitorious, so you can access it from every pc with an internet connection, without worrying about in what folder/pendrive/external drive you put it before formatting the pc.<br>
One click, and you backup all your projects online; an other click ( + cool anti-conflict method ), and you'll get them back :)<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>
</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></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>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.<br>
<br>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.<br>
</div></div></blockquote></div></blockquote><div><br>Ok, then lets design some generic method for this. When someone gets an outline of a method, mail to the list and we can discuss. :) <br></div></div></blockquote><div>
<br>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>
<br>Well, I'm going to take my DC examinations, bye >.<<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></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"><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 clear="all">----<br>Jason "moofang" Lim Yuen Hoe<br><a href="http://yuenhoe.co.cc/" target="_blank">http://yuenhoe.co.cc/</a><br><br></div></div>
<br>_______________________________________________<br>
Plasma-devel mailing list<br>
<a href="mailto:Plasma-devel@kde.org" target="_blank">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>_______________________________________________<br>
Plasma-devel mailing list<br>
<a href="mailto:Plasma-devel@kde.org" target="_blank">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" target="_blank">http://www.shantanutushar.com</a><br>
<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>