Hi, On Tuesday 26 August 2008 12:11:50 P Zoltan wrote: > I think in long term it's good for the project. However, I see a few > problems which should be resolved in order to make ktechlab successful. > > Being part of the kdeedu means more users for ktechlab. These users will > want to report bugs and request features, maybe they will ask for all kind > of documentation. Supposing they write a mail on the mailing list, the > question is if the developers will be able to fix the bugs and implement > the requested features. The problem is that the source code is really > messed up, and it's really hard to implement anything. I think if we can > put togethere a plan to get past this, the project will gain momentum. I organized the porting in a way, that I completely review the existing source-code. The GUI will be completely rewritten (that's what I started) and I will see, how much of the back-end stuff can be used. Since you started the refactoring of the back-end data structure, everything has to be reviewed and some parts rewritten. All that doesn't effect the front-end for now. All the new GUI parts need some interfaces implemented to fit to our data-structure.
All in all I want to have the port (nearly) finished, before moving to kde-edu. At the moment I have a local mercurial repo, where I commit my changes and I will sync that with the sourceforge.net svn repo from time to time. (Since there is nothing to see yet, there is nothing in svn for now.) bye julian ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Ktechlab-devel mailing list Ktechlab-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ktechlab-devel
