Keep it simple!
Make some small simulation, make it work well.  Then make another
small simulation, make that work well.  Factor out common parts as you
go on.  Then make a 3rd small simulation, and factor out the common
parts.  Rinse and repeat as necessary.
That will be a much more stable development than trying to make it
with plugin structures etc from the start.


On 4/27/06, Stefan Kombrink <katakombi@gmail.com> wrote:
> If you are targeting Win/OSx and Linux you'd better just using Qt4.
> I can tell you from experience that it is easier than Qt3 at least if you
> don't have any experience until then.
> Learning KDE and Qt at the very same time seems tough to me, although plugin
> structures could be easier to implement with KDElibs.
> Sorry, this is not meant to be an anti-KDE-advertisement, but I just want to
> tell you that you try to do a lot and your project is still a little bit
> ...what I'd call underspecified :)
> Do you have examples of simulations you'd like to offer?
>
> >
> >
> >
> >
> >
>
>
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<