<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">---------- Messaggio inoltrato ----------<br>From: Sebastian Kügler <<a href="mailto:sebas@kde.org">sebas@kde.org</a>><br>
To: <a href="mailto:plasma-devel@kde.org">plasma-devel@kde.org</a><br>Date: Sun, 03 Apr 2011 23:01:49 +0200<br>Subject: Re: [GSoC] PlasMate: first release proposal<br>Hey Diego,<br>
<br>
On Thursday, March 31, 2011 20:03:31 Diego Casella wrote:<br>
> after hearing sebas' interest about GSoC project aimed to release a stable<br>
> version of PlasMate, I've collected some ideas and wrote this very first<br>
> draft of the proposal [0] :)<br>
> As always, comments are highly appreciated!<br>
<br>
> @sebas: as you suggested, I didn't included the "code refactoring" thing,<br>
> but I think a little bit of modularization wouldn't hurt; what do you think?<br>
<br>
It depends, I'm not really against refactoring parts of the code where, the<br>
goal however needs to be to get a first working version. You've mentioned that<br>
in your proposel already, but I think the focus should shift slightly. </blockquote><div><br>With "polish the code" I meant fix memleaks, remove i18n puzzles and so on; now I've explained it better, btw :)<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Some hints that would make it more interesting:<br>
<br>
- State the goal more clearly, for example in terms of what will be working<br>
and tested by the end of your GSoC project. I'd personally like to see the<br>
following:<br>
<br>
* working and intuitive complete workflow for creating Plasma "apps"<br>
(creating, editing, previewer and publishing)<br>
* basic debugging facilities for QML Plasmoids (for example a scripting<br>
console where your print() output ends up, an object inspector)<br></blockquote><div>+1. A scripting console is a great idea, added to the list.<br>Plus, I've extended that concept for every Plasmoid type, since it is really useful. It will also partially address the plasmoid sizing issue you mentioned above ;)<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
* Fixing most important problems: plasmoid sizing in the previewer (especially<br>
when the Plasmoid fails to load, the display explodes and one can't read the<br>
error messages)<br>
* The publisher needs a way to export the Plasmoid to a remote device (for<br>
example a "publish to device buttons", which makes testing the widget on a<br>
target device way easier (can be done using Plasmoid sharing)<br>
* Improve documentation for writing Plasmoids, covering basic Plasma Widgets,<br>
UI guidelines, etc.<br>
* Working workflow for dataengine development<br>
<br>
- I'm not entirely sure in how far runnners are really important at this<br>
point, and how much work is needed for that. It's probably one of the features<br>
that can go onto the afterburner, if it benefits the above goals.<br>
<br>
- If you have plans to further maintain and develop Plasmate (which I guess is<br>
your intention anyway, given your track record so far), it would be good to<br>
note that in your proposal since it makes it more interesting for people. The<br>
purpose of GSoC is to get people involved after GSoC.<br></blockquote><div>Oh I thought this was implicit.<br>Added this too ;)<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
- The proposal should also have more detailed milestones, I'd propose bi-<br>
weekly milestones, which take one or more (or one split up ;)) of the above<br>
points, and specify those in terms of accountable items. This eases also the<br>
mid- and end-term evaluations.<br></blockquote><div>I suck with milestones, so please have a look and tell me what do you think/if something is missing :)<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
- You haven't mentioned communication in your proposal, additional to the<br>
usual suspects, status reports would be very much appreciatd. You can tie<br>
those to the above milestones,<br>
<br>
> :)<br>
><br>
> [0]:<br>
> <a href="http://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/diego_casella/1">http://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/diego_casella/1</a><br>
<br>
Thanks for the proposal :)<br></blockquote><div>You're welcome, Cheers!<br><br>Diego<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
Cheers,<br>
--<br>
sebas<br>
<br>
<a href="http://www.kde.org" target="_blank">http://www.kde.org</a> | <a href="http://vizZzion.org" target="_blank">http://vizZzion.org</a> | GPG Key ID: 9119 0EF9<br>
<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><br clear="all"><br>-- <br>H: Who is Watson without Sherlock Holmes?<br>G: Watson was a genius in his own right.<br><br>My personal blog: <a href="http://polentino911.wordpress.com/" target="_blank">http://polentino911.wordpress.com/</a><br>
<br>