Thanks for the feedback.<br><br>Ressurecting KPoker is not really an option for me. Looking at the screenshots I think CSPoker is already more advanced than KPoker. I'm also very familiar with the CSPoker codebase which would give the project better chance of success.<br>
<br>How well supported is Java (6) in KDE?<br><br>I'm leaving for a 2 week road trip tomorrow morning so I'd have to write up a proposal quickly.<br><br>Cheers,<br><br>Guy<br><br><div><span class="gmail_quote">2008/3/24, Mauricio Piacentini <<a href="mailto:piacentini@kde.org">piacentini@kde.org</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Eugene Trounev wrote:<br> > Yes, all is well, but Andy may be, or may not be interested, on the other hand<br> > here we have people who are ready and willing to do it. Why turn donwn a<br> > perfectly good offer? However, I do agree that we should contact Andy first.<br>
<br> <br>Sure. But look carefully at my text: I was mainly answering to your<br> <br>question if he had a poker game before or not. And I also said:<br> <br> >> year, so it will probably come back eventually. Not that this prevents<br>
>> other poker games from getting in<br> <br> <br>See? So, let me be clear: nothing against a new poker game, if there is<br> someone wanting to develop it in playground. In some cases it can<br> actually be easier to start fresh, I know. But I still think that<br>
eventual resources coming from SoC should probably be directed to<br> improving existing apps/libraries/frameworks. This is only my personal<br> opinion, but I have seen similar messages in other lists.<br> <br><br> Regards,<br>
Mauricio Piacentini<br> <br> <br> <br> <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">https://mail.kde.org/mailman/listinfo/kde-games-devel</a><br>
</blockquote></div><br>