<br><br><div class="gmail_quote">On Mon, Mar 12, 2012 at 1:23 AM, Stefan Majewsky <span dir="ltr"><<a href="mailto:stefan.majewsky@googlemail.com">stefan.majewsky@googlemail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Sun, Mar 11, 2012 at 8:32 PM, Supreet Pal Singh <<a href="mailto:supreetpal@gmail.com">supreetpal@gmail.com</a>> wrote:<br>
> I would appreciate a quick reply either directing me to the email address of<br>
> the mentor<br>
<br>
</div>We don't have one at the moment. I wrote the idea, but will not have<br>
time to mentor it. Since most of the project is not kdegames-specific<br>
(e.g. QML use is very widespread among Plasma devs), we hope for a<br>
mentor from some other area of the KDE community to step up when we<br>
have a good proposal.<br></blockquote><div><br></div><div>Do you recommend me approaching the plasma devs now or after we have final proposal? </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
> or preferably some directions on how to go about the project.<br>
<br>
</div>Okay, that's going to be a long text.<br>
<br>
Since you already have experience with QML, I'd suggest you think<br>
about which game you want to do. Although it is very exciting to<br>
create a new game from scratch, we had quite some bad experiences with<br>
new games being written by GSoC students. It will therefore increase<br>
your chances if you propose to port an existing game to QML.<br>
<br>
All current games, along with their current graphics stack, are listed<br>
on [1]. Maintainers can be seen in the list at [2]. We would very much<br>
appreciate if the game to be ported would be one which uses<br>
KGameCanvas at the moment. This framework can be understood as a very<br>
simple replacement for QGraphicsView, and is considered deprecated, so<br>
we would like to eliminate uses of it.<br></blockquote><div><br></div><div> I believe it would be safer to use an existing game. It would be nice if a maintainer whose game is based on KGameCanvas posted in this thread , since i don't have any bias and it would make the work faster.</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
It will help your proposal if you know your way around the game on<br>
which you plan to work. Most of our games have open bug reports and<br>
feature requests on <a href="http://bugs.kde.org" target="_blank">bugs.kde.org</a>. Look for some junior job and submit<br>
a patch at <a href="http://svn.reviewboard.kde.org" target="_blank">svn.reviewboard.kde.org</a> if you like.<br>
<br></blockquote><div>No git? :(</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Since you need to present a tentative timeline for your project, I'll<br>
give some remarks on that as well: Although I'm not that familiar with<br>
QML, I expect that porting a normal-sized game should not take you<br>
more than half of the GSoC time when you're already experienced with<br>
QML.<br>
<br>
That's why we want more out of this project: After having finished the<br>
QML port, you should be prepared to give some recommendations on how<br>
to adjust our libraries for usage with QML. Stuff like: "The way this<br>
and that class works does not fit into the QML workflow, for this and<br>
that reason." And perhaps even: "I suggest this and that change to the<br>
library to make it integrate well with QML."<br>
<br>
What's the reasoning behind this? In the 4.9 iteration, we're breaking<br>
binary and source compatibility in libkdegames to do some major<br>
cleanup. [3] While we're doing this, we're also keeping an eye on QML<br>
preparedness. We do not expect the result (i.e. what will be released<br>
with 4.9) to be QML-friendly already, but it should allow us (and<br>
you!) to build first QML-based code upon it. By the time of the 5.0<br>
release, when we have another opportunity for ABI breakage, we want to<br>
know which changes need to be made.<br>
<br>
So it really is a long text, with a lot of bla-bla-bla and<br>
yadda-yadda-yadda which you probably don't even need to know about,<br>
but it's always nice to have such a text available for reference. If I<br>
forgot anything which is of interest, please do not hesitate to write<br>
back. Please direct your answers to the mailing list instead of my<br>
personal address, my availability is currently limited during the<br>
workweek.<br></blockquote><div><br></div><div>I understand , I will try and make sure that the text is as comprehensible and useful as possible because it seems to be the main motive of this project. :) </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Greetings<br>
Stefan<br>
<br>
[1] <a href="http://techbase.kde.org/Projects/Games/Porting" target="_blank">http://techbase.kde.org/Projects/Games/Porting</a><br>
[2] <a href="http://techbase.kde.org/Projects/Games/Maintainers" target="_blank">http://techbase.kde.org/Projects/Games/Maintainers</a><br>
[3] <a href="http://community.kde.org/Games/API_cleanup" target="_blank">http://community.kde.org/Games/API_cleanup</a><br>
_______________________________________________<br>
kde-games-devel mailing list<br>
<a href="mailto:kde-games-devel@kde.org">kde-games-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kde-games-devel" target="_blank">https://mail.kde.org/mailman/listinfo/kde-games-devel</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Thanks<br>Supreet<br><br>