<br><br><div class="gmail_quote">On Thu, Aug 13, 2009 at 9:56 AM, Cristian Oneţ <span dir="ltr"><<a href="mailto:onet.cristian@gmail.com">onet.cristian@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="im">On Thu, Aug 13, 2009 at 3:09 PM, tonyb<<a href="mailto:tonyb.lx@ntlworld.com">tonyb.lx@ntlworld.com</a>> wrote:<br>
> I'm really impressed with the progress you guys have been making. A couple of<br>
> questions:<br>
><br>
> 1. Where there are both Qt and KDE versions of a class (e.g. K/QMessageBox),<br>
> is there a preference to use the KDE version, even if the Qt version provides<br>
> the functionality we want? (My thinking is that when we port to Win, the Qt<br>
> versions are likely to be in a more mature state and produce less in the way<br>
> of problems).<br>
</div>AFAIK if we are a KDE application we should use the KDE versions<br>
because many of the widgets provide KDE specific functionality. As for<br>
porting to Windows we are going to be able to do that because KDE<br>
itself is being ported so I don't expect any issues with the KDE<br>
objects (mainly widgets).<br>
<div class="im"></div></blockquote><div><br>I agree. The recommendation I got from most developers was to use the KDE classes, particularly widgets due to styling issues, customization and so on. <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="im"><br>
<br>
> 2. What's the division of labour? I'm happy to take on conversion of the<br>
> database stuff, since I was responsible for most of it in the first place, and<br>
> I've already done some Qt3->4 database conversion in my private projects, also<br>
> the GnuCash importer if I can remember how it's supposed to work :-(<br>
</div>There is the project's wiki page<br>
<a href="http://techbase.kde.org/Projects/KMyMoney" target="_blank">http://techbase.kde.org/Projects/KMyMoney</a> there you can find out who<br>
is working on what and if you start working on something maybe you<br>
should add it there so that the others will know and avoid<br>
overlapping.</blockquote><div><br></div></div>Also, log there any issues you find, so the others are aware of it.<br><br>I will prep a table which details the overall status of the modules, to get a better appreciation of how we are doing and how much work is left to do. I will need your input for that, so I will ping you back when I'm at it.<br>
<br>