On Saturday 08 November 2008 20:28:00 Glen wrote: > First things first, I think. > > We need a dev roadmap before we can start arguing file formats. > > 1. What do we want it to *do*? > > 2. How do we make it do what we want, and how can we leverage what we > already have to make it do it sooner? > > We're already discussing #2 without being too sure of #1. > > We do have to get the QT4/KDE4 port completed if we want to get it into > kdeedu (grawr this app doesn't belong there... it belongs in kdeeng, > kdeedu is full of toys.) I partly agree here. The point why I see KTechLab in kdeedu is, because of it's really easy to use interface. It's ready to be used in (higher) education. Engineers do want something more practical here, don't they? Some something that plays together with all the professional tools out there.
I for myself use this discussion as some kind of brain storming what would be our possibilities without inventing everything from scratch. I agree that we have to define, what exactly we want, before getting more precise on techniques we are going to use. -- julian
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------- 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
